...
Table of Contents
Table of Contents | ||
---|---|---|
|
Introduction
...
There are two system sheets that you should not change the sheet name and column header in the sheet. These sheets are required and used by system to execute the rules:
Field Data Inputs sheet: defines input parameters. Row 1 is column header. From row 2, you need to define the data fields and corresponding converted input parameters.
Field Name column: Raw input parameter name or data field. It will tell which data (i.e. placeholders) is retrieved from available Seamless services.
Converted Parameter column: Define parameter name that will be used in the Rules spreadsheet.
Description column
Rule Declarations sheet: defines the rules and what is the rule’s decision table as well as output parameters. This sheet contains list of rules. Each rule is defined on each row.
Rule Name column: define any rule name.
Rule Inputs column: define parameter name for the rule. Pickup from column B in sheet "Field Data Inputs". If more than one input, use "," to separate.
Rule Sheet Name column: Define the name of sheet containing decision table to get the result based on a set of input values. Name can be whatever but you need to create a new sheet with this name.
Rule Outputs To Parameters column: Define output parameter name of the rule. Output can be any data type: string, Boolean, number… Examples: For promotion code: the output must be Boolean. For customer scoring: the output is number.
Decision table sheet: define the possible input values (conditions) and the output result. Mostly, we need to define all of the expected conditions with expected result, others will fall in default condition with default result. Row 1 is column header. Row 2 is to define what input parameter to be used to get value for condition check. $param will be replaced by the value of the same column and the following rows (from row 3).
Condition column: define the condition to check. If there are more than one condition, you need to add more Condition columns.
Action column: define the output result.
From row 3, you need to define all of the expected conditions with expected result.
To avoid listing unlimited conditions, you need to define the default condition. So if the input values don’t fall into expected conditions, it will fall in default condition with default result.
Condition values are case-sensitive. For ex: if the values 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 default result.
Constants sheet: If the case does not fall in any conditions in the decision table sheet "NewBusinesQuote", system will return the error (column C) and error message (column B). This is a default sheet, please do not change.
...