As a Digital.ai Template creator, I would like to be able to define a set of tasks that do something such as start application ( which in my case involves calling startup scripts and other job processing scripts through remote tasks ). And then have that saved as a custom task that could then be used in other release templates. This would be helpful as some applications may rely on the startup/shutdown of another app when they are also deploying. And they have a separate release template, so currently I have to duplicate the exact steps in several templates. Which is painful to maintain. I was hoping the recent workflows would address this, and I could create a startup workflow that I would be able to call from releases...but unfortunately I don't see a way to call workflows from a release, but also see an idea for that, which could possibly solve this issue for me if implemented correctly.
by: Patrick S. | 3 months ago | Templates & Releases
Comments
Thank you for the idea. Have you considered building a template where the current 'Create Release' task could trigger a dedicated template for the use case you mentioned (starting an application via remote tasks)? Are there any limitations to this approach that led you to suggest an alternative using a task group template?