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

regenrating html attach to workflow

rajivgupta

Hi all,

I have a dcr and corresponding html attached in my workflow before going to any of the reviewer.
In the review process of 3 reviewers if any of the reviewer wants to change the DCR , the html should also be regenrated .

Can anyone suggest me any approach for doing that .

Regards,
Rajiv

Find more posts tagged with

Comments

Pawan

...In the review process of 3 reviewers if any of the reviewer wants to change the DCR , the html should also be regenrated ....

The purpose of reviewer should be to review and not to edit. If the reviewer rejects, then the flow should go back to the author or editor and the review process should start again.
Please give your environment details.

rajivgupta

Unix
TS 6.5 sp2

Adam Stoller

Hi all,

I have a dcr and corresponding html attached in my workflow before going to any of the reviewer.
In the review process of 3 reviewers if any of the reviewer wants to change the DCR , the html should also be regenrated .

Can anyone suggest me any approach for doing that .

Regards,
Rajiv

In general, I would agree with Pawan's response - however I have worked on a number of workflow processes in which "editorial reviews" were desired to make "simple fixes" instead of sending the entire process flow back to the content author and going through all the reviews again.

However, the solution is pretty much the same in either case - you need an automated task (externaltask, urltask, or cgitask) that processes all DCRs associated with the job to [re]generate all the output pages from those DCRs and ensure that the output pages are associated with the job.

There's no OOTB task for this - you have to create it yourself because it generally involves a number of customer-specific variables.

The flow, though, should be pretty easy:

(AuthorWork)->(PrepForReview)->(Review)->(PrepForPublish)->(Publish)

The above is a simplistic example - but hopefully sufficient for this thread. The PrepForXxx tasks would be the ones that take care of regenerating the output files.