Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
                                        
FeaturesSub Feature / PropertiesRequiredDescription
Signix E-Signature-
Implemented Signix as a vendor for Electronic Signature on forms. Additional information on Signix can be found on the Signix page in our documentation.




Native E-Signature

-


Native E-Signature support via HTML5 for Tablets and Mobile Devices using a stylus, finger or mouse.

. Additional information can be found on the Native E-Signature page.


Signing with Javascript in Form 

Native E-Sign Popup – Displays a signature box with the name of the role that is to sign.
(e.g. “Owner 1 – Sign Here”)


 

Geolocation Tagging

 

Capture the signer’s location using HTML5 Geolocation. (http://www.w3schools.com/html/html5_geolocation.asp)


Signature Summary Page

 

Adds a dynamically generated signature summary page that lists the signers and related data.

    • See “QFE – Native E-Sign – Signature Summary Information – Mockup.docx”

Navigate To Sign Fields

Walk the users through the signing process via a javascript that navigates to each signature field.

    • Using the signing sort order, displays the signature fields in order to the user. If multiple instances of the same role exist, then show each instance of that role before moving to the next role.
    • When the user clicks the SIGN button, positions the first unsigned signature field to the center of the screen. When the user signs and clicks SAVE navigate to the next signature field.

Display Sign Page Thumbnails 

Display page thumbnails with a signature icon to indicate pages that need signing.

    • Green icon is for pages where all signatures are complete.
    • Yellow icon is for pages where there is at least one unsigned field (whether required or not)
    • Red icon is for pages where a signature is required, the field is not signed and the user triggered a submit event.
   




New Field PropertiesField Background Color 
Field Background Color – allows customer to set the background color of fields in HTML.
Set Field Background Color Methods – provides various methods to set the background color
  • By Role
  • By Field Name

AttachFile

 

Attach File – adds an attach file icon/button next to the field for the user to supply a file attachment. Set to TRUE to display the file attachment button


 AttachTitle 

AttachTitle – optional – the title to display to the user (e.g. “Proof of Citizenship” so user uploads a copy of their ID or birth certificate)


 MaxFieldLength  
Restrict how many characters can be entered into a field by adding the “maxlength” attribute to the field.

MinValue

 


Allows user to set the minimum accepted value for a field by setting the “min” field attribute with a value

 MaxValue 
Allows user to set the maximum allowed value for a field by setting the “max” field attribute with a value

RegEx 
The pattern attribute specifies a regular expression that the <input> element’s value is checked against by setting the “pattern” attribute with a reg-ex expression value.

 AutoComplete 
if TRUE add the “autocomplete” attribute to the field. Give user the ability to add this feature at the “form” attribute level instead AND the field level.

SemiRequired 
A required field is evaluated when the submit button is clicked the first time and ignored/bypassed on the second submit button click in a row (if the submit button is clicked and fields are modified, start the two-click count over).

RequiredByRefField 
(Required) Specifies a reference field that if not empty makes this field required.

 RequiredByRefFieldValues 
(Optional) Specifies one or more values separated by commas that cause the field to become required when the reference field value matches the values in provided in this property.

Spellcheck 
TRUE turns on spellcheck for the field by adding the spellcheck=”true” attribute to the field (HTML5 only).

ToolTip 
Sets the “placeholder” field attribute with a tool tip value. A default placeholder value should be specified for fields named in the Quik! Field Defintion by using the field description value,

FieldType 

Converts a textbox field into one of the following field types (user must specify relevant values and this feature only affects textboxes) by setting the appropriate input type or HTML element type: Drop-down list - The <select> element defines a drop-down list and the <option> elements defines the options to select.

  • MultiLine – The <textarea> element defines a multi-line input field (a text area).
  • Range – The <input type=”range”> is used for input fields that should contain a value within a range. Must set Min value and Max value.
  • Month – The <input type=”month”> allows the user to select a month and year.
  • Week – The <input type=”week”> allows the user to select a week and year.
  • Time – The <input type=”time”> allows the user to select a time (no time zone).
  • DateTime – The <input type=”datetime”> allows the user to select a date and time (with time zone).
  • DateTimeLocal – The <input type=”datetime-local”> allows the user to select a date and time (no time zone).
  • Email – The <input type=”email”> is used for input fields that should contain an e-mail address.
   




New Form Properties

Set Field Background Color

  




 AutoComplete     





Buttons and Button Name Properties

New Button – Email

 

Displays an email pop-up window to capture the recipient’s name, email address and a verify code. Verify Code is stored with the Routing Status in tblFormPackageRouteStatus


HTMLButtonClearName 
Renames the Clear button

 HTMLButtonResetName 
Renames the Reset button

 HTMLButtonSaveName 
Renames the Save button

 

HTMLButtonLoadName

 


Renames the Load button

HTMLButtonSubmitName 
Renames the Submit button

HTMLButtonPrintName 
Renames the Print button

HTMLButtonSignName 
Renames the Sign button

EnableNativeESign   


HTML4Compatible  


 SignHideEmptySigners   


SignMultipleDocs  


 SignOrderLock   


FieldAttributesManagerTest   


FieldAttributesManagerOff  


RoutingRulesOn  


RoutingRuleFormGroupID     





Calculated Field Pop-Up

- 
When a user begins editing a value in a calculated field, display a pop-up that shows the underlying fields that calculate the field (e.g. FullName should display Prefix, Fname, Mname, Lname, Suffix fields). Completing the entry re-calculates the field and updates the underlying base fields that populate the rest of the form, including other instances of the calculated field.   




Custom Alternative Data Buttons

- 
The customer can add an Alt Data Button next to any single field name and provide a list of fields to use (similar to a dropdown list but displayed as a “+” button).   




DocuSign Integration Enhancements

SignHideEmptySigners

 


When set to TRUE, hide any signing roles in the E-Sign Popup screen where a Fullname or Fname field exists on the form and contains no value (i.e. no person was entered on the form and is therefore not expected to sign). If no Fname or Fullname field exists for the signing role, then do not hide the role in the E-Sign popup – always show it.


SignMultipleDoc

 


When set to TRUE, put each FormID into the DocuSign envelope as a single PDF. When FALSE (current, default behavior) the form package is delivered to DocuSign as a single PDF.

 



 

SignOrderLoc

 


If TRUE, set the sign order fields as read-only and not editable by the user.

 

Sign Type Modification

 


All the roles on the e-sign popup are signers, so the Sign Type should default to “Email To Sign” (in the future other signing options will be added to the dropdown list so this needs to remain a drop-down list). The easiest solution is to remove the “Send Copy” option and force the user to use the “Add Recipient” button to send copies instead.


Add Recipient Button 

Clicking the Add Recipient button adds a row to the e-sign popup for additional recipients to receive a copy after all other recipients.


 

Send On Behalf Of (SOBO)

  • SOBOFlag
  • AuthUserID
  • SenderUserID
 


No

(DocuSign Feature) Allows a single user in an account to authenticate for other members of the account. When originally conceived, it was meant for sending fully-defined envelopes only. Since then, most other API functions have been allowed - making this really an "authenticate on behalf of" function instead of just a sending function.

  • SOBOFlag - Default is false. When true, DocuSign's Send On Behalf Of (SOBO) is enabled.
  • AuthUserID - the CustomerUserID in tblESignatureCredentials for the authenticating user
  • SenderUserID - the CustomerUserID in tblESignatureCredentials for the sending user
   




HTML5Only Output

- 

Setting this option to FALSE forces the engine output to only be in HTML5 code and only works in higher-level browsers, setting it to TRUE generates the existing HTML5 and HTML4 code tags. The Default setting is TRUE (for legacy customers).

    




New HTML Field Types

DropDown Boxes 

Convert from existing drop-down in PDF, or convert any field into a drop-down with values

 

  




User-Added Attachments

-

 


(Optional) When set to TRUE, displays the file attachment panel and file attachment image button. Displays a list of attachments to remove or add more. Attachments can be a file that we convert to PDF or a photo captured by their device.


 Convert Files to PDF  


 

Take Photo and Attach

  


 

Attachment List in QFV

  




Upload Attachments 
Users can upload their own attachments to the form for printing and signing.   




Javascripts

Auto-Shrink Text in Textboxes

 


-

iScroll Modification

 
-

 

Disable Print Button

 
-

Disable Send Button 
-   




Quik! Enterprise Manager Overhaul

Form Groups

  


 

Form Search

   


Upload Forms

  




 

Field Attribute Manager

  




Routing Rules

  




Edit Route Message Content

  




Form Links Manager

 

 


 

AutoSubscribe

  




Individual Form Subscription

  




 

Account Setup

   


Implementation Resources  

 

...