SearchUser loginPopular contentAll time:
Valuation Firm GuideClient Guide
|
Important change - related party segment now shows Funder as well.We've put in place a small change to add in the Funder for certain jobs. You can tell the two related parties apart with the identifier prefix. Client://RelatedParty[@RelPartyType='Lender' and starts-with(Identifier/@UniqueID,'VXCL-')]/CompanyName/@BusinessName The Client is the Bank. There is always only one Client per job. Funder://RelatedParty[@RelPartyType='Lender' and starts-with(Identifier/@UniqueID,'VXF-')]/CompanyName/@BusinessName In most cases there will be one funder per job. There will not be more than 1. This change will be available as of Monday May 11th, 2009. By doconnor at 2009-05-09 15:58 | API | Client Guide | Valuation Firm Guide | login to post comments
Accepting a Job - process changeSome time ago we designed it so valuers were assigned before appointments in ValEx. This has led to the often confusing error message of No office valuer exists, and is generally a pain for all parties. To fix this, we'll be adding a 'default valuer' setting in our valuation firm setup areas. Our valuation firm users won't have to change anything, however when we deploy there may be some setup and configuration changes we'll need to make. We are currently looking at implementing this approximately Mon June 15th 2009. Documents From Clients (RequestSupportingDoc)We now support RequestSupportingDoc from clients. Example below: <RequestSupportingDoc DocType="Image" RequestorIncludedDoc="Yes" ResponderToReturnDoc="No"> <Identifier UniqueID="DOC0000001" Type="LenderAssigned"/> </RequestSupportingDoc> We require the document in the AttachmentSegment as per the article on Attachments (Reports, Images, Title Details etc). Changes to Delay ReasonsPlease be advised that as of 23 February 2009 we will require a Delay Reason to be sent with any Delay workflow. Please also note that our Delay Reasons will also be modified slightly. Estimated Selling Period / Estimated SettlementNOTE: The following article has now been DEPRECATED - please refer to the article on Expected Selling Period
LIXI 1.4.3The new version of the LIXI standard defines an EstimatedSettlement element. For a while now, we have have been capturing Expected Selling Period under the Value tab of reports. This is also rendered in our reports under the Additional Comments. We accept:
When we translate your integer to our enumeration; we use the following translation: for months <= 3, we assume a selling period of 3 months. Months 4-6, we assume a selling period of 6 months. Otherwise, we assume greater than 6 months. To enter a comment, we will continue to read //ExpectedSellingPeriodComment as below. This method was for LIXI 1.3, and an alternative is now present in LIXI 1.5 In our 1.3 series schema, we looked for:
If the estimated selling period is greater than 3 months, an ExpectedSellingPeriodComment should be provided. Assessed Market Value, Estimated Market Value, and Contract PriceLIXI defines LIXI defines
ExamplesAssessed Market ValueIf the <EstimatedValue EstimateBasis="CertifiedValuation"> 250,000.00 </EstimatedValue> or //ValueComponent/MarketValueAsIfComplete[@Type="SinglePoint"]/@ValueCeiling See also: Assessed Market Value - best location Contract PriceIf the <EstimatedValue EstimateBasis="ContractPrice"> <Date>2004-01-01</Date> 250,000.00 </EstimatedValue> Estimated Market ValueIf the <EstimatedValue>315,000.00</EstimatedValue> Or: <EstimatedValue EstimateBasis="CustomerEstimate"> 250,000.00 </EstimatedValue> By dbezborodov at 2009-01-27 11:18 | API | Client Guide | Valuation Firm Guide | login to post comments
Lodging valuation queries for ClientsWe've implemented in ValEx the ability for client to lodge post valuation queries. Webservice changesWe have be published a new soap action in our production environment. You can view the WSDL documentation: requestValuationQuery(LIXIValuationResponse xml, int reason_id, string comment) The first argument, xml is simply your updated valuation response packet. The second is the reason for amending. It is an int from 1-4; meaning:
Next is a comment of 5 words or more explaining why the report needs amending. ValEx user interfaceSee alsoTips for Finding Documentation and Keeping What's Left of Your Hair During DevelopmentSuggestions welcome! Finding LIXI Documentation / Getting Help
A Suggested Testing ApproachIntegration development process:
Development tips:
ValidationWondering about the different levels of validation within ValEx, and when you get certain errors? The different levels are:
Amending completed reportsWe'll be implementing some changes in ValEx to help make the Mortgage Manager Query/Valuer Report Amendment Process more efficient on Monday, December 15th 2008. We will be allowing Valuers to amend reports without having to use the ValEx Team as an intermediary. Valuers' ability to open a report for amendment is based on Client preferences. UI ChangesWithin the user interface, we'll be allowing valuers to trigger an amendment, add a quick note as to why, and basically just get out of the way for trivial things - ie, typos or missing photos. In the short term, we'll be improving the error emails we currently generate when a LIXI valuation response reaches us; to be more informative for users - in effect, please login to the site to open your report for amendment. As a longer term goal, we'll be allowing valuation firms to submit an amended report with an amendment reason and comment. Web Service ChangesWe will be publishing a new soap action in our test environment by December 15th. We will update our WSDL and this article when we have published it. It will be along the lines of: submitAmendedValuationResponse(LIXIValuationResponse xml, int reason_id, string comment) The first argument, xml is simply your updated valuation response packet. The second is the reason for amending. It is an int from 1-4; meaning:
Last is a comment of 5 words or more explaining why the report needs amending. |
Related LinksNavigation |
Recent comments
10 years 18 weeks ago
11 years 10 weeks ago
11 years 12 weeks ago
11 years 12 weeks ago
11 years 17 weeks ago
11 years 41 weeks ago
11 years 46 weeks ago
11 years 51 weeks ago
11 years 51 weeks ago
11 years 51 weeks ago