Define the look and behavior of your application by setting display options at a
harness level. Display options help you configure error presentation, container
settings, and harness auditing to further customize your user interface.
For example, you can set up a section to display a customized message when the harness
registers an error.
Search for and open the harness that you want to
On the Display options tab, in the Form-level
errors list, define how you want to display form-level
To display errors in a standard section at the top and bottom of the
user form, select Default.
To display errors in a standard section at the top of the user form,
select Top of harness.
To display errors in a custom section that you place in the harness,
select In configurable section, and then, in the
Custom error section field, define the section
that contains the error message.
For example: To display errors in a custom section, select Custom error
section, and then enter the name of the target section, for
If you decide to use a custom section, the standard form-level error section
is not displayed at run time. Therefore, ensure that the harness layout contains
the custom section. Otherwise, the system does not display error
Optional: To display form-level errors even when a field-level error occurs, select
Optional: To cause the entire run-time work item to scroll vertically as a single unit,
select Keep error display visible.
In the Field-level errors list, define how you want to
display field-level errors:
To mark fields with errors with a standard error icon and display error
text in a tooltip, select As image with
To display the error text above the field with the error, select
As full error text.
Optional: To display header icons, select Show container
Optional: To force the harness to adopt the minimum width that is defined in the skin
rule, select Enforce CSS minimum width.
Optional: To record every time that a user requests the form that is produced by the
harness, select Enable auditing, and then define the when
condition for the audit.
Each time that the form is displayed, your application can add an instance of
the Log-DataAccessAudit class to support auditing,
reporting, and analysis. The added instance identifies the date, time, operator
ID, harness, customer party and work item ID.
For harnesses that are the basis of a custom page in a portal, in the
Initialization section, define the behavior of the
harness on load:
In the Visibility list, define when the users
can see the harness.
Optional: To launch a data transform when the harness loads, in the
Data transform field, enter target data
Note: Applications that use Cosmos React do not use
harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.
In the form, click Save.
For example: In this scenario, when the harness registers and error, the UI displays a custom
section. In preparation, you create a customError section that
contains the target error text, and then add that section to the harness. You also set
the visibility in the section to the hasMessages when rule from
@baseclass, which is an out-of-the-box rule that handles custom
error sections. The following figure illustrates the section configiration.