Optional. Complete the Display Options tab to control the presentation of form-level and field-level error messages. You can customize the fonts, colors and image used in field-level messages in the Skin rules. See Skin form Components tab General Errors.
You can also use this tab to configure optional logging of each use at run time of this rule.
> Error Display
Form-level errors are reported against properties not present on the current form. By default, the messages appear in a standard form-error message section. You can display the error messages in one of three ways:
|Custom Error Section||
This field appears only when you select
For an example, see Pega Community article How to create a custom error section in user forms.
Field-level errors (such as leaving a required field blank) are reported against properties on the current form. You can display them in one of two ways:
Keep visible – Leave cleared in most cases. Select this check box to cause the entire run-time work item to scroll vertically as a single unit, except for the button bar and form error area which remain visible at the top.
|Show container icons||Select this check box to display container (header) icons to the user.|
|Enforce CSS minimum width||
Select this check box to enforce the Minimum Screen Width set in the skin. This determines the smallest width to which a user can compress the screen width before text is truncated and horizontal and vertical scroll bars appear. The minimum value provides consistent alignment by preventing columns and text from wrapping.
When the Enforce CSS minimum width check box is selected, the Minimum Screen Width setting, located in the Skin form — Components tab — Layouts — Legacy layouts, applies to all harnesses, regardless of whether the harness contains a Smart layout.
Select to enable auditing of the user forms produced by this harness. Additional fields display.
Enable this feature only if such detailed auditing is needed in your application. Auditing increases the database workload of your application and can produce large volumes of log data.
Complete these optional fields to record each time a user requests the user form based on this harness. Each time the form appears, your application can add an instance of the Log-DataAccessAudit class, to support later compliance auditing, reporting, and analysis. The added instance identifies the date, time, Operator ID, harness, Customer party (if any) and work item ID.
Logging occurs upon initial display of the form; it does not require that the user update any fields. You can create reports on Log-DataAccessAudit instances, or export the data for analysis.