PowerLender. All Articles in All Categories. Generated by KnowledgeBuilder -

Transcription

1 PowerLender All Articles in All Categories

2 Contents Replication 1 Laptop Replication 1 The Network Adapter Could Not Establish the Connection 1 Database Information 1 SQL Server 2 SQL Server Reserved Words 2 New Client Installation 15 Removing VMP Documents from LRF 15 VMP Documents - New Client Installation 16 Crystal Reports 16 Crystal Reports and Citrix 16 Citrix 17 Interface Information 17 XML Interfaces 17 Is CLUES part of CLOUT or CLOUT part of CLUES? Or are they the same thing? 17 I\'m using an EDI function with the print option enabled, but it isn\'t working. 18 Troubleshooting XML Interfaces 18 Setup 19 PowerLender and Barcoding 19

3 There are no articles in this category. Replication There are no articles in this category. Laptop Replication The Network Adapter Could Not Establish the Connection In this case PowerLender could not connect to the localhost Add Articledatabase. From the log "The Network Adapter could not establish the connection' while getting connection using URL Solutions: Is the database running? Is the URL correct? Is the username and password correct? Is the security on the database rejecting the connection? Have you tried connecting to the database using the vendor's tools as the PowerLender user? Have you tried instead of localhost? Database Information Includes database specific information, questions, etc. There are no articles in this category. 1 of 19

4 SQL Server Information relating directly to MSSQL (SQL Server) SQL Server Reserved Words Microsoft SQL Server uses reserved keywords for defining, manipulating, or accessing databases. Reserved keywords are part of the grammar of the Transact-SQL language used by SQL Server to parse and understand Transact-SQL statements and batches. Although it is syntactically possible to use SQL Server reserved keywords as identifiers and object names in Transact-SQL scripts, this can be done only by using delimited identifiers. The SQL Server reserved keywords are: ADD EXIT PRIMARY ALL FETCH PRINT ALTER FILE PRIVILEGES AND 2 of 19

5 FILLFACTOR PROC ANY FLOPPY PROCEDURE AS FOR PROCESSEXIT ASC FOREIGN PUBLIC AUTHORIZATION FREETEXT RAISERROR AVG FREETEXTTABLE 3 of 19

6 READ BACKUP FROM READTEXT BEGIN FULL RECONFIGURE BETWEEN GOTO REFERENCES BREAK GRANT REPEATABLE BROWSE GROUP REPLICATION 4 of 19

7 BULK HAVING RESTORE BY HOLDLOCK RESTRICT CASCADE IDENTITY RETURN CASE IDENTITY_INSERT REVOKE CHECK IDENTITYCOL RIGHT 5 of 19

8 CHECKPOINT IF ROLLBACK CLOSE IN ROWCOUNT CLUSTERED INDEX ROWGUIDCOL COALESCE INNER RULE COLUMN INSERT SAVE COMMIT 6 of 19

9 INTERSECT SCHEMA COMMITTED INTO SELECT COMPUTE IS SERIALIZABLE CONFIRM ISOLATION SESSION_USER CONSTRAINT JOIN SET CONTAINS KEY 7 of 19

10 SETUSER CONTAINSTABLE KILL SHUTDOWN CONTINUE LEFT SOME CONTROLROW LEVEL STATISTICS CONVERT LIKE SUM COUNT LINENO SYSTEM_USER 8 of 19

11 CREATE LOAD TABLE CROSS MAX TAPE CURRENT MIN TEMP CURRENT_DATE MIRROREXIT TEMPORARY CURRENT_TIME NATIONAL TEXTSIZE CURRENT_TIMESTAMP 9 of 19

12 NOCHECK THEN CURRENT_USER NONCLUSTERED TO CURSOR NOT TOP DATABASE NULL TRAN DBCC NULLIF TRANSACTION DEALLOCATE OF 10 of 19

13 TRIGGER DECLARE OFF TRUNCATE DEFAULT OFFSETS TSEQUAL DELETE ON UNCOMMITTED DENY ONCE UNION DESC ONLY UNIQUE 11 of 19

14 DISK OPEN UPDATE DISTINCT OPENDATASOURCE UPDATETEXT DISTRIBUTED OPENQUERY USE DOUBLE OPENROWSET USER DROP OPTION VALUES 12 of 19

15 DUMMY OR VARYING DUMP ORDER VIEW ELSE OUTER WAITFOR END OVER WHEN ERRLVL PERCENT WHERE ERROREXIT 13 of 19

16 PERM WHILE ESCAPE PERMANENT WITH EXCEPT PIPE WORK EXEC PLAN WRITETEXT EXECUTE PRECISION EXISTS PREPARE 14 of 19

17 New Client Installation Contains information necessary to install PowerLender at a new client location. Internal only. Removing VMP Documents from LRF To Remove all VMP forms from the MLM, before delivery, run the following.sql statements to remove any instances from the FORM table and the BOIL table. Run the SELECT statements and review to ensure all records selected are correct, then run the DELETE statements. SELECT Name, Sequence, Description, FileName FROM `boil` Where FileName like '%OVL' SELECT * FROM `boil` where FileName like '%fnt' select PrimaryKey, Description, BoilerPlatePath FROM `form` Where BoilerPlatePath like '%OVL' Delete FROM `boil` Where FileName like '%OVL' Delete FROM `boil` where FileName like '%fnt' 15 of 19

