Insert Content

Summary Tab

FIeld Name	XPath	Values
Property type of the Valuation	//FullRegistered/RealEstate/Residential/@Type	String (restricted)
Title Details - Tenure Type	//FullRegistered/RealEstate/Location/Title/@TenureType	String (restricted)
Title Details - Lot/Unit No	//FullRegistered/RealEstate/Location/Title/@TorrensLot	String (free text)
Title Details - Plan Number	//FullRegistered/RealEstate/Location/Title/@TorrensPlan	String (free text)
Title Details - Volume / Folio No	//FullRegistered/RealEstate/Location/Title/@TorrensVolume and/or //FullRegistered/RealEstate/Location/Title/@TorrensFolio	String (free text of combined fields up to 30 characters)
Title Details - Further Detail	//FullRegistered/RealEstate/Location/Title/@OtherTitleDescription	String (free text)
Title Details - Encumbrances/Restrictions	//FullRegistered/RealEstate/Location/Title/Encumbrance/Comment	String (free text) Multiple comment nodes are combined by comma separation
Site Dimensions	//FullRegistered/SiteDetailResponse/SiteDimensions	String (free text)
Site Dimensions (attributes)	//FullRegistered/SiteDetailResponse/SiteDimensions/@Frontage //FullRegistered/SiteDetailResponse/SiteDimensions/@Depth //FullRegistered/SiteDetailResponse/SiteDimensions/@IrregularShape	String (free text)
Site Area	//FullRegistered/SiteDetailResponse/SiteArea/@Size	Number
Unit of Measurement	//FullRegistered/SiteDetailResponse/SiteArea/@UnitOfMeasurement	Acres, Hectares or SquareMeters
Zoning Instrument	//FullRegistered/Zoning/@ZoningType or //FullRegistered/Zoning/@OtherDescription	String (free text) If ‘OtherDescription’ is provided; ValEx will use its value otherwise will use value of ZoningType
Zoning Effect	//FullRegistered/Zoning/@ZoningEffect	String (free text)
Main Building Type	<xs:enumeration value="Yes"/> <xs:enumeration value="No"/>
Current Use	//vx:Job/vx:Property/vx:Detail/vx:CurrentUse Please note, if validating against the main XSD schema it is mandatory to also specify CurrentUse on the following 2 nodes as either "Residential" or "Non-Residential" //FullRegistered/SiteDetailResponse/SiteDescription/@CurrentUse //FullRegistered/SiteDetailResponse/PropertyCharacteristics/@CurrentUse However when this node is specified, it will overridden any previously specified CurrentUse: //vx:Job/vx:Property/vx:Detail/vx:CurrentUse	Residential MultiResidential CommercialResidential NonResidential Commercial ServicedApartment ResidentialVacantLand StudentAccommodation SeniorsLiving Rural RuralResidential None (to clear this field)
Year Built Indicator	//FullRegistered/SiteDetailResponse/PropertyCharacteristic/@YearB uiltIndicator	String (restricted) BuiltAbout Circa ToBeErected YearBuilt
Year Built	//FullRegistered/SiteDetailResponse/PropertyCharacteristic/@YearBuilt	String (Free text – ValEx will parse year at the start of the string) e.g. @YearBuilt=”1990 string” => display “1990” in the below box
Actual Weekly Rent	//FullRegistered/SiteDetailResponse/PropertyCharacteristic/@Actua lWeeklyRent	String (Non-negative number) E.g. “2,400”, “$450”, “400”, “350.50”
Year and description of any modifications done	//FullRegistered/SiteDetailResponse/PropertyCharacteristic/@YearM odified	String (Free text) E.g. “1995 some description here”, “some description here”
Marketability	//FullRegistered/RiskAnalysis/@Marketability	String (free text)
Heritage Issues	//FullRegistered/RiskAnalysis/@HeritageIssue	String (restricted) To specify no, this field must contain either "not known", "none" or "n" To specify yes, any value is valid and will be used as a comment
Environment Issues	//FullRegistered/RiskAnalysis/@EnvironmentIssues	String (restricted) To specify no, this field must contain either "not known", "none" or "n" To specify yes, any value is valid and will be used as a comment
Essential Repairs	//FullRegistered/SiteDetialResponse/PropertyCharacteristic/@EssentialRepairs //FullRegistered/RiskAnalysis/@EssentialRepairs	String (Free text) Essential repairs comments from ‘PropertyCharacteristic’ will always override comments from ‘RiskAnalysis’ Leave blank if output needs to be set to ‘None’ If ‘None’ or ‘Not Known’ is sent as a comment, output will be set to ‘Yes – Comments below’ with text ‘None’ as a comment.

