Connector Enhancements

The following third party integrations are now better than ever in the Lifecycle Management Suite 16.05 release!

CUDL Citizenship Status Field

The CUDL connector has been enhanced to map Citizenship Status to the Lifecycle Management Suite. Prior to this enhancement fields that collected citizenship status existed in both the Lifecycle Management Suite and CUDL, but no mapping existed between the two fields. Now, CUDL's CitizenshipStatus field is directly mapped to the Application > Applicants > Residency Status Id field within the Lifecycle Management Suite.

CUNA Protection Advisor and IMM

Additional GAP and MRC Fields

The CUNA Protection Advisor connector has been enhanced to store additional GAP and MRC fields. Prior to this enhancement, these fields were not transmitted or stored within the Lifecycle Management Suite. As result, the following new fields are available within reports, views, rules, and the CUNA Protection Advisor screen’s response card:

CUNA Field Name	Lifecycle Management Suite Field List Path
InsuranceVehicleCode	Application > CrossSell > Insurance Vehicle Code
InsuranceVehicleClass	Application > CrossSell > Insurance Vehicle Class
IsInsuranceVehicleDiesel	Application > CrossSell > Is Insurance Vehicle Diesel
IsInsuranceVehicleFourWheelDrive	Application > CrossSell > Is Insurance Vehicle Four Wheel Drive
IsInsuranceVehicleTurbo	Application > CrossSell > Is Insurance Vehicle Turbo
InsuranceSubtotal	Application > CrossSell > Insurance Subtotal
InsuranceTax	Application > CrossSell > Insurance Tax
InsuranceIssueDateOfCoverage	Application > CrossSell > Insurance Issue Date Of Coverage
IsInsuranceGAPPlus	Application > CrossSell > Is Insurance GAP Plus

These fields are not available for customer defined screens.

The IMM Data Dictionary has also been enhanced to support additional CrossSell fields, which may be used populate CUNA Protection Advisor fields within loan documents. Prior to this enhancement, GAP and MRC/MBD forms needed to be manually completed and did not auto-populate within IMM forms. Now, the following fields to be mapped within loan documents:

Application > CrossSell > Certificate Number
Application > CrossSell > Insurance Term In Months
Application > CrossSell > Insurance Term In Miles
Application > CrossSell > Insurance Deductible
Application > CrossSell > Insurance Effective Date Of Coverage
Application > CrossSell > Insurance Vehicle Code
Application > CrossSell > Insurance Vehicle Class
Application > CrossSell > Is Insurance Vehicle Diesel
Application > CrossSell > Is Insurance Vehicle Diesel
Application > Application > CrossSell > Is Insurance Vehicle Four Wheel Drive
Application > Application > CrossSell > Is Insurance Vehicle Four Wheel Drive
Application > CrossSell > Insurance Subtotal
Application > CrossSell > Insurance Tax
Application > CrossSell > Insurance Issue Date Of Coverage
Application > CrossSell > Is Insurance GAP Plus
Application > CrossSell > Is Insurance GAP Plus
Credit Union ID parameter from the CUNA Mutual Calculator Connector
Application > CrossSell > Is Insurance Vehicle Turbo
Application > CrossSell > Is Insurance Vehicle Turbo

The aforementioned Application > CrossSell fields are also available for IMM documents when using the Allied IQQ, Car Solutions, and SWBC Unity connectors.

Dealertrack

Deal Update Functionality

The Loan Origination module now supports Dealertrack's Deal Update functionality!

This functionality provides institutions with the ability to receive updates to a decisioned loan application from Dealertrack, and seamlessly apply the updates to the application in the Lifecycle Management Suite, without having to withdraw the existing application, and create a new one. When the Deal Update functionality is active for an institution, and terms of a decisioned application are changed, Dealertrack is now able to send deal update notifications to the Lifecycle Management Suite, and update the terms of the loan while the application is still in progress.

For example, if a loan is declined, but the applicant decides to purchase a less expensive car, the dealer can submit the new terms to Dealertrack, who can then modify the terms, and send the update to be applied to the existing application in the Lifecycle Management Suite.

In order to update Dealertrack applications in the Lifecycle Management Suite, each institution must enable the Deal Update feature with Dealertrack.

DocuSign

The DocuSign connector is now available for use in Virtual Capture!

When the document delivery method for an envelope is set to online, the system now populates a signing URL for the primary applicant during envelope creation to allow documents to be signed from the Web Signature Documents Panel in Virtual Capture using the DocuSign connector.

Additionally, when a recipient performs a signer action in DocuSign, a Signing Status and Signing Event now populate for each recipient of a document envelope in the Lifecycle Management Suite.

The following enhancements have been made in the Lifecycle Management Suite to support the new capabilities of the DocuSign connector:

