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

how to attach files to workflow without disturbing workflow configuration files.

sowju

Is it possible that by submitting DCR the relative .js file generated will also be submitted to workflow ???

Is this can be done through presentation template???

Find more posts tagged with

Comments

vpatel

Is it possible that by submitting DCR the relative .js file generated will also be submitted to workflow ???

Is this can be done through presentation template???

Which .js file are you talking about?

Adam Stoller

Which .js file are you talking about?

For that matter, which workflow are you (sowju) talking about? Is this a TS workflow or an SP workflow?

mart2001

Your dcr generate js files? If you put some logic into your presentation templates, I am sure you can get the js files and then add those files to the workflow.

Is it possible that by submitting DCR the relative .js file generated will also be submitted to workflow ???

Is this can be done through presentation template???

Adam Stoller

Your dcr generate js files? If you put some logic into your presentation templates, I am sure you can get the js files and then add those files to the workflow.

Huh? Why would the PT know anything about a workflow?

Lozza

You've not really been explicit with what you're asking, so I've taken a guess. I'm assuming that you're generating an HTML file and a Javascript file from a DCR, and want to submit & deploy both together.

My usual favoured method would be to allow your users to submit just the DCR through a "tt_data" workflow, bypassing the manual generation. The first task in the workflow could be an external task which runs the iwgen CLT to generate the HTML and JS, and use $TASK->AddFile(..) to attach both files to the workflow job. Later workflow tasks, e.g. for submitting and deploying, and any further steps, would then operate on the DCR, the HTML file and the JS.

However if you are expecting your users to generate and submit the HTML files manually, there's an alternative method you might like to consider. You can set extended attributes during generation with the iwextattr CLT. These attributes could list associated files which you want the workflow to attach. The first task in your workflow can check for these extended attributes, and attach the files to the job. The subsequent deployment task will then pick the JS file up as well as the HTML file. I don't like this as much, because it's more for the editors to do and get wrong, and the iwextattr CLT can be quite intensive if you're doing it a lot.

Lots of food for thought there, some of it rambling and unclear, but hopefully it's enough to get you going.