0

Creating conditions and results

 Creating a condition

To evaluate input values, it is necessary to create conditions. Click the Add button (+) beside Conditions to create a condition and enter the standard details. You can also set validations on what values should be entered in the conditions. 

 

 

After creating the condition, you can start entering the condition values in the rows. 

Choosing operators

To evaluate the condition values, you have the option to choose the type of operation that best suits your needs. If you need to evaluate condition values within a specific range, click Range and choose the lower and upper limit operators. If you need to evaluate with only one operator, choose Single.

 

Example:

Let’s say you’re managing a decision table for loan approval.

If you want to evaluate the applicants' credit scores within a specific range (for example, 600 to 800), you can choose Range and select the lower limit operator (> or >=) for 600 and the upper limit operator (< or <=) for 800. 

If you are using a single criterion, such as a minimum credit score of 700, choose Single and pick the operator (> or >=) for 700.

 

 

Creating a result

Click the Add button (+) beside Results to create a result and enter the standard details. You can also set validations on what values should be entered in the results. 

 

 

After creating the result, you can start entering the result values for the corresponding conditions, including the default condition.

Note:

A minimum of one result row will always be present, corresponding to the default condition.

FAQ

1. Can I edit a decision table inside a deployed app when someone is already editing it?

If you have access to the decision table, you can take over the editing from that person and edit only the values in the decision table. The changes made by the other person will be auto-saved, and they will be restricted from further editing until you’re done with your editing.

Only one person can edit a decision table at a time.

2. Can I edit a decision table inside an app’s development environment when someone is already editing it?

If you’re a developer in the app, you can take over the editing from that person and edit the conditions and results in the decision table. The changes made by the other person will be auto-saved, and they will be restricted from further editing until you’re done with your editing.