Multiple task templates in Digital Product Release

[MyR]

We have certain requirements and trying to understand how to achieve this in Digital Product Release.

- Is it possible to use different task templates for each task in the phases of release templates? Each task will require different data to be collected and need to have their own workflows. Some tasks might have over 10 data elements that need to be collected.

- Another requirement is that based on a specific data element collected, additional tasks may need to be added. While we have the ability to add tasks, how do we select the specific task template we want to use?

[Colin OBrien]

Hi @MyR,

When you refer to using different task templates, are you meaning which fields are required on the task or which fields are automatically filled out from a sys_template?

For creating tasks based on the input from other tasks, we don't support that yet. It is part of a larger Release Orchestration feature that we have in our backlog. You can build this out today with Flow Designer it just won't be something managed in the DPR workspace.

Thanks,

Colin

[MyR]

The release task uses sn_dpr_model_release_task. We need to capture additional data depending on the release task. The data elements to be captured will be different for each release task. As an illustration, in one of the planning tasks we may need to ask for a project id, and for a design task we may need to ask for some technical details. How do we add custom fields to the release task table in such a way that the user only sees the applicable/required fields on the form depending on whether they are on the planning task or design task?

[kchadwick]

Did you ever solve this?

[MyR]

No