To deliver a code-free environment where projects can be created and deployed quickly, appRules employs “Sourced Values”. In simple terms, a Sourced Value allows you to quickly select a source for a value and an identifier for it. To specify a sourced value, you select the Source and then specify a value identifier (Source Value Identifier). Below are some examples of the many sourced values used in appRules:
| Source | Value Identifier |
|---|---|
The above examples give you an idea of how Sourced Values are defined and used in appRules. They can be used to get and set data anywhere in your projects.
By providing a rich set of editors to manage Sourced Values, appRules is able to provide a very powerful and flexible combination that gives users the fastest and most compact environment for configuring workflow activities, actions, conditions, and orchestrating processes.
Below is an example of Sourced Values used for configuring a query:
The example below shows Sourced Values in use for mapping.
String
The String source allows you to enter any value in the value identifier.
Example:
String:John Smith
DataFieldValue
The DataFieldValue source gets a value from a record that exists in a specific Source or Target in the project.
Example:
DataFieldValue:Employees.LastName
Gets the value of the LastName column in the Employees record.
DateTime
The DateTime sourced value points to a date/time related value. They can also be used to specify other date/time related data. Example:
DateTime:DateTimeNow
Generates the current date/time.
ActionField
The ActionField source allows you to select an action that you have defined using the Action Editor to get a value.
