SearchUser loginPopular contentAll time:
Valuation Firm GuideClient Guide
|
Current Use (vx:CurrentUse)Current Use is parsed from the vx namespace. This appears on the Summary tab. Valid values are for Residential MultiResidential CommercialResidential NonResidential Commercial ServicedApartment ResidentialVacantLand StudentAccommodation SeniorsLiving Rural RuralResidential None - to clear this field. vx NamespaceWe have recently extended the LIXI standard by creating a new vx namespace. To use this namespace, simply declare the namespace as below: <ValuationTransaction xmlns:vx="https://vx.valex.com.au/lixi/schema/vx/0.1/#" ...>
You may then include nodes belonging to the vx namespace under the Schema ValidationFeatures supported: vx:DelayWe have created a ValEx namespace to escape LIXI limitations. The first feature of this namespace enables valuation firms to specify a delay reason ID that relates directly to how delay reasons are modeled within ValEx. If the An example follows: <?xml version="1.0" encoding="utf-8"?> <ValuationTransaction xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://vx.valex.com.au/lixi/schema/1.4.1/ValuationTransaction.xsd" xmlns:vx="https://vx.valex.com.au/lixi/schema/vx/0.1/#" ProductionData="No"> <-- LIXI Standard Content here --> <vx:Job> <vx:Status> <vx:Delay ReasonID="4"> <vx:Comment>Unit test delay comment</vx:Comment> </vx:Delay> </vx:Status> </vx:Job> </ValuationTransaction> Delay reasons are: ID Reason 4 Next visit to Location 9 Request is Outside of Lender policy 13 Inspection Contacting Issues 14 Access Issues 15 Property Identification 16 Insufficient Documentation (Client/Lender/Broker to Provide) 17 Other 18 Cancellation Request 19 Request to Change Service Type 20 Fee Approval 22 Request to Change Service Type and Higher Fee Approval Testing Tools - Ordering Test JobsOrder test jobs using our testing tool. LIXI Queue LogWithin ValEx, we have a LIXI Queue Log. This can be useful for debugging LIXI issues.
This is an explanation of some of the less obvious information:
You can download the following files:
Receiving a Copy of the Final Valuation Response After Submitting to the Client (for Valuation Firms)Note: This is not for Clients! This is for Valuation Firms! We support sending a copy of the final valuation response that is sent to the client to the valuation firm. The implementation is a simple as adding a The LIXI message will be similar (but not the same) as you send back to us. Basically, the response will be an interpretation of your response, which is a standard LIXI message (not a workflow). All ValEx identifiers will be in their usual locations. If you want an example of the LIXI message that is sent, log into ValEx and check the Queue Log for any completed LIXI job. You should look for a response sent to the valfirm (we queue the LIXI message even if we do not support actually sending it). Due to the queue system, the response may be delayed by up to 10 minutes on average. Extending the LIXI standardsOne problem we have encountered a number of times is the requirement to go beyond the LIXI valuation standards. This is because the LIXI standards really do represent the most common uses; but the ValEx platform and its partners are seeking to innovate - the two goals of innovation and standards often conflict. Consequently for the 1.4.1 version of the ValEx XSD, we are introducing a minimal change to allow much greater extensibility. We are introducing an <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="skip"/> node. What this allows is for lixi partners to define information in a non-lixi namespace; without breaking schema validation. For instance: <ValuationTransaction xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:foo="http://foo.com" ProductionData="No"> <-- Appearing after the RelatedPartySegment or AttachmentSegment --> <foo:Foo>Hello! I'm a custom string, but could be any valid custom XML structure</foo:Foo> </ValuationTransaction> We are strongly advocating this amongst the LIXI valuation and CAL standards group as a way to move forward with custom or proprietry requirements; whilst still remaining LIXI standard compatible. You can preview and update to the 1.4.1 schema; which is not yet in use by the ValEx application. Escalation of Service TypeBetween a job order being place and the valuation being completed, a job can be escalated. Two main circumstances trigger a Service Type Escalation:
Service type escalation implies that a service type is changed incrementally from a minor service (such as a Kerbside Inspection) to a major service (such as a Residential Short Form requiring full inspection). escalate() Web ServiceWhen a job is escalated, we send through a SOAP request to the escalate() operation (if implemented) on a Valuation Firm Web Service to notify the valuer. We expect to the Web Service to have the following semblance: <message name="escalate"> <part name="valuationMessage" type="xsd:string"/> <part name="reason" type="xsd:string"/> <part name="from_service_id" type="xsd:int"/> <part name="to_service_id" type="xsd:int"/> <part name="comments" type="xsd:string"/> </message>
Escalation ReasonsA list of Reason IDs and their humanised strings is available. PropertyCharacteristics/@YearModifed Built AdditionsWe now parse <PropertyCharacteristics YearModified="2005 Added a second storey." ... This will populate the below two fields in ValEx: Rental Value Range
<ValueComponent LikelyWeeklyUnfRental="200-250" ...> This is available as of 1st December 2010. |
Related LinksNavigation |
Recent comments
10 years 12 weeks ago
11 years 4 weeks ago
11 years 6 weeks ago
11 years 6 weeks ago
11 years 11 weeks ago
11 years 35 weeks ago
11 years 40 weeks ago
11 years 45 weeks ago
11 years 45 weeks ago
11 years 45 weeks ago