Version: 20.05 (EOL)
Using Txn attributes
In order to display Txn information in the UI, you need to setup some mappings via the dataIndex attribute. The dataIndex value is a Txn attribute in the underlying configuration.
For example:
{
  ...
  mappings: {
    ...
    $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 order specified, stopping when a value is found.
For example:
{
  ...
  mappings: {
    ...
    $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 | StringSupported operations: Selection, Filter, Sort Filter transactions based on the authStatusof the transaction. | 
| clientCode | StringSupported operations: Selection, Filter, Sort Filter transactions based on the clientCode. | 
| emailAddress | StringSupported operations: Selection, Filter, Sort Filter transactions based on the emailAddressassociated with the submission. | 
| formCategory | StringSupported operations: Selection, Filter, Sort Filter transactions based on the form template version's association to the category specified. | 
| formCode | StringSupported operations: Selection, Filter, Sort Filter transactions based on the form code of the submitted form. | 
| formDataMap | ObjectSupported operations: Selection, Filter Filter transactions based on an entry in the formDataMap. Supports exact match of value but not extract name.Examples: 
 | 
| formName | StringSupported operations: Selection, Filter, Sort Filter transactions based on the form name of the submitted form. | 
| formStatus | StringSupported operations: Selection, Filter, Sort Filter transactions based on transaction form status. | 
| groupName | StringSupported operations: Selection, Filter, Sort Filter transactions based on the association with submission groups with names specified. | 
| milestones | StringSupported operations: Selection, Filter, Sort Filter transactions based on submission milestones. | 
| properties | ObjectSupported 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 | StringSupported operations: Selection, Filter, Sort Filter transactions based on the association with spaces with name(s) specified. | 
| submitKey | StringSupported operations: Selection, Filter, Sort Filter transactions based on the submission submitKey. Matches to one transaction record. | 
| timeAbandoned | StringSupported 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 | StringSupported 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 | StringSupported 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 | StringSupported 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 | StringSupported 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 | StringSupported 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 | StringSupported operations: Selection, Filter, Sort Filter transactions based on the tracking code. Matches to one transaction record. | 
| userLoginName | StringSupported operations: Selection, Filter, Sort Filter transactions based on the user login name. | 
| userSaved | BooleanSupported operations: Selection, Filter, Sort Filter transactions based on the user saved property. 
 | 
| job.jobRefNumber | StringSupported operations: Selection, Filter, Sort Filter transactions based on job reference number. | 
| job.timeCreated | StringSupported operations: Selection, Filter, Sort Filter transactions based on job creation time. | 
| job.timeLastModified | StringSupported operations: Selection Select job time value for the transaction. | 
| job.jobKey | StringSupported operations: Selection Select job key value for the transaction. | 
| job.name | StringSupported operations: Selection Select job name value for the transaction. | 
| job.currentAction | StringSupported operations: Selection Select job's current action for the transaction. | 
| job.currentStep | StringSupported operations: Selection Select job's current step for the transaction. | 
| job.status | StringSupported operations: Selection Select job's status for the transaction. | 
| job.timeCompletionScheduled | StringSupported operations: Selection Select job's completion schedule time for the transaction. |