Object definition scope

• Record definitions
• View definitions
• Process definitions
• Rule definitions
• Named list definitions
• Association definitions

You can define the scope to either limit the use of definitions within the same application or allow the definitions to be used outside the application. Defining the scope allows you to control the usage of the definitions by other developers or consuming applications.

Definition scope is of the following types:

• Application/Library
• Public

The following table provides the details for each of the types:

Guidelines to change the scope of the definition

The information in the following section helps you to decide when to change the scope of the definition:

• You can always change the scope of the definition from Application/Library to Public.
• After you release your application or library, ensure that you do not change the scope of the released Public definitions in the next version of your application or library.
• If you have not released your application or library, you can change the scope of a definition from Public to Application/Library. However, in this case you must export and redeploy the application (or library) and any other dependent application (or library) after the development to ensure:
  • No other definitions outside the deployed application or library have used the Application/Library scoped definitions. The deployment fails, if the Application/Library scoped definitions are used by definitions outside the deployed application/library.
  • Customization option is set to "Not allowed" for all the Public scope definitions that used definitions for which you changed the scope from Public to Application/Library.

Where to go from here

Making definitions available for customization