Show TOC

Adding Field ControlLocate this document in the navigation structure

This topic treats the concept of field control in the context of SAP Fiori application development for transactional use cases.

Field Control in a Nutshell

Field control is a means that you can provide as information to the service on how data has to be displayed for consumption in the SAP Fiori UI.

In general, the following characteristics are relevant when providing field control:

  • Read-only: - Will the user be allowed to change the value of a field (or a node instance)?

  • Mandatory: - Must the user provide a value?

  • Hidden: - Should a field be available for consumption in the UI?

    Note

    We do not cover this characteristics in this topic since the relevant information is provided by...

    • The consumption annotation @Consumption.hidden: true. In such a case, this information is part of the consumption view, not part of the service.

      More on this: Consumption Annotations

    • The UI annotation @UI.hidden:true. The information in this case is in fact part of the service, but not exposed to the end-user.

      More on this: UI Annotations

The field control can relate to individual properties (node attributes in BOPF) or a whole entity (business object node instance in BOPF).

The field control information is either static or dynamic:

  • Static - The field control information is valid for all instances of a business object node, regardless of their state. For example, consider a field PAID in an invoice scenario that is always read-only since it can only be changed by an action, not directly by the consumer after an update procedure.

    More on this: Static Field Control

  • Dynamic - The field control information depends on the state of the node instances. For example, the field COMMENTS should be read-only if the invoice‘s PAID attribute is set to true.
    Note Further information on this topic is not yet available!