Title Lessee

When adding a RelatedParty of type "TitleLessee" ensure that a corresponding RelatedEntityRef RelatedID links to the UniqueID of the corresponding Title Node.  In this example the RelatedID and UniqueID are "Title1".

Related Party Node: 

<RelatedParty RelPartyType="TitleLessee">     <Identifier UniqueID="TitleLessee1" Type="BrokerAssigned"/>     <PersonName>         <FirstName>Test</FirstName>         <Surname>User</Surname>     </PersonName>     <RelatedEntityRef RelatedID="Title1"/> </RelatedParty>

Title Node: 

<Title> <Identifier UniqueID="Title1"/> </Title>

VX Node

Building Type

Main Building under Property Summary begins with a Building Type specified here:

XPath: /vx:Job/vx:Property/vx:Detail/vx:BuildingType

Transaction Type

Transaction Type under Sales Evidence tab:

/vx:Job/vx:Loan/@TransactionType

Value Tab

This page outlines LIXI fields and their corresponding mappings to a report within the Property Services Gateway (PSG).  Please note, fields will be required/hidden based on the report type used.  Although not documented here, you can see which fields are required for a specific report by opening that report in the PSG's test environment and seeing which fields appear under the corresponding tab.

Sales Evidence Tab

This page outlines LIXI fields and their corresponding mappings to a report within the Property Services Gateway (PSG).  Please note, fields will be required/hidden based on the report type used.  Although not documented here, you can see which fields are required for a specific report by opening that report in the PSG's test environment and seeing which fields appear under the corresponding tab.

Market Risk Tab

This page outlines LIXI fields and their corresponding mappings to a report within the Property Services Gateway (PSG).  Please note, fields will be required/hidden based on the report type used.  Although not documented here, you can see which fields are required for a specific report by opening that report in the PSG's test environment and seeing which fields appear under the corresponding tab.

Report Integrity Questions

The report integrity questions are designed as prompts to the valuer to ensure they have covered off areas of concern.
The questions are modeled around the RiskRating node and uses the following XPath for flagging ‘Yes/No/Unknown’ responses to the questions:
/ValuationTransaction/Message/ValuationType/FullRegistered/RiskAnalysis/RiskRating/@Rating

The rating values that should be used here are:

In addition, each of these questions is distinguished by a separate RiskRating Identifiers used with the following XPath:
/ValuationTransaction/Message/ValuationType/FullRegistered/RiskAnalysis/RiskRating[@RatingType='Other']/Identifier/@UniqueID 

VRA Questions

Valuation Risk Alerts (VRAs) are required by certain clients/funders.
Each risk item on a report can either be checked or unchecked (Yes/No), and if checked a comment could be entered.
A VRA question are modelled around the RiskRating node and uses the following XPath for flagging ‘Yes/No’ responses to the questions
/ValuationTransaction/Message/ValuationType/FullRegistered/RiskAnalysis/RiskRating/@Rating

The rating values that should be used here are:

If the question is answered as ‘Yes’, then a minimum 5 word comment must be provided in the corresponding Comments field for the question:
/ValuationTransaction/Message/ValuationType/FullRegistered/RiskAnalysis/RiskRating[@RatingType='Other']/Comment

In addition, each of these questions is distinguished by a separate RiskRating Identifiers used with the following XPath:
/ValuationTransaction/Message/ValuationType/FullRegistered/RiskAnalysis/RiskRating[@RatingType='Other']/Identifier/@UniqueID 

The following are a list of the Identifiers for each of the Report Integrity questions shown on the Sales Evidence tab of the report:

Recent Construction Confirmation Questions

Land Tab

This page outlines LIXI fields and their corresponding mappings to a report within the Property Services Gateway (PSG).  Please note, fields will be required/hidden based on the report type used.  Although not documented here, you can see which fields are required for a specific report by opening that report in the PSG's test environment and seeing which fields appear under the corresponding tab.

Comments Tab

This page outlines LIXI fields and their corresponding mappings to a report within the Property Services Gateway (PSG).  Please note, fields will be required/hidden based on the report type used.  Although not documented here, you can see which fields are required for a specific report by opening that report in the PSG's test environment and seeing which fields appear under the corresponding tab.

Building Tab

This page outlines LIXI fields and their corresponding mappings to a report within the Property Services Gateway (PSG).  Please note, fields will be required/hidden based on the report type used.  Although not documented here, you can see which fields are required for a specific report by opening that report in the PSG's test environment and seeing which fields appear under the corresponding tab.