Data composer shows several different types of data elements. This page provides some examples of those data elements and how they are used in the system.
Common Data Elements
| Data Entity Type | Description | Example |
|---|---|---|
| Chronology | ShareDo supports a filterable view of Chronology within Data Composer. This is so Data Subject Access requests (and others) can show "case history". |  |
| Custom Data Capture (e.g. Acquisition Details) | Where custom data is added to a work type (e.g a formbuilder) then the data is available via the data composer. The data item type will be named the same as the title of the formbuilder aspect that has been added to the work type. |  |
| DateTime | Date Time field | |
| GUID | Unique identifier | 63baefa4-33c6-4dd7-979f-aca100a877ef |
| HTML | A field containing data stored in HTML format |
These fields provide a further drill down to get the data either with or without html tags. HTML: <b>something in bold</bold> Text: something in bold
|
| Integer | Integer | 123 |
| Jurisdiction | Used for legal jurisdictions or regions this type of fields requires a further drill down to extract name or other information. |  |
| Location |
Location data types allows access to address information for participants or ods (master data) entities. You are able to drill down to see the types of location that are available based on your own configuration of the system (e.g. correspondence, billing) and then to get the various address fields). More information can be found on the Common Queries - Address Information page. |
|
| List of Related Documents | List of meta data around related documents. Your implementation of the system may be linked to a document management system such as iManage or Sharepoint. This list will allow you to access related meta data about the document such as title. | List of documents that have been added to a particular work type. Read the working with lists page to understand more about working with a list of information.
|
| List of Work Item Bases | List of related work types e.g. child work types such as task associated with a service request |
A common use for the 'List of Work Item' field types is child work types associated with a work type. For example if you have an work type that is an IT Service Desk Ticket you then may have a number of child tasks associated with that such as 'Fix software', 'QA software'. Data composer will look at your work type and see what possible relationships it could have with other work types, child is just one of these. When you are looking to use this data in document templates or configuration you will need to define more specifically what you are looking for - read the working with lists page to understand more. |
| ODS Entity |
ODS Entity data element allows the user to drill down into information held on the master data record for the holder of a particular role. This includes any master data information. Note that locations (addresses) although held on the master data record are also added specifically in relation to a participants role on a work type and often that is the address that should be used. For example if Mega Bank is added as the lender on a matter they may have hundreds of branch addresses held on their master data record but only one is relevant to the particular work type. |
 |
| OptionSetValue | A value where the user selects from an option set (list of values). |
Option set field provides a further drill down so that you can get the correct data required from the option set. This could be the id, name etc depending on usage. Id (Integer) - the option value id number Name (Text) - The display name for the option set value ShortName(Text) - the short name defined for the option set item MeaningCode(Text)- the meaning code defined for the option set item e.g. #open, #positive |
| Participant Role Order | When configuring participant roles you are able to define 'role ordering' which means that when participants are added an order is captured e.g. first buyer, second buyer. The role order data element allows further drill down to see the order defined in different formats e.g. value, 1, ordinal second. |  |
| Participant Role Type | Indicates the role type held and allows drill down to collect meta data about the role e.g.name |  |
| Participant Type | Participant types can be added onto the master data definition for an ODS entity. This data type allows further drill down to get the meta data associated with participant types |  |
| Phase | The phase of a work item - requires drilling further to extract the correct data |
When you configure the different phases for your work items then there are various pieces of data including the name. An item of type phase in the data composer allows you to drill down further to determine which piece of data you wish to use for example you may just wish to use the name or you may want to get the indicator for if the work item is open or not.
|
| Roles | A list of participant roles |
Provides detailed further breakdown of participants.
|
| Text | Text field | My title |
| Work Item Base | This data element can link to another single instance of a work type. For example a parent work type e.g. Contract under which a service desk ticket is created. |
Provides a detailed further breakdown of the work type to which this is linked. If the work type is linked by this relationship to more than one other work type then you can use the type path / specific type filter to get more details. For example if a work type can have a parent of both contract and statement of work then by default information which is available to both will be visible in the data composer. If you have data that is specific to a statement of work (e.g. SLA's) then you must specify you want to see statement of work only data and then those type specific fields will be displayed. Once you are looking at data for the work item base (e.g. parent) then the data displayed behaves in the same way as any other work item e.g. you can then drill down to view participant data fields for participants on the work item you are viewing (e.g. statement of work). Read the working with lists page to learn more.
|
