Using a User-Defined Variable

After you have named your user-defined variable (UDV) and assigned a value (populated it), you are ready to use it in a Decision Ruleset rule.

You do this by referencing the name you gave it and prefix it with the UDV type ACCT_UDV, CUST_UDV, or SRVC_UDV:

• ACCT_UDV (prefix for UDV names created in an Account UDV Management ruleset so that a name called CardRange is entered as ACCT_UDVCardRange)
• CUST_UDV (prefix for UDV names created in a Customer UDV Management ruleset so that a name called BostonCount is entered as CUST_UDVBostonCount)
• SRVC_UDV (prefix for UDV names created in a Service UDV Management ruleset so that a name called Cash_TXN_Count is entered as SRVC_UDVCash_TXN_Count)

For example, you have been asked to collect the sum-total of all cash transactions that occur in a single day. If the total of these transactions exceeds $500, then you want to decline subsequent transactions for that day and create a case.

In order to decline and create a case, a rule must be created in a Decision Ruleset to check the value in your UDV against the number 500.

Behavior Flag

When you need to identify a section of your portfolio specific characteristics, you can set a flag to identify these customers or cards. The most common behavior flag is identifying VIP accounts. The behavior flag can be set as a string or integer type. Below are samples of both.

//Integer UDV indicates that the account is a VIP. 
if 
  (
  condition
  )
then 
  {
  ACCT_UDVVIP_Ind = 1 ;
  }

In the previous example, the UDV is set to one when the conditions are met. In the below example, the same is occurring. The difference is the data type or the UDV. You must create the Integer UDVs in the Integer UDV Management ruleset. String UDVs are created in the String UDV Management ruleset.

 //String UDV indicates that the account is a VIP. 
if 
   (
   condition
   )
then 
   {
   ACCT_UDVVIP_Ind2 = "Y" ;
   }