Adding security and display conditions
Adding conditions to your widget layout is essentially adding the trigger conditions that determine if the widget displays.
Primary condition
This procedure continues from the previous steps, from an open Widget Layout Details form.
To set conditions:
1. | Open a widget layout. The Widget Layout Details form opens. |
2. | To set conditions on your widget layout, click Set Conditions. The Execution Trigger Detail form opens. |
Area | Function |
---|---|
1. Primary Condition | The primary condition must be met before all other conditions are evaluated. Primary Conditions are not required, but if present they must be satisfied. |
2. Add Additional Conditions |
Additional conditions allow you to configure complex display conditions, which when combined with the weighting system provides the ability to create complex trigger conditions when used in an expression. When adding Additional Conditions, you will have a Label field to complete. The Label value is used when constructing Expressions. |
3. Expression |
As conditions (other than the primary) are added, they act as an OR condition. For example, adding three additional conditions without an expression would mean: If 'This' or 'That' or 'The Other Thing' – then display the widget. Expressions can be used to create more complex conditions under which the widget will display. Example: "('This' AND 'That') OR 'The Other Thing'" For an extensive discussion about conditions, see the topic Condition expressions. |
Departments and Security Entities
Departmental and Security Entity Conditions work in a similar fashion.
1. | From the open widget layout, in the Execution Trigger Detail form, select Department or Security Entity. The Trigger Condition form opens. |
2. | Departmental and Security Entity Conditions work in a similar fashion. For type Department or Security Entity select the associated value. These are always an Equals condition. |
Trigger Condition | Options |
---|---|
Department | Select the user's Default department as selected on the user profile. If a Department trigger is set, the user must be in that department to satisfy the condition. |
SecurityEntity | Select a Security Entity associated with a role in which the user is a member. If an Entity trigger is set, the user must be in a role with at least View access to that Entity. |
Expression
When adding additional conditions, the Expression field is exposed. The option is used when building condition expressions.
Field Value Expressions
Commonly used in Workflow, Field Value Expressions are the most robust of the trigger conditions.
Field | Description |
---|---|
Type | When FieldValueExpression is selected as the type, additional fields display to allow configuration of the source dataform and associated elements. |
Source | Select the Dataform that determines the triggering condition. |
Trigger Field | Select the trigger field from the Source dataform. |
Operator |
Select the logical operator:
The operators are field specific. If the Trigger field selected is a Text field, numerical operators will not be available. |
Trigger Value |
Trigger Value is the value to the right of the operator in the equation. The trigger value determines whether the condition is met. For example: Pricing State Source | State Field | Equals Operator | "FL" Trigger Value means "If the Pricing State, State field Equals Florida." |
Expression Label (option) | When adding additional conditions, the Expression Label field is exposed. This is used when building condition expressions. |
Condition Expression: Bringing it all together
After additional conditions have been configured with labels, you can use these labels to build complex Condition Expressions.
In the Dataform header widget example:
• | The Primary condition is the Number Of Stories field, which must be greater than 2. |
• | If this primary condition is met, the system then analyzes the Additional Conditions using the Condition Expression. This condition expression is built using the Expression labels on the additional conditions and applying the appropriate logic. In the example, this would be: |
• | EITHER (the Owner Occupied field = 'Yes' AND (the Property State field equals 'GA' OR 'AL')) |
• | OR (the User has at least view rights to the biz_RequestTypeCategory_Environmental entity AND (Number of Stories field is Greater than 5 AND the Property State field equals 'AZ')) |
In this way, very complex trigger conditions can be built to display or hide the appropriate Widgets.