Reference tags are used to link question answers data, and constant values, to other data dynamically. All reference tags are contained within square brackets '[ ]' and operators and other path data, like pointing at specific answers when there are multiple, uses a point '.'.
Question are usually formatted [q 'question number' . 'answer number/name'], so a question with multiple answer questions will just change the answer number or name for each answer. However some questions can have unique outputs and multiple of them, in these cases the answer number becomes a string like filename or base64.
If you are unsure what the correct reference tag is meant to be, the question reference is noted in the top right of the inspector panel, clicking on this reference will copy its reference tag to your clipboard.
Alternatively, simply click and drag the answer to a text box and it will be automatically filled with that questions reference tag.
Questions should only refer to other questions which come earlier in the form structure.
References to later questions (a forward reference) may work, but can also behave unreliably; for this reason forward references are not recommended.
Question reference tags operate differently within a repeater context.
Within a repeater, question tags are only able to retrieve answer data from within their current repeat. To reference a previous repeats' question answer the previous tag is required.
Finding reference dependencies is in the question more options menu, in the inspector panel, next to the question reference. You can also get to it using the context menu, in the Pages panel, when you right-click an item that can be referenced.
Additional operators can provide extra control to the data being passed through reference tags.
- [Protect.q1.1] - Used to protect a value after it has been referenced so it can't be edited by the user.
- [q1|default] - A question reference default value can be set using the pipe character | and entering the default value after it.
When sending emails to users (usually the assignee of a Workflow task), SmartIQ can replace a number of pre-defined values with corresponding information which it might otherwise be difficult or tedious for the designer to obtain.
|User comments on workflow submit|
|[ProjectName]||Published name of project|
|[StateName]||Name of workflow state|
|[AssigneeFullName]||Full name of assigned user|
|[AssigneeFirstName]||First name of assigned user|
|[AssigneeSurname]||Surname of assigned user|
|[RequesterFullName]||Full name of requester|
|[RequesterFirstName]||First name of requester|
|[RequesterSurname]||Surname of requester|
|[SenderFullName]||Full name of sender|
|[SenderFirstName]||First name of sender|
|[SenderSurname]||Surname of sender|
|[ReceiverFullName]||Full name of receiver|
|[ReceiverFirstName]||First name of receiver|
|[ReceiverSurname]||Surname of receiver|
|[AccessCode]||Temporary user access code for the assigned temporary user|
|[ProjectLink]||HTML hyperlink to the in progress workflow. Note: |
|[ProjectUrl]||Similar to project link but returns the raw URL only. Usually so that it can be rendered in a paricular way by the designer.|
|[WorkflowId]||Unique identifier of the workflow task|
|[Choice]||Refer to Email Approval for details.|
|[QuestionText]||Where the notification is in the context of a question, for example, a comment notification, the question text of the item in context will be rendered.|
The [ProjectLink] reference tag is replaced by a HTML link that points to the current workflow state for a project.
Reference tags in a project link can be combined using '|'.
Parts of the resulting Project Link can be overridden with:
These are passed as a pipe-separated list of key-values:
[ProjectLink|LinkUrl=https://google.com|LinkText=This is a link to google]
The above example will result in a link like:
<a href="https://google.com">This is a link to google</a>
ProduceUrl is supplied, other values will be appended to it to construct the URL as if the supplied value were the Produce URL of the system.
The positions of the placeholders in the formatted link are as follows.
If LinkText is not supplied:
<a href="LinkUrl">ProjectName - StateName</a>
If LinkText is supplied and is not empty:
If LinkText is supplied as empty:
FlagAsTempUseris supplied as a pipe-separated argument and the user is attempting to access a form that they have already completed, they will see a This form is no longer available message rather than the user login screen.
|[RowNumber]||Retrieves the current page number|
|[RowCount]||Counts and returns the total number of pages|
|[Previous.q 'question number'.'answer number']||References a question answer in the previous repeat, by simply adding 'Previous.' in front of the normal question reference tag SmartIQ will resolve the current repeat answer using the previous repeats question answer. For example, if designers want to reference the answer of question 1 from the previous repeat and not the current q1.1, this is when [Previous.q1.1] is used.|
The 'previous.' reference tag will make a repeated question return 0 if the question is self referencing.
Action inputs in workflow can reference previous action output using [parentaction.output]
Certain properties of certain blocks can't read reference tag data or don't have any reference tag data. These are Exemptions, where reference tags don't work or are inapplicable.
Writable Data Objects
|Action Button||Class Name|
|Choice||Option List - Grouping Id|
|Answer - Value|
|Data||Auto Complete - No Data Text|
|File Selection||Upload File - Button Text|
|Upload File - Answer File/ Save by Unique label|
|Camera Back - Take Photo Button Text|
|Launch URL Question||Input - URL -> Name|
|Video Player||Vimeo - Public Link|
|Visuals||Input - Name - Name property (used a different project)|
|Page||Repeating - Repeat Name|
|Section||Repeating - Repeat Name|
|Call SQL Stored Procedure||Stored Procedure Parameter - Name Input|
|CMIS Save Document||Access Control Entries (Principal: Permission)/ Metadata (Parameter = value)- Name Input|
|CMIS Update Document||Access Control Entries (Principal: Permission)/ Metadata (Parameter = value)- Name Input|
|Convert Document to Base64|
|Post to Webhook Action||Answer Values/ Custom Headers - Name Input|
|Salesforce Create Record Action||Field - Name Input|
|Salesforce Update Record Action||Field - Name Input|
|Save to AWS S3 Bucket Action||Metadata - Name Input|
|Send Email Action||Email Headers - Name Input|
|Send to REST Service Action||Custom Headers/Form Values - Name Input|
|Send to SOAP Service Action||Custom Headers - Name Input|
|Set Project Property||Custom Property - Name Input|
|SmartIQ Prepare Form Action||Values - Name Input|
|State||Due Date - Days After|
|State||Submission - Submit Button Text|
|State||After Submission - Submitting Text|
Updated 2 days ago