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

Submit Workflow Customization... Submit DCR's?

TommyWillB

Currently (TS 6.7.1) when you unlock a DCR-generated HTML file, it asks you if you'd also like to unlock the parent DCR. (That's nice! Very user-friendly.)

Unfortunately, the user is not presented the same option when they submit a DCR-generated HTML file... Only the HTML gets submitted, and the DCR remains locked/un-submitted. (Lame and un-user-friendly.)

This is terribly confusing to non-technical writers, who are the main target demographic of TeamSite Forms Templating.

Is there some way to customize/enhance/extend the out-of-box Submit workflow so that it always also submits the DCR parent of an generated HTML page?

Find more posts tagged with

Comments

hitc

You could just add a task to the workflow that would read the metadata of the html file. Since the html file was generated by a dcr, there is metadata pointing from wich dcr the html page was generated from. So you could just do an unlock and/or a submit of the dcr.

Jamik

You could also add the DCR file to the workflow along with the HTML file so that both the HTML and DCR get submitted to the staging area of your branch then it would also get unlocked just like the HTML file. This is what we do with our xml files when users submit them. when a users selects an xml file we also add the dcr to the workflow but we only send the xml through OpenDeploy task but both get sent through the submit task so both files get unlocked from workflow.

Also the unlocking of the html and dcr file is a relatively new feature (sometime in the 6.x version was when it was added can't remember when exactly) back in the day you had to unlock the generated files and the DCR file seperately the unlock did not unlock both. So yeah, Interwoven eventually gets some userfriendly functionality enabled Smiley Wink

nipper

2 points. 1st, if you have WF set for tt_data, then when someone edits and saves a DCR they are prompted to submit the DCR (and generated content). That is a good practice.

Second, you certainly can add that functionality, esp if you write your own WF. If you use the OOTB wf, that can be added.

Finally, there are cases where I want to submit the generated content but not the DCR. Those are quite infrequent and special cases, but they do happen.

Get your users used to #1 is the best approach.