All entities should provide a descriptive flexfield to allow customization. (OMS-74049)
Code a descriptive flexfield as a text item, displaying two characters (width of 0.2"). (OMS-74050)
The prompt associated with the descriptive flexfield is "[ ]".
In a single row block, the "[" is the prompt, and is drawn .05" to the left of the item and centered vertically. The "]" is boilerplate placed .05" to the right of the item, also centered vertically. (OMS-74051)
In a multi-row block, the prompt is "[ ]" drawn .05" above the item and centered horizontally.
The descriptive flexfield is located as the last item in each block on the content canvas. When regions exist, the descriptive flexfield is located after the region (not as an item within a particular region). (OMS-74052)
In exceptional cases, where the aesthetics of the single-row block are compromised by locating the descriptive flexfield last, it may be located elsewhere, but should always appear at the "end" of a group of fields (for example, as the last field of the context canvas fields before an alternative region). Regardless of its location, it is always the last sequenced item of the block.
The descriptive flexfield Forms field should be navigable, but should not allow input. It adheres to all text item standards. (OMS-74053)
Flexfield code will automatically show the concatenated values in the descriptive flexfield Forms field.
Descriptive flexfield uses a user-level profile that determines whether the flex window should pop open upon the user navigating into the field. (OMS-74054)
EXCEPTION: In folder blocks, the flexfield window must not automatically open because this would prevent the user from resizing the field.
At form startup, the descriptive flexfield is disabled if the customer has not activated the flexfield by defining and enabling segments.
If the user invokes the descriptive flexfield before the independent fields of context-sensitive segments are populated, then the following will occur:
If there are global segments, the window will open, and text will display indicating that other context-sensitive fields cannot currently be populated.
If there are no global segments, then no window will open and a message will indicate that the context-sensitive fields cannot currently be populated.
Behavior of the descriptive flexfield window itself :
Any successful navigation out of the window moves the cursor to the next field.
Canceling the window moves the cursor to the previous field.
During validation, if mandatory segments are missing, then flex will issue a message. In the cases where it can be done, the flex window will open automatically upon the user acknowledging this message; in those that it cannot, the user will have to invoke the window.
For information on implementing descriptive flexfields, see the Oracle Applications Developer's Guide.