Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Field Data Inputs sheet:

    1. There are 2 input parameters defined: quoteBusinessFlow and quoteProductName.

    2. The data field of those 2 input parameters are quote.businessFlow and quote.productName respectively. These data field name are fixed (defined by Seamless services, please do not change).

  2. Rule Declarations sheet:

    1. There is one rule which has 2 input parameters: quoteBusinessFlow and quoteProductName (they are defined in sheet Field Data Inputs).

    2. And 1 output parameter, named “is_valid” (this means “Promotion code is valid or not).

    3. “NewBusinessQuote” is the sheet name where contains decision table to get the result based on a set of input values from 2 input parameters quoteBusinessFlow and quoteProductName. So you will see a sheet “NewBusinessQuote” next to.

  3. NewBusinessQuote sheet:

    1. There are two conditions to check: one condition on quoteBusinessFlow. The expected values are “NewBusiness” or “Renewal” (These values are understood by the Seamless services).

    2. And another condition on quoteProductName. The expected value is “Travel” (Please use the correct name defined in Product Builder).

    3. From row 3, you need to list all of the conditions that the output result is_valid should be TRUE. So here are 2 valid combinations {“New Business”, “Travel”} and {“Renewal”, “Travel”), which is_valid = TRUE. And others will fall in default condition, hence is_valid = FALSE.

    4. Condition values are case-sensitive. For ex: the value in rule sheet is defined as “Renewal”, when user provides “renewal” as the input for the rule, system will not recognize it and it will fall in default condition with is_valid = FALSE.

Example 2

Define a rule to check when creating a new claim, Date of Loss should be not in the future or outside the policy effective period.

If Date of Loss is in the future or outside the policy effective period, it will return a validation message.

Example file:

View file
nameClaimCreationValidation_Version 9.xlsx

Example 3

Define a rule to check when creating a new claim reserve, the new total reserve amount of the cover in one claim should not exceed the policy’s cover limit.

If the new total reserve amount of the cover in one claim exceeds the policy’s cover limit, it will return the validation message “Total reserve amount of cover is greater than cover limit.”

Example file:

View file
nameClaimReserveValidation_Version 2.xlsx

Example 4

Define a rule to check when creating a new claim payment, the new total payment amount should not exceed total reserve amount of the same cover, damage/injury type, cause type, payment code in one claim.

If new total payment amount exceeds total reserve amount of the same cover, damage/injury type, cause type, payment code in one claim, it will return the validation message “Total payment amount is greater than the corresponding total reserve amount.”

Example file:

View file
nameClaimPaymentValidation_Version 2.xlsx

Example 5

Define a rule to check when creating a new claim recovery received, the new total recovery received amount should not exceed total recovery amount of the same cover, damage/injury type, cause type, payment code in one claim.

If new total recovery received amount exceeds total recovery amount of the same cover, damage/injury type, cause type, payment code in one claim, it will return the validation message “Total recovery received amount is greater than the corresponding total recovery amount.”

Example file:

View file
nameClaimRecoveryReceivedValidation_Version 3.xlsx