sap fiori request for approvals 2.0 sp01

7/26/2019 SAP Fiori Request for Approvals 2.0 SP01

http://slidepdf.com/reader/full/sap-fiori-request-for-approvals-20-sp01 1/26

SAP Fiori for Request Approvals 2.0 SPS 01

Document Version: 2.0 – 2016-03-07

CUSTOMER

SAP Fiori for Request Approvals 2.0



SAP Fiori for Request Approval 2.0 SPS 01 CUS TOM ER

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2

Table of Contents

1 SAP Fiori for Request Approvals 2.0 ................................................................................ 1-3

2

Installation Information ...................................................................................................... 2-5

3

My Inbox ................................................................................................................................ 3-8

4 App History: My Inbox ....................................................................................................... 4-11

5 App Implementation: My Inbox ........................................................................................ 5-12

6 App Extensibility: My Inbox ............................................................................................. 6-22





1 SAP Fiori for Request Approvals 2.0

This SAP Fiori product contains the My Inbox transactional app that runs on the SAP Fiori Launchpad.

Note

The My Inbox application is the successor of the Approve Requests application, thus we recommend

to implement My Inbox. If you have already installed Approve Requests, please consider switching to

My Inbox.

Product Information

Product SAP Fiori for Request Approvals

Release 2.0

Support Package Stack SPS 01

Delivery Date 01/2016

System Landscape Requirements

Before you start to install this SAP Fiori product and implement the My Inbox app, ensure that your system

landscape has been set up to enable SAP Fiori.

Front-End Components Delivered with (Product

Version Stack)

SAP enhancement package 1 for SAP

NetWeaver 7.0 SPS 03







SAP Fiori Front-End Server 2.0 SPS 01

SAP NetWeaver 7.0 SPS 18



SAP NetWeaver Gateway 2.0 SPS 10






Version Stack)


Back-End Components Delivered with (Product

Version Stack)


NetWeaver 7.3 SPS 15 (for BPM support)


NetWeaver 7.4 SPS 10 (for BPM support)

SAP Fiori System Landscape Options <>

<>

<>

Configuration of Front-End Server <>

For more information about the required software products, see <>.





2 Installation Information

Each SAP Fiori app consists of front-end components (such as the user interface) and back-end components

(such as the OData service). The product SAP Fiori for Request Approvals 2.0 contains the front-end

component of the My Inbox SAP Fiori app and has to be installed on your front-end server.

Prerequisites

Before you install this product, ensure that your system landscape has been set up to enable SAP Fiori:

SAP Fiori System Landscape Options

<>

<>

<>

Activities

The table lists the installation tasks required for the My Inbox apps.

Before performing the steps below make sure that all the required SAP Notes are implemented. For more

information, see the Release Information Note for SAP Fiori My Inbox (2221151).

If you run your front-end server on SAP NetWeaver lower than 7.4, complete the following steps:

Step Task Back-End/Front-End Server

1. Install one of the following

SAP NetWeaver versions:

SAP enhancement package 1

for SAP NetWeaver 7.0 SPS

03



01



06



01



Front-end server

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3232323131353126










SAP NetWeaver Gateway 2.0

SPS 10

2. Install SAP NetWeaver Gateway2.0 SPS 10

Front-end server

3. Install SAP IW PGW 100 (IW_PGW

100) SP 07

Front-end server

4. Install UI ADD-ON 2.0 FOR NW Front-end server

5. Install SAP Fiori for Request

Approvals 2.0 (UIX01CA1 200)

SPS 01

Front-end server

6. If you run your back-end server

on SAP NetWeaver lower than7.4, install SAP IW BEP 200

(IW_BEP 200) SP 10

Back-end server

7. If you are implementing the My

Inbox app for SAP BPM, install

SAP enhancement package 1 for

SAP NetWeaver 7.3 SPS 15.

Back-end server

If you run your front-end server on SAP NetWeaver 7.4, complete the following steps:


1. Install SAP NetWeaver 7.4 SPS

09

Front-end server

2. Install SAP IW PGW 100

(IW_PGW 100) SP 07

Front-end server


Approvals 2.0 (UIX01CA1 200)

SPS 01.

Front-end server


on SAP NetWeaver lower than

7.4, install SAP IW BEP 200(IW_BEP 200) SP 10

Back-end server



SAP enhancement package 1 for


Back-end server

If you run your front-end server on SAP NetWeaver 7.5, complete the following steps:


1. Install SAP NetWeaver 7.5 SPS00.

Front-end server