18 Delete FROM `form` Where BoilerPlatePath like '%OVL' VMP Documents - New Client Installation Before we install a new client we need to make sure we know what VMP documents they have licensed. In the UNI-FORM days, we obtained the information in one of three ways: 1. The information would come to us with the contract. That was when they used ASC as the gobetween for purchasing the VMP documents. Tim - do we even act as the middleman any longer? 2. After support received the contract, Client Services would do an introduction call. We had a checklist of questions one of which was to find out what document sets were purchased. 3. If we knew the client purchased VMP documents, but we could not obtain a list from them in a timely manner, we would contact VMP directly to find out what was purchased. We can still do this. Our rep, Brian Hart, is listed in CustomerFirst under Wolters-Kluwer. With PowerLender, it is part of the information gathering during the initial implementation meeting. (It's included on the implementation meeting outline.) It's important that we know before we even install the customer which VMP document sets they have purchased. We are not supposed to deliver unlicensed VMP documents to our clients. (For convenience, the documents are imported and have fields already plotted.) Before we install, we are supposed to execute a SQL script that deletes those documents that were not licensed. Crystal Reports Crystal Reports and Citrix 16 of 19

19 Though Crystal Reports is not supported by Business Objects as a Citrix application, Crystal Reports can be made available to remote users using Citrix. The attached document provides troubleshooting information. Citrix There are no articles in this category. Interface Information There are no articles in this category. XML Interfaces Is CLUES part of CLOUT or CLOUT part of CLUES? Or are they the same thing? They are both Countrywide: CLUES The Countrywide CLUES automated underwriting service provides a loan purchase decision, provided all conditions are satisfied, for a specific loan program based on a loan application, additional underwriting information, and accompanying credit report. CLUES is able to underwrite loan programs that Countrywide offers CLOUT The CLOUT service is Countrywide s prequalification tool that opens up the entire spectrum of loan products to users. CLOUT combines, under user control, the CLUES, DU, and LP automated underwriting engines and returns automated underwriting decisions. Each underwriting engine can be accessed by either a Detailed or a Streamlined submission. In addition to the information normally provided for an automated underwriting decision, the user defines filter criteria, such as loan type, term, payment type, lien position, etc. that specifies the types of loan programs that are of interest to the borrower. CLOUT submits the loan for loan 17 of 19

20 programs that satisfy the filter criteria and returns the results, along with pricing information. Information on loan programs for which there are guideline violations are also returned, to provide additional financing options should the guideline violations be corrected. The results are organized as a collection of underwriting decisions, along with information relating to the loan program and pricing information corresponding to each decision. I\'m using an EDI function with the print option enabled, but it isn\'t working. When using an EDI function with a defined print token, the print token is ignored for all XML interfaces. Printing is controlled through the attachments window. Troubleshooting XML Interfaces As our lenders are beginning to develop XML interfaces, more problems are being routed through Tech Support. Here is the start of a list on how you can help with the escalation process on these problems. Feel free to add your suggestions as you run into situations. 1) Always request these files from the client: a log file at least at level 3 - preferably cleaned out to just the one incident in question; the request and response file (if any) from the XML folder under PowerLender for the transaction in question. Reminder: we need to be careful about receiving files with private information on a consumer. 2) Is the lender using a named map or a MISMO map from the View side of the XML data map screen? 3) The data interchange format being used may be helpful. Ask for a listing of the data interchange format being used. 4) Keep in mind the silly things that can cause problems: Is the field in question mapped? Is the field in question turned on for this loan type? Is the field in question populated? 5) Your patience is needed. As more of these interfaces are implemented by our lenders, we will all learn things as we go along. The first interfaces - CBC Companies Credit and Flood; First American CREDCO Credit and Flood were developed a couple of years back. 6) Be Prepared! This is more than a scout motto...the LRF can be used as a sample for helping you understand how these interfaces work. There are checklists and, with some vendors, even testcases. These can be printed from: \\cicero\public\lop\qa\functionality Checklists\Setup\Data Interchange. 7) Know that the lenders will be asking for enhancements to these drivers on things we did not think of during the initial design and implementation process. That is fine with us and does not mean that these are bugs. If the interface works, these are enhancements. 18 of 19

21 Setup Contains information on the various PowerLender setup routines. PowerLender and Barcoding PowerLender is able to print any loan application value on any document as a barcode. This feature is programmed into PowerLender. Why you print barcoded values is based on the purpose of the document. PowerLender is also able to read any barcoded value from any document. This is done using a barcode "wand" reader that behaves like your keyboard. The confusion is whether there is any purpose to this, and right now PowerLender lacks any user interface element to make barcode reading useful. UNI-FORM had a simple routine called "Receive Barcoded Documents". You wanded in the loan application key from a barcode on a document, like a VOD. UNI-FORM retrieved that loan application. You then wanded in the output form key that was also barcoded on the document, so UNI-FORM knew what kind of document was received. UNI-FORM retrieved the output form record, which told UNI-FORM the document's "received date" field number and "route to" field number. UNI-FORM stored today's date in the "received date" field in the application record to indicate when that document was received for that loan application. UNI-FORM also evaluated the "route to" field definition and displayed the result to the user, so the user knew what to do with the document. PowerLender doesn't have any equivalent to "Receive Barcoded Document" because we were unsure at the time we wrote PowerLender whether UNI-FORM users even used it. It would be easy to provide PowerLender with a similar dialog. I'm telling you this because we get questions from clients and potential clients about barcoding. The correct answer is "Yes, PowerLender can read and write barcodes. How do you use barcodes?" We need to drill down to the barcoding purpose. The purpose may be what we used to provide in UNI- FORM, but it may be something new and different that we didn't anticipate, and may become a simple and useful PowerLender enhancement. It's not that PowerLender "can't do barcodes". It's just that right now it doesn't do them well. 19 of 19