C:\DITA\WKFS_oXygen_Files\fragments\webhelp.fragment.head.xml
Jump to main content C:\DITA\WKFS_oXygen_Files\fragments\webhelp.fragment.before.body.xml

# Add a Condition to Check for Highlighting in the Transaction

The best practice to implement a features in a signature area is to use a condition and cooresponding flag in the transaction being processes. You can add the feature without the condition and this will permanently enable (or turn on) the signature feature(s) selected. The condition could be written to test any transaction field.

Before you define the fill feature with a color attribute, you must add a condition to the document and include a new element, EnableHighlight, in the condition. The EnableHighlight element, when present at the document level in an REQ, activates the SignatureHighlightColor attribute. If this element is not present in a document, highlighting is disabled (even if the SignatureHighlightColor attribute is defined.
Note: Adding the EnableHighlight element at the document level outside a condition results in highlighting being permanently enabled in the document, not in the transaction. This is not the suggested best practice.
To add a condition for this purpose, using the Outline Editor perspective, select the target Document element in the requirements file and right-click to add a Child Element. In the right-click menu, click Condition. In the condition, add the PTR for the condition to check for the HighlightSignatureIndicator to be enabled (on/true/yes). The condition holding the EnableHighlight element evaluates the transaction to always include highlighting when the condition (true) is met. The PTR look like: `IF /TxnHighlightSignaturesInd = '1' THEN INCLUDE ENDIF`. When the Condition test is true, the INCLUDE command enables, or turns on, the elements in the condition.
C:\DITA\WKFS_oXygen_Files\fragments\webhelp.fragment.after.body.xml