How User-Defined Rules Work

The user-defined rules option lets you customize the behavior of windows in Solar Eclipse to suit your business needs. To create user-defined rules, you must have the SUPERUSER authorization key assigned. Only those with SUPERUSER assigned can make fields required that normally are not, mask the values in fields for sensitive information if the user is not authorized for that information, or disable a value that you do not want changed.

Example: Required Fields

Many fields in the system are required, but you can add a requirement value to a field that does not normally have that value. This option is used most often in conjunction with changing the background color for a field.

Note: Not all input fields support the Required property. If Required does not display, it needs to be added by Eclipse developers to become an option.

ClosedBefore

ClosedAfter

Example: Masking Values

Used in conjunction with the Disable rule, you can hide the values in the field unless the user has the appropriate authorization.

ClosedBefore

ClosedAfter

For a check box field, the system grays out the check box, but the field name is still readable:

Example: Highlighted Text

By default, fields are only highlighted when the cursor is on the field to make it active. However, you can change the background color on fields, to draw attention to it. This option is used most often in conjunction with making the field required.

ClosedBefore

ClosedAfter

How Do I See What Has Been Modified?

The system provides a log for what has been modified using the user-defined rules.

From the Help menu, select Customized Components on this Screen to view a list of rules applied to the current screen. For example: