Activities that set application preferences for users

Use application preferences, which are associated either with an operator ID regardless of access group or with the operator ID for a specific access group, to store data in a place that is visible and editable by users who have limited security. Typical end users cannot edit operator IDs but can edit their application preferences, which they can set on their own operator IDs or on other operator IDs.

For example, an insurance claim processor can apply a custom filter to a work list and save it as a preference so that the next time he or she logs in to the application, the work list is filtered appropriately.

You can use the D_pxGetPreference data page to retrieve your current set of preferences.

CAUTION:

Users can read information from and write information to other users' preferences.
Do not store sensitive information as preferences.

Note: When you remove an access group from your Operator ID form, you also remove any preferences that are associated with it.

Use the following rules to systematically set your preferences:

pxSetPreference: Call this activity to set one preference at a time for the current operator ID.
pxSetPreferencePage: Call this activity to set multiple preferences at once for the current operator ID, based on the Page, Page Group, or Page List parameter that you specify.
pxSetPreferenceForOtherOperator: Call this activity to set one preference at a time on another operator ID.
pxSetPreferencePageForOtherOperator: Call this activity to set multiple preferences at once on another operator ID, based on the Page, Page Group, or Page List parameter that you specify.