MadCap Software Forums

Hello All, I'm wondering if I'm missing something obvious.

When reviews are received from others who have edited the content of a review package using contributor, the tracked changes are all displayed fine when I'm doing the compare, and then subsequently accepting the new version into Flare. But when I accept the document Flare forces me to "accept all changes" within the reviewed file, which means that who changed what, where, and why get lost when I merge the file into the main project.

Is there a way to retain these tracked changes? The button in Flare "Track changes" is greyed out unless you actually have a topic open, it doesn't seem to be a setting that can remain on for the project as a whole.

Have I missed a setting somewhere? Is there an easy fix for this?
When a finished document needs to go through compliance for sign off, they need to see all of the changes - but currently these exist in multiple versions of the review packages (which is cumbersome to check for this purpose), rather than the single doc.

Any ideas?
Thanks in advance.

Welcome to the forums!

Unfortunately, I don't think Flare can behave as you'd like. What you describe Flare (and Contributor) doing is as designed. I don't know of a workaround for your workflow, using Contributor. (There might be a way using Flare + Central, but I'm new to Central myself and so cannot offer any advice at this time. I just know that multiple reviewers can review the same file in Central, instead of there being multiple instances of a file with each reviewer's comments and changes.)

Anyone else got ideas to help our new friend?

Hello, and thanks!
I thought that might be the case - but I wanted to make sure I wasn't missing a button somewhere!
If this is normal operation, then at least I know and can figure a way to work with it.

Julia

I edited my original post as you were posting, so please go back and reread mine for an additional idea.

Hi Nita, thanks again. Central will be the next thing we trial out, so it may help with this issue. I'll figure it out!