Table of Contents
As the end user progresses through a workflow, they will slowly build up information or data. This data is organized into something called a "dictionary". You can see this dictionary using the toggle in the top left hand corner of a page when viewing a running workflow. The example below shows an example of what you might find there:
{
"StudyInfo": {
"documents": {
"AD_CoCApp": {
"category1": "Ancillary Document",
"category2": "CoC Application",
"category3": "",
"Who Uploads?": "CRC",
"id": "12",
"description": "Certificate of Confidentiality Application",
"required": true,
"study_id": 2,
"code": "AD_CoCApp",
"display_name": "Ancillary Document / CoC Application",
"count": 0,
"files": []
},
"AD_CoCAppr":
Some scripts will add data to the model automatically, as in this example. But you can also add data to this structure using BPMN, and DMN. As well as make decisions based on value in this dictionary.
Dot Notation
You can reference this data using something called "Dot Notation", So if you needed to display the name of a specific document you would write: StudyInfo.documents.AD_CoCApp.display_name
This dot-notation syntax can be used to add data to the structure in forms. It can be used in an exclusive gateway within a BPMN diagram to decide which direction to take in a fork. It can be used as the input variable in a decision table.
When creating data, please be sure to use simple short-as-possible strings. the "_" character and "-" character are permitted, but other symbols may cause a problem.