Defining CDS Annotations for Metadata-Driven UIs
Metadata-driven UIs are dynamic UIs because metadata, namely CDS annotations in this context, are stored in a repository and can be retrieved from the client as needed. CDS annotations depend on the UI in which they are supposed to be used.
UIs might differ from user to user. Even though if, for example, three different users use the same application, each of them might have different permissions or different preferences, which results in different UI perspectives. Users might want to personalize their UIs and see different columns in tables, for example. CDS annotations offer default views for modelling UIs, however, CDS annotations can be overruled by personalization preferences.
The following chapters inform you about CDS annotations that you can use to define metadata-driven UIs, and answer the following questions:
- How can I define the title of a field or a table?
- How can I define the columns of a field or a table?
- How can I define fields for filtering?
- How can I define the header of an object-page floorplan?
- How can I define the body of an object-page floorplan?
- How can I group fields?
- How can I expose elements to UIs?
- How can I overwrite default labels?
- How can I position fields?
- How can I prioritize fields?
- How can I define charts?
- How can I visualize criticality?
- How can I visualize trends?
- How can I visualize criticality based on trend calculation?
- How can I visualize a person responsible and a reference period?
- How can I use the dataField type #AS_DATAPOINT?
- How can I define a contact?
- How can I define navigation between screens?
- How can I define navigation to external web sites?
- How can I define navigation based on actions executed on semantic objects?
- How can I define actions?
- How can I display fields in a text area?
- How can I mask fields?
- How can I hide fields?
- How can I define interaction between annotations?