Hi,
We have a requirement to create 2 custom tasks in the deployment manager.
The “CR Number” input should be taken from the cutom task 1, and then display the same value in custom task 2. Please advice how values captured in a custom task can be shared across and whether this is doable?
Thank You!
Yes, this is definitely doable, and the most efficient way to handle it is by saving the captured value into the Pipeline Context on the Orchestrator. During the execution of Custom Task 1, use a post-processing activity to write the CR Number to a specific property within the pipeline’s shared data model. Once this value is stored, Custom Task 2 can be configured to read that exact property from the pipeline data to use as its own input parameter. This method allows the system to maintain a single source of truth for your data throughout the entire deployment lifecycle. By mapping the output of the first task to a global pipeline property, you ensure the CR Number is automatically passed to the next task without manual effort. This approach keeps your workflow seamless and ensures that information flows perfectly from one step to the next.