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

generate and deploy files using dcr associated in a workflow

abhishekv

Hi All,

I am a newto teamsite and workflow modeller

i want to generate file using dcr associated in a workflow (workflow configured for submit event) and deploy these generated files to server.
How can I achive it using workflow modeler.

I am using TS 6.7.1 Workflow Modeller

Find more posts tagged with

Comments

kaalraa

Hi All,

I am a newto teamsite and workflow modeller

i want to generate file using dcr associated in a workflow (workflow configured for submit event) and deploy these generated files to server.
How can I achive it using workflow modeler.

I am using TS 6.7.1 Workflow Modeller

Thanks
Abhishek V

You need to create a workflow with minimum of 4 tasks - Select DCR File; Generate and Submit Files reading values from DCR; Deployment task and End Task.

Still, if you need more info, please elaborate more on your requirements.

Pawan

You need to create a workflow with minimum of 4 tasks - Select DCR File; Generate and Submit Files reading values from DCR; Deployment task and End Task.

Still, if you need more info, please elaborate more on your requirements.

In addition to the above you have to implement the failure transition as well, on submit or deployment failure. If you do not track this, then your flow may get stuck for unknown reasons.
You can even implement the successful deployment notification as well.

Adam Stoller

You need to create a workflow with minimum of 4 tasks - Select DCR File; Generate and Submit Files reading values from DCR; Deployment task and End Task.

Still, if you need more info, please elaborate more on your requirements.

The selection of the DCR is presumably happening before the instantiation of the workflow - since it was clearly stated this is a submit workflow.

I'd say the minimum would be two tasks - but the norm would be four:

The above all assumes the complete lack of a review and approval process, explicit setting of metadata, and any number of other options (e.g.: email notification ... which could be subsumed by the custom script(s))Since scripts are involved - you need to be comfortable coding them - either in Perl or Java -- or hire someone to do it for you.

abhishekv

Thanks for your prompt response.

Adam Stoller

In addition to the above you have to implement the failure transition as well, on submit or deployment failure. If you do not track this, then your flow may get stuck for unknown reasons.
You can even implement the successful deployment notification as well.

Good point - that could easily take it from a 2-4 task workflow to a 4-6 task workflow (again, minimums)

nipper

In addition to the above you have to implement the failure transition as well, on submit or deployment failure. If you do not track this, then your flow may get stuck for unknown reasons.
You can even implement the successful deployment notification as well.

Not just Deployments. Failure task for the Generate as well.

Also, use timeouts for all external tasks. If they do not complete in a reasonable amount of time, go to the admin fix task. I use 1 minute for email timeouts, 30 minutes for my generate HTML task. 15 minutes for deployments.

One final note, for your generate HTML task, if your DCR includes images, I attach those images to the job as well.

Andy