Boolean operator "OR" / Condition Tags

Hello,
can anybody imagine a publishing-surrounding, in which it would be appropriate to use the "OR"-Operator?
If you can't imagine such a surrounding, please let me know too.
Best regards,
Klaus

Sure. I can come up with several real world examples, here's one. Imagine a cascading level of privilege for published material - Unclassified, Classified, Secret, and Top Secret. I have all of these levels represented in my repository and I use conditional tagging to mark the content appropriately.
Because the level is cascading, each security level can view its own level and all those below it. For example, if I have Secret clearance, I'm also allowed to view Unclassified and Classified material. So, to publish for Secret-level users, I use a conditional logic of including content that is tagged for Unclassified OR Classified OR Secret.
Russ

Similar Messages

Error message when trying to delete a conditional tag.

When attempting to delete a conditional tag, the following error occurred and then the program closed down:
0x00ca1940/ 0x00000000
Anyone come across this error. In addition, I have had similar errors occurred when resizing graphic frames. Once the error occurs, the program shuts down.

Paul,
It might help if you let us know which version and build of FM that
this happened in.
Was the tag still in use throughout the document when you tried to
delete the condition? Did you get any prompts about deleting the
condition?

Text Inset in Container File Loses Conditional Tag

Hi,
(Framemaker 8.0p277,unstructured)
I have a number of books that make use of text inset and conditional text. Some text insets contain conditional text in their source. Then, after the inset is put into the container file, the inset may be further conditionalized. This illustrates the situation:
--- Text Inset ---
This inset was created for end users.
When using function X, blah blah blah
-----End Inset----
The red text indicates an InternalDocComment condition. This inset is then placed into the container file where it has another condition applied, PrintOnly for example. PrintOnly is in blue.
The writer is able to set all this up fine. After placing the inset into the container, she selects the inset and applies PrintOnly. The text inset appears in blue and the InternalDocComment as visible shows the maroon of two mixed colors. The writer saves the file, continues working on the files, then later in the week, the writer opens the container file. The blue color indicator is gone from the inset. When the writer selects the inset and chooses Apply Conditional Text, the Conditional Text dialog shows the current selection is Conditional (radio button) but no tags appear in the In portion of the dialog.
I've tried using spacer paragraphs in and around the text inset to see if we can get the conditional tag to "stick" but nothing is working.
Has anyone run into this before?
TIA,
Mary

I use a lot of conditional text and insets but within a structured document. I have noticed that FrameMaker does not always do what one thinks it does. For example, copy a piece of unconditional text and paste it in the middle of conditional text and the pasted text remains unconditional. Each time you open the document, FrameMaker updates the text insets. In your case, it is updating a text inset that is on the whole unconditional. So, my guess is that it bringing it in as unconditional, much like the copy and paste example above. You might test this by creating a small document with the inset and over conditioning, saving it in the mif format, opening the mif file, and looking at how the conditioning is applied. Then save the Frame file, open it, save as mif, and repeat the above. If the containing file conditions DO hold up, then try removing the conditioning within the containing file and reapplying it; this may help to clear out some bad conditioning.
I vaguely recall trying to conditionalize a text inset within the containing document and had problems. I cannot remember what exactly the problems were. My solution was to do the conditioning within the inset file itself. So, if the text inset is always to be conditionalized in the containing document, then do the conditioning within the document itself.

Conditional tags displaying incorrectly in printed document output

I have a project that has several conditional tags. When I generate the project in Flash, the flash output displays the conditional tags correctly; however, when i generate the project as printed documentation, the TOC displays additional topics that are outside of the conditional tags defined to display. I have checked the defined outputs for both the flash and printed documentation and they are the same/correct. I use to work on RH6 and never had this issue until i converted to 8. The defined conditions have not changed since the conversion. I have uploaded the 8.01 patch and the issue is still present. Can someone please assist?

If a project has ten topics with all ten in the TOC and two have tags applied, when you generate the help eight topics will be generated and the TOC the user sees will show eight topics.
Now switch thinking to printed documentation, the first time you create it that TOC will show the same ten topics but the document will again only contain the eight untagged topics.
That assumes in both cases you use a build expression that excludes the tags.
If I have understood you correctly that explains why you see ten topics in the print layout but only get eight in the document.
Note too that if you later add items to the TOC for the project, they are not automatically added to the print layout as well. After the first generation of the printed documentation, the contents are no longer synchronised.
Does that cover what you wanted? If not, tell me where I am not following you.
See www.grainge.org for RoboHelp and Authoring tips
Follow me @petergrainge

Best way to conditionally tag for translation from English to Spanish?

Is it best/more efficient to conditionally tag for translation from English to Spanish in structured FrameMaker or in Robohelp?

