As discussed in previous chapters, links connect a parent and a child business component in a 1:M or M:M relationship. The usual way to display data in such relationships to the end user is a view with one applet per business component, displaying the parent record on top and the list of child records below. These views are also called detail views.
The following screenshot shows the Opportunity Detail - Contacts View as an example of a detail view:
The view displays one opportunity record on top using a form applet and a list of contact persons associated to the opportunity using a list applet.
When we examine this example further we find the following considerations:
A separate view means additional effort with regard to the administration of access control and responsibilities
End users may only be interested in the information displayed by the form applet but the database has been instructed to fetch the contact data as well, which can impact performance when...