In Actionstep Builder, there are two types of fields: variable and instruction. Each has rules about how they are used.
Working with Variable Fields
A variable is the basic unit of data in Builder. It is used to determine and merge custom information about a client or matter in documents you are generating for them.
There are different types of variables: Text, Number, Date, True/False, Selection, and Object.
The following rules apply to variable fields:
- Variable names can include only letters, numbers and underscores.
-
When inserted in a Word template or used in a Builder field (like a question prompt), the variable field must be enclosed in curly and square brackets {[ ]}, like this:
Field Used in Word Template Field Used in Builder Online Workspace - Variables used in formulas or expressions do not need these brackets.
- When including filters, punctuation, or formatting with a field, these come after the variable name and a pipe character:
Working with Instructions Fields
An instruction is used to tell Builder to perform a specific task within your template. Examples of instruction tasks include merging content if certain conditions are selected or inserting a list of information.
The following rules apply to instruction fields:
- Instructions must be lowercase and one word, e.g., {[elseif]} vs. {[ELSE IF]}:
- When inserted in a Word template or used in a Builder field (like a question prompt), the instruction field must be enclosed in curly and square brackets {[ ]}, like this:
- When using a selection variable to test for a certain value as part of an instruction, that value must be referenced using two equals signs:
- When using a selection variable to test whether a certain value is NOT part of a condition, the value must be referenced using an exclamation point and a single equal sign:
-
If the opening instruction is on its own line, the closing instruction must also be on its own line. Similarly, if the opening instruction is inline, the closing instruction must also be:
Inline Own Lines/Paragraphs
Note: If you receive errors saying, for example, the if field has no matching endif,
check to make sure the opening and closing if/endif statements are on their own
line. You may need to show paragraph marks to make sure there are actual paragraph
breaks and not line breaks.
Additional Resources:
Updated