Temenos Lifecycle Management Suite - Loan Origination Product Guide
Rules Management - Rule Categories
Administrator Guide > Rules Management > Rules Management - Rule Categories

Rules are broken down into Categories. Each category contains a grouping of like rules. Each rule category is able to be assigned and called at specific times during the application lifecycle.

Business Rule Category Assignment and Execution Description
Aggregates All rules automatically executed during Risk, Pricing and Decision Models. Rules written in this category should be authored at the Applicant and Application entities. This ensures that the aggregates are calculated for each applicant and the entire application.

Unused rules within this category can be disabled. By disabling Aggregates which are not being used, only the active Aggregates are called during the application process.

When authoring custom aggregates, the application level aggregate needs to include filtering for "IncludeInApplicationAggregates is true".
Applicant Import Automatically executed when an application is created or when an additional applicant is added to an application.

Executed to bring in applicant information fields as needed for the Core Processor integration (applicant demographics, assets, liabilities, etc.).

These rules can also be written under the Applicant.Liabilities entity to modify the IsSecured value of a liability created from the Core system (set IsSecured = True/False).

Rules written to modify the CreditReportAccountNumber field, such as a rule to remove leading zeros, should be written under the Applicant Import category. This imports applicant liabilities from the Core in the same way that they appear in the credit report tradeline to ensure that they de-dupe correctly.
Application Changed Automatically executed when the application decision or status is changed. Executed any time an application decision or status is changed. This category is meant to be used to change data on the application based on various information, such as a decision or status changing.
Calculate Automatically executed on Save & Next processing. Executed anytime application data is saved. This category is meant to be used to calculate field values that need to be updated each time data is changed on the application. Before authoring a rule under this category, please contact Temenos to review.
Concurrent Application Processing Automatically called as part of the Decision Model. Executed as part of the Decision Model. It also looks for any Attributes of the Associated Applications to potentially include the application as a liability for decision on the current application.
Counteroffer Processing The new InRule category is run once each Counteroffer is saved. It does NOT run during an Accept processing. This category allows users to run Counteroffer rules that can set fields on the Create Counteroffer screen.
Credit Bureau Selection Assigned to the Sub-Product on the Credit Bureau tab. This rule type is executed to determine which bureau to send the request to when pulling Credit.
Cross-sell Products Assigned to Sub-Product on the Cross-sell Products tab in Loan Application Types. This rule type is executed when loading the Cross-sell screen to determine what Cross-sell Products should be offered to the applicants.
Cross-sell Replacement Processing Automatically executed when loading the Cross-sell Products screen to determine what Cross-sell Products should be offered to the applicants. Where the institution decides the criteria for generating Replacement Cross-sells on the Cross-sell screen.
Cross-sell Replacement Selection Automatically executed when loading the Cross-sell Products screen to determine what Cross-sell Products should be offered to the applicants. Where the institution decides which of their Sub-Products they are going to use to replace specific Trade Types on the Credit Report.
Decisioning Assigned to Stages defined within Decision Models. Executed during the Decision Model process. The following functions are performed:
  • Aggregates are calculated.
  • Ratios are calculated.
  • Stipulation rules assigned to the Sub-Product are executed.
  • The first "stage" of the decision model is executed. Unless a stop processing action is returned, the next sequential stage of rules is executed.
  • If a Decision of Auto_Approved is assigned, Approval Processing is automatically executed.
  • If a Decision of Auto_Rejected is assigned, Rejection Processing is automatically executed.
The Decision category also provides institutions the ability to author rules that automatically disburse applications.
Default Values Assigned to Sub-Products on the Default Values tab in Loan Application Types. Executed during creation of new applications to set default values on the application.
Disbursement Automatically executed during Disbursement. Executed to set fields as needed for the Core Processor integration.
Document Generation Automatically executed after Document Selection rules during the Document Generation process. Executed to generate documents using third party connectors such as IMM or CUNA LoanLiner. Document Generation rules provide the ability to manipulate the data that is going out, change the data on an application, add custom fields, etc.
Document Processing Automatically executed as part of the Document Generation process. Executed to update or change fields on an application prior to creating documents. For example, to change the NMLS user to the user processing the application.
Document Selection Automatically executed during Document Processing. This rule type defines which documents should be created for the selected sub-product during Document Processing.
Editability Automatically executed during application processing. This rule type is used to refine User and Security Group editability permissions. When writing Editability rules, rule authors are able to refine editability to users and security groups.

