Using Txn attributes
In order to display Txn information in the UI, you will need to setup some mappings via the dataIndex
attribute. dataIndex
is a Txn attribute in the underlying configuration that will be used as the value for the field. For example:
{
"$primaryApplicant": {
"label": "Name",
"dataIndex": "properties['PrimaryName']",
"type": "text"
}
}
Fallback dataIndex
In some cases you may want to define a fallback dataIndex
. Say you want to display a value in the table that is not available for certain Txn statuses. You can define dataIndex
as a list that is checked in the specified order, stopping when a value is found. For example:
{
"$primaryApplicant": {
"label": "Name",
"dataIndex": ["properties['PrimaryName']", "formDataMap['PrimaryName']"],
"type": "text"
}
}
Supported attributes
Here is the list of attributes and supported operations that can be used within a Workspaces configuration.
Attribute | Description |
---|---|
authStatus | String Supported operations: Selection, Filter, Sort Filter transactions based on the |
clientCode | String Supported operations: Selection, Filter, Sort Filter transactions based on the |
emailAddress | String Supported operations: Selection, Filter, Sort Filter transactions based on the |
formCategory | String Supported operations: Selection, Filter, Sort Filter transactions based on the form template version's association to the category specified. |
formCode | String Supported operations: Selection, Filter, Sort Filter transactions based on the form code of the submitted form. |
formDataMap | Object Supported operations: Selection, Filter Filter transactions based on an entry in the Examples:
|
formName | String Supported operations: Selection, Filter, Sort Filter transactions based on the form name of the submitted form. |
formStatus | String Supported operations: Selection, Filter, Sort Filter transactions based on transaction form status. |
groupName | String Supported operations: Selection, Filter, Sort Filter transactions based on the association with submission groups with names specified. |
milestones | String Supported operations: Selection, Filter, Sort Filter transactions based on submission milestones. |
properties | Object Supported operations: Selection, Filter Filter transactions based on submission properties. Supports exact match of both name and value for a single property per search. Examples:
|
spaceName | String Supported operations: Selection, Filter, Sort Filter transactions based on the association with spaces with name(s) specified. |
submitKey | String Supported operations: Selection, Filter, Sort Filter transactions based on the submission |
timeAbandoned | String Supported operations: Selection, Filter, Sort Filter transactions based on the time abandoned timestamp in the format "yyyy-MM-dd", "yyyy-MM-dd HH:mm:ss" or "yyyy-MM-ddTHH:mm:ssZ" (the returned date format). Examples:
|
timeCompleted | String Supported operations: Selection, Filter, Sort Filter transactions based on the time completed timestamp in the format "yyyy-MM-dd", "yyyy-MM-dd HH:mm:ss" or "yyyy-MM-ddTHH:mm:ssZ" (the returned date format). Examples:
|
timeCreated | String Supported operations: Selection, Filter, Sort Filter transactions based on the time created timestamp in the format "yyyy-MM-dd", "yyyy-MM-dd HH:mm:ss" or "yyyy-MM-ddTHH:mm:ssZ" (the returned date format). Examples:
|
timeRequest | String Supported operations: Selection, Filter, Sort Filter transactions based on the time request timestamp in the format "yyyy-MM-dd", "yyyy-MM-dd HH:mm:ss" or "yyyy-MM-ddTHH:mm:ssZ" (the returned date format). Examples:
|
timeSubmitted | String Supported operations: Selection, Filter, Sort Filter transactions based on the time submitted timestamp in the format "yyyy-MM-dd", "yyyy-MM-dd HH:mm:ss" or "yyyy-MM-ddTHH:mm:ssZ" (the returned date format). Examples:
|
timeUserLastModified | String Supported operations: Selection, Filter, Sort Filter transactions based on the time user last modified timestamp in the format "yyyy-MM-dd", "yyyy-MM-dd HH:mm:ss" or "yyyy-MM-ddTHH:mm:ssZ" (the returned date format). Examples:
|
trackingCode | String Supported operations: Selection, Filter, Sort Filter transactions based on the tracking code. Matches to one transaction record. |
userLoginName | String Supported operations: Selection, Filter, Sort Filter transactions based on the user login name. |
userSaved | Boolean Supported operations: Selection, Filter, Sort Filter transactions based on the user saved property.
|
job.jobRefNumber | String Supported operations: Selection, Filter, Sort Filter transactions based on job reference number. |
job.timeCreated | String Supported operations: Selection, Filter, Sort Filter transactions based on job creation time. |
job.timeLastModified | String Supported operations: Selection, Filter Filter transactions based on job last modified time. |
job.jobKey | String Supported operations: Selection Select job key value for the transaction. |
job.name | String Supported operations: Selection Select job name value for the transaction. |
job.currentAction | String Supported operations: Selection Select job's current action for the transaction. |
job.currentStep | String Supported operations: Selection Select job's current step for the transaction. |
job.status | String Supported operations: Selection Select job's status for the transaction. |
job.timeCompletionScheduled | String Supported operations: Selection Select job's completion schedule time for the transaction. |