Home → Using LincDoc 3.1+ → DANG Rule Wizard → Creating and Editing Custom Conditions
10.2. Creating and Editing Custom Conditions
Custom conditions are user-configured Boolean (true or false) expressions that drive system behavior. A condition statement or clause may be singular or may be evaluated in conjunction with other clauses using AND (All of the following) or OR (Any of the following) to create more complex expressions.
Creating a Custom Condition
You create a custom condition using the Edit condition dialog box.
Important: Although this procedure is written from the standpoint of using the Fields/Sections tab on the Admin dialog box, it also applies to conditions created throughout the LincDoc interface, starting with step 3 below.
- Verify that you are viewing the Fields/Sections tab on the Admin dialog box.
- For any condition option (such as Condition to display, Required, or Read only), click the arrow button to the right of the option.
Note: You need to click the advanced check box to see some of these options.
- Select new condition from the list of displayed options.
The Edit condition dialog box appears, and the currently selected form field is highlighted in the Name text box. - Determine the type of editing mode that you want to use. The following options are available:
- normal mode. This mode is the default option (shown above) and provides a simplified interface for creating conditions.
- advanced mode. This mode allows you to specify advanced calculations. You can access it by clicking the advanced button.
Creating a Condition Using the Normal Editing Mode
You can create a condition using normal mode, which provides a simplified interface.
- Verify that you are viewing the normal (default) mode as described in the procedure above.
- Specify a name for the condition in the Name text box.
Each condition must have a unique name. Once the condition is defined it is available throughout the eForm or Document Package's condition lists. - Determine the condition's dependency using the All or Any options:
- All of the following. The condition is only satisfied if all of the defined clauses are met.
- Any of the following. The condition is satisfied if any (at least one) of the defined clauses are met.
- Using the drop-down list (highlighted below), select the field that the condition will use from the set of eForm or Document Package fields.
The field's type controls the operator list and comparison values. For example, if the comparison field is numeric, numeric comparisons are available. If the comparison field is a drop down list, the comparison values are automatically filled with the drop down list's options. - Specify the condition's operator from the second drop-down list (highlighted below).
For a complete list of conditions, see Using Available Condition Operators. - Specify the condition's value using the corresponding text box (highlighted below).
For complete details, see Specifying the Condition Value. - Add or remove conditional clauses as described in Adding or Removing Additional Clauses.
- Click OK to save your new condition and close the Edit condition dialog box.
Note: You can also click clear to return the dialog box to its original, non-configured condition.
Creating a Condition Using the Advanced Editing Mode
You can create a condition using the advanced editing mode, which provides greater flexibility in the condition creation, but is not as easy to use as the normal mode.
- Verify that you are viewing the advanced mode (by clicking the advanced button) as described in step 4 in the procedure above.
Once you click the button, the advanced mode is displayed. - Proceed to Advanced calculations.
Note: If desired, you can return to the normal editing mode by clicking the normal entry button.
Using Available Condition Operators
The operator controls the type of comparison.
| Operator | Description | Context | Available with Mobile |
|
AfterDate |
True if the comparison field's value is after the comparison date (specific date or date field). |
date |
✓ |
|
AfterDateTime |
True if the comparison field's value is after the comparison date and time (specific date/time or date/time field). |
datetime |
✓ |
|
AfterTime |
True if the comparison field's value is after the comparison time (specific time or time field). |
time |
✓ |
|
All |
True if all of the check box group items have been selected. |
checkbox groups |
✓ |
|
Any |
True if any of the check box group items have been selected. |
checkbox groups |
✓ |
|
BeforeDate |
True if the comparison field's value is before the comparison date (specific date or date field). |
date |
✓ |
|
BeforeDateTime |
True if the comparison field's value is before the comparison date and time (specific date/time or date/time field). |
datetime |
✓ |
|
BeforeTime |
True if the comparison field's value is before the comparison time (specific time or time field). |
time |
✓ |
|
Between |
True if the comparison field's value is equal to either of the two comparison values or within the range of the two comparison fields. |
numeric - (integer, decimal) |
✓ |
|
BetweenDate |
True if the comparison field's value is equal to either of the two comparison values (specific dates or date fields) or within the range of the two comparison fields. |
date |
✓ |
|
BetweenDateTime |
True if the comparison field's value is equal to either of the two comparison values (specific date/time or date/time fields) or within the range of the two comparison fields. |
datetime |
✓ |
|
BetweenTime |
True if the comparison field's value is equal to either of the two comparison values (specific time or time fields) or within the range of the two comparison fields. |
time |
✓ |
|
Contains |
True if the value of the comparison field includes the comparison value text. |
alphanumeric (text) |
✓ |
|
EndsWith |
True if the value of the comparison field concludes with the comparison value text. This is a case sensitive comparison. |
alphanumeric (text) |
✓ |
|
Equal |
True if the value of the comparison field is the same as the comparison value. This comparison is case-sensitive. |
alphanumeric (text, numeric, checkbox, code list) |
✓ |
|
EqualNoCase |
True if the value of the comparison field is the same as the comparison value. This comparison is not case-sensitive. This is available in advanced conditions only. |
alphanumeric (text, numeric, checkbox, code list) |
✓ |
|
FALSE |
A simple Boolean function that always returns a value of "false". |
none | ✓ |
|
Greater |
True if the value of the comparison field is larger than the comparison value. |
numeric - (integer, decimal) |
✓ |
|
GreaterOrEqual |
True if the value of the comparison field is the same or larger than the comparison value. |
numeric - (integer, decimal) |
✓ |
|
HasRole |
True if the value of the current user in effect has the selected role. This operator is often used to hide sensitive fields from unauthorized users (for example, fields that are "for office use only"). Note: Advanced mode is required to specify the condition's related parameter. |
form security | ✓ |
|
IsBlank |
True if the value of the comparison field is blank. |
alphanumeric | ✓ |
|
IsEmpty |
True if the value of the comparison field has a blank value. |
alphanumeric (text, integer, decimal, date, checkboxes, code list) |
✓ |
|
IsGuestUser |
True if the user is the guest user. (Advanced condition) |
none |
✓ |
|
IsInGroup |
True if the value of the user is a member of the comparison value's LDAP or AD group. Note: Advanced mode is required to specify the condition's related parameter. |
alphanumeric (text) |
✓ |
|
IsNotEmpty |
True if the value of the comparison field is not blank. |
alphanumeric (text, integer, decimal, date, checkboxes, code list) |
✓ |
|
IsNull |
True if the value of the comparison field has a no value. This operator should only be used in advanced comparisons. |
alphanumeric (text, date, checkbox) |
✓ |
|
IsOpenForm |
True if the eForm is running in OpenForm mode. (Advanced condition) |
none |
|
|
IsSigned |
True if the document has been signed. (Advanced condition) |
none |
✓ |
|
IsWebServiceSync |
True if a data sync is currently being performed, such as when syncing data that was initially recorded offline (such as using an iPad at a remote site) to your main service once a connection is re-established. This function is useful for preventing actions from occurring during the "After signing" event that should instead be done during the "After sync signing" event. |
none |
|
|
LastMonth |
True if the comparison field's date occurs within last month. |
date, time |
✓ |
|
LastSixMonths |
True if the comparison field's date occurs within the last 6 months. |
date, time |
✓ |
|
LastTwoWeeks |
True if the comparison field's date occurs within the last 14 days. |
date, time |
✓ |
|
LastWeek |
True if the comparison field's date occurs within the last 7 days. |
date, time |
✓ |
|
LastYear |
True if the comparison field's date occurs within the last 365 days. |
date, time |
✓ |
|
Less |
True if the value of the comparison field is smaller than the comparison value. |
numeric - (integer, decimal) |
✓ |
|
LessOrEqual |
True if the value of the comparison field is the same or smaller than the comparison value. |
numeric - (integer, decimal) |
✓ |
|
None |
True if none of the checkbox group items have been selected. |
checkbox groups. |
✓ |
|
Not |
True if checkbox is not selected. |
checkboxes. |
✓ |
|
NotAll |
True if any defined sub-condition is true. Note: Advanced mode is required to define related sub-conditions. |
checkbox groups. |
✓ |
|
NotEqual |
True if the value of the comparison field is not the same as the comparison value. |
alphanumeric (text, integer, decimal, checkboxes, code list) |
✓ |
|
OneOf |
True if the value of the comparison field is found in the set of comparison values. |
alphanumeric (text, integer, decimal, checkboxes, code list) |
✓ |
|
SignatureIsDeclined |
True if the given signature field was specifically chosen to be declined when viewing the generated document in the doc viewer. |
signing/signatures | |
|
StartsWith |
True if the value of the comparison field begins with the comparison value text. This is a case sensitive comparison. |
alphanumeric (text) |
✓ |
|
TRUE |
A simple Boolean function that always returns a value of "true". |
none | ✓ |
|
ViewerClosedJustSigned |
True if the viewer was just displayed and a signature was captured (due to the completion of an "after signing" event). Allows you to verify that an automatic close occurred. |
signing/signatures |
Specifying the Condition Value
Comparison values may be any constant value (such as a given text string or number) or other eForm fields.
- To specify a constant value, click the
button, and enter a text string or value in the corresponding text box (highlighted below).
- To specify a field from your eForm or Document Package, click the
button, and select the desired field from the corresponding drop-down list (highlighted below). The available fields will vary, based on the initial conditional field selected earlier ("addtl_cvg_maternity" in the example below).
Adding or Removing Additional Clauses
You can create complex conditions by specifying more than one conditional clause. Additional clauses are added using the + button (highlighted below).
When clicked, a new clause appears immediately below the clause containing the clicked + button. In the following example, a third clause was added between the two existing clauses by clicking the + button in the first clause.
You can also remove a clause using the - button (adjacent to the + button).
Examples: Conditions
A simple example of a condition would be a test of a field's value. For example, evaluate the value of a preferred contact list (shown below).
In this example, the condition's name is contact_ph_required. The condition's field is contact_optlist. Its operator is set to Equal, and its value is the Home Phone field.
A more complex example, shown below, could involve displaying a preferred contact time if the user entered a home phone number or a cell phone number. Also, notice that the Any of the following option is selected.