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

Does anyone use Visual Annotate?!

rsearle

I just found out that Visual Annotate doesn't work for DCR's. Does this seem ludicrous to anyone? Has anyone found a good way to use workflow to annotate DCRâ€™s using their generated HTML?

Find more posts tagged with

Comments

Migrateduser

It doesn't seem so ludicrous if you consider that it's mostly intended for users that are not even technical enough to be using DCT's in the first place.

We're using it for several groups -- one of them is Legal, where they just want to mark up a piece of generated content and send it off to someone who will make those changes in the DCT. Once the changed DCR is generated, it will replace the older copy, but the annotations will still be easily recoverable, allowing an approver to see that the changes took place.

Does that make sense?

What is your intended use for VA?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Migrateduser

It doesn't seem ludicrous to me. There's no presentation in the DCR, so I would expect there to be anything to draw on. OTOH, I guess there's no major technical reason not to be able to do the same thing with the DCR editing screen that you do with the generated page, so you could probably put in a feature request for it if it bugs you that bad.

There are enough other serious problems with VA to push that one way down toward the bottom of the list.

Your anticipated solution is correct. Have the users generate the page and the reviewer can annotate it. All of our HTML content is produced by templates and all of our workflows use VA. I don't have a sense yet of whether the users are actually making use of it or not.

rsearle

I'd like to have editors edit the DCR and reviewer be able to annotate the generatedHTML, but I don't want it to be too cumbersome.

Is there away to automatically add the generated HTML to the workflow -- and if so, how is this generated HTML related to the DCR in which is originated?

Does it have to be added to the workflow?

Migrateduser

The generated HTML files are related to the DCR and DCT because of the extended attributes set on the generated file, specifically TeamSite/Templating/PrimaryDCR, TeamSite/Templating/PrimaryDocumentType, and TeamSite/Templating/PrimaryPT. As far as adding the generated file automatically to the workflow, you might prefer to start the workflow with the DCR and have an external task generate the file, and then attach.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

nico

bummer to see that it has to be part of a workflow to work, wish it was easier to implement as well. we are not using it yet but would love to if we could figure out how.

reddyl

VA can be enabled to annotate the attached files to the workflow review process. I have used it and found it to be use full for review process. VA does not work that great with flash files.