Frequently detail screens have API calling actions that only require the primary key of the current entity to be passed as the input. When a detail view is brought up in the user interface, there is always at least one entity key passed to the detail view. This entity key consists of an XML structure containing the attributes that uniquely identify that entity. For example, the entity key of the order entity always contains an attribute for order header key. This entity key is automatically passed to the detail API of that entity. When this type of action is configured on a detail view, no other steps are required to ensure the right input is passed to the API.