Implementation of Pre and Post Execution Processes
The TDM task enables adding Pre-execution process and Post-execution process processes in the task's Advanced settings. The pre-execution processes run in the beginning of the task's execution, before all the related LUs have been executed. The post-execution processes run at the end of the task's execution, after all the related LUs have been executed.
Examples:
- Running a cleanup flow before executing the task's LUs.
- Sending an email to the tester to notify them that the execution of a task has ended.
- Adding an execution note to the task's entities (part or all entities). The execution note can be later be viewed in the self-service application.
Implementation Steps
1. Create the Pre or Post Execution Flow
The pre or post execution processes are Broadway flows. These flows can have external parameters that can be overridden by the task's creator.
Adding an Execution Note to the Task's Entities
A new Actor has been added in TDM 9.4: EntityExecutionNote. This Actor updates the relevant records in task_execution_entities TDM DB table to populate the execution_note field for the required entities.
See an example below:
2. Add the Flow to PostAndPreExecutionProcess MTable
- The PostAndPreExecutionProcess MTable defines the list of pre-execution and post-execution flows to run before or at the end of a task's execution.
- Populate the list of Broadway flows, the flow's LU, and the process type (pre/post). The LU can be empty if the processes are defined under Shared Objects, whereby the TDM task execution process sets the LU Name to TDM when running Batch commands to carry out pre/post execution processes.
- Redeploy the LUs populated in this table, the TDM LU, and the Web-Services.
3. Add the Flow to PostAndPreExecutionProcess MTable
- TDM self-service application setup - add the pre and post-execution processes to the relevant Business Entities.
- Click here for instructions.
Implementation of Pre and Post Execution Processes
The TDM task enables adding Pre-execution process and Post-execution process processes in the task's Advanced settings. The pre-execution processes run in the beginning of the task's execution, before all the related LUs have been executed. The post-execution processes run at the end of the task's execution, after all the related LUs have been executed.
Examples:
- Running a cleanup flow before executing the task's LUs.
- Sending an email to the tester to notify them that the execution of a task has ended.
- Adding an execution note to the task's entities (part or all entities). The execution note can be later be viewed in the self-service application.
Implementation Steps
1. Create the Pre or Post Execution Flow
The pre or post execution processes are Broadway flows. These flows can have external parameters that can be overridden by the task's creator.
Adding an Execution Note to the Task's Entities
A new Actor has been added in TDM 9.4: EntityExecutionNote. This Actor updates the relevant records in task_execution_entities TDM DB table to populate the execution_note field for the required entities.
See an example below:
2. Add the Flow to PostAndPreExecutionProcess MTable
- The PostAndPreExecutionProcess MTable defines the list of pre-execution and post-execution flows to run before or at the end of a task's execution.
- Populate the list of Broadway flows, the flow's LU, and the process type (pre/post). The LU can be empty if the processes are defined under Shared Objects, whereby the TDM task execution process sets the LU Name to TDM when running Batch commands to carry out pre/post execution processes.
- Redeploy the LUs populated in this table, the TDM LU, and the Web-Services.
3. Add the Flow to PostAndPreExecutionProcess MTable
- TDM self-service application setup - add the pre and post-execution processes to the relevant Business Entities.
- Click here for instructions.
