Identify the Fields to Be Masked

Your implementation should list every field on every page and XAI service request that requires masking

Classify each field into one of the following categories:

An element that is retrieved by invoking a business object, a business service, or a service script
A field that is retrieved by invoking a page service
A field that is retrieved by invoking a search service
An ad hoc characteristic type's value

Primary keys cannot be masked. A field defined as a unique identifier of a row cannot be configured for masking. Masking a field that is part of the primary key causes a problem when attempting to update the record. This restriction also applies to elements that are part of a "list" in a CLOB on a maintenance object. One or more elements in the list must be defined as a primary identifier of the list. Be sure that primary key elements in the list are not ones that require masking.

Masking applies to strings. Only fields with a data type of String can be masked.

List members that contain different "types". Consider a page with a list that contains a person's phone numbers. You can set up the system so that a person's home phone has different masking rules than their work number. If your implementation has this type of requirement, the list of masked fields should contain an entry for each masking rule.