Contents x
Rules Step Glossary
  • 24 Jun 2022
  • 5 Minutes to read
  • Print
  • Dark
    Light
Contents

Rules Step Glossary

  • Updated on 24 Jun 2022
  • 5 Minutes to read
  • Print
  • Dark
    Light
Article Summary

Overview 

The following article details all steps found in the Rules category in the Step Toolbox.


Step NameDescriptionLocation Inputs/Outputs
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. Users configure Input and Output data within the Truth Table Editor via the Edit (pencil) button. Different evaluation criteria are added to the Table in each corresponding cell within a row. Data may be manually input or populated from a Report. 


Designer Entities > Rules		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. To edit the Rule, select the Edit button under Rule Id in the Properties panel for the step. The Rule itself is simply configured as a user would configure a standard Rule in Decisions.


Designer Entities > Rules		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. Running a Matrix Rule produces an outcome from a column value and produces another column, and an outcome from a row produces another row.


Designer Entities > Rules		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. To create a Rule Chain, users must define an Input for the Rules and then connect those Inputs to the added Rule. 


Designer Entities > Rules		Inputs:
Depends on the Flow

Outputs:
Not Supplied Inputs (List of DataDescription)
Run RuleThe standard Run Rule step that allows a user to select a specific Rule that they want to add to a Flow.
Designer Entities > Rules		Inputs:
Depends on the Flow

Outputs:
Depends on the Flow
Date After TodayA Rule typically used for scheduling times; determines if the specified date is after the current date.
Designer Entities > Rules		Inputs:
Date Value (DateTime)

Outputs:
True/False (Boolean)
Add Task Date Before TodayA Rule typically used for scheduling times; determines if the specified date is before the current date.
Designer Entities > Rules		Inputs:
Date Value (DateTime)

Outputs:
True/False (Boolean)
Text ContainsChecks if a String Value contains the specified String of text.
Designer Entities > Rules		Inputs:
Contains String (String), String Value (String)

Outputs:
True/False (Boolean)
Number Greater ThanDetermines if the Test Value is greater than the Number To Check.
Designer Entities > Rules		Inputs:
Number To Check (Decimal), Test Value (Decimal)

Outputs:
True/False (Boolean)
Is Valid EmailChecks if an email is valid and returns a True/False value.
Designer Entities > Rules		Inputs:
Text To Check (String)

Outputs:
True/False (Boolean) 
Pick or Create Matrix RuleThe [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. Users may also Capture the Rule's audit history via the Capture Audit History boolean. 
Designer Entities > Rules		Inputs:
Depends on the Rule

Outputs:
Depends on the Rule
Pick or Create RuleThe strong 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 from a pre-built rules in the Step Toolbox, or create their own via the Rule Editor. Additionally, the Rule Editor may be used to edit pre-existing Rules for specific cases. 
Designer Entities > Rules		Inputs:
Depends on the Rule

Outputs:
Depends on the Rule
Pick or Create Truth TableThe [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. The step also offers additional options to use Runtime Selection or the Champion Challenger with the Truth Table, via the Selection dropdown menu. 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. The step also offers additional options to use Runtime Selection or the Champion Challenger with the Truth Table, via the Selection dropdown menu.

Designer Entities > Rules		Inputs:
Depends on the Rule

Outputs:
Depends on the Rule
Is App SelectedDetermines if the correct App is selected by using the App Id and the App Store Id.
Designer Entities > Rules > System Defaults > App Store
Inputs:
App Id, App Store Id

Outputs:
None
Text Longer ThanChecks if the text is longer than the specified amount and returns a boolean true/false response.
Designer Entities > Rules > System Defaults > Default Form Validation Rules
Inputs:
Length, Text Value.

Outputs:
None
Text Shorter ThanChecks if the text is shorter than the specified amount and returns a boolean true/false response.
Designer Entities > Rules > System Defaults > Default Form Validation Rules
Inputs:
Length, Text Value.

Outputs:
None
Number Less ThanChecks if the number is smaller than the specified amount and returns a boolean true/false response.
Designer Entities > Rules > System Defaults > Default Form Validation Rules
Inputs:
Number to Check, Test Value

Outputs:
None
Date Today or Before TodayCompares the input date to the date specified in the step.
Designer Entities > Rules > System Defaults > Default Form Validation Rules
Inputs:
Date Value

Outputs:
None
Date Before TodayDetermines if the input date is before the current date.
Designer Entities > Rules > System Defaults > Default Form Validation Rules
Inputs:
Date Value

Outputs:
None
Value Is FalseDetermines if the input value matches the specified value. 
Designer Entities > Rules > System Defaults > Default Form Validation Rules		Inputs:
Value

Outputs:
None
Was this article helpful?
What's Next
Decisions
Resources
Organization
Connect