Enhancement	Description
New DocuSign Fields	The following fields have been added to support the ability to capture the delivery method for an envelope, as well as the signing URL and signing status for envelope recipients: DocuSignDeliveryMethod - This field pulls values from the DOCUMENT_DELIVERY_METHOD lookup in System Management > Origination > Field Configurations to identify the delivery method for a DocuSign envelope. This field has been added to the Field List for rules, views, and reports, and is now a required field within the General tab of the New DocuSign Envelope window. DocuSignSigningURL - This field captures the signing URL for each envelope recipient. This field is only available in the Lifecycle Suite database, and the API. DocuSignRecipientStatus - This field identifies the signing status for each envelope recipient. This field is a system-defined lookup that has been added to System Management > Origination > Field Configurations, is available to be added to rules, views, and reports, and now appears within the Recipients tab of the New DocuSign Envelope window. The Signing Status for each recipient also now populates in the Recipients column of the grid in the DocuSign screen. Signing Event Id – This field identifies the signer event associated with each recipient, and pulls values from the system-defined DOCUSIGN_RECIPIENT_SIGNING_EVENT lookup added to System Management > Origination > Field Configurations. This field is available to be added to rules, views, and reports, and now appears in the Recipients column of the grid in the DocuSign screen. With this feature, the Document Delivery Method field has also been made available in the Field List for Virtual Capture screens.
Updates to the DocuSign screen and New DocuSign Envelope window	The following enhancements have been made to the grid in the DocuSign screen: A column for Delivery Method has been added to the DocuSign screen to enable users to easily view the delivery method assigned to the envelope directly within the grid. The Recipients column has been updated to list the Signing Status for each recipient, as well as a field for Signing Event, which displays values such as CANCEL, SIGNCOMPLETE, and IDCHECKFAILED, to identify the action taken by a recipient. In addition to the enhancements to the grid, the following updates have been made to tabs within the New DocuSign Envelope window: A field titled Delivery Method has been added to the General tab to provide the ability to identify the delivery method for each DocuSign envelope. This field defaults to the Document Delivery Method that is set for the application, but can be updated for the specific envelope by selecting a value of Email or Online from the drop-down list. The Recipients tab in the New DocuSign Envelope window now includes a read-only column for Signing Status which displays the signing status for each recipient among the envelope details.
Add Recipient to DocuSign Envelope Rule Template	The Add Recipient to DocuSign Envelope template has been added to the Rules Management application to allow institutions to automatically add one or more recipients to a DocuSign envelope through execution of an EsignatureDefaultValues rule.
Create DocuSign Envelope Action	The Create DocuSign Envelope Action is now available in System Management > Origination > Event Processing to automatically create a document envelope, execute the configured ESignature Default Value rules, and send the envelope to DocuSign during the defined event.
SITEROOT Parameter in the Database	A SITEROOT parameter has been added to the database to allow institutions to define the location applicants are redirected to in Virtual Capture once the documents in an envelope are successfully signed in DocuSign. This parameter navigates the applicant back to Virtual Capture from DocuSign to allow the system to update recipient statuses in the Lifecycle Management Suite, and display the applicable status messages to the applicant in Virtual Capture. The value of the SITEROOT parameter is determined by each institution, and set in the database by a Temenos Customer Care or Professional Services representative after the upgrade to 16.05.

For more information, please see the DocuSign Connector Guide.

FICO CCS

The Lifecycle Management Suite has been enhanced to support the FICO CCS connector. Using the FICO CCS connector, institutions are able to manually and automatically contact applicants via phone, email, and text message regarding their application status for new applications from within the Lifecycle Management Suite. Using this connector, institutions are able to effectively communicate with applicants which will

For more information on the FICO CCS connector, visit www.fico.com.

RouteOne

Net Proceeds

The RouteOne connector has been enhanced to support a new host value that enables institutions to send a value to the Net Proceeds field within RouteOne during disbursement. Prior to this enhancement, the Lifecycle Management Suite was unable to transmit a value to the Net Proceeds field.

For more information on authoring the Net Proceeds rule logic, please see the Defining Rules topic within the RouteOne Connector Guide.

Silanis

Automatically Add Recipients

The Silanis connector now allows institutions to automatically add recipients to a Silanis package!

A new Add Recipient to Silanis Package template has been added to the Rules Management application to enable the ability to automatically add one or more recipients to a Silanis package through execution of an EsignatureDefaultValues rule.

When the Create Silanis Package action executes during the application process, the EsignatureDefaultValues rule executes to add the recipients that meet the rule criteria to the package with the Signing Role, Security Type, and Order defined in the Add Recipient to Silanis Package template.

Custom Mapping for Application Fields

Institutions are no longer limited to only mapping Term, Payment Frequency, and Payment Method to custom values in Silanis!

The Custom Field Mappings section of the Silanis Connector page now includes an and button to allow administrators to select an Application level field to map to a custom value in Silanis, or remove a custom mapping from document packages at their institution.

When is clicked, a Field Selector window appears to provide system administrators with the ability to select a field from a list of all editable standard Application level fields available in the Lifecycle Management Suite, as well as any Application custom fields configured by the institution in System Management > Custom Fields.

Once a Lifecycle Management Suite field is added to the grid, administrators can click within the Current Mappings column to define the Silanis custom field that the corresponding Lifecycle Management field is to be mapped to when the Silanis package is completed.

After the upgrade to 16.05, the Payment Amount, Payment Frequency, and Term fields continue to appear in the Custom Field Mapping grid.