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; } } }

Single Task/Multiple Task

saurabh4984

Hi,
I have always had this question, that, if it is possible for me to incorporate multiple functionalities in a single external task the should I have only one task in my workflow or I should bifurcate the functionality in two and have two tasks in my workflow. For eg, If I have to do data deploy and OpenDeploy and If I am using WFM then should I have one External task where I would call the DD script and then make use of some Deploy Task(or another external task) for the OD.
What is recommended?
Please Guide.

TIA

Find more posts tagged with

Comments

curiousmaverick

I have one implementaion where OD and DD is done from the same script which gets called from an external task. Bt then OD and DD are not invoked simultaneously.

I guess you still can do it, provided you take adeqaute care in handling the callback part.

curiousmaverick

One way of doing it will be using DeployNRun.

For eg; you can do your DD as DNR. The script then will do the OD. If it fails, send the appropriate return code which will rollback DD as well.

saurabh4984

One way of doing it will be using DeployNRun.

For eg; you can do your DD as DNR. The script then will do the OD. If it fails, send the appropriate return code which will rollback DD as well.

Thank you! I would also like to know what is recommended. To have multiple tasks or to have a single task which would take care of all the deploys(Data and Open). I know this might differ from requirement to requirement. But still, would like to know what is the recommended way to handle this kind of requirements,

Adam Stoller

Hi,
I have always had this question, that, if it is possible for me to incorporate multiple functionalities in a single external task the should I have only one task in my workflow or I should bifurcate the functionality in two and have two tasks in my workflow. For eg, If I have to do data deploy and OpenDeploy and If I am using WFM then should I have one External task where I would call the DD script and then make use of some Deploy Task(or another external task) for the OD.
What is recommended?
Please Guide.

TIA

I think you chose a bad example, as DD should generally be run from within the OD process to provide true transactionality (which is usually desired) - Perhaps a better example is:

If you need to generate HTML pages from some DCRs and deploy those pages to a web server - should you use one task or two?

My preference would be to try to use one rather than having back-to-back externaltasks, the rationale is a bit mixed:

over the long run.From a newbie development perspective where you want to try to use as much OOTB stuff as you can and avoid having to actually write code - the answer is the opposite - if there's an OOTB piece for part of what you want to do - split things up so that you can use the OOTB piece and write less custom code.So - it's more a matter of perspective and personal preference. I think that if your choice is between writing a 10-task job and a 50-task job (that do the exact same thing) - you're better of learning how to write it as a 10-task job in the long run. If your choice is between writing a 10-task job and an 11-task job - it's a coin-flip and doesn't really make much of a difference which way you go.

saurabh4984

Thanks for putting some light. I always had this question, but not now. Smiley Happy