In this article
The Workflow document is written in CDL and contains a set of tasks that re executed to add the relevant program assets (such as surveys, dashboards, etc) into the new program. It consists of several sections, such as defining fields that will be dynamically referenced by any subsequent tasks, and then the workflow tasks themselves, which are executed in the order a presented in the workflow CDL document.
The workflow document contains a set of field definitions which are used to dynamically reference assets as part of the program creation. Here are some examples:
Defined item | Example from workflow CDL |
Program Title: This will reference the title of the program that is inputted on program creation. | field definition { name: "title" type: "string" required: true }
|
Surveys: Surveys are referenced in a naming convention by the folder name of the survey containing the survey XML, followed by “surveyuri” For the example, this is referring to the Survey contained in the Surveys -> onlineTransactional folder.
Note: The name in the workflow document must be lower case, although this can refer to a folder with mixed case. | field definition { name: "onlinetransactionalsurveyuri" type: "string" required: true }
|
Dashboards: Studio dashboards are referenced in a naming convention by the folder name of the survey Containing the dashboard CDL, followed by “dashboarduri” For the example, this is referring to the Studio dashboard contained in the Dashboards -> shopperInsights folder.
Note: The name in the workflow document must be lower case, although this can refer to a folder with mixed case.
| field definition { name: "shopperinsightsdashboarduri" type: "string" required: true }
|