IMM University's LiquidOffice Training Class - Quiz #2 Question Title 1. What is the file extension of the finished form that gets uploaded into eSign? JPG BMP XFM PDF Question Title 2. Which of the following document names are NOT in an acceptable naming convention? Application-AXX143.pdf Guaranty-Agreement-CUNA-150.pdf CA-DMV-REGISTRATION.pdf Consumer_Addendum_To_OE_Credit_Plan(@ddend*m!).xfm Question Title 3. The eSigns form name must be less than 50 characters including the extension (.pdf). True False Question Title 4. When using the Expression Builder in LiquidOffice Forms Designer to create a calculation, the target field that will be performing the function can be set to either ‘Numeric’ or ‘Text’. True False Question Title 5. The following steps are required for all eSign documents (including text-only documents): 1) eSign objects (CURPDF, IMMDOCTYPE) 2) The default code generated via JSCodeGenerator should be copied into document’s script editor 3) Project Settings should be set to “Display Client Specific JavaScript Event Model” and “Acrobat Forms” True False Question Title 6. To support duplex printing, the designer must insert a blank page at the end of a document when the page count is an odd number. This way when a user prints more than one document together, the second document's first page will not print on the back side of the first document's page. True False Question Title 7. There is no option in LiquidOffice Forms Designer to turn on/off duplex printing. You will need to enable duplexing before clicking OK to print when opened the document is opened within eSign. True False Question Title 8. When creating a document from scratch, you can copy text from a Microsoft Word\Excel document and paste into an LiquidOffice Forms Designer document. True False Question Title 9. Although documents with submit buttons will work in V 5.3 SP1 or 2015 and above, they are no longer required. eSign will hide the submit buttons when the documents are uploaded into V 5.3 SP1 or 2015 and above. True False Question Title 10. There is a preset naming convention that needs to be followed in order for Duplicate Fields to function correctly in eSign. Which one of the following is the correct naming convention? ‘P_APPLICANT_NAME,’ ‘P_APPLICANT_NAME_D1,’ ‘P_APPLICANT_NAME_D2’ ‘P_APPLICANT_NAME,’ ‘P_APPLICANT_NAME_P1,’ ‘P_APPLICANT_NAME_P2’ ‘P_APPLICANT_NAME,’ ‘P_APPLICANT_NAME_C1,’ ‘P_APPLICANT_NAME,’ ‘P_APPLICANT_NAME_1,’ ‘P_APPLICANT_NAME_2’ Question Title 11. The JSCodeGenerator utility gives you the ability to generate the JavaScript code required for documents to work within eSign. If the FI is creating and/or maintaining their own documents, it is mandatory that the FI purchase JSCodeGenerator. True False Question Title 12. When making a change that only involves the text on a document, you will have to re-run the JSCodeGenerator to create new JSCode to reflect the text change. True False Question Title 13. The project settings in Script Editor is a REQUIRED setting - “Display Client Specific JavaScript Event Model” and “Acrobat Forms” before saving and compiling JavaScript code within the Script Editor of the document. True False Question Title 14. An eSign document (when displayed and processed) requires a few mandatory data entries for some fields before clicking the “Continue” button. How do I set up the mandatory fields in LiquidOffice Forms Designer? Check the “Entry Required” property of the field. Check the “Read-Only” property of the field. Check the “Entry Required” and “Read-Only” property of the field. Enter all mandatory fields prior to generating JavaScript in JSCodeGenerator. Question Title 15. In what section of the default JavaScript code would you paste a custom JavaScript function that you want to execute when the form is loaded? Inside the try-catch-error block provided under the IMM_CSTM_OnFormLoad function. The IMMValidateForm function It doesn’t matter where I paste my custom code. None of the above Question Title 16. For a signature or initial field, what is the correct field naming convention? TEWEB_SIG_i, TEAWEB_INI_i SIGNATURE_i, INITIAL_i SIG_i, INI_i TEAWEB_SIG_HOSTPREFIX_i, TEAWEB_INI_HOSTPREFIX_i – Replace the “HOSTPREFIX” with the signing party’s field prefix ex: A_ for primary applicant and C_ for co-applicant. Question Title 17. For each signature field the corresponding DATE (TEAWEB_SIG_HOSTPREFIX_i_DATE) field is NOT required. The designer may select to NOT map the DATE field. True False Done