2. Install SAP IW PGW 100

(IW_PGW 100) SP 08.

Front-end server


Approvals 2.0 (UIX01CA1 200)SPS 01.

Front-end server


on SAP NetWeaver lower than

7.4, install SAP IW BEP 200

(IW_BEP 200) SP 11.

Back-end server



SAP NetWeaver 7.5.

Back-end server

More Information

For general information about downloading and installing SAP Fiori components, see <>.





3 My Inbox

With the transactional app My Inbox, you can make important decisions via mobile or desktop devices

anywhere and anytime. Using this app, you can process your standard and custom workflow tasks based on

the decision options defined in the back-end system.

All Items Inbox

With the My Inbox app, we deliver a pre-configured All Items tile in the SAP Fiori Launchpad, which enables

you to easily process all your tasks.

Note

You must add the All Items tile from the catalog to view this tile in the SAP Fiori Launchpad.

Scenario-Specific Inbox

The My Inbox application also offers you the possibility to define your own workflow scenarios and create

scenario-specific tiles in the SAP Fiori Launchpad. For more information, see App Implementation: My Inbox.

Outbox

With the My Inbox application, you can configure the Outbox tile, which enables you view the completed and

suspended tasks.

Key Features

You can process tasks from your SAP Business Workflow, SAP Business Process Management (BPM),

and 3rd party providers.

You can define the decision options you want to display (for example, approve or reject).

You can perform the standard actions (for example, claim, release, or forward a request).

These actions are available by default; no customizing is needed in the back-end system.

You can perform mass actions, that is, process several tasks of the same type at the same time.

You can view and add comments.

You can view custom attributes that provide additional information about the task instance.

You can view, upload, and delete attachments.

You can create and manage substitution rules to manage the tasks in your absence.

You can send emails or post tasks on a pre-configured JAM site.

You can view the business cards of the application users.

You can browse, sort, filter, and group tasks requiring action.

You can extend the standard application to cover additional UI or functionality needs.





You can easily process all your tasks with the pre-configured All Items tile.

You can view the support information of the application to resolve error conditions.

You can view the task history for Business Workflow tasks.

You can view the additional information provided in the object links for Business Workflow tasks.

You can view the completed tasks and suspended tasks from Outbox tile.

You can filter the tasks based on substitute users.

Note

Substitution and Open task feature are not supported in mobile devices.


The My Inbox app consists of front-end components, such as the user interfaces and OData service. You can

use the app with any SAP back-end component that contains workflows. If you run your back-end server on

SAP NetWeaver lower than 7.4 and you want to process tasks from your SAP Business Workflow, ensure thatthe IW_BEP component is installed on your back-end server. The front-end components are delivered in

separate products and have to be installed in a system landscape that is enabled for SAP Fiori.


Version Stack)














Version Stack)



Version Stack)

SAP enhancement package 1 for SAP NetWeaver

7.3 SPS 15 (for BPM support)


<>

<>

For more information on Gateway stack, see 1942072[RD1].

For more information about the required software products, see <>.









Component for Customer Incidents

For creating customer incidents, use the following component: CA-INB-FIO.





4 App History: My Inbox

Note

Starting with the initial delivery date, the app is delivered with each support package stack of the

respective SAP Fiori product. This document only lists support package stacks in which the app has

been enhanced or changed. If the app was not changed in a particular support package stack, then

this support package stack is not mentioned in this document.

The My Inbox app has been enhanced as follows:

SAP Fiori for Request Approvals 2.0 SPS 01 (Delivery Date 01/2016)

For more information, see SAP Note 2221151.

New/Enhanced Key Features

Outbox

You can view the completed and suspended

tasks with the Outbox tile.

Filter

You can filter the tasks based on substitutedusers.

Unplanned substitution

You can assign a substitute for unplanned

absence.








5 App Implementation: My Inbox


Before you start to implement the app, ensure that your system landscape has been set up to enable SAP

Fiori. This also implies that the front-end and back-end components for your app are already available in this

system landscape:


<>

<>

Configuration of Front-End Server <>


Version Stack)









SAP Fiori Front-End Server 2.0 SPS 01






Version Stack)



Version Stack)

SAP enhancement package 1 for SAP NetWeaver

7.3 SPS 15 (for BPM support)

Ensure that the front-end component of the app is in place on your front-end server. It is automatically

installed with the UI add-on.

Front-End Server: Front-End Component of App

(Software Component)

UIX01CA1 200 SP01

Ensure that the following Gateway components are in place on your front-end server.

