When working with processes, especially when a process is also used as a sub-process within another, it's crucial to have a reliable way to determine if a specific action step has been successfully completed. Using session variables provides a consistent method for tracking this, ensuring your process logic is sound.

Need

You need a dependable method to confirm whether a specific action step has finished executing. 
This method must work both when the action is part of a standalone process and when it's within a sub-process. 


Summarized Solution

To verify if an action step is complete, you can check its CORE_END_DATE session variable after the process has run. The existence of a timestamp for this variable confirms that the action step has finished.


Detailed Solution

Here is the step-by-step guide by using session variables for confirmation:

1. Set up the Processes

First, you'll have a main process, let's call it test_process. You will also have another process, test_process2, which includes test_process as a sub-process. 
The goal is to check the completion of a specific action step within test_process.

 

2. Run the Processes

Execute both test_process (as a standalone process) and test_process2 (which runs test_process as a sub-process).

3. View the Session Variables

After execution, inspect the session variables for the specific action step you are monitoring.

  • In a standalone Process: Look for the CORE_END_DATE variable associated with the highlighted action step. A populated date and time value confirms the step is completed.

  • In a sub-process: Similarly, when checking the session of test_process2, drill down into the sub-process step for test_process. You will find the same CORE_END_DATE variable for the action step, confirming its completion within the sub-process context.

In a Process
In a sub-process


You can use other CORE_ session variables, such as CORE_START_DATE and CORE_STATUS, to get more detailed insights into the execution status of your process steps.