There are a number of places within data composer / document tag browser where you may be required to work with lists of data. This could be looking for lists of participants holding a particular roles, looking for lists of child tasks associated with a work type or many other scenarios. This section describes the key concepts and actions required to work with lists in the data composer.
The following are some common examples of where lists can be found in data composer, there are though many more and this will vary depending on your configuration.
If you are looking for data / document tags ensure you are working in the correct context - if you are tagging documents you should be using the document tag browser from the document template configuration for the template the tag is for.
| List | Description | Example |
|---|---|---|
|
List of participants holding a role (Work Item Query > Work Item > Roles > Select Role Name) |
A work item may have a participant role where more than one person, organisation or team may hold the role. For example in the sale of a property there may be more than one participant who holds the role of buyer. Therefore data associated with buyers will initially be a list |  |
| Child Work Types |
When configuring work types you are able to define relationships between work types. Some of these may be child relationships. For example a work type frequently has a parent-child relationship with the standard task work item (and anything under its path) so you can create tasks, email for your work type. When looking at the data model therefore there is a list of work item base which essentially is a list of work types that could be associated by a child relationship |
 |
| Ancestor Work Types |
As above but for work types that sit above the current work type in the hierarchy |
|
| List of Wiki | List of wiki entries for a work type |  |
| List of email contact types | List of email contact types available on an ods record (accessed via the ODS Data Composer) |  |
| List of Related Documents | List meta data associated with documents that have been related to a work item |  |
How Are Lists Used?
Lists can be used either as they are or they can be further filter and specialised for more detailed usage. In document templates, for example, a list can be bound to a table in the document and then various fields from the list used to list out data. Calculated lists can be created in the data composer to pre-filter or sort these lists prior to use in a document. List can also be used for reference in the creation of calculated fields e.g. If the list count of witnesses is 0 then set some text to 'No witnesses'.
What Data is Available in a List?
The data available in a list will, as expected, depend on what you are listing. For example a list of participants will contain data associated with participants and allow you to drill down into the low level detail for those participants e.g. data held on their ODS master data record such as email address, role etc.
Lists that contain mixed types of data e.g. different work types such as a lists of work types that sit under the 'task' path - this may include things such as emails, tasks, SMS messages - will only initially show the common data elements e.g. reference, title. You can then specialise your list further if you wish by adding filters and refinements. These are available in the user information for querying data but for use in document templates the filters / sorts will need to be made permanent by creating a calculated list.
Filtering Lists in Data Composer / Document Tag Browser
To explore the data available to you then you may wish to filter or sort lists to get to specialist data.
Do you want to specialise? When you click into your list you may then be offered the opportunity to specialise a bit further. So for example we could have possible child work types of Task, Payments or any other child relationships you want to set up. These could hold very different data elements so we may wish to specialise further and say what type of things we are looking for. We could for example limit this to show any type of task
Do You Want to Limit the Statuses of Work-items?
You are able to limit the work items included in a query to open, closed, removed
Click on the Resolve button to apply your filter.
Do You Want to Only See a Specific Record, e.g. the First?
If you can have more than one instance of a work type you may wish to have only the first instance show for example the first buyer, or the second buyer.
If you then click on resolve you will see that you are now looking at data specific for the first buyer. If you click on the field to see the tag definition you will see that this is now contains an indicator that this is only the first participant. e.g workitem.roles.buyer!1.participantId. More information around document tag formats can be found here.