Front-End Server: Gateway Component SAP IW PGW 100 (IW_PGW 100) SP 07





If you run your back-end server on SAP NetWeaver lower than 7.4, ensure that the following Gateway

component is in place on your back-end server.

Back-End Server: Gateway Component SAP IW BEP 200 (IW_BEP 200) SP 10

For more information about the installation of SAP Fiori products, see <>.

Note

The app offers the possibility to upload documents. For security reasons, we strongly recommend

that you install an appropriate virus scanner in your SAP Fiori system landscape and define

sufficiently restrictive scan profiles to prevent the upload of malicious content.

For more information on virus scanning and scan profiles for SAP Fiori apps, see <>.

Required SAP Notes

You can find the required SAP Notes for the My Inbox app in the Release Information Note for SAP Fiori My

Inbox (2221151).

Implementation Tasks

The following sections list tasks that have to be performed to implement the My Inbox app. The tables contain

the app-specific data required for these tasks:

Front-End Server: Activate OData Services

Component Technical name

OData Service (Version Number) Task Gateway Service 2.0

(/IWPGW/TASKPROCESSING Version 2)

For more information, see SAP Help Portal at http://help.sap.com Technology SAP Gateway SAP

NetWeaver Gateway 2.0 Configuration and Deployment Information Configuration Guide SAP NetWeaver

Gateway Configuration Guide Configuration Settings for SAP NetWeaver Gateway Supported Scenario

Configuration Settings for OData Channel Scenarios Configuring the Task Gateway Service .

For more information about activating OData services, see <>.

Front-End Server: Activate SAP UI5 Application

Component Technical name

SAP UI5 Application CA_FIORI_INBOX




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com








For more information about how to activate the ICF service, see <>.

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

The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access

those Fiori 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 <>.

SAP delivers technical catalogs for groups of SAP Fiori 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.

Prerequisites for Implementation

Before implementing the My Inbox application, ensure the following:

1.

Make sure that you have at least one workflow in the back-end system(s) that defines the task types to be

used for My Inbox. Ensure that all the authorizations required for the workflows are maintained.

2.

Make sure that the required SAP Notes are implemented.

3.

Configure the connections between the Gateway system and your back-end system(s) from which you

want to retrieve the work items.

If you are implementing the My Inbox app for SAP Business Workflows, for more information, see SAP

Help Portal at http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0

Configuration and Deployment Information Configuration Guide SAP NetWeaver Gateway

Configuration Guide OData Channel Configuration Connection Settings on the SAP NetWeaver

Gateway Hub System Connection Settings: SAP NetWeaver Gateway to SAP Systems .

If you are implementing the My Inbox app for an SAP NetWeaver Business Process Management (BPM)

system, you must create a logical port to your BPM system, before installing the Task Gateway service. To

integrate BPM, you require SAP NetWeaver 7.31 SP15 or higher. For more information, see SAP Help

Portal at http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0

Configuration and Deployment Information Configuration Guide SAP NetWeaver Gateway

Configuration Guide Configuration Settings for SAP NetWeaver Gateway Supported Scenario

Configuration Settings for OData Channel Scenarios Configuring the Task Gateway Service .

Then, create an SAP system alias for your application. For more information, see SAP Help Portal at

http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0 Configuration and

Deployment Information Configuration Guide SAP NetWeaver Gateway Configuration Guide OData

Channel Configuration Connection Settings on the SAP NetWeaver Gateway Hub System ConnectionSettings: SAP NetWeaver Gateway to SAP Systems Creating the SAP System Alias for Applications .

4.

Activate the Task Gateway Service in Customizing for SAP NetWeaver under Gateway OData Channel

Administration General Settings Activate and Maintain Services .

For more information, see section To activate the service at http://help.sap.com Technology SAP

Gateway SAP NetWeaver Gateway 2.0 Configuration and Deployment Information Configuration

Guide SAP NetWeaver Gateway Configuration Guide Configuration Settings for SAP NetWeaver

Gateway Supported Scenario Configuration Settings for OData Channel Scenarios Configuring the

Task Gateway Service .

5. Assign the software version to the service in Customizing for SAP NetWeaver under Gateway OData

Channel Administration General Settings Assign Data Provider to Data Model activity .

For more information, see section To assign the software version to the service at http://help.sap.com

Technology SAP Gateway SAP NetWeaver Gateway 2.0 Configuration and Deployment Information




















Configuration Guide SAP NetWeaver Gateway Configuration Guide Configuration Settings for SAP

