Skip to content

Files

Latest commit

 

History

History
320 lines (152 loc) · 17.7 KB

header-a05d7fc.md

File metadata and controls

320 lines (152 loc) · 17.7 KB

Header

The following annotation-based properties can be defined on the Header node of an Object Page:

All properties are based on the @UI.HeaderInfo annotation.

If @UI.HeaderInfo does not exist, it is created as soon as one of the properties above gets a value.

If @UI.HeaderInfo annotation is defined in the lower layer, such as service, the values of these properties are marked with the "(base layer)" suffix indicating the value origin. Once changed at least one property value, the complete annotation is copied to the local annotation file and (base layer) suffix is no longer displayed to indicate it.

Type Name/Type Name Plural

String properties describing the main object of the page. Type Name is displayed in on the very top of the Object Page: Type Name Plural represents a plural form of the object name and is displayed as a table header on the previous page. As these properties are mandatory, they are set to the empty string if not (yet) defined otherwise. The properties support internationalization. For more information, see Internationalization (i18n).

Title

Title is a property representing the main object of the page. It is displayed in the page header area. You can choose one of the direct properties of the page entity provided in the dropdown. If you set it to None, Object Page header will not display the title. The default text will be displayed instead. Always define the Title if the Visible property of the page header is set to true.

Note:

The none option is not available if the Title is defined in a lower layer such as service.

Image

  • Adds property ImageUrl with the selected property as a value to the UI.HeaderInfo.
  • Value is a path pointing to string properties of the entity or of a to one associated entity.
  • To remove ImageUrl property, you can select the option None.

For more information on images, see: Using Images, Initials, and Icons.

Initials

  • Adds property Initials with the selected property as a value to the UI.HeaderInfo.
  • Value is a path pointing to string properties of the entity or of a to one associated entity.
  • To remove Initials property, you can select the option None.

Icon URL

  • Adds property TypeImageUrl with the SAP icon text as a value to the UI.HeaderInfo.

    Example:

    sap-icon://accept

  • Value is a string pointing to a SAP Icon such as from the Icon Explorer.

Header actions are displayed in the object page header as buttons. You can maintain the following kinds of header actions in the Page Editor:

Standard Actions

The SAP Fiori elements framework provides standard generic actions such as Edit and Delete by default for object pages in all applications if certain criteria are met. If these standard actions are provided, you can hide them in your application UI by switching on the Hidden property.

Once you have activated the Hidden property using the toggle button, the Hide by Property field is displayed right after it. You can set the condition for dynamic hiding by selecting one of the suggested Boolean properties from the dropdown list. If the selected property evaluates to true in runtime, the button will be hidden, otherwise it will be displayed. You can select None to revert back to static hiding.

Note:

When you hide the Edit button, the UI.UpdateHidden annotation is applied to the entity set of the respective object page. When you hide the Delete button, the UI.DeleteHidden annotation is applied.

Annotation-Based Actions

These actions are based on the following records of the UI.Identification annotation, applied to the main entity of the page:

  • UI.DataFieldForAction with the Determining property set to false or not defined. These actions are performed within the application.
  • UI.DataFieldForIntentBasedNavigation actions are used for external navigation from the current application to a different (target) application, configured in SAP Fiori launchpad.

You can add, delete and maintain the header actions in the same way as described in Table Actions.

Note:

The properties Importance and Requires Context are not relevant for the header actions.

The Criticality property impacts the sequence of the actions in the Object Page header. Therefore, once you change its value from None to Positive or Negative (or vice versa), the sequence of the action nodes in the Page Editor outline view is automatically updated.

You can move header actions to the Form sections based on the same entity, as long as these actions are not semantically highlighted. You can move the actions based on UI.DataFieldForAction to the Footer.

Custom Actions

Custom actions are based on application extensions. For more information, see Adding Custom Action.

Header sections show that the key information on the Object Page entity are displayed in the header area. The visualization of this information depends on the section type.

To add a Header section, perform the following steps:

  1. Click the Object Page to open the Page Editor.

  2. Navigate to the Header section and click the ➕ (Add) icon.

    As a result, a list of section types supported in the page header appears.

  3. Choose the desired section type, respond to the prompts, and click Add.Object Page Header Section

  4. Depending on the section type selected, additional information is needed:

    • Form Section - Label
    • Data Point Section - Value Source Property
    • Progress Section - Value Source Property
    • Rating Section - Value Source Property
    • Chart Header Section - Chart Type. You are prompted for more information depending on the selected chart type, same as for Chart Column.

Once the header section is generated, you can add and maintain its properties in the Property Panel.

Form Section

The Form header section displays a group of fields under the common label. Once you add the Form section, no fields are added automatically. Add the fields you need using the ➕ (Add) icon in the Fields node.

For more information, see Form Section

Progress Section

The Progress header section visualizes the numeric value you chose as an indicator of a progress towards a certain target. You can modify the generated label and a default target as well as define a description for your progress indicator, apply the semantic coloring based on the value criticality and provide a tooltip.

Target initially the progress indicator is generated based on the value you entered and the default target (goal) of 100. You can then modify the target by setting it to a different numeric constant or choose a numeric service property that represents a target. For that, you first choose the target value type and then the desired number or property.

For more information, see the following: Appendix Criticality, Measures and Currencies Tooltip

Data Point Section

The Data Point header section is used to display the single point of the key data. It's typically a number but can also be textual, for example, a status value. Initially, it is generated with a minimum property based on the value you entered. You can then enhance it in the Properties pane with additional features, such as semantic coloring based on criticality. You can also add a tooltip describing the value. If your data point represents a numeric value, you can additionally define the measure or currency for it if this isn't done in the base level.

