Framemaker 2020 -- Bug 9622 now 1 year old and not fixed - Product default conditional tags

[cheryls1730789]

On 1/29/2021 I entered a bug about 2 default conditional tags (which cannot be removed) in FrameMaker 2020:

FM_PDF_Comments_Highlight

FM_PDF_Comments_Underline

Where I work we heavily use conditional tags and having 2 that cannot be removed is not acceptable (which is why we have remained on FM 2019). I have posted about this roughly 5 to 6 months ago where I was told it would be in the next release, but my bug is still listed with a status of Open.

The bug has 18 votes from other users who also want this fixed. How many people have to vote for this before this gets fixed?
If others would like to vote for this, go to Adobe's tracker at:
https://tracker.adobe.com/

and look for bug 9622

thank you for those who have voted

[shalomb61686619]

I added my vote, but why is the Tracker site so slow??

[cheryls1730789]

Thank you for voting.  No idea why the site is slow. That would be an Adobe question.

[shalomb61686619]

Of course. But it is always slow.

[K.Daube]

IMHO because there are to many entries in the bug base...

[shalomb61686619]

Because there are too many  bugs in the products?

[Barb Binder]

I would like to vote for this (because it is a problem) but not finding it. Can one of you share the link?

~Barb

[cheryls1730789]

Barb,

Go to 
https://tracker.adobe.com/

and then search for bug 9622. It should come right up.

Thank you for voting for my bug.

Cheryl

[Jeff_Coatsworth]

Here's the link I have Barb - https://tracker.adobe.com/#/view/FRMAKER-9622

[Barb Binder]

That's what I needed, Jeff. Thank you. No idea why my search didn't work. 

~Barb

[4everJang]

To me it looks like these are used for the PDF review feature in FM, which would make it impossible to remove them from the product, as that would remove the option to import PDF review comments.

If you are not using PDF reviews, the tags might be there but no content will be marked with it, which IMHO should not cause any problem at all.

I will not vote for this as I believe this is not a bug at all.

[K.Daube]

You may be right Jang, it may not be a real bug, but at least it is a very annoying feature. IMHO things which are not required by the user should be hidden. Especially when cleaning out older documents things like these raise a number of questions - whether they can be deleted or not.

With the varibles we have the concept of System Variables (can not be deleted) and User Variables which can be deleted. So it should be possible to flag these alements as 'system use' and hide them in the list display.

[frameexpert]

They don't need to be removed from the product; they just need to be hidden in the interface because they are for use by the PDF review feature and not intended to be manually applied by the user.

[4everJang]

Then it might be better to fill out a feature request, not a bug report. It is not a bug and when it is filed in the wrong category it may end up being ignored completely.

[cheryls1730789]

Ok.  I just checked and PDF Review is in FM 2019 that I use. However those conditional tags do NOT display in FM 2019, therefore they were hidden in that version. They are not hidden in FM 2020. Therefore I consider that a bug.    I do both documentation and program testing here. And where I work that is definitely considered a bug.

Sorry. I don't know what Adobe considers that.  Feature requests are normal new items.

[frameexpert · Accepted solution]

I would consider this a bug. The following conditions are for FrameMaker internal use only and shouldn't be available to the user. They are not displayed in the Condition Tags panel.

FM8_SYSTEM_HIDEELEMENT
FM8_TRACK_CHANGES_ADDED
FM8_TRACK_CHANGES_DELETED

I don't know anything about the PDF comment feature. Are there any cases where you would manually apply the conditions below to FrameMaker content? If not, they should be hidden as well.

FM_PDF_Comments_Highlight
FM_PDF_Comments_Underline

Here is the ExtendScript code I ran to write all of the condition formats in an active document to the Console panel:

#target framemaker

var doc, condfmt;

doc = app.ActiveDoc;
condFmt = doc.FirstCondFmtInDoc;
while (condFmt.ObjectValid () === 1) {
    Console (condFmt.Name);
    condFmt = condFmt.NextCondFmtInDoc;
}

[LinSims · Accepted solution]

They can hide the conditions for tracking changes unless you have track changes on. They should be able to hide these, too.

In fact, they used to. The import comments from PDF has been a part of FM for several releases now, but those conditions being visible at all times didn't show up until FM2020.

[Sameek5F86]

Hi All,

We were not able to prioritize this user experience issue - sincere apologies for the same.

We will address it in our next release (FM 2022).

Thanks

Sameek