Legacy platform

Customizable components

Customization of UI components and behavior logic.

You can develop and deploy a business-relevant application in the shortest possible time. A common customization configuration framework is provided for development and deployment of extensions that work across a set of supported applications. You can either add your own capability or completely replace any existing capability to meet your own unique processes and workflow within the organization.

During differential screen customization process, you can modify the behavior of UI components. You can add widgets, modify widgets, rearrange widgets, and hide widgets on a screen. However, during the process of differential screen customization, you cannot use hot keys or do any application tasks such as search records, modify data, or open windows. However, to do any application tasks, exit the process of differential screen customization.

You can customize an existing application that is installed during runtime without recompiling or modifying the original source code.

Override customization contrasts with differential customization. In override customization, you can completely replace the application-provided screens with custom screens. For more information, see Replace an application-provided screen with a custom screen and Copy and customize the application-provided screen. Whereas, in differential customization, you can change only parts of the application-provided screens by using the Extensibility Workbench. The changes that are made to an existing component are limited to a particular set of properties. You cannot change the arbitrary properties, and therefore, results in upgrade issues.

Table 1. Customizable components
Component Supported method of customization
Widgets Differential extensibility
Screens Both differential and override extensibility
Wizards Override extensibility
Mashups Both differential and override extensibility
Events Differential extensibility
Note: You must clear the browser cache to view the customization changes. Sometimes, browsers retain the cached data and may not reflect the customization changes, if you are accessing the application by using the URL. In such cases, you must close the application and clear the cache before accessing it again.