For more information, see the following: Appendix Criticality Measures and CurrenciesTooltip

Rating Section

The Rating header section displays numeric value you chose with the corresponding number of stars out of the certain maximum (target). Initially it's generated based on the value you entered and default target value of 5. Subsequently, you can modify the generated label and set the target to any other integer number in the properties pane as well as enter a description and a tooltip.

See Appendix for more information on Criticality, Measures and Currencies and Tooltip.

Micro Chart Section

The Micro Chart header section allows you visualizing the numeric properties of your service as micro charts of different types. Initially micro charts are generated based on the minimum required information you entered and some assumed defaults. You can modify some of the generated chart properties as well as define optional ones in the properties pane.

Required and optional properties you can configure depend on the selected chart type.

Note:

You cannot change the type or main value (measure) of the micro chart. If you need to modify one of these properties, just add a new micro chart section and delete an existing one instead.

Radial Chart

Radial chart displays the numeric value compared with the target. Both values you choose when generating a radial micro chart. Then you can choose a different numeric service property to be used as a target in the properties pane, as well as set a description for your chart and apply the semantic coloring based on the value criticality.

See Appendix for more information on Description and Criticality.

Bullet Chart

Bullet chart visualizes the numeric value on a given scale. Besides, the main value, you can display addition ones, such as target or forecast on the same scale as well as set a description for your chart and apply the semantic coloring based on the value criticality.

Target Value

Apart from the main value, bullet chart can also display an additional value as a target. You can choose a numeric service property to be used as a target in the properties pane.

Forecast Value

Bullet chart can also display an additional value to indicate a forecast. You can choose a numeric service property to be used as a forecast value in the properties pane.

Minimum and Maximum Values

Bullet Chart scale is based on the minimum value (by default 0) and maximum value you chose when generating this micro chart.

You can modify the scale of the chart by updating these minimum and maximum values. You can either define these values based on the service properties of numeric type or as fixed number. For that, you first choose the Maximum (Minimum) value type and then the desired number or property.

Criticality

To semantically color the bullet chart according to the value criticality, you can either choose a property with the criticality information or define the criticality information in place. So, first you need to choose the Criticality Source. When set to Property, you're prompted to choose a service property containing the criticality information. When set to Calculation, you have to choose the desired improvement direction:

  • Minimize: low values are considered as best
  • Maximize: hight values are considered as best
  • Target: values close to the target are considered as best Depending on the selected direction, enter the values to be used as threshold for critical and warning coloring.

For more information on setting the radial chart description, see Appendix.

The user can change the order of the sections in the application header. By using the drag-and-drop functionality, drag the required section to a different position within the Header Sections node:

  • When dropped, the records in the UI.Facets collection are reordered.
  • When SAP Fiori application is rendered, sections are displayed based on the records sequence in the UI.HeaderFacets annotation.

Move multiple sections

To move the multiple sections to another position, perform the following steps:

  1. Use the [Ctrl] + [Click] combination to select more than one section.
  2. Drag the selected section to the desired position with your pointer.

To delete the section in the application, perform the following steps:

  1. Navigate to the section node in the outline.
  2. Click the 🗑️ (Delete) icon to open the Delete Confirmation popup window.
  3. Click Delete to confirm the action.

Note:

This action deletes respective UI.ReferenceFacet record from UI.Facets.

Note:

To remove unreferenced UI.FieldGroup annotation, run the cleanup procedure that deletes the unreferenced annotation.

Label

All the Header sections regardless of the type contain the Label property. They can be based on a different annotation properties depending on the section type. For example, the Label for the Form section is based on the Label property of the UI.ReferenceFacet record within the UI.Facets annotation since the Label of the Data Point section is based on the Title property of the UI.Chart annotation. Nevertheless, you can maintain the Label for all the Header section types in the same way. All the other Header section properties depend on the Header section type.

To change the section label, perform the following steps:

  1. Select the required section and navigate to the properties pane area.

  2. Enter a new name in the Label text box. This field defines the text to be displayed at a section label.

    As a result, the section is renamed both in the Page Editor and in the application preview.

See Label Maintenance for more information.

Note:

See Internationalization (i18n) for translation if not yet there.

Sorting chart data in micro chart header sections is set in the Sort Order property of the header section. This property is only visible if you have the Presentation Variant property defined for the micro chart header section. This requires SAPUI5 version 1.130 or higher defined as the minUI5Version in the manifest.json file. You can only sort chart data in micro charts that are area or line type.

Presentation Variant

The Presentation Variant property shows the UI.PresentationVariant annotation that defines the micro chart header section's presentation options, such as sorting. To view the sorting properties, you must set the Presentation Variant: Annotation to New.

When the Presentation Variant: Annotation is set, you can define one or more direct properties of the entity by which to sort the header section. Under Presentation Variant: Sort Order, click Add Sort Property. A new table row for the sort property is added with Property and Direction fields. Choose a property and direction to sort by to update the sorting logic for your micro chart in the header section.

If you have multiple sort properties, you can define in which order they apply by moving them up and down within the sort property.

You can remove the reference to the UI.PresentationVariant annotation generated by the Page Editor by setting the Presentation Variant: Annotation to None.

Note:

To remove unreferenced UI.PresentationVariant annotations generated by the Page Editor from the annotation file, run the cleanup procedure. This also removes the other unreferenced UI.PresentationVariant annotations defined with qualifiers to keep your annotation file as clean as possible.