Conditions are a key component of Kianda rules. They are the triggers that result in fully dynamic forms and add an important level of interactivity, creating pathways within a process based on user interaction.
Conditions work on the ‘if…then…else’ principle: ‘if’ the condition exists ’then’ an action happens, ’else’ another action happens. There are three parts to applying a condition to a rule (depending on the rule that is used):
- Create the condition(s)
- Create the action(s) that will be applied as a result of the first condition being in place
- Create the otherwise action(s) based on other conditions being in place
For example, let’s take a simple Training Request and Approval Process, whereby an employee fills out a request form, the details of which are sent to a manager for review in an approval form. In this approval form, the manager can either a) approve the request with a signature or b) not approve the request and provide feedback on why.
Training Process flowchart
A condition is created based on the Manager Decision radio list:
- Condition: If the decision is ‘Yes’
- Action: Then the Signature button appears
- Otherwise action: Else the decision is ‘No’ and the Feedback text box appears
One of the most commonly used rules that uses conditions is the Workflow rule Hide or Disable. This is used as an example in the video and in the Getting started section below.
Using conditions in rules: Example of Hide or disable
Getting started with conditions
Conditions are recognisable in Kianda from the Conditions button found in rules and dashboards.
To create a condition:
- Select a form or forms, field or fields and then, a rule, for example Hide or disable, as found in the left side menu > Add a rule > Workflow > Hide or Disable.
- Click on Edit conditions.
- Click on Add a conditions group.
- In the Edit conditions dialog box, choose from the elements below, by drilling down to the form(s) or field(s) that you want to apply the rule to.
In the case of multiple conditions, you can use And or Or to create compound conditions.
- Click on OK.
- Create the actions and, where applicable, otherwise actions. The action will depend on the rule that is chosen. For example, for the Workflow rule, Hide or Disable, click on the field under Action and choose the form(s) or field(s) where you want an action applied.
Action elements for Hide and Disable
Then click on the field for actions and choose one of seven possible actions to apply.
The actions within Hide or disable are:
a) Hide will hide a process element (forms or fields) from view
b) Show will show the element
c) Disable blocks a user from editing an element
d) Enable allows a user to add a value to an element
e) Toggle visible will toggle between showing an element or not, based on subsequent clicks of a field that the rule is applied to
f) Toggle enable will toggle between allowing an element to be edited or not, based on subsequent clicks of a field that the rule is applied to
g) Hide and clear will allow you to hide a process element and clear the details. For example, if a toggle button has this rule applied, with an otherwise action of show as actions on a textbox, then if one value is chosen on the toggle button, the user is allowed enter details into the textbox, otherwise the field is hidden and cleared of data so that no data can be retrieved; this may be useful for sensitive information like a social security number on a form.
Click on + Add to add more actions.
Click on Add otherwise action to add more actions based on other values for the condition.
The video demonstrates how a condition works within the Hide and Disable rule and highlights that multiple groups of conditions can be used to impact multiple actions to create highly sophisticated form interactions.
You can use rules to create actions without conditions too. In this case, the rule will simply execute - for example, when the form or field is clicked on.
To learn more about controls (fields) go to Controls.
To find out more about how expressions are used in rules go to Expressions.
To return to the previous pages click on the links below
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.