This is more info gathering at this point, full requirements are not yet defined. Definitely want the RH help translated; might also need the FM book translated, but not sure.

RoboHelp 6: Conditional Tag Issue

It seems that RoboHelp 6 will not publish my project
correctly if there are more than 6 conditional tags applied.
Help?

Hi. I wonder whether the issue here may be the length of the
conditional build tag names here. Although there is no limit in the
number of characters that can be given to a tag, there is in the
conditional build statement you specifiy in your single source
layout. The limit is 255 characters INCLUDING your NOT/AND/OR
operands. If you have long tag names you'd be surprised how quickly
this 255 character limit gets used up.

Problem in Conditional tag

Dear friends,
I am using conditional tag feature on one of my topics in robohelp and the topic is getting excluded from the output. However, the numbering in TOC doesn't change. For example,I have the following sections in my help file:
1.1 A
1.2 B
1.3 C
If I apply CT on 1.2 it is excluded from the output but the TOC appears as follows:
1.1 A
1.3 C
1.2 is removed but the numbering is still the same.
Can anyone help me in solving this problem. The numbering should also get modified in the TOC like:
1.1 A
1.2 C

Is the document going to be updated regularly and you are going to repeatedly import it into a new project? If it is, then maybe linking would be a better option.
You wouldn't necessarily have to have two documents. Create two documents, one with the numbered headings and one without.
When you want to update Rh, you use Word's style organiser to apply the un-numbered headings. Then you switch back.
Of course, you need to check with product management that not having numbering in online help is OK. Better still, challenge why do you need that legal type numbering at all. Sometimes it is because developers like that style of numbering too but they are not the users of the help and documents.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Using Multiple Conditional Tags with Multiple WebHelp Outputs

I have a project that I have created for a web application. Within the web application, there are 3 types of customers (Commercial Accts, National Accts, and Tier 1 Customers).
I have tagged each help topic that is associated with the help topics I have created.
Then, I created 3 webhelp outputs and 3 TOCs for each customer type.
My goal is to publish the project, where each customer type has their own generated output. Doing it this way, what is listed in the TOC help topics for each customer type is not displaying correctly.
Example: National Accounts TOC
What is generated:
I have tagged the help topics within the TOC to the appropriate conditional tag. Please help. Any advice? I can also be reached at [email protected]

I have a project that I have created for a web application. Within the web application, there are 3 types of customers (Commercial Accts, National Accts, and Tier 1 Customers).
I have tagged each help topic that is associated with the help topics I have created.
Then, I created 3 webhelp outputs and 3 TOCs for each customer type.
My goal is to publish the project, where each customer type has their own generated output. Doing it this way, what is listed in the TOC help topics for each customer type is not displaying correctly.
Example: National Accounts TOC
What is generated:
Please help. Any advice? I can also be reached at [email protected]

FM 9: Cannot apply conditional tags

I've been able to create conditional text tags, apply them, and see the conditional indicators fine in several documents using FM 9. Recently, in a new book, I'm unable to apply conditional tags. I believe I've figured out the new UI, since conditional tagging has worked before. I can create tags and configure them fine, but when I apply them to text, a table, graphic, etc. nothing happens; the text remains unconditional.

What specific version of FM, as shown in Help > About? What O/S and service pack level?
Does FM's built-in Comment condition work for you?
As a test, I'd suggest creating a small test file, create a new condition and apply it to some easily searchable text, e.g. "zzxy" or something, and also apply FM's built-in "Comment" condition to another piece of text, then saving the file as MIF. Then look at the MIF with a text editor, or the excellent freebie MIFBrowser,
http://www.wideman-one.com/gw/tech/framemaker/mifbrowse.htm
and search for the text. You should be able to see whether the condition(s) have been applied to the text correctly (or not), and also see how the conditions themselves are defined in the Condition Catalog entries.
Sheila

Aggregation Befre Calculation with Boolean Operator (BW3.5)

Dear All,
Here I am trying to create a 'Calculated Key Figure' with some logical expression to verify the value of other columns(ie: stock value = 0, market value = 0...etc) and I would like to calculate the result 'Before Aggregation'; Somehow, the calculated key figure with Boolean Operator can not be chosen as 'Before Aggregation'. I tried to create 2nd CKF to include the 1st CKF so that I am able to select the 2nd CKF as 'Before Aggregation', but the result just dont seem to be right.
Any Idea to do this kinda calculation? Thanks a lot.
B.R
Charlie

Instead of creating a calculated Key Figure, create a formula in the query and try whether it is giving a desired output??

Formula string with boolean operations

