Long Form XML

Insert Title Here

Action Updates

An Action Update will act like a Delay, in the sense that it will not remove other status, like, appointment & inspected, however, when applied it will be the primary status of the job.

Marking the Job as Inspected will remove any previous Action Update (like a delay). However, an Action Update can be applied after an Inspection has been confirmed (like a delay).

When a Delay is applied to a Job already, the Action Update will not override the Delay. The Action Update will be applied as a sub status to the Delay on the Job, the Delay will remain the Primary Status. If an Action Update is on a Job and then a Delay is applied, the Delay will become the primary status of a Job, and the Action Update will not be removed, but will become a secondary status on the job.

New LIXI SOAP Operations

addActionUpdate(valexId, update_code, comment)

This is the standard operation that should be called for adding an Action Update to a job.
The update_code should correspond to one of the following action update categories in the mappings below:

ValEx LIXI
Lack of Sales Evidence lack_of_sales
I have/will Miss a Deadline miss_deadline
Insufficient Documentation (ValFirm to Resolve) insufficient_documents
Quality Assurance quality_assurance
Clarity Required on Policy clarity_required_on_policy

actionUpdateFeeApproval(valexId, reason_code, fee_amount, comment)

This is the operation to call for adding an action update where the reason is to seek approval for a higher fee on a valuation request.
The reason_code should correspond to one of the following action update categories in the mappings below:

ValEx LIXI
Nature of the Property nature_of_the_property
Size of the Property size_of_the_property
Location of the Property location_of_the_property
Report Type report_type

actionUpdateReassignment(valexId, comment, fee_amount)

This is the operation to call for adding an action update where the reason is to seek approval for a re-assignment of a previously completed valuation.

actionUpdateServiceTypeWithFeeApproval(valexId, comment, fee_amount)

This is the operation to call for adding an action update where the reason is to seek a service type change with a higher fee approval on a job.

Multiple Dwellings on One Title and TBE Multiple Dwellings on One Title

Two new Report Types will be created and received from the Valuer:

  • Multiple Dwellings on One Title
  • TBE Multiple Dwellings on One Title

We will be adding the following options to //FullRegistered/@ReportType:

  • Multiple-Dwelling
  • TBE-Multiple-Dwelling

Two new Property Types will be created and received from the Valuer:

  • Multiple Dwellings on One Title
  • TBE Multiple Dwellings on One Title

We will be adding the following options to //vx:Job/vx:Property/@Type

  • Multiple Dwellings on One Title
  • TBE Multiple Dwellings on One Title

The following fields will have information duplicated on the Output Report (i.e. include the information for each dwelling):

Property Summary:

  • Built About
  • Car Accommodation
  • No of Car Spaces
  • Car Areas
  • Living Areas
  • Outdoor Areas
  • Other Areas

Main Building Section:

  • Style
  • Main Walls and Roof
  • Street Appeal
  • Window Frames
  • Main Interior Linings
  • Flooring
  • Internal Condition
  • External Condition
  • Bedroom Number
  • Bathroom Number
  • Accommodation
  • Interior Layout
  • PC Items
  • Fixtures and Features

To enable multiple dwellings in LIXI, we will allow valuation firms to replicate the following nodes:

//FullRegistered/SiteDetailResponse/PropertyCharacteristics
//FullRegistered/CarAccomodation
//FullRegistered/ImprovementAreas

ValEx will match these in order, for instance if you send through

2 PropertyCharacteristics
2 CarAccommodations
2 Living ImprovementAreas
2 Outdoor ImprovementAreas
2 Other ImprovementAreas

ValEx will match the first property characteristics, the first car accommodation, the first living improvement area, the first outdoor improvement area and the first other improvement area as one dwelling on the report. Then the second of each as the second dwelling on the report.

Please ensure you only send multiple for property and report types of multiple dwellings, and that there is a matching number of PropertyCharacteristics, CarAccommodation, Living ImprovementAreas, Outdoor ImprovementAreas and Other ImprovementAreas nodes.

We’ll be adding parsing from //PropertyCharacteristics/@Attachment to fill in the attachment field, and continue parsing from //PropertyCharacteristics/@StyleDescription for the levels field.

The attributes we will be looking for multiple of to render to the report are:

PropertyCharacteristics:

