Front-End Server : Activate OData Services

For more information about activating OData services, see section Front-End Server: Activate OData Services in the SAP S/4HANA UI Technology guide.

For more information, see SAP Help Portal at http://help.sap.com under  Technology Platform SAP Gateway SAP Gateway 2.0 Configuration and Deployment Information Configuration Guide SAP Gateway Configuration Guide Configuration Settings for SAP Gateway Supported Scenarios Configuration Settings for OData Channel Scenarios Configuring the Task Gateway Service .

Front-End Server : Activate SAP UI5 Application

For more information about how to activate the ICF service, see section Front-End Server: Activate ICF Services of SAPUI5 Application in the SAP S/4HANA UI Technology guide.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to the apps. In the launchpad, the user can see and access those apps that have been assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see section Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad in the SAP S/4HANA UI Technology guide.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

Configuring a Task and Decisions

Enter and define a task and those decision options from your workflow task that you want to display in the My Inbox app.

To configure a task and decisions, follow the steps below in the back-end system where you maintain your workflow template.

1. In Customizing for SAP NetWeaver, choose  Gateway Service Enablement Content Workflow Settings Maintain Task Names and Decision Options .

2. Fill in the Step Name table as described below and save your entries:

   • Workflow ID: Enter the ID of your workflow template.

   • Step ID: Enter the task step from your workflow template.

   • Icon MIME Repository Path: Leave this field blank.

   • Step Description: Enter the task name.

3. Select the entry in the Step Name table and choose Decision Keys in the navigation panel.

4. Add and define your decision options in the Decision Keys table as described below and save your entries:

   • Key: Enter the decision key.

     Decision keys are numeric and sequential and correspond to the position of decision options in the Workflow Builder. Enter the first decision option with key 1, the second decision option with key 2, and so on.

   • Icon Mime Repository Path: Leave this field blank.

   • Decision Text: Define the label of the decision option.

     This name is displayed on the application screen as a button label. The proposed length of the decision text is maximum 14 characters. Decision texts longer than 14 characters will not fit to the device screen.

   • Comment On: If you want to make it mandatory for the user to add a comment when executing a decision, select this checkbox.

   • Nature: Here you have the following options:

     • Select POSITIVE for the approve type decision option.

       The decision option is displayed either as a green push-button or in a gray popover (depending on the space available) on the detail screen of the application.

     • Select NEGATIVE for the reject type decision option.

       The decision option is displayed either as a red push-button or in a gray popover (depending on the space available) on the detail screen of the application.

     • Leave the field empty for multiple decision options.

       The decision options are displayed either as gray push-button or in a gray popover (depending on the space available) on the detail screen of the application.

        Note

       If the step type for the workflow task is not User Decision, implement BAdI /IWWRK/BADI_WF_BEFORE_UPD_IB. For more information, see App Extensibility: My Inbox.

Defining the Workflow Scenario

Define your workflow scenario by completing the following steps in your Gateway system: add a scenario, assign the consumer type, assign roles, and define tasks.

1. Add a workflow scenario.

   1. In Customizing for SAP NetWeaver, choose  Gateway Service Enablement Content Task Gateway Service Scenario Definition .

   2. Choose New Entries.

   3. Fill in the Scenario Decision table as described below and save your entries:

      • Scenario Identifier: Define a scenario ID.

      • Scenario Display Name: Define a name for your scenario.

      • Scenario Order: Not relevant for My Inbox.

      • Technical Service Name: Enter /IWPGW/TASKPROCESSING.

      • Version: Enter 2.

      • EntitySet External Name: Enter Task.

      • Property External Name: Enter TaskDefinitionID.

      • Default Sort by Property: Define how you want to sort the work items on the list screen of the application. If you do not set this parameter, the default value is CreatedOn.

         Note

        You can use all the properties of the task collection here.

        To display a list of all the possible properties, see SAP Help Portal at http://help.sap.com under  Technology Platform SAP Gateway SAP Gateway 2.0 Content Information Content Guide SAP Gateway Content Guide SAP Gateway Supported OData Channel Scenarios Task Gateway Task Gateway Administrator Task Gateway Service Task Gateway Service Version 2 Task Collection .

        The property you have selected is added to the list of possible sorting properties on the detail screen of the application.

         Note

        You can also define the sorting principles on the UI of the application. You can choose from a list of properties.

      • Mass Action: If you set this parameter to true, you can process, for example, approve or reject, several tasks of the same type at the same time.

      • Class for Scenario Count: Leave it empty.

         Note

        If the scenario is not part of the Business Workflow engine or BPM, and you want to see the number of tasks pending for this scenario, enter the name of the class that implements the /IWWRK/IF_TGW_SCENARIO interface in the back-end system.

      • Quick Act.: Select the Quick Act. checkbox to enable quick approval of workflow items by swiping on the screen.

        This field is only relevant if you use a touch screen device.

2. Assign the consumer type to the scenario.

   1. Select the row containing your approval scenario and choose table Assign Consumer Type to Scenario in the navigation panel.

   2. Choose New Entries.

   3. In the Task Gateway Consumer Type field, select TABLET.

   4. Save your entries.

3. Assign a role to the consumer type and the scenario (optional).

   Now you can assign an approval scenario to a number of roles, that is, the scenario will only be available to users who are assigned to at least one of the relevant PFCG roles.

   1. Select the row for TABLET (for all devices), and choose Assign Role to Consumer Type and Scenario in the navigation panel.

   2. Choose New Entries.

   3. In the Role column, select the role you want to use.

   4. Save your entries.

