Add or Remove Exposed Endpoints
When your application has many inter-related business objects, you can add or remove endpoints that these business objects expose. Tailoring the endpoints to expose only those that you require controls the size of the metadata file that describes your endpoints and maximizes application performance, both at design time and runtime.
Let’s say your application uses the Employee, Department, Location, and Project business objects, which refer to one other as follows:
Description of the illustration bo-endpoints-edit-relationship.png
With this relationship, the first level of accessor endpoints for the main Employee object (/departmentObject and /projectObject) are included by default in the Employee object's resource definition. Other deeper endpoints are not included. Now, if you want to show the department and location names in a Table of Employees, you need to add endpoints that are not included by default, but which are required to expose this data. For example, you must add the nested /departmentObject/locationObject endpoint (not selected by default) to show an employee's location.
Optionally, if you want to restrict access to employee project information, you can remove the /projectObject endpoint (selected by default).
To select the endpoints you want to expose for a business object: