In version 1, a workflow trigger execution always requires one or more ‘watched’ files to change on disk. There are a couple of options if you want to trigger a workflow (WF2) to run after a snapshot has been created (in WF1):
Create a small triggering file to export after the snapshot
Following the Take snapshot step in WF1, you could export a file and use this as the watched file for the trigger execution on WF2. You want the trigger file to be small, to avoid needing to unnecessarily export data that won’t be used. One approach is to use a Filter step to only select the firts row (as in my example below).
You could also use Transform to hide all but a single column, and finally use a Constant function to that field. The constant value could describe the purpose of the file ideally, for clarity, and may also include a timestamp (Current Timestamp) to indicate last updated date.
Using this new trigger file to trigger WF2 execution would require the trigger to be present as a source in WF2, but it doesn't actually need to form part of the workflow's process. In the example below, the file "Trigger Test 1" can be specified as a source trigger in the YAML
Use the custom Execute Workflow step
Depending on your Data Studio license, you may be able to make use of the Execute Workflow custom step to trigger WF2 from WF1:
This step is only available through our consultancy teams, as it is not part of the core Data Studio v1 solution
Scheduling in v2
It's useful to note that scheduling a series of workflows to run in sequence is easy to achieve in Data Studio version 2 by creating a schedule:
Schedules can also be triggered from events such as automated file loads, via new Notifications options in the UI
Neil
New Member
Answers
Hi @Neil
In version 1, a workflow trigger execution always requires one or more ‘watched’ files to change on disk. There are a couple of options if you want to trigger a workflow (WF2) to run after a snapshot has been created (in WF1):
Create a small triggering file to export after the snapshot
Following the Take snapshot step in WF1, you could export a file and use this as the watched file for the trigger execution on WF2. You want the trigger file to be small, to avoid needing to unnecessarily export data that won’t be used. One approach is to use a Filter step to only select the firts row (as in my example below).
You could also use Transform to hide all but a single column, and finally use a Constant function to that field. The constant value could describe the purpose of the file ideally, for clarity, and may also include a timestamp (Current Timestamp) to indicate last updated date.
Using this new trigger file to trigger WF2 execution would require the trigger to be present as a source in WF2, but it doesn't actually need to form part of the workflow's process. In the example below, the file "Trigger Test 1" can be specified as a source trigger in the YAML
Use the custom Execute Workflow step
Depending on your Data Studio license, you may be able to make use of the Execute Workflow custom step to trigger WF2 from WF1:
This step is only available through our consultancy teams, as it is not part of the core Data Studio v1 solution
Scheduling in v2
It's useful to note that scheduling a series of workflows to run in sequence is easy to achieve in Data Studio version 2 by creating a schedule:
Schedules can also be triggered from events such as automated file loads, via new Notifications options in the UI