- Latest Version 1.128
- Version 1.126
- SAPUI Version 1.124
- SAPUI5 Version 1.122
- SAPUI5 Version 1.120
- SAPUI5 Version 1.118
- SAPUI5 Version 1.116
- SAPUI5 Version 1.114
- SAPUI5 Version 1.112
- SAPUI5 Version 1.110
- SAPUI5 Version 1.108
- SAPUI5 Version 1.106
- SAPUI5 Version 1.104
- SAPUI5 Version 1.102
- SAPUI5 Version 1.100
- SAPUI5 Version 1.98
- SAPUI5 Version 1.94
- SAPUI5 Version 1.92
- SAPUI5 Version 1.90
- SAPUI5 Version 1.88
- SAPUI5 Version 1.86
- SAPUI5 Version 1.84
- SAPUI5 Version 1.82
- SAPUI5 Version 1.80
- SAPUI5 Version 1.78
- SAPUI5 Version 1.76
- SAPUI5 Version 1.74
- SAPUI5 Version 1.72
- SAPUI5 Version 1.70
- SAPUI5 Version 1.68
- SAPUI5 Version 1.66
- SAPUI5 Version 1.64
- SAPUI5 Version 1.62
- SAPUI5 Version 1.60
- SAPUI5 Version 1.58
- SAPUI5 Version 1.56
- SAPUI5 Version 1.54
- SAPUI5 Version 1.52
- SAPUI5 Version 1.50
- SAPUI5 Version 1.48
- SAPUI5 Version 1.46
- SAPUI5 Version 1.44
- SAPUI5 Version 1.42
- SAPUI5 Version 1.40
- SAPUI5 Version 1.38
- SAPUI5 Version 1.36
- SAPUI5 Version 1.34
- SAPUI5 Version 1.32
- SAPUI5 Version 1.30
- SAPUI5 Version 1.28
- SAPUI5 Version 1.26
- Latest Version 1.128
- Version 1.126
- SAPUI Version 1.124
- SAPUI5 Version 1.122
- SAPUI5 Version 1.120
- SAPUI5 Version 1.118
- SAPUI5 Version 1.116
- SAPUI5 Version 1.114
- SAPUI5 Version 1.112
- SAPUI5 Version 1.110
- SAPUI5 Version 1.108
- SAPUI5 Version 1.106
- SAPUI5 Version 1.104
- SAPUI5 Version 1.102
- SAPUI5 Version 1.100
- SAPUI5 Version 1.98
- SAPUI5 Version 1.96
- SAPUI5 Version 1.94
- SAPUI5 Version 1.92
- SAPUI5 Version 1.90
- SAPUI5 Version 1.88
- SAPUI5 Version 1.86
- SAPUI5 Version 1.84
- SAPUI5 Version 1.82
- SAPUI5 Version 1.80
- SAPUI5 Version 1.78
- SAPUI5 Version 1.76
- SAPUI5 Version 1.74
- SAPUI5 Version 1.72
- SAPUI5 Version 1.70
- SAPUI5 Version 1.68
- SAPUI5 Version 1.66
- SAPUI5 Version 1.64
- SAPUI5 Version 1.62
- SAPUI5 Version 1.60
- SAPUI5 Version 1.58
- SAPUI5 Version 1.56
- SAPUI5 Version 1.54
- SAPUI5 Version 1.52
- SAPUI5 Version 1.50
- SAPUI5 Version 1.48
- SAPUI5 Version 1.46
- SAPUI5 Version 1.44
- SAPUI5 Version 1.42
- SAPUI5 Version 1.40
- SAPUI5 Version 1.38
- SAPUI5 Version 1.36
- SAPUI5 Version 1.34
- SAPUI5 Version 1.32
- SAPUI5 Version 1.30
- SAPUI5 Version 1.28
- SAPUI5 Version 1.26
Object Page – Footer Bar
Intro
The SAP Fiori elements object page template supports the features and settings for the object page footer detailed below.
For design information, see the Object Page Floorplan guidelines and the links below.
Feature Availability
Footer Bar Actions |
Availability |
Finalizing Actions | Available |
Save | Default in edit mode |
Close on Save | Available with SAP Fiori elements for OData V2 only |
Save and Edit | Available, for non-draft applications with SAP Fiori elements for OData V2 only |
Apply | Available, for the subobject page in draft-enabled applications only |
Message Popover Button | Default, visible only when messages are present. |
Cancel | Default in edit mode only |
Enabling / Disabling of Actions | Available |
Footer Bar Actions
In create and edit modes, the footer bar appears at the bottom of the screen.
Finalizing Actions
You can add finalizing actions to the footer bar.
A message toast is displayed when an operation is successful.
Finalizing actions complete the work on the current screen, by permanently changing the object state. You can also set them to navigate away from the object page.
Note that developers may call these actions determining actions.
For more information, see:
Save
The action is displayed by default in edit mode.
After saving, the user stays on the object page for applications both with and without draft handling enabled.
You can enable users to automatically navigate back to the list report when they save with SAP Fiori elements for OData V2. To do this, ask your development team to add close logic to the Save action.
Save and Edit
You can enable this action in non-draft applications with SAP Fiori elements for OData V2.
With the Save and Edit action, users save current changes and stay on the object page to continue editing.
Apply
You can enable this action in the footer bar of a subobject page in draft-enabled applications.
With the Apply action, users conclude the create or edit activity, save the draft, and navigate one step up in the object hierarchy to the object page.
Similarly, when the subobject page is open in flexible column layout with three column layout, clicking Apply now closes the column where the subobject is displayed and returns the user to the object page.
Message Popover Button
Turned on by default, the button is only visible when messages are present and allows the user to open the message popover. The color of the message button reflects the most crtical message level.
The message popover displays the count of error messages.
Messages without a criticality level are treated as information messages.
With SAP Fiori elements for OData V2, the messages in the message popover are grouped by section and table so users can easily locate where they need to take action.
For more information, see:
Cancel
The action is displayed by default in edit mode.
Enabling / Disabling of Actions
You can enable or disable footer bar actions according to certain conditions. For example, to prevent users from archiving a sales order that is still being processed, you can enable the Archive action only for sales orders with the status Delivered or Cancelled.
Note that even if you disable all footer bar actions, the footer bar still appears onscreen for the display of the message popover, described above.
Related Links
Elements and Controls
- Object Page Floorplan (guidelines)
- Object Handling (Create, Edit, Delete) (guidelines)
- Action Placement (guidelines)
- Message Popover (guidelines)