Rule Engine

in docid\ chwdkcrrh anazqjweaw9 , the rule engine provides a way to add a direction to the onboarding flow as a way of incorporating certain evaluation checks, it can also add customizable conditions and rules to the flow a rule is generally composed of multiple conditions tied together by a logical operator create rules 1 choose a flow choose a docid\ aqagtpv2vzxenbxphahku from the available list 2\ select a screen select a docid\ xsd0meic4aadzddtkedsy from the flow to add rules/conditions 3\ add conditions on selecting a particular page, the first step in creating rules is to add conditions generic onboarding currently provides 3 types of conditions a no conditions on selecting this type, you only have to provide the destination screen b logical conditions on selecting this type, you must create a condition with the following fields variable operator value c docid\ stbktrocpf 1c5 xe5ugc on selecting this type, we must first select the api from the api list, and then map all the api input variables to the corresponding page variables lastly, you must create a condition with the following fields variable operator value 4\ add rules once the required conditions are created, you can create a rule by combining conditions with various logical operators you also have to specify the destination on true/false role of rule engine rule engine enables us to connects or unifies all the pages of a particular flow defines the navigation to be followed throughout the process define conditions and rules that will drive set navigation components of rule engine a rule engine consists primarily of conditions and rules conditions are defined and weaved together using rules, which ultimately define the navigation to be followed across pages conditions conditions are the parameters/constraints that will drive the navigation condition lays the foundation to define rules conditions can be either logical based implies definition using various variables available in pages tied with logical operators it also enables the performing of logical comparisons/computations as well api based implies the definition of variables that are linked to a certain api and tied with operators aids inputting various types of checks as well in place no conditions on selecting this type, you only have to provide the destination screen rules various types of logic operators can weave various conditions together to form different types of navigation a rule is the result of the assignment of conditions that result in a defined type of navigation the ultimate driver of navigation is determined by the output of the conditions associated with the rule (true/false/uncertain) as an example, if "condition 1" is true then go to page 2, if it's false then go to page 3 note in the rule engine, we choose the operator ‘all’ if there is only one condition and ‘any’ if there are multiple conditions getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at