Skip to main content
Known Participant
September 26, 2013
Question

FM Conditional Build Tags Not Processed Correctly in RH

  • September 26, 2013
  • 1 reply
  • 2481 views

I am using TCS 4, fully updated.

I have Frame books that are linked to Robohelp projects; in the RH project FM Conversion settings, I have Apply FrameMaker Conditional Text Built Expressions selected.

In FrameMaker, I have the conditional text set the way I need it, and the content displays correctly.  Two CB tags are used in the content; we'll just call them A and B.  In Frame, CBT A is displayed.  When I update the project in RH, I get CBT B instead.

I then set Frame to display CBT B.  This time, RH correctly displayed CBT B.

Just to try an eliminate random weirdness, I set the entire tst file to unconditional.  It ALL displayed in RH.  But then I re-applied the two CBTs.  Back to square one.

Getting very frustrated w. TCS4.  Never had this problem in earlier versions.

Does anyone have any suggestions?  An option of last resort would be to unselect the Apply FrameMaker Conditional Text Built Expressions option and process CBTs in RH; it appears to work, but would make managing the projects--particularly context IDs--maddening. I prefer to see the content before it's generated.

Does anyone have any ideas?

This topic has been closed for replies.

1 reply

Jeff_Coatsworth
Community Expert
Community Expert
September 26, 2013

What if you set “A” in FM; updated the book(s), then did a “Force Update All” in RH? Does that have any impact?

Known Participant
September 26, 2013

That’s my standard procedure:

In Frame:

Set Conditional build Tags for Book

Apply

Update Book.

Save

Got to RH

Confirm that the Apply FM Build Expression is set

Force Update All

I noticed the problem after doing a Force Update All; I did subsequent testing using a single file. Sorry I didn’t make that clearer.

Jeff_Coatsworth
Community Expert
Community Expert
September 26, 2013

No problem – I’m an import guy myself, and I send it all over to RH & then apply the CBT at the time of WebHelp generation. To eliminate a link/import bug, you could try an experiment with a new blank project – set one up and use the settings.isf from your real project, then confirm the Conversion settings and import it all in – then have a look if any “B” stuff got in.