Overview
The following article details all steps found in the Designer Entities -> Rules category in the Step Toolbox.
| Location | Step Name | Description | Inputs/Outputs |
|---|---|---|---|
| Designer Entities > Rules | Run Truth Table | The Run Truth Table step is used to add a Truth Table to a Flow in Decisions. Truth Tables are used to compare possible Input combinations to reach different outcomes based on the combination of values. | Inputs: Depends on the Flow Outputs: Depends on the Flow |
| Flow Aware Rule | The Flow Aware Rule Step is used to create and use a Flow Aware Rule for use in a Decisions Workflow. Flow Aware Rules are rules that do not allow the user to define Inputs as they by default take in all data from the Flow. This allows users to build Flows and utilize Rules quicker and more efficiently. | Inputs: Depends on the Flow Outputs: Depends on the Flow | |
| Run Matrix Rule | The Run Matrix Rule step is used to implement a Matrix Rule into a Decisions Workflow. Matrix Rules are designed to evaluate data based on configured settings for each column or row. This allows users the ability to nest rule evaluations within each row or column. | Inputs: Depends on the Flow Outputs: Depends on the Flow | |
| Run Rule Chain | The Run Rule Chain step is used to utilize Rule Chains within a Flow in Decisions. Rule Chains allow users to sequence logic and utilize the results from an earlier Rule in one later along the chain. Rule Chains utilize typical Decisions Rule logic and allow users to utilize Matrix Rules, Statement Rules, True False Rules, and Truth Tables within the build. | Inputs: Depends on the Flow Outputs: Not Supplied Inputs (List of DataDescription) | |
| Run Rule | The Run Rule step is used to add and use Rules in a Flow. Rule Steps can be setup to reflect real business rules typically contain two outcomes; typically, a true or false value. The step allows users to either select rules in the Step Toolbox, or create their own. | Inputs: Depends on the Flow Outputs: Depends on the Flow | |
| Pick or Create Matrix Rule | The [Pick or Create Matrix Rule] step is used to add a Matrix Rule to a Flow in Decisions. Users Pick or Create the rule based on the corresponding button. This offers the additional options of Runtime Selection or running the rule using the Champion Challenger via the Selection Type drop down. | Inputs: Depends on the Rule Outputs: Depends on the Rule | |
| Pick or Create Rule | The [Pick or Create Rule] step is used to add and use Rules in a Flow. Rule Steps can be setup to reflect real business rules typically contain two outcomes; typically, a true or false value. The step allows users to either select from a pre-built rules in the Step Toolbox, or create their own via the Rule Editor. | Inputs: Depends on the Rule Outputs: Depends on the Rule | |
| Pick or Create Truth Table | The [Pick or Create Truth Table] step is used to select or make a Truth Table, and add it to a Flow in Decisions. This step allows users to utilize Truth Tables to evaluate possible outcomes based on different combinations of Input data. | Inputs: Depends on the Rule Outputs: Depends on the Rule | |
| Parse Bool | The Parse Bool rule converts a string value and casts this value as an object. The Rule accepts only Y, N, T, F, True, False, Yes, and No as valid inputs. The step is case insensitive. | Inputs: ToString (String) Outputs: Output (Object) | |
| Random Rule | The Random Rule generates a true/false boolean value at random with a percentage input to alter the odds of the value evaluating true. | Inputs: Percent True (Int32) Outputs: True/False (Boolean) | |
| Sampling Rule | The Sampling Rule generates a true/false boolean value at random with a percentage input to alter the odds of the value evaluating true. The Rule also inputs a String value which can be used as a way to evenly distribute the outcome paths for a set size. | Inputs: Percent True (Int32) Sample Key (String Outputs: True/False (Boolean) | |
| Rules > System Defaults > App Store | Is App Selected | The step determines if the App is selected by using the App Id and the App Store Id. | Inputs: App Id (String) App Store Id (String) Outputs: None |
Rules > System Defaults > Default Form Validation Rules | Date After Today | A Rule typically used for scheduling times; evaluates as True if an inputted date is after the current date. | Inputs: Date Value (DateTime) Outputs: True/False (Boolean) |
| Text Contains | Checks if a String Value contains the specified string of text. | Inputs: Contains String (String) String Value (String) Outputs: True/False (Boolean) | |
| Date Today or After | Compares the inputted date to the current date. The Rule will evaluate as True if the inputted date occurs on or after the current date | Inputs: date Value (DateTime) Outputs: True/False (Boolean) | |
| Number Greater Than | Determines if the Test Value is greater than the Number To Check. | Inputs: Number To Check (Decimal) Test Value (Decimal) Outputs: True/False (Boolean) | |
| Is Valid Email | Checks if an email is valid and returns a True/False value. | Inputs: Text To Check (String) Outputs: True/False (Boolean) | |
| Text Longer Than | Checks if the text is longer than the specified amount and returns a boolean true/false response. | Inputs: Length (Int32) Text Value (String) Outputs: None | |
| Text Shorter Than | Checks if the text is shorter than the specified amount and returns a boolean true/false response. | Inputs: Length (Int32) Text Value (String) Outputs: None | |
| Number Less Than | Checks if the number is smaller than the specified amount and returns a boolean true/false response. | Inputs: Number to Check (Int32) Test Value (String) Outputs: None | |
| Date Today or Before Today | Compares the input date to the date specified in the step. | Inputs: Date Value Outputs: None | |
| Date Before Today | Determines if the input date is before the current date. | Inputs: Date Value Outputs: None | |
| Value Is False | Determines if the input value matches the specified value. | Inputs: Value (Boolean) Outputs: None | |
| Value Is True | Determines if the inputted boolean value is true | Inputs: Value (Boolean) Outputs: None | |
| Rules > System Defaults > Assignments | Any Assignment Late or Warning | Determines if any assignment in a list has reached a Late or Warning state | Inputs: Assignments [List of Assignments] Outputs: None |
| Has Date Passed | Determines if the specified month for an inputted date has passed | Inputs: Date String (String) Date Value (DateTime) Month (Int32) Outputs: None |