NetWeaver Gateway Supported Scenario Configuration Settings for OData Channel Scenarios

Configuring the Task Gateway Service .

6. If you run on SAP NetWeaver lower than 7.4, assign the back-end system aliases for the Task Processing

Service (/IWPGW/TASKPROCESSING Version 2) in Customizing for SAP NetWeaver under Gateway

OData Channel Development with IW_BEP Registration Assign SAP System Aliases to OData Service.

If you run on SAP NetWeaver 7.4, assign the system aliases for the Task Processing Service in

Customizing for SAP NetWeaver under Gateway OData Channel Administration General Settings

Assign SAP System Aliases to OData Service .


NetWeaver Gateway 2.0 Development Information Developers Guide SAP NetWeaver Gateway

Developer Guide OData Channel Basic Features Service Life-Cycle Activate and Maintain Services

.

Note

Ensure that all application related roles and permission are assigned to the My Inbox user.

Configuration Tasks

If you want to use the pre-configured All Items tile, section Configuring the SAP Fiori Launchpad is optional,

and section Defining the Workflow Scenario is not relevant.

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 application.

Note

This section is only relevant if you are implementing the My Inbox application for your SAP Business

Workflow.

If the step type for the workflow task is User Decision, configuring a task and decisions is optional.

Follow the steps below if you want to make any of the following configuration settings:

Add or hide a decision option

Change the label of a decision option

Define the nature of a decision option (positive or negative)

Make comments mandatory for a decision option

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 SettingsMaintain 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:

o Select POSITIVE for the approve type decision option.

The decision option is displayed either as a green pushbutton or in a gray popover (depending on the

space available) on the detail screen of the application.

o Select NEGATIVE for the reject type decision option.

