10,854
edits
Salesforce admins: Urgent action required!
Rules editor: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
Various rules can be defined for each of the [[user interface components]], such as [[form]] or [[view]]. They are edited in [[Woodford]]. | Various rules can be defined for each of the [[user interface components]], such as [[form]] or [[view]]. They are edited in [[Woodford]]. | ||
== Actions that trigger rule execution == | |||
When you edit a UI component in [[Woodford]], you can define actions that trigger rule execution. | When you edit a UI component in [[Woodford]], you can define actions that trigger rule execution. | ||
| Line 122: | Line 124: | ||
; Export XML, Import XML: Rules can be exported and reused in a different location in the project or in a different project. | ; Export XML, Import XML: Rules can be exported and reused in a different location in the project or in a different project. | ||
== Building a step == | |||
Each rule consists of steps. Every type of step can be described as an expression with usually three parts (from left to right): | |||
* '''Variable''' - usually this is the thing that we're about to modify in this step | |||
* '''Operation''' - this is the operation, comparison or function that we perform | |||
* '''Argument(s)''' (optional) - parameters of the function | |||
the left side that we will refer as variable, right side which we will refer as argument and an operation (like function or comparison) between them. We can create these types of steps Function Step, Condition step and Variable step. | |||
== | === Operations === | ||
Each variable data type will have different set of functions. See the table for details. | Each variable data type will have different set of functions. See the table for details. | ||