ESignature Default Values

The information that can be automatically set within an ESignature Default Values rule, as well as the point at which the rule is executed, may differ depending on the ESignature connector implemented at the institution. For detailed information on authoring ESignature Default Values rules for a specific connector, please see the applicable connector guide.

Automatically executed when the screen for the ESignature connector is opened.

This rule type is used to assign default attributes for a template, such as the Email Subject and Email Body.
Event Processing Assigned to the Rules tab within an Event Processing pairing. This rule type is used to define conditions that stop an Event Processing Action from executing.
Fees

Assigned to Sub-Products on the Fees Tab in Loan Application Types.

 Executed when an application is created, when an application is decisioned, and as part of the Calculate process. 
Get New Member Account Automatically executed when the “Generate” button is clicked during Funding. Rules set the values to be sent to core for fields that are needed to create the new person record as part of the Core Processor integration.
Loan Officer Approval Limits Assigned to Sub-Product on the LOA Limits tab. This rule type is executed during manual approval processing to determine if the current user is authorized to approve the application or if an override is required. If the manual approval is authorized, a decision of LO_Approved is assigned and Approval Processing is automatically executed.
Pricing Assigned to Pricing Models. Executed during Pricing Model processing. Discounts and Premiums are added to a collection which are then totaled and applied as follows:
  • All discounts are totaled and compared to the maximum discount defined on the pricing model. The lower of the totals is used as the total discount for the application.
  • All premiums are totaled and compared to the maximum premium defined on the pricing model. The lower of the totals is used as the total premium for the application.
  • The total discount and total premium are applied to the base rate defined on the pricing model.
  • The minimum and maximum thresholds defined on the pricing model are enforced on the resulting interest rate.
Product Selection Executed via a call in the API when creating external applications. Executed if business rules are needed to determine for which Sub-Product the application should be created (i.e. CUDL applications).
If the external source is already setting the Sub-Product on the application, it is not be necessary to use this category of rules.
Queuing Automatically executed when creating a new application and when closing an application from the workspace, if the application is not pinned to its current queue. Executed to determine in which queue the application should be placed. An application can be assigned to a queue with or without pinning it to that queue.
Ratios All rules automatically executed during Risk, Pricing and Decision Models. Rules written in this category should be authored at the Applicant and Application entities. This ensures that the aggregates are calculated for each applicant and the entire application.
Risk Assigned to Risk Models. Executed during Risk Model processing, which is used to determine a Risk Tier for each applicant. Average, High, and Low risk tier values are automatically assigned to the application based on the risk tier assigned to each applicant. If a Risk Tier is not assigned to each applicant risk fail and the user is unable to proceed.
The most frequent cause of risk failing is the risk model being configured to look for scores that are not obtained from the credit report. Rules used to assign a risk tier for each applicant should be configured to look for scores for any active credit bureau.
Stipulations Assigned to Sub-Product on the Stipulations tab in Loan Application Types. Executed as part of Decision validation to determine what stipulations should automatically be required for Approval and Disbursement.
TradeProcessing Automatically executed during the Credit Reporting when the Tradelines (obtained from the credit reports) being used for the application are parsed and stored.

Rules written in this category should be authored at the Applicant.Liabilities collection to ensure proper execution across all liabilities. These rules are written to exclude liabilities (set IsExpense = False), calculate $0 payments using the balance and/or limit or modify the IsSecured value of a liability created from a credit report tradeline (set IsSecured = True/False).
Validation Assigned to screens and workflow model. Executed when a screen is saved or a specific process occurs (such as Decision, Document Processing, Disbursement and Decline) in the UI.                

 

 

©2018 Temenos Headquarters SA - all rights reserved.

Send Feedback