The decision option is displayed either as a red pushbutton or in a gray popover (depending on the


o

Leave the field empty for multiple decision options.

The decision options are displayed either as gray pushbuttons or in a gray popover (depending on the


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.

Note

This section is only relevant if you want to define and use a scenario-specific tile.

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:





o Scenario Identifier: Define a scenario ID.

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

o Scenario Order: Not relevant for My Inbox.

o

Technical Service Name: Enter /IWPGW/TASKPROCESSING.

o

Version: Enter2

.

o EntitySet External Name: Enter Task.

o Property External Name: Enter TaskDefinitionID.

o 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

Technology SAP Gateway SAP NetWeaver Gateway 2.0 Content Information Content Guide

SAP NetWeaver Gateway Content Guide SAP NetWeaver 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.


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


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.


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:

1. Start the Workflow Builder.

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

3. Open the approval step.

4.

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.


Configuring the SAP Fiori Launchpad for the All Items Tile

In your Gateway system, assign the SAP_FND_BCR_MANAGER_T business catalog role to the application users.

Add the All Items tile from the Tile Catalog to your Launchpad.

If you want to change the pre-configured All Items tile, you can do so by following the steps below:

1. In your Gateway system, assign the SAP_FND_BCR_MANAGER_T business catalog role to the application

users.

2. Start the launchpad designer in your NetWeaver Gateway system with the following URL:

http://<server>:<port>/sap/bc/ui5_ui5/sap/ARSRVC_UPB_ADMN/main.html.

3. Select the Manager Approval (Cross) – Content catalog.

4. Select the All Items tile and fill in the Parameters field as described below:

Enter 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'.





Enter allItems=true&massAction=<true or fales>&quickAction=<true or

false>&sortBy=<property to be used for sorting>&listSize=<number of items you

want to display on your list screen>.

o 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:

o

massAction = true

o quickAction = true

o sortBy = CreatedOn

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

5.

Choose Save.

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 enable Outbox, create a tile as described below.


users.



3.

Select the SAP: Cross - Transactional Apps (SAP_FND_TC_T) catalog.

4. Add a new tile.

5. Choose the App Launcher - Dynamic tile.

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

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

o

Icon: Use any of the available icons.

o Service URL: Enter

/sap/opu/odata/IWPGW/TASKPROCESSING;v=2;mo/TaskCollection/$count/?$filter=

Status eq 'FOR_RESUBMISSION' or Status eq 'COMPLETED'.

o Semantic Object: Enter WorkflowTask.

o Action: Enter displayInbox.

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

where

- scenarioID or allItems is mandatory.

- listSize is optional.

- Default ListSize is 300.

7. Choose Save.

8. Copy the scenario-specific tile you have just created to the SAP_FND_BC_MANAGER_T business catalog.





For more information, see SAP Help Portal at http://help.sap.com -->. http://help.sap.com Technology

Platform SAP Fiori For SAP Business Suite Configuration of SAP Fiori Infrastructure Setup of SAP Fiori

Launchpad .

Configuring the SAP Fiori Launchpad for Your Scenario-Specific Tiles

To enable My Inbox, create a tile for each workflow scenario as described below.


users.



3. Select the SAP: Cross - Transactional Apps (SAP_FND_TC_T) catalog.

4. Add a new tile.

5. Choose the App Launcher - Dynamic tile.

6.

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: Enter

/sap/opu/odata/IWPGW/TASKPROCESSING;mo;v=2/ScenarioCollection?$filter=key eq

'<your scenario identifier>'.

Semantic Object: Enter WorkflowTask.

Action: Enter displayInbox.

Parameters: Enter scenarioId=<ID of your scenario>&listSize=<number of items you want

to display on your list screen>

where:

o scenarioID is mandatory.

o listSize is optional. The default is 100.

7. Choose Save.

8. Copy the scenario-specific tile you have just created to the SAP_FND_BC_MANAGER_T business catalog.

For more information, see Setup of SAP Fiori Launchpad.[RD2]

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.[RD3]

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?s

ap-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:

http://help.sap.com/





http://help.sap.com/fiori_bs2013/helpdata/en/a7/1564526ba1f25fe10000000a423f68/frameset.htm



http://help.sap.com/fiori_bs2013/helpdata/en/40/7c5f525d5df35fe10000000a423f68/frameset.htm




http://help.sap.com/fiori_bs2013/helpdata/en/c4/bd5d521178f55fe10000000a423f68/frameset.htm













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:

o massAction = true

o

quickAction = true

o sortBy = CreatedOn

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

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?sa

p-client=<client>&sap-ushell-config=headerless#Shell-runStandaloneApp?sap-ushell-

SAPUI5.Component=cross.fnd.fiori.inbox&sap-ushell-

url=/sap/bc/ui5_ui5/sap/ca_fiori_inbox&allItems=true&massAction=false&quickAction=t

rue&listSize=300&sortBy.

Specifying Visualization Parameters for Tasks

The supported visualization types in SWFVISU transactions are:

BSP Standard Standard BSP

ABAP WebDynpro ABAP WebDynpro

Object Not Represented Does not display open task action

UI5 based on BSP UI5 based on BSP

INBOX_GEN My Inbox generic application

For more information, see 2200084.

[RD4]









6 App Extensibility: My Inbox

Use

You can extend the My Inbox app according to your business needs for different aspects. For this purpose, the

following extensibility options are available:

Change the list view (S2)

Change the detail view (S3)

Extend the application with additional views

Extension Points

To extend My Inbox, you can use the following extension points:

View Control ID Use

S2.view.xml CustomerExtensionForObjectListItem Allows you to replace the list item

template with your custom list item

template on the list screen.

Make sure that the ID of your custom

list template is the same as the ID of

the standard list item template.

S3.view.xml CustomerExtensionForObjectHeader Allows you to replace the header of

the detail screen with your custom

header.

S3.view.xml CustomerExtensionForInfoTabContent Allows you to define the content you

want to display on the Info tab.

S3.view.xml CustomerExtensionForNoteTabContent Allows you to define the content you

want to display on the Note tab.

S3.view.xml CustomerExtensionForAttachmentTabC

ontent

Allows you to define the content you

want to display on the Attachment

tab.

S3.view.xml CustomerExtensionForAdditionalTabs Allows you to create additional tabs.

S3.view.xml CustomerExtensionForAdditionalDetails Allows you to display additional

information on the detail screen.

S3.view.xml CustomerExtensionForObjectLinkTabCo

ntent

Allows you to define the content you

want to display on the Object Link tab.

S3.view.xml CustomerExtensionForHistoryTabConte

nt

Allows you to display the content you

want to display on the History tab.





View Control ID Use

ViewSubstitution.view.xml CustomerExtensionForSubstitutionRow

Header

Allows you to add columns in the

substitution table.

ViewSubstitution.view.xml CustomerExtensionForSubstitutionRow

Data

Allows you to add column list items in

the substitution table.

TaskUI_S3.view.xml CustomerExtensionForNoteTabContent Extends the note tab content.

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller Hook Use

S2.controller.js extHookGetCustomFilter Allows you to create customfilters that can be used for

filtering the workflow.

S2.controller.js extHookChangeFilterItems Allows you to replace the

standard filters with custom

filters based on the filter key.

S2.controller.js extHookChangeSortConfig Allows you to change those

properties that can be used for

sorting the workflow tasks.

S2.controller.js extHookChangeGroupConfig Allows you to change those

properties that can be used for

grouping the workflow tasks.

S2.controller.js extHookChangeMassApprovalButtons Allows you to add, remove, and

change the action buttons on

the list screen in mass action

mode.

S2.controller.js extHookGetPropertiesToSelect Allows you to retrieve additional

attributes for Task entity from

the back-end system.

S3.controller.js extHookChangeFooterButtons Allows you to add, remove, and

change the action buttons (for

example, claim, release, and

forward) on the detail screen.

S3.controller.js extHookGetEntitySetsToExpand Allows you to retrieve additional

entities from the back-end

system.

S3.controller.js extHookOnDataLoaded Allows you to perform additional

requests and process the

retrieved data.





Controller Hook Use

Forward.controller.js extHookChangeListSizeLimit Allows you to change the

number of recipients displayed

on the Forward screen.

ViewSubstitution.controller.js extHookAddFooterButtonsForSubs Allows you to add buttons forthe substitution screen.

UI Controls

The following UI controls can be hidden from the app UI:

View Control ID Use

S3.view.xml MIBNoteIconTabFilter Allows you to hide the Note tab on the detail

screen.

S3.view.xml MIBAttachmentIconTabFilter Allows you to hide the Attachment tab on the

detail screen.

Business Add-Ins (BAdIs)

To extend My Inbox and add custom code in the Task Gateway Service, you can use the following Business

Add-Ins:

BAdIs in the Back-End System

The BAdI below is only relevant if you are implementing the My Inbox application for your SAP Business

Workflow.

Before Update BAdI (/IWWRK/BADI_WF_BEFORE_UPD_IB)

You can use BAdI /IWWRK/BADI_WF_BEFORE_UPD_IB to handle decision runtime in the

following cases:

o Step type for the workflow task is not User Decision.

o

You want to execute an action before the work item is updated with the user decision.For more information, see SAP Help Portal at http://help.sap.com Technology SAP Gateway

SAP NetWeaver Gateway 2.0 Content Information Content Guide SAP NetWeaver Gateway

Content Guide SAP NetWeaver Gateway Supported OData Channel Scenarios Workflow Services

Workflow Task Service: Central Hub Deployment with IW_BEP Backend Installation Workflow

User Exits .

To provide the custom attributes definition and data, an enhancement spot is provided on the IW_BEP

add-on (to be implemented on the backend system on which the IW_BEP add-on is deployed). The

customer can provide implementations filtered by the Task Definition ID. For this, you must provide an

implementation to the /IWWRK/BADI_TGW_CUSTOM_ATTR BAdI in the

/IWWRK/ES_TGW_CUSTOM_ATTRIBUTE enhancement spot. After implementing the BAdI, you can








consume the custom attribute as follows: Use navigation property CustomAttributeDefinitionData in

entity TaskDefinition to navigate to the CustomAttributeDefinition collection.

BAdIs in the Gateway System

Task Gateway: Change subject in query (/IWPGW/BADI_TGW_TASK_QUERY)

You can use this BAdI to change the task title for all items on the list screen.

Task Gateway: Modify task data (/IWPGW/BADI_TGW_TASK_DATA)

You can use this BAdI to change the task title or task description on the detail screen.

Task Gateway: Provide User details (/IWPGW/BADI_TGW_USER_DETAIL)

You can use this BAdI to change the user details on the detail screen.


NetWeaver Gateway 2.0 Content Information Content Guide SAP NetWeaver Gateway Content Guide

SAP NetWeaver Gateway Supported OData Channel Scenarios Task Gateway Workflow Task Service:

Central Hub Deployment with IW_BEP Backend Installation Workflow User Exits .






www.sap.com/contactsap

© 2016 SAP SE or an SAP affiliate

company. All rights reserved.

No part of this publication may be

reproduced or transmitted in any form or

for any purpose without the express

permission of SAP SE or an SAP affiliate

company.

SAP and other SAP products and services

mentioned herein as well as their

respective logos are trademarks or

registered trademarks of SAP SE (or an

SAP affiliate company) in Germany and

other countries. All other product and

service names mentioned are the

trademarks of their respective

companies. Please see http://www.

sap.com/corporate-

en/legal/copyright/index.epx#trademark

for additional trademark information and

notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark








sap fiori request for approvals 2.0 sp01

Documents