Automating Decisions

Question 1

From where can be a decision rule invoked?

Answer 1

1 . a decision shape in the flow
We use flows in case processing to determine which path the case goes down. Using decision rules in our flows automates the case processing. For example, a decision table can decide if the case requires approval from another manager or if it can move to the next step in the business process.

2. using a declare expression
   Declare expressions can use decision trees or decision tables to get a specific value based on a set of conditions. For example, if the customer lives in Massachusetts, has a credit score above 720, and is paying at least 20% as a down payment, then the APR for the car loan is 1.7%.
3. using a method in an activity step
   Decision trees are used in activities when we want the activity to decide whom to route the case to or what the escalation activity on the SLA should perform.

Question 2

Decision rule types?

Answer 2

There are four types of decision rules that we can write to evaluate decisions: 
	• When
	• Decision trees
	• Decision tables
	• Map Value

Question 3

Decision Tree’s Features?

Answer 3

• applying the If- Then- Else construct
• can have many branches which evaluate different properties to determine a decision
• can use a direct expression, a function rules or when rules for building the condition.
• allows nesting, which means it can invoke another decision tree or other decision rules such as a decision table or a map value.

Question 4

When Rule’s Features?

Answer 4

• they can return only one of two values – True or False. - to decide which one of the two paths the case can take
• used in other rules like UI, data transforms, other decisioning rules and declare expressions to evaluate a condition.
• can use a Boolean expression
• can use a function rule part of the library shipped in the product
• can use a custom function defined as part of the application.
• can involve any number of conditions and can be combined using AND, OR & NOT.

Question 5

Decision Table’s features?

Answer 5

• presenting the set of conditions using a tabular structure
• very user friendly to for managers (resembles a spreadsheet)
• best option if we are using a smaller number of unique properties to evaluate the decisions.
• give us the option to evaluate all rows to arrive at a decision
• let us increment values on the specified condition which is useful in implementing scoring.
• can invoke another decision table
• each property gets a column
• rows added in a way that each of these columns have values (most likely)
• columns can use properties for specifying a set of conditions
• The property can be compared against a single value like or a range.
• cells can be split to represent OR
• can return values
• can set property as return (after enabling property set)
• could return more than a single property

Question 6

Map Value’s feature?

Answer 6

• let us determine a specific value based on one to two properties
• used in special circumstances where we the values of one to two factors decide the outcome. (e.g. interest rates for bank accounts and customer types)
• map values can be chained to other map values as well if we need to use more than two properties to determine the outcome.

Question 7

Available actions for a Decision Tree?

Answer 7

Actions:

• return: usually return a value, these values can then be used in the calling rule such as the declare expression or the flow.
• evaluate: check values on a specific property and decide its course of action. (property is specified on the Input tab)
• continue: is used to check additional conditions
• otherwise: is always used as an else condition
• take action: can also be configured to set a value to properties and this can be done using the Take Action option in the menu.
• call Decision Tree
• call Map Value
• call Decision Table

Question 8

Decision Tree usage restrictions (for business user)?

Answer 8

• Allowed return values (property or listed values)

Checkboxes:

• Allowed to Change Functions (+ Allowed functions (list))
• Allowed to Add Nodes
• Allowed to Evaluate Properties
• Allosed to Call Decision
• Allowed to take Actions (+ Allowed actions (list))

Question 9

How “Evaluate all rows” option works on a Decision table?

Answer 9

Evaluate all rows - continues evaluating other conditions even if one condition is satisfied. Cannot return values and hence we cannot execute the decision rule.

Question 10

Decision Table usage restrictions (for business user)?

Answer 10

Allowed results (property, list)
Checkboxes:
- Allowed to update row layout
- Allowed to update column layout
- Allowed to change property sets
- Allowed to build expressions
- Allowed to return values

Question 11

Available checks?

Answer 11

Check for Consistency - verifies that there are not any unreachable paths in the rule and that there are no logic conflicts
Check for Completeness - populates all values that are part of otherwise, giving us an opportunity to review and maybe add logic for those conditions. Completeness is just a suggestion by PRPC and we need not always use it.

The rules can be tested by using the Run option in Actions menu.