4. Define tasks for your scenario.

    Note

   You can define several tasks for your scenario. Make sure that you follow the steps below for each task.

   1. Choose Scenario Definition in the navigation panel, and select the row containing your approval scenario.

   2. Choose Task Definition for Scenario in the navigation panel.

   3. Choose New Entries.

   4. Enter the task type ID for your approval workflow.

       Note

      In case of SAP Business Workflow, you can find your task type ID in the back-end system as described below:

      • Start the Workflow Builder.

      • Search for the workflow definition you would like to enable.

      • Open the approval step.

      • Go to Control tab, and check the Task field.

5. In the SAP System Alias field, enter the source system alias for the task type.

    Note

   Make sure that the Task Gateway Service is connected to the selected system aliases.

6. Save your entries.

Configuring the SAP Fiori Launchpad for the All Items Tile

To configure the All Items tile, perform the following:

1. Choose the App Launcher - Dynamic tile.

2. Select the newly created tile, and fill in the following fields as described below:

   • Title: Enter the name of your workflow scenario, for example, Capital Expenditure Approval.

   • Icon: Use any of the available icons.

   • Service URL:

     /sap/opu/odata/IWPGW/TASKPROCESSING;v=2;mo/TaskCollection/$count/?$filter=Status eq 'READY' or Status eq 'RESERVED' or Status eq 'IN_PROGRESS' or Status eq 'EXECUTED'.

   • Semantic Object: Enter WorkflowTask.

   • Action: Enter displayInbox.

   • Parameters: Enter allItems=true&massAction=<true or false>&quickAction=<true or false>&sortBy=<property to be used for sorting>&listSize=<number of items you want to display on your list screen>&showAdditionalAttributes=<true or false>.

     You can define massAction, quickAction, and sortBy, if you want to overwrite your default settings. If you do not define these parameters, the following default values are used:

     • massAction = true

     • quickAction = true

     • sortBy = CreatedOn

     • listSize defines the number of items you want to display on the list screen. The default is 100.

     • showAdditionalAttributes=true; if you want to display custom attributes in the List View.

Configuring the SAP Fiori Launchpad for the Outbox Tile

Ensure that you have the following prerequisites:

• The SAP NetWeaver Gateway version on your front end server corresponds to SAP NetWeaver Gateway 2.0 SP 11.

• You have installed SAP IW PGW 100 (IW_PGW 100) SP 08.

To configure the All Items tile, perform the following:

1. Choose the App Launcher - Dynamic tile.

2. Select the newly created tile, and fill in the following fields as described below:

   • Title: Enter the name of your workflow scenario, for example, Outbox.

   • Icon: Use any of the available icons.

   • Service URL: Enter /sap/opu/odata/IWPGW/TASKPROCESSING;v=2;mo/TaskCollection/$count/?$filter=Status eq 'FOR_RESUBMISSION' or Status eq 'COMPLETED'.

   • Semantic Object: Enter WorkflowTask.

   • Action: Enter displayInbox.

   • Parameters: Enter allItems=true&outbox=true&listSize=<number of items you want to display>.

     • scenarioID or allItems is mandatory.

     • listSize is optional. The default is 300.

For more information, see SAP Help Portal at http://help.sap.com under  Technology Platform SAP Fiori For SAP Business Suite Configuration of SAP Fiori Infrastructure Setup of SAP Fiori Launchpad .

Configuring the Fiori Launchpad for Expert View

You can access the newly created tile in the launchpad. On accessing the newly created tile, you can view the expert view.

Configuring the SAP Fiori Launchpad for Scenario-Specific Tiles

More Information

For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.

Launch My Inbox without Fiori Launchpad

To launch My Inbox directly, without navigating from Fiori launchpad, log on to, https://<server>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<client>&sap-ushell-url==/sap/bc/ui5_ui5/sap/ca_fiori_inbox&sap-ushell-url=/sap/bc/ui5_ui5/sap/ca_fiori_inbox&<other URL parameters>.

My Inbox supports the following URL properties:

• allItems= true; to access all tasks for the user.

• scenarioId= <scenario ID as defined in Task Gateway>; if a specific scenario is configured in task gateway.

• massAction= true; to enable or disable Mass Action in My Inbox.

• quickAction= true; to enable or disable quick actions on mobile devices.

• sortBy= CreatedOn; specify default sort by property. It can have any values from task entity.

• listSize= <value>; specify a numeric value to limit the number of tasks loaded in the My Inbox.

  You can define massAction, quickAction, and sortBy, if you want to overwrite your default settings. If you do not define these parameters, the following default values are used:

  • massAction = true

  • quickAction = true

  • sortBy = CreatedOn

  • listSize defines the number of items you want to display on the list screen. The default is 100.

  • showAdditionalAttributes = true; if you want to display custom attributes in the List View.

• scenarioId= scenario ID as defined in Task Gateway; if a specific scenario is configured in task gateway. The massAction and quickAction values will be based on values defined in the Task Gateway.

Example of the URL parameters usage:

https://<server>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<client>&sap-ushell-config=headerless#Shell-runStandaloneApp?sap-ushell-SAPU_I5.Component=cross.fnd.fiori.inbox&sap-ushell-url=/sap/bc/ui5/sap/ca_fiori_inbox&allItems=true&massAction=false&quickAction=true&listSize=300&sortBy.

Configuring My Inbox to Display Additional Attributes in Master List

1. Choose the tile configuration for All Items tile or Scenario-Specific tile.

2. In Parameters, add showAdditionalAttributes = true as value.

    Note

   Additionally, you must perform a back-end configuration to create custom attributes with pre-defined names. For more information, see SAP Note 2305330.

Integrating a Custom SAPUI5 Fiori Application

Ensure that SAPUI5 Fiori application is on the same front end server.

Specifying Visualization Parameters for Tasks

The supported visualization types inSWFVISU transactions are:

For more information, see SAP Note 2200084.