For
OData V4
based applications, the templates used by the Page Editor to provide this flexibility is published as part of our Open UX tools@sap-ux/fe-fpm-writer
. This new transparency allows everyone to inspect the source behind the scenes.
You have the ability to create a custom column for your table in a List Report or Analytical Chart page.
- In the Page Editor outline view next to the Columns header, click the ➕ (Add) icon to add a new column.
- Provide the following information:
-
Column Key - Key for the column
-
Header Text - column title
-
ID - unique ID is automatically created, but can be modified
-
Select Column Fragment
- Create New Fragment
- Use Existing Fragment
-
Column Fragment Name
-
Select Cell Fragment (in case of responsive table type)
- Create New Fragment
- Use Existing Fragment
-
Cell Fragment Name
-
Anchor Column - select one of existing columns in the table. You can select where you want to insert the custom column, before or after the selected target column.
-
Placement - Before/After
-
Leading Property - If the content of your custom column refers to a property such as {Price}, you need to include a corresponding
leadingProperty
entry in the column definition.
-
The custom column fragment and cell code are looked up and written to the project's ext
folder. A custom column can be dragged into a new position using the handle in outline view. Click the 🗑️ (Delete) icon to delete a custom column.
-
In the Page Editor outline view next to the Columns header, click the ➕ (Add) icon to add a new column.
-
Provide the following information:
-
Header Text- column title
-
Select Column Fragment
- Create New Fragment
- Use Existing Fragment
-
Column Fragment Name
-
Anchor Column - select one existing column in the table.
-
Placement - Before/After. You can select where you want to insert the custom column, before or after the selected anchor column.
-
Generate Event Handler - True/False
-
Width - width of the new column
-
The custom column fragment and optional default controller code is written to the project's ext
folder. A custom column can be dragged into a new position using the handle in outline view. Click the 🗑️ (Delete) icon to delete a custom column.
You can create a custom section as part of your Object Page using the Page Editor.
- In the Page Editor outline view of your Object Page, click the ➕ (Add) icon on the Sections node. For
OData V4
, click Add Custom Section from the menu. ForOData V2
, the selection will be prefilled. - Provide the following information:
- Title - the label of the custom section
- View Type - types are View or Fragment (
OData V2
only) - Select Your Fragment/View- choose new or existing
- Fragment/View Name - the file name of the artifact
- Anchor Section - select one of the existing sections in the Object Page
- Placement - before, after or replace (
OData V2
only) - Generate Event Handler - Decide whether a demo controller should be created (
OData V4
only)
On clicking Add, the custom section fragment, view, and or controller code is written to the project's ext
folder. A custom section can be dragged into a new position using the handle in outline view. Click the 🗑️ (Delete) icon to delete a custom section.
You can create a custom action in your List Report and Object Page using the Page Editor for OData V4
applications.
- In the Page Editor, click the ➕ (Add) icon on the Actions node and click Add Custom Action from the menu.
- Provide the following information:
- Action ID - ID for the action.
- Button Text - Text displayed on the button.
- Anchor - Key of another action to be used as placement anchor.
- Placement - Define placement after or before the anchor action.
- Action Handler File - Decide if you want to add to exiting file or create new action handler file.
- Handler File - If you selected add to existing file, select the action handler file.
- Action Handler Method - Select if you want to create new function or add to an existing function.
- Handler Method - Select handler method.
- Required Selection - Toggle if this is required or not.
On clicking Add, the custom action is written to the project's ext
folder. A custom action can be dragged into a new position using the handle in outline view. Click the 🗑️ (Delete) icon to delete a custom action.
This feature is only available for
OData V4
and with@sap/ux-specification
version 1.96 or higher. For more information, see https://www.npmjs.com/package/@sap/ux-specification.
You can create a custom view in your List Report and Object Page using the Page Editor for OData V4
applications.
-
In the Page Editor, click the ➕ (Add) icon on the View node and click Add Custom View from the menu.
The custom view feature is only available on List Reports that do not contain a chart.
-
Provide the following information:
- Key - Unique tab identifier.
- Label - View title.
- Select Your Fragment - Enter new fragment or choose an existing one.
- Fragment Name - The file name of the artifact.
- Generate Event Handler - Decide whether a demo controller needs to be created.
On clicking Add, the custom view is written to the project's ext
folder. A custom view can be dragged into a new position using the handle in outline view. Click the 🗑️ (Delete) icon to delete a custom view.
This feature is only available for
OData V4
and with@sap/ux-specification
version 1.96.29, 1.102.14 or higher. For more information, see https://www.npmjs.com/package/@sap/ux-specification.
You can create a controller extension as part of your List Report and Object Page using the Page Map for OData V4
applications.
-
Launch the Page Map. For more information, see the Launching Page Map section in Define Application Structure.
-
In the Page Map view, click the (Show Controller Extensions) icon for your selected page.
-
You see the list of existing controller extensions for the selected page in the Properties Panel.
-
You can add a new controller extension by clicking Add Controller Extension.
In the pop-up window, provide the required information.
-
You can then change the order in which the extensions are executed using the drag-and-drop functionality, or using the (Move Up) or (Move Down) icons.
-
You can also click the (Edit in source code) icon to navigate to the respective controller code file.
For more information about controller extensions and related examples, see Controller Extensions.