Temenos Lifecycle Management Suite - Account Origination Product Guide
Rules Management - Tips and Tricks
| Administrator Guide > Rules Management > Rules Management - Tips and Tricks |
This topic includes the following tips and tricks for creating Business Rules:
To remove the Rules Management application, navigate to windows explorer and enter the following path into the address bar: C:\Users\user name (John Doe: Jdoe)\AppData\Local\Apps\2.0. Delete the folders within this location.
 |
The next time Rules Management is launched, it must be installed. |
If two rules are configured to change the same field and are being run at the same point in processing, an infinite loop occurs. To avoid this, put all rule logic to set the field into one rule.
After selecting a [value], press the right arrow on your keyboard to highlight the selection and display the caret extender (^). Select the enter key to display the list of value options.
To define a value for a field, select from a list of lookup values. After a field is selected, click the … to display a list of available fields to add to the expression. Enter has a value of or does not have a value of within the top of the drop-down list:
A placeholder for [list value] appears. Click [list value] to select the appropriate lookup value from the Value list that displays:
When setting the value of a lookup field using the set the value of a field action template, enter value within the top of the list drop-down and select value from list to select a value from the field’s lookup list.
To undo or add to a selection, right click on the selected item and choose an edit option from the list that displays:
 |
When deleting a field, expression, etc., all additional criteria after the deleted item is also removed. |
To modify the rule type selected, click the "If" at the top of the rule being authored.
Changing the type of rule determines whether or not the existing criteria is retained or deleted. For example:
When using templates, all placeholders MUST be completed or a compile error is returned when saving the rule or decision table.
When using the display a message templates, it is possible to combine fields, text, and line breaks by using the concatenate function. This function concatenates all of the values passed to it into a single string that is displayed in the message. Use the following example to understand how to use the concatenate function within the display an informational message template:
 |
To insert a line break, include <BR> within the expression. |
|
An unlimited number of values can be included in the expression. |
|
When using the concatenate function, include a space before the first letter of the text in order to separate the text from the concatenated value. Without a space added, the concatenated values and text are combined. |
When building If/Then type rules in Business Language that require the placement of parenthesis, it is recommended to use one of the following Conditional Expressions:
Conditional Expressions can be nested and should be used instead of parenthesis to handle precedence. They can also be used in conjunction with logical operators (and/or).
When using the action template set the value of a field, use Expression Builder to add complex values to the expression. Use the following example to assist with accessing and using Expression Builder.
e
Expression Builder can also be used to populate a NULL value for a field using the steps below:
Through Business Language Editor, a date can be converted to string format by using the format function. Select a format option such as Long date or Short date or enter a custom date/time format.
If desired, system administrators can author an Event Processing rule to modify the case of field values in an application. For example, when an application is submitted from a third party, field values may be converted from upper and lower case to all upper case in the application. Using the "convert" action in a rule, institutions are able to set the value of certain fields to a specific case during the application process.
Watch the following video to assist with authoring an Event Processing rule that sets field values to a desired case during the application process:
|
There are many ways to author a rule; therefore, the following rule should be used as an example ONLY. |
When creating a rule, do not configure a rule name that is identical to the name of a field being used within the rule. Rules under the same entity must also be named differently in order to save the Rule Application. If this field is the same for more than one rule under the same entity, an error message is received when trying to save the Rule Application.
In the Core System, the ID Number and ID Issuing State may be stored in the same field (e.g.: 123456/CA). However, this data is stored in two fields in the Origination module, and the Issuing State should not populate with the IDNumber field.
To remove the last three characters of a field value, use a regular expression replacement. This only removes the last three characters if it matches a slash, then two characters (upper or lower case).
When you need to manually move a parenthesis, and switching and editing in Syntax mode does not fix it or does not allow it, follow these steps:
When using templates that get a score/aggregate/ratio for an application or applicant, the template returns a value of “-1” if the score/aggregate/ratio does not exist. The following condition tests to True if the Low BEACON Score does not exist:
To prevent this type of unexpected result, the rule must be authored as shown below in order to account for missing collection members:
Temenos Infinity restricts the addition of more than one review indicator with the same name to an application. Therefore, Temenos recommends writing rules only from the Application entity when determining if a Review Indicator should be added.
spacer_81291c7b-8529-4286-926f-30e2a7134af4