//PropertyCharacteristics/@YearBuilt
//PropertyCharacteristics/@YearBuiltIndicator
//PropertyCharacteristics/@StyleDescription
//PropertyCharacteristics/@MainWallType
//PropertyCharacteristics/@RoofConstructionMaterial
//PropertyCharacteristics/@StreetAppeal
//PropertyCharacteristics/@WindowFrames
//PropertyCharacteristics/@MainInteriorLinings
//PropertyCharacteristics/@FloorConstructionMaterial
//PropertyCharacteristics/@InternalCondition
//PropertyCharacteristics/@ExternalCondition
//PropertyCharacteristics/@NumberOfBedrooms
//PropertyCharacteristics/@NumberOfBathrooms
//PropertyCharacteristics/@MainBuildingComment
//PropertyCharacteristics/@InternalLayout
//PropertyCharacteristics/@PCItems
//PropertyCharacteristics/@FixturesAndFittings

CarAccomodation:

//CarAccomodation/@OtherDescription
//CarAccomodation/@NumberOfVehicles
//CarAccomodation/@CarArea
//CarAccomodation/@CarAreaUnits

ImprovementAreas:

//ImprovementAreas/@AreaType
//ImprovementAreas/SiteArea/@Size

These duplicated fields will not be sent to Clients via Web Services.

For Short Form reports information is only to parse for dwellings 1 and 2. If a LIXI ValFirm tries to send more than 2 dwellings on a Short Form report, these will error at their end and they will be unable to submit the report.

Expected Selling Period

The Estimated Selling Period will have the following updated options that the Valuer can select from:

  • 0 – 6 months
  • 6 – 12 months
  • 12 months and greater

We previously accepted (see Estimated Settlement):

//FullRegistered/ValueComponent/EstimatedSettlement
//FullRegistered/ValueComponent/EstimatedSettlement/Duration[@Length] as an int.
//FullRegistered/ValueComponent/EstimatedSettlement/Duration[@Unit="Months"]

We will now require as per LIXI 1.6:

<xs:element name="SalesMarket">
……
            <xs:attribute name="ExpectedSellingPeriod">
                        <xs:simpleType>
                                    <xs:restriction base="xs:NMTOKENS">
                                                <xs:enumeration value="Less than 6 months"/>
                                                <xs:enumeration value="6 to 12 months"/>
                                                <xs:enumeration value="Greater than 12 months"/>
                                    </xs:restriction>
                        </xs:simpleType>
            </xs:attribute>
……
</xs:element>

To enter a comment, we will continue to read //ExpectedSellingPeriodComment as below.

//FullRegistered/ValueComponent/ExpectedSellingPeriodComment

If the estimated selling period is greater than 6 months, an ExpectedSellingPeriodComment should be provided.

Sending a Contacting Status

Valuation Exchange will expect firms to send through a Contacting Status when the Valuer/Valuation Firm has made contact with the Inspection Contact, in the following format.

addContactingNote(ValEx_id, comment)

Query Update from Valuation Firm

The Valuation Firm, instead of closing the Query, can provide a Query Update, which provides the client with an update on how the Query Resolution is progressing, this should be applied at the 24 hour mark, if the query cannot be resolved.

For this, Valuation Firms will need to call the following method on the ValEx webservice:
addQueryUpdate(ValEx_id, comment)

Cancellation Request

This is a notification to advise that there is a cancellation made on the valuation.

Valfirms should implement the following method:
cancel(valuationMessage, reason_id , comment)

Documentation and Communication Path

To allow valuation firms to retrieve client settings for a particular valuation we’ll be adding a new soap method to return settings specific to a particular valuation:

fetchSettings(ValEx_id)

We’d recommend you ping this at certain points during the valuation cycle. At least when the request is first ordered, but we would also recommend looking to update as the valuer starts typing their report.

The first two settings we’ll be adding to this are the communication path, and documentation path.

These will be available via the following XPath in the response returned from ValEx:

//settings/communicationPath
which can be either “Client” or “ValEx”, and

//settings/documentationPath
which can be either “Client” or “ValEx” or “Valfirm”

We will not be providing a schema at this time to ensure we can add additional settings without all firms needing to update at once.
We would like firms to simply use XPath to look up the nodes they need as we will be looking to add new nodes on a semi regular basis.

Example below:



12345678
Client
Valfirm

Query Request

A notification to advise that a Query has been requested on a valuation report.

Valfirms should implement the following new method:
query(valuationMessage, reason_id, comment)

Address Updated

This is a notification to advise that there are new address details on the valuation request.

ValEx will simply resend this as a standard order() with new details.