Hello all,
I created sample logic to do Boolean operations with string.
Example:
(True or false) && False = false
False && True || false = false
Note: Syntax should not be any error (like wrong brackets/extra and/or.
Can anyone tell me is these is any way to optimize this code?
Munna
Attachments:
Formula String to Boolean operations.zip ‏30 KB

I figure there has to be a way to get to a formula node by way of scripting. So I started playing around.
See this.
Now this is just a VI that is basically operating on itself and shows the classes and properties do exist.
I think for your situation, you would need to dynamically create a new subVI. Run scripting code to generate a formula node, the inputs and output node to the formula, controls and indicators to link to those nodes along with the wiring connections. Then place the formula expression into the formula. Then dynamically call the VI (may need to save it first) to send it your values and return the output.
It seems like it would be a lot of work, but certainly doable.
Attachments:
Example_VI.png ‏34 KB

Conditional tag identifier in Word?

I am looking for a possibilty to define conditional tags in my connected Word documents via the Word style-definitions. Does anyone know whether that is possible an how?
Could not find any hint in the documentation.
Thx!

I've just found a reference to the following methods for applying conditional text in Word:
* Styles with hidden text using different templates
* "includetext" fields that take content from different sub-documents
* Macro-controlled conditionals
* The IF field
I have no experience of using any of these though. I have also not tested whether these would come across into the RoboHelp output when you update the link. You'd also have the issue of training your users on how to set this up and use it. It doesn't sound like a totally straightforward end user task.

Porting X5 to R9 and conditional tags

Hello,
I am trying to port conditional tag information from RoboHelp
X5 to R9. I can already port RoboHelp X5 content to R9. However,
with our current process the conditional tag information is not
ported. After I have ported the content and I run the report tool,
no tag information is displayed. I made sure that I selected
conditional tags in the topic properties, options section.
Does anyone know if there is a specific RoboHelp X5 file that
contains this information? Can I copy that file over somehow so
that when I run the report tool in R9 it will show each topic and
the tags that are applied to it?
Currently the way we port is by creating a new project in R9
and then copying the files .hhk and hhc from the X5 project into
the new directory. I'm going to test and see if by copying the
rhbuildtag.apj file into the new project if that will reestablish
the build tag information in the reports section.
Thanks,
Michael Randall

Hi Peter,
Thanks for the quick response. I was talking about RoboHelp
9.2 when I mentioned R9. I tried your suggestion but it didn't
work. After I recreated the same build tags RoboHelp did not
automatically register the tags to the topics.
After I created the tags, I saved the project, closed it, and
then reopened it in hopes that that might trigger it.
I then tried to generate a report hoping maybe that would
work, but still no luck.
I'm wondering how the tags stay assigned to the topics after
they are applied. I don't see a special file that links them per
topic.
Any other ideas?
btw, I've seen and used your web site. It was very helpful
when I was trying to figure out what was wrong with the baggage
file features in X5
Thanks,
Michael Randall

Errors trying to apply a Boolean expression for conditional text

I have been trying to create some Boolean expressions to filter conditional text, with mixed results. The Boolean expression is three conditions separated by ORs followed by four conditions preceded by AND NOTs. When I apply the expression, FrameMaker exhibits and error and has to quit. The numbers in the error message are:
9004, 4908044, 6134440, 5459515
The hidden log file appears to be nothing more than a stack dump.
Do the numbers listed above indicate anything?
Are there any known limitations on how long a Boolean expression can or should be? One expression with one fewer OR worked.
Does there need to be a space between an AND and a NOT? The builder does add one, so I assume it is not necessary.
Does anyone have some general rules of thumb when working with Boolean expressions for conditional text?
Thanks,
Van

Van,
The error values are meaningless to users. However, please do send the logfiles to the [email protected] address.
As far as conditionals go, the general rules are that conditon names must be quoted and that if your ar using the NOT, it must run together with the AND or OR, e.g. ANDNOT ORNOT.
There's an articel in the Developer Connection on using the boolean operators at http://www.adobe.com/devnet/framemaker/articles/fm8_single_sourcing.html
Perhaps if you posted the condition that caused the crash, someone might be able to spot an error.

Conditional Tag - Under Construction

Hi,
Have pages not within the TOC or linked to, but still come up
under the Search results. If I do not want these pages to be
searchable, do I apply the Under Construction Build tag, or could I
make it Status > Ready for Review ?
Thanks!

You are misunderstanding what topics go into an output. All
topics go in except those that have a conditional tag that gets
them excluded via the build expression. The fact they they are not
in the TOC and have no links to them is irrelevant.
If you apply a build tag to exclude them, they will not be in
the output but it seems your goal is to have them in the output but
not searchable. Snippet 94 on my site will help you with that.
The Ready for Review status does not exclude topics.
I suggest you experiment in a dummy project before setting
things up in your real project.

Boolean operator "OR" / Condition Tags

Similar Messages

Maybe you are looking for