Tags have been renamed to Dynamic data. Dynamic data in Arbor Workflows may be unavailable because the field type is incompatible, data is collected later, the Trigger Form omits it, conditional logic makes it non-guaranteed, or Arbor Data requires an Option Set.
When building or editing a workflow in Arbor Workflows, using Dynamic data will pull data from previous steps (like a student’s name from a form or a comment from an approval) and insert them into later steps (like an checklist, decision, email or within an update).
If trying to insert a tag but cannot find the specific data field you need in the dropdown list, it is usually due to one of the following three reasons.
The data is not in a format that can be used in that field
For a piece of information to appear in dynamic data, the question type in your form must match the field you are trying to use it in.
Recipient Bar: If you are trying to pull a recipient in the "To" field of a step, the data must have been collected using an Email question type in your form. If you used a "Short Text" question type to ask for an email address, the system won't recognise it as a valid email recipient and it won't appear in the Dynamic data list for that specific field.
What to check: Go back to your Trigger Form or Form Step and ensure the Question Type matches the intended use (e.g., use "Date" types for date fields, "Email" types for recipients).
You can also use Dynamic data for recipients from the roles you have set in 'Custom Roles' or as part of 'Arbor Roles'.
The data collection happens later in the workflow
Workflows function linearly. You can only pull data through the workflow that has already been captured in a previous step.
If you are on Step 3 (e.g Send Email) and you want to use information that is collected in a form at Step 4, that data will not be available. The system cannot pull information that hasn't been submitted yet.
What to check: Look at your workflow order. If the information you need is collected in a later step, you will need to move that step earlier in the sequence or move your communication/action step further down.
Missing data from the Trigger Form
All workflows start with a form to capture trigger information. If you find you are missing a core piece of data throughout the entire workflow (e.g., a "Staff Absence Reason" or "Student ID"), it may be because that field wasn't included in the initial trigger, or any step types that can collect data.
What to check: Open your Trigger Form at the very start of the workflow builder. Ensure all "Must Have" data points are included as questions here so they are available in Dynamic data for every subsequent step.
Conditional logic and "Guaranteed Data"
If you are using Conditional Logic (available on the Perform tier for Schools and Plus/Advanced for MATs), some steps or questions may be skipped based on a user's previous answers.
To ensure a workflow doesn't "break" mid-run, Dynamic data will often only show data that is guaranteed to be collected.
If you have a Form Step that only appears if a "Decision" was marked as "No," any data collected in that specific form is not guaranteed to exist for every person going through the workflow. Therefore, the system may prevent you from using that data in a later "Send Email" step because, for many users, that data field will be empty.
What to check: Review your logic rules. If you need a piece of data to be available in a final step, ensure the question is part of a mandatory, non-conditional step (like the Trigger Form) rather than a conditional branch.
Dynamic Data unavailable in an Arbor Data step
Arbor Data Steps have a set of required fields that rely on information to be collected prior to the step. If the required field is not displaying any available data when trying to add this, it is likely that is a question that is required to be in the Arbor Option Sets format. These areas include:
Currently available Option Sets include:
Title: (e.g., Mr, Mrs, Miss, Dr, Mx)
Gender: (As defined by MIS standards)
Country: (A full standardised list of countries)
Job Role: (Matches the Arbor Business Roles)
Guardian Relationship Type: (e.g., Mother, Father, Foster Carer, etc.)
Postal Address Type: (e.g., Home, Work, Previous)
You will need to update the question type at the point this data is collected in order to be able to use it within this step.
Summary Checklist for Dynamic Data
If data is missing, ask yourself:
Format: Is the question type an 'Email' type or 'Date' type?
Order: Does this step happen after the information is collected?
Presence: Is this question hidden behind Conditional Logic?
Tier: Does my current tier (Core, Comms, or Perform) support this many steps or "Send Something" actions?
Comments
Article is closed for comments.