Core Enhancements

In addition to the various enhancements made throughout the Lifecycle Management Suite, new core functionality has also been introduced to increase productivity and efficiency in the connection between the Lifecycle Management Suite and the following core interfaces:

Core

Feature

Description

Corelation KeyStone, DataSafe, DNA, and Symitar

CREATE_MEMBERSHIP_INCLUDE_JOINT parameter

The CREATE_MEMBERSHIP_INCLUDE_JOINT parameter has been added to the database to allow institutions to determine whether or not joint applicants are automatically linked to a new primary member account in the core. By default, this parameter is set to false (0) to maintain the existing core functionality at each institution. When the CREATE_MEMBERSHIP_INCLUDE_JOINT parameter is set to true (1), the following behavior occurs when a new member account is created in each of the below cores:

For institutions on Corelation KeyStone: While the CREATE_MEMBERSHIP_INCLUDE_JOINT parameter does appear in the database, the functionality is not currently available in the Corelation KeyStone core.

The following behaviors do not occur when the primary applicant is an existing account holder. For a complete overview of the behavior that occurs in each core, please see the applicable core connector guide.

Core	Description
DataSafe	Records are created for the first two joint applicants under the Non Member Account that is created for a new primary applicant in DataSafe.
DNA	Joint applicants are created when a new member account is created, and are automatically linked to the new member account in DNA.
Symitar	Joint Name Records are created for all joint applicants when the Primary Name Record is created under a new membership account in Symitar.

If it is desired to change the value of the CREATE_MEMBERSHIP_INCLUDE_JOINT parameter, please contact a Temenos Custom Care or Professional Services Representative.

DataSafe

Disbursement Warning for Discrepancies in DataSafe During Disbursement

The DataSafe interface has been enhanced to return a disbursement warning in the Lifecycle Management Suite when there are data discrepancies in DataSafe at time of disbursement. When this occurs, the loan is able to disburse successfully, but a disbursement warning is displayed in the Lifecycle Management Suite to alert users that the issue(s) exist and must be manually addressed in the core; a disbursement warning listing the issue(s) is appended to the disbursement success message for the loan, and is also added to the Notifications tab in the Lifecycle Management Suite.

DNA

CURRACCTSTATCD Host Value

The DNA interface now includes the CURRACCTSTATCD host value which allows institutions to set the status of an asset or liability when applicant data is imported from DNA. Prior to this enhancement, the ability to set the status of an asset or liability was not available during applicant import. Now, institutions can write a rule that executes during applicant import to automatically set the account status for host assets or liabilities, and effectively evaluate the status of each liability and asset imported from DNA.

DNA

Host values to EXCLUDEADDRESSDEMOGRAPHICS, EXCLUDEEMAILDEMOGRAPHICS, and/or EXCLUDEPHONEDEMOGRAPHICS

The DNA interface now supports the ability to separately exclude address, phone, and/or email demographics from being transmitted to DNA during disbursement. Prior to this enhancement, institutions were only provided with the ability to suppress transmission of all applicant demographics to DNA at time of disbursement. Now, the following host values are available to allow institutions to separately exclude address, email, and/or phone demographics from the DNA disbursement process:

EXCLUDEADDRESSDEMOGRAPHICS
EXCLUDEEMAILDEMOGRAPHICS
EXCLUDEPHONEDEMOGRAPHICS