nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deploy task success failure in workflow modeler

catorarn

Solution: TS671SP1/WFM1001/OD62+patch1/LS302
attached: workflow model of CPW Preview Selected Content.

I have a workflow which selects files in a URL task (custom java code). Then it has a Deploy Task. When the deploy task finishes, I would like to get the Deployment status back to the user in a cgi screen somehow.

How would I go about this in workflow modeler?

I know from the Publish LiveSite Content workflow that comes out of the box with LiveSite 302 that I have to have a continuous sequence of URL tasks including the deployment in a URL task. We do not want to use URL tasks for deployments.

Find more posts tagged with

Comments

Faizi

Check the "Publish LiveSite Content" workflow deeply. Play with it try to find idea.

catorarn

After my investigations of the Livesite workflow I have made the following observations.

1. It is possible to keep the WF instantiation Form open, if the WF uses CGI or CGI like tasks. However, if the flow is broken by another task like Submit etc. then the instantiation form is closed.

2. The Livesite workflow uses a CGI task to call a custom java service that in turns calls a Open Deploy job. Using the standard Deployment task does not seem possible, if one wants to render the failure message back to the customer.

Faizi

1. It is possible to keep the WF instantiation Form open, if the WF uses CGI or CGI like tasks. However, if the flow is broken by another task like Submit etc. then the instantiation form is closed.

This is correct as per as my understanding. In this OOTB workflow the main role played by "workflow-resource-config.xml" file. which is some java classes and jsp.

2. The Livesite workflow uses a CGI task to call a custom java service that in turns calls a Open Deploy job. Using the standard Deployment task does not seem possible, if one wants to render the failure message back to the customer.

For rendering deployment message, Use CGI task, define it in config file and write custom java class and inherit standard deployment class.
Hope this will give some pointer.