In the search forms, the content of the forms is stored in the variants. When a variant is selected, the form is filled according to the data saved. If the form previously contained values, they will be removed beforehand.

Table variants include column layout, sorting, filtering, and categorizing – provided the user can customize each. Again, when a variant is selected, the current layout, sorting, etc. is discarded and replaced with that in the variant.

Within variant management, a distinction is made between three types of variants:

If changes are made in the selection view or in the hit list, this is indicated with an asterisk (*) in the name of the variant.

For search fields, the change will not apply until you leave the field.

Changes are saved in the My Views selection dialog with the button Save or Save as.

This dialog displays all variants that are marked as favorites. To load a variant, select it.

In the dialog My Views, the following buttons are available:

Button	Description
Save	Saves the changes made to the current variant. This button is displayed only if the current variant has been changed and it is a custom variant.
Save as	Saves the changes to the current variant as a new variant. Open the dialog Save View by clicking on the button. Here, the user can make the following settings: View: Unique name of the variant Set as default: The variant will be used as the default variant if this check box is activated. Public: The variant will be saved as a public variant if this check box is activated. The variant will be saved as a private variant if this checkbox is deactivated or if it is not displayed. The check box is available only if the user has the WEB_GLOBAL_VARIANTS user attribute equal to X. OK: Saves the variant Cancel: Cancels the operation.
Manage	Opens the dialog Manage Views. All available variants can be managed in this dialog. For more information, see Management of variants.

In the dialog Manage Views, all variants to which a user has access are listed.

The Search field allows the user to search for specific variants and to filter the list of variants.

The Manage Views dialog consists of the following columns:

The Save button is used to save the changes. Deleted variants are not actually deleted until you have saved.

The Cancel button can be used to discard the changes made, including deletions.

When integrating xSuite work items into the SAP Fiori My Inbox, certain limitations must be observed.

Limitations that affect the expert mode are to be distinguished from those affecting the "normal" mode.

In the settings.json file of the xSuite Base Library, the following section must be configured:

"__comment__": "------------- MYINBOX SETTINGS -------------",
"myinbox": {
     "__comment__":
"***** MAPPING SYSTEM + CLIENT TO RFC ******",
     "sc": {
           "exampleSystem": {
                "clientA":                 "",
                "clientB":                 ""
           }
     },
     "__comment__": "***** MAPPING SYSTEMALIAS TO RFC **********",
     "alias": {
           "exampleAlias":                 ""
     }
},

Specify the systems plus client and the respective RFC connections under "sc". Store the system alias and the associated RFC connections under "alias".

The system is set up with the following structure:

Configure the section in the settings.json file as follows:

"__comment__": "------------- MYINBOX SETTINGS -------------",
"myinbox": {
     "__comment__": "***** MAPPING SYSTEM + CLIENT TO RFC ******",
     "sc": {
           "S01": {
                "100":               "RFC_S01_100",
                "800":               "RFC_S01_800"
           },
           "P02": {
                "200":               "RFC_P02" 

           },
     },
     "__comment__": "***** MAPPING SYSTEMALIAS TO RFC **********",
     "alias": {
           "S01100":                  "RFC_S01_100",
           "S01800":                  "RFC_S01_800",
           "P_02":                    "RFC_P02",
     }
},

Create five new target mappings on the gateway system, using Transaction /UI2/FLPD_CUST.

Under Catalogs, select the catalog containing the xSuite App tiles and the corresponding target mapping

In the Target Mapping tab, use the Create Target Mapping button to create five new target mappings in succession.

Click the Create Target Mapping button to open the Configure: Target mapping view.

All values must be entered according to the following tables. Note that values are case-sensitive.

The task visualization and the visualization parameters for each task to be displayed in the My Inbox app must be configured in the back-end system.

This configuration is performed via transaction SWFVISU.

Create new entries under Task Visualization. In the Task column, enter the number of the task. In the Visualization Type column, always select the value Intent-Based Navigation.

In Visualization parameters, always create the visualization parameters for all task visualizations created.

A list of all possible tasks and the corresponding visualization parameters can be found under:

On the back-end system, the labels of tasks displayed in SAP Fiori My Inbox can be optionally changed.

This configuration is performed via transaction SPRO → SAP Customizing Implementation Guide → SAP NetWeaver → SAP Gateway Service Enablement → Content → Workflow Settings → Maintain Task Names and Decision Options.

Under Step Name, an existing entry can be edited or a new entry can be created for this purpose. The entry is language-dependent, i.e. the description is maintained for the current SAP GUI logon language.

For each entry, the desired task name must be entered in the Step Description column for the corresponding combination of workflow ID and step ID.

In SAP Fiori My Inbox, the tasks of the AVAG and LVAG roles are both labeled Approval. To enable the user to distinguish between the tasks, the name for the AVAG role should be changed from Approval to AP Approval.

The workflow ID for a role can be determined in the transaction /WMD/BC_SPRO → xSuite Business Solutions → Workflow → Basis → Basic Settings → Assign Roles.

The work item ID searched for can then be determined for the role in the table. In this example, the searched work item ID of the role AVAG is WS00288903.

The step ID for the workflow ID can be determined via transaction PFTC in the Workflow Builder. There, the task type Workflow Template must be selected, and the ID of the task entered without WS, i.e. 00288903 in this example.

The Workflow Builder must be called up in the Basic Data tab.

In the Workflow Builder, the Step ID can be determined for the Approval dialog in the navigation area. In this example, the step ID is 70.

In transaction SPRO → SAP Customizing Implementation Guide → SAP NetWeaver → SAP Gateway Service Enablement → Content → Workflow Settings → Maintain Task Names and Decision Options, a new entry is created for workflow ID WS00288903 and step ID 70:

After saving the new entry, the new name AP Approval will be used in the SAP Fiori My Inbox.