Related terms
Implementation classes (collectively called an implementation class layer) define the extension, reuse, and specialization of assets in a framework class layer to meet the business requirements of an enterprise's organization, division, or organizational unit. For example, you can build two division-level implementations — business auto loan and personal auto loan — on an organization's auto loan framework layer.
Typically, cases related to application processes are instances of case type classes that belong only to the implementation layer.
Organization classes (collectively called the organization reuse layer) contains assets that need to be reused for business-wide business logic (such as standard properties, decision tables, and service-level agreements) and enterprise-wide data assets (such as classes and rules for data stored in the system, and classes and rules for access to data in external systems, via connectors). In most configurations, your implementation and framework layers inherit (by pattern inheritance) from organization classes.
For example, the MyCo enterprise wants to reuse the property that holds an employee's serial number on an enterprise-wide basis, so that the various applications used by that employee across the enterprise can consistently rely on the same serial number property for the same employee.
When you create an implementation application using Application Express , you specify a built-on framework layer and an organization class layer.
Use the Inheritance option available on the Application Explorer to identify the inheritance relationships among these classes..
In most projects, you do not build on implementation applications. By default, they do not appear in the Built on Application drop-down list Application Express, Step 1. You can override this behavior by clearing the Do not show this application as a built-on choice in App Express check box on the application rule's Documentation tab.