Version: 22.04
Using Txn attributes
You can display Txn information in the Workspaces UI by defining mappings in the dataIndex
attribute which is a Txn attribute in the underlying configuration that can be used as the value for a field.
Example
{
...
mappings: {
...
$primaryApplicant: {
label: 'Name',
dataIndex: 'properties["PrimaryName"]',
type: 'text',
},
...
}
...
}
Fallback dataIndex
In some cases you may want to define a fallback dataindex
. Let's say you want to display a value in the table that is not available for all Txn statuses. You can define dataIndex
as list, and the second value is checked if the first value is not there. For example:
{
...
mappings: {
...
$primaryApplicant: {
label: 'Name',
dataIndex: ['properties["PrimaryName"]', 'formDataMap["PrimaryName"]'],
type: 'text',
},
...
}
...
}
Below is a list of attributes and the supported operations that they can be used for in the Workspaces configuration.
Criteria Attribute | Description |
---|---|
authStatus | String Filter transactions based on the authStatus of the transaction. Supported operations: Selection, Filter, Sort |
clientCode | String Filter transactions based on the clientCode. Supported operations: Selection, Filter, Sort |
emailAddress | String Filter transactions based on the emailAddress associated with the submission Supported operations: Selection, Filter, Sort. |
formCategory | String Filter transactions based on the form template version's association to the category specified. Supported operations: Selection, Filter, Sort |
formCode | String Filter transactions based on the form code of the submitted form. Supported operations: Selection, Filter, Sort |
formDataMap | Object Filter transactions based on an entry in the formDataMap .Supported operations: Selection, Filter Supports exact match of value but not extract name. For example:
|
formName | String Filter transactions based on the form name of the submitted form. Supported operations: Selection, Filter, Sort |
formStatus | String Filter transactions based on transaction form status. Supported operations: Selection, Filter, Sort |
groupName | String Filter transactions based on the association with submission groups with names specified. Supported operations: Selection, Filter, Sort |
milestones | String Filter transactions based on submission milestones. Supported operations: Selection, Filter, Sort |
properties | Object Filter transactions based on submission properties. Supported operations: Selection, Filter Supports exact match of both name and value for a single property per search. For example:
|
spaceName | String Filter transactions based on the association with spaces with name(s) specified. Supported operations: Selection, Filter, Sort |
submitKey | String Filter transactions based on the submission submitKey. Will match to one transaction record. Supported operations: Selection, Filter, Sort |
timeAbandoned | String Filter transactions based on the time abandoned timestamp. Supported operations: Selection, Filter, Sort Specify the timestamp using one of the following formats:
|
timeCompleted | String Filter transactions based on the time completed timestamp. Supported operations: Selection, Filter, Sort Specify the timestamp using one of the following formats:
|
timeCreated | String Filter transactions based on the time created timestamp. Supported operations: Selection, Filter, Sort Specify the timestamp using one of the following formats:
|
timeRequest | String Filter transactions based on the time request timestamp. Supported operations: Selection, Filter, Sort Specify the timestamp using one of the following formats:
|
timeSubmitted | String Filter transactions based on the time submitted timestamp. Supported operations: Selection, Filter, Sort Specify the timestamp using one of the following formats:
|
timeUserLastModified | String Filter transactions based on the time user last modified timestamp. Supported operations: Selection, Filter, Sort Specify the timestamp using one of the following formats:
|
trackingCode | String Filter transactions based on the tracking code. Will match to one transaction record. Supported operations: Selection, Filter, Sort |
userLoginName | String Filter transactions based on the user login name. Supported operations: Selection, Filter, Sort |
userSaved | Boolean Filter transactions based on the user saved property True: "userSaved = 1" False: "userSaved = 0" or "userSaved = null". Supported operations: Selection, Filter, Sort |
job.jobRefNumber | String Filter transactions based on job reference number. Supported operations: Selection, Filter, Sort |
job.timeCreated | String Filter transactions based on job creation time. Supported operations: Selection, Filter, Sort |
job.timeLastModified | String Select job time value for the transaction. Supported operations: Selection |
job.jobKey | String Select job key value for the transaction Supported operations: Selection |
job.name | String Select job name value for the transaction. Supported operations: Selection |
job.currentAction | String Select job's current action for the transaction. Supported operations: Selection |
job.currentStep | String Select job's current step for the transaction. Supported operations: Selection |
job.status | String Select job's status for the transaction. Supported operations: Selection |
job.timeCompletionScheduled | String Select job's completion schedule time for the transaction. Supported operations: Selection |