Configurations and personalizations

When you make configuration and personalization changes, a copy of the Landmark Pattern Language (LPL) source is changed.

Configurations are modifications that an administrator can make. They include changes to the look and feel of menus, pages, and various user interface objects and actions that are associated with a business class. Configuration changes apply to all users.

Personalization changes apply only to the user making the change. For the change to be global, the personalization must be made into a configuration.

• If the LPL is personalized, then the personalization is used.
• If the LPL is configured, then the configuration is used.
• If the LPL has a personalization and a configuration, then the personalization is used.
• If there are no personalization or configurations, then the delivered LPL is used.

Configuration and personalization changes are saved to separate files that are stored separately in the database and are not affected by upgrades. When you upgrade to a new application version, you do not see any new changes that are delivered for the configured or personalized LPL.

Your configuration and personalizations may be affected by a new delivery of the business class. If a configuration uses a field or action that is not available because the LPL was removed from the base delivery, then that field or action is ignored. Run the LPL Version Analysis tool to identify and troubleshoot these types of issues.

See LPL version analysis.