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

OutputFile Workflow issue

yogesh_bhavarthi

Hi

The output file in a DCR is set using IWPageGeneration.setOutputFile().

If this DCR is edited while it is attached in the workflow and then saved using "finish", will the generated (HTML) output file, automatically get attached to the workflow?

What will happen if the output file is not previously present?

Config:
TeamSite 6.5 on UNIX

Yogesh

Find more posts tagged with

Comments

Adam Stoller

Hi

The output file in a DCR is set using IWPageGeneration.setOutputFile().

If this DCR is edited while it is attached in the workflow and then saved using "finish", will the generated (HTML) output file, automatically get attached to the workflow?

What will happen if the output file is not previously present?

Config:
TeamSite 6.5 on UNIX

Yogesh

No - in the scenario you describe the output file would not automatically get added to the workflow - but if the output file was already attached to the workflow and the page was re-generated during the workflow - then you don't have to worry about re-attaching it.

If you use a standard / consistent naming scheme for DCRs, their output files, and the PTs used to generate them - then you can handle all this programmatically without any issues.