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

Maintain Versions

Abishk

Hi everyone,
I have a requirement to maintain the number of versions of the DCR as well as the Output generated xml file.
-->e.g. if the DCR has been submitted twice, the output file must also be submitted twice only.
-->Also when i revert a DCR to, say the 1st version the Output file should also get reverted to the 1st version.
-->I tried using SyncRevert but the functionality isn't working. As in the event doesn't get registered. Refer thread-http://devnet.interwoven.com/forums_vb/showthread.php?t=24805&forumid=11
Any suggestions on what could be the best approach to fix this issue..
Thanks..

Teamsite 7.1 Windows 2003 Platform

Find more posts tagged with

Comments

Adam Stoller

Provide your own custom interface for handling reverts to replace the OOTB one (have fun coding it).

Theoretically, you could have more versions of the DCR than you do generated output file. You could have more versions of the generated output file than the DCR but that's less sensical. Depending on the workflows available and what they do - maintaining a 1:1 relationship between versions of DCR and their generated output should be do-able.

Given that the output file is generated, however, means that it should always be possible to re-generate it - so the fact that you revert a DCR doesn't necessarily mean you have to revert the generated file too - presumably the workflow that you would use to [re-]submit the reverted DCR takes care of the page generation process and thus would overwrite the reverted generated page anyway.

Pawan

May I know the business requirement for this?
Are you planning to do the same thing on preview too?

Abishk

May I know the business requirement for this?

My idea was just to maintain a 1:1 relationship between the DCR and the output generated file. but as adam suggested--

Given that the output file is generated, however, means that it should always be possible to re-generate it - so the fact that you revert a DCR doesn't necessarily mean you have to revert the generated file too - presumably the workflow that you would use to [re-]submit the reverted DCR takes care of the page generation process and thus would overwrite the reverted generated page anyway.

I can always regenerate the file so i guess i dont need to do it. otherwise is can do it always using the Workflow.

Are you planning to do the same thing on preview too?

Well no.. only with the generated files.