introduction to universal worklist

7/27/2019 Introduction to Universal Worklist

http://slidepdf.com/reader/full/introduction-to-universal-worklist 1/90

Introduction toUniversal Worklist



Business Task ManagementIntroducing Universal Worklist

Collaboration Tasks

UWL System Configuration

Customizing UWL, adding a new view

Substitution and Attachments in UWL

Appendix: Details for adding a new system toUWL and user personalization




Collaboration Tasks







SAP AG 2007, SAP 4

Business Task Management – Definition

Business Task Management is the automation,

execution and monitoring of tasks Coordinate and execute tasks arising from automated process flows

and spontaneous events

Track the progress of tasks

Tasks include a wide variety of activit ies Business Transaction

Alert

Form

Desktop Document

Impromptu Request



SAP AG 2007, SAP 5

Lifecycle of a Task

ProcessInstance

Trigger to startprocess

Process description

Task description

Possible task

participants

WorkItem

User claims the

Activity or Task Activity

ActivityUser

Interaction

Form

Business transactionDesktop document



SAP AG 2007, SAP 6

Execution of Business Task Management

Task 1

TASK MANAGEMENT UI (Universal Worklist)

Task 2

Events trigger tasks(workitems, notifications)

User Interaction

with BPM Runtime

Stable Processes

Human Interaction

Collaborative Processes

Ad Hoc Processes

Dynamic Processes

Task x

BPM RUNTIME

Collaboration tasks

Guided Procedures

Business workflows



SAP AG 2007, SAP 7

Functional Areas

Universal Worklist

Single point of access for managing your work

Can be personalized to suit each user’s working sty le

Process-specific views can be customi zed for expert users

Collaboration Tasks

Enables end-users to c reate their own ad hoc processes and drive coll aboration

Includes various types of collaboration tasks including actions, approvals, and feedback

Users track progress of their delegated task

Guided Procedures

Designed to implement process flows with greater ease and speed across multiple applications

Integrates backend system transactions

Includes process templates that can be easily re-used or copied and easily changed

Interactive Forms

Generate forms that contain data extracted from core systems

Use dynamic or static forms

Accelerate forms-based business processes

Business Workflow

Structured, repeatable, simple to complex business process

Manages the tasks that need to be performed and who should perform the tasks

Ensures business process deadlines, compliance regulations, and service agreements are appropriatelymonitored and enforced

Alerts

Exception-triggered noti fications

Define fo llow-on activiti es

Inter-System alerting




Collaboration Tasks







SAP AG 2007, SAP 9

How Do I Manage All My Work?

Traditionally users had to access a variety of inboxes to v iew and

act on important tasks

The large number of applications and tasks make it difficult to

understand and priorit ize work

The Universal Worklist simplif ies the user’s work

Single consistent interface

Easy to use

Easy to access



SAP AG 2007, SAP 10

Universal Worklist Features at a Glance

Give users a unif ied and centralized access to their work andrelevant information. Users do not have to search for their work.

Aggregate task i tems from multiple and different systems into onelist.

SAP Business Workflow

Collaboration Tasks

Alert Management System

Knowledge Management Notifications

Guided Procedure Actions

Custom worklists enable specific views for specific tasks

Enable users for direct decisions and actions

Users can personalize appearance to suit their individual working

styles

Can funct ion as an application-specific inbox – applications canbypass having to implement their own inbox



SAP AG 2007, SAP 11

First look at the Universal Worklist

UWL is part of the standard user end role, accessed via Home - Work

Hint: To Refresh your lists of tasks, use the drop

down menu near the Hide Preview link.



SAP AG 2007, SAP 12

UWL provides task list, execution, and context

Task Context

Task Lis t

Task Execution



SAP AG 2007, SAP 13

Launch Work Transaction

Parameterized launching for

• BSP

• iView

• URL• Web Dynpro

• SAP GUI (for HTML)



SAP AG 2007, SAP 14

Standard Task Views & Filters




Collaboration Tasks







SAP AG 2007, SAP 16

Collaboration Task Features at a Glance

End-users can easily create their own processes without any prior experience with workf low systems

Gives users the power to deal with quickl y changing businesscondi tions. Users use collaboration tasks to spontaneously collaboratewithout needing to wait for company-wide business process change

Makes it easy to define one-time processes. The minimal effor t requiredmeans that users will use collaboration tasks to deal with many one-

time situations

End-users can check the status of processes they have created andensure that work is completed on time

Users can link new processes to work items they receive. This providesthem with an easy way to perform and track additional work that may berequired in response to a work request



SAP AG 2007, SAP 17

Collaboration Task Wizard to create Tasks

The following figure shows the type of collaboration tasks

available and the applications that use collaboration tasks.

Collaboration

Launchpad (CLP)

Collaboration Room

(CR)

UniversalWorklist (UWL)

New Task

New Task

New Task

Create Ad Hoc

Request Single-Step Task

Multiple-Step Task

Request for FeedbackRequest for Nomination

Single-Step Task

Multiple-Step Task

Request for Feedback

Request for Nomination



SAP AG 2007, SAP 18

Collaboration Tasks Wizard – New Task



SAP AG 2007, SAP 19

Collaboration Tasks Wizard – Task based on an existingwork item

Original task is locked until

collaboration task completes




Collaboration Tasks







SAP AG 2007, SAP 21

Add the system to UWL Configuration (1)

System Administration -> System Configuration-> Universal Worklist &

Workflow

AdhocSystem is for

collaboration tasks.

ActionInbox is for KM

notifications.



SAP AG 2007, SAP 22



Workflow



SAP AG 2007, SAP 23


Web Dynpro Launch System: Enter System Alias for a system definition with J2EE port

defined in the WAS system attribute.*

User Roles: Delimit who can get work items via the user role. For example, you can

assign a portal role here, such as “ buyer” . Only users with the role “buyer” will see items

from B7QCLNT000 in UWL.*

System Configuration Groups: Option to have various tabs that point to UWL. UWL items

for B7QCLNT00 will onl y appear in portal navigation tabs that are mapped to a specific

configuration group.

Pull Channel Delta Refresh Period: How often we should check to see if new items haveentered the user’s inbox.*

Snapshort Refresh Period: How often we should retrieve all items from the backend

system.*

Asterik items (*) deno te items that are new in NW2004s.



SAP AG 2007, SAP 24

Register the Work Item Types

Look at each workflow step and ask “ How

should I launch this step”

TS30000016 = SAPGui for HTML

TS99700023 = ITS MiniApp TS99700034 = BSP

TS99700087 = URLB7QCLNT000




Collaboration Tasks







SAP AG 2007, SAP 26

Customized Application Specific Views

User can look at all tasks, or select a view for specific tasks.



SAP AG 2007, SAP 27

Types of UWL Optional Configurations

You can create custom worklists

View for specific task

View for user decision

View for to make multiple choices simultaneously

You can conf igure how the work item launches

SAP Transact ion (SAPGUI for HTML or ITS MiniApp or IAC)

iView or Portal Page

Business Server Page

WebDynpro Appl ication



SAP AG 2007, SAP 28

Add a custom view for a specific task

Standard view – no custom view

Custom View



SAP AG 2007, SAP 29

Two different custom views for the same work item



SAP AG 2007, SAP 30

Steps to create a custom view for a specific task

1. Identify the actual task number that correlates to the exact step

you want to customize.

2. Determine the exact attributes you want to use as columns.

3. Create a XML file with your custom view.

4. Upload your XML file.



SAP AG 2007, SAP 31

Identify the task to be customized

Transaction code: SWDD

Workflow: WS74500036



SAP AG 2007, SAP 32

Determine the exact attributes



SAP AG 2007, SAP 33

Create an XML file: Major components

XML File has two major components:

Item type: Identifies the exact task and listseach attr ibute that wil l be used.

View: Defines the name of the view, how it wil l

work, and the custom columns for the view.



SAP AG 2007, SAP 34

Create an XML file: Define the Item Type

<ItemType name="uwl.task.webflow.TS74507936"

connector="WebFlowConnector"

defaultView="myApprovalView"

defaultAction="viewDetail"

executionMode="pessimistic">

<CustomAttr ibuteSource id="ABAP_BOR"

objectIdHolder="externalObjectId"

objectType="FORMABSENC"

cacheValidity="final">

<Attribute name="DEPARTMENT" type=“str ing" displayName=“ Department"/>

<Attribute name="LASTDAYOFABSENCE" type="date" displayName="Last day of absence"/>

<Attribute name="FIRSTDAYOFABSENCE" type="date" displayName="First day of absence"/>

<Attribute name="COSTCENTER" type="string" displayName="Cost Center"/>



SAP AG 2007, SAP 35

Create an XML file: Define View

<View name="myApprovalView" width="98%"

supportedItemTypes="uwl.task.webflow.TS74507936"

columnOrder="attachmentCount, detailIcon, subject, createdDate, Department,FIRSTDAYOFABSENCE, LASTDAYOFABSENCE"

sortby="createdDate" visibleRowCount="10" headerVisible=" yes"

selectionMode="SINGLESELECT"

tableNavigationFooterVisible="yes"

emphasizedItems="new"

displayOnlyDefinedAttributes="no">

<Descriptions default="Vacation Requests to Approve">

<ShortDescriptions>

<Description Language="en" Description=" Vacation Requests to Approve" />

</ShortDescriptions>

</Descriptions>



SAP AG 2007, SAP 36

Define Actions for the View

<Actions>

<Action reference=" removeFromNavigation" />

<Action reference="addToNavigation" />

<Action reference="personalize" />

<Action name="launchSAPAction"

handler="SAPTransactionLauncher" >

</Action>

</Actions>



SAP AG 2007, SAP 37

Upload XML file (1)

1. Select System Admin istration->System conf iguration->Universal Worklis t &

Workflow and select Click to Admin ister Item types and view definitions .

2. Select Upload New Configuration and enter you fi le name and upload for the

appropriate system.

3. You should receive a successful message.



SAP AG 2007, SAP 38

Upload XML file (2)

4. Clear the cache.



SAP AG 2007, SAP 39

View Result



SAP AG 2007, SAP 40

Decision Customization

The user can submit multiple decisions at once if

the applications provides a corresponding view for the item type.

Technically, the UWL can execute the selected decision as

Business Workflow User Decision

Function Module call (any)

Item completion with update of (name, value) pair in the workflow container

Terminating Event

No coding required, this can be configured in the view XML.



SAP AG 2007, SAP 41

Example of customized user decision step

Example of XML required for this decision based on a BusinessWorkflow user decision step:

<Action name="goCol" groupAction=" yes” handler="UserDecisionHandler">

<Properties> <Property name=“ decisionKey" value="0001" />

</Properties> <Descriptions default="Continue"/>

</Action>



SAP AG 2007, SAP 42

Example of decision using the workflow container

Results from UWL are

evaluated in the workflow



SAP AG 2007, SAP 43

Launch Customization: ITS MiniApp for SRM

Launches

a MiniApp

XML Example

<Action

name=“ launchSAPAction”

handler=“SAPMiniAppLauncher”>



SAP AG 2007, SAP 44

Launches

a BSP

Launch Customization: BSP for Business Workflow

XML Example

<Action name=“ launchWsHandler”

handler=“XhandlerLauncher”>



SAP AG 2007, SAP 45

Launch Customization: ABAP Web Dynpro

XML Example

<Action name=" launchWebDynProABAP"

handler="SAPWebDynproABAPLauncher“ >

Launches an

ABAP Web

Dynpro

1

2

3



Business Task Management

Introducing Universal Worklist

Collaboration Tasks







SAP AG 2007, SAP 47

Substitution via dropdown menu

Hint: Manage Subst itut ion Rules is accessed via the drop

down menu near the Hide Preview link.

Substitution requires NW2004s for BOTH UWL and your

backend system.



SAP AG 2007, SAP 48

Substitution (1)



SAP AG 2007, SAP 49

Substitution (2)



SAP AG 2007, SAP 50

Substitution (3)



SAP AG 2007, SAP 51

Substitution (4)



SAP AG 2007, SAP 52

Follow Up (Resubmit)



SAP AG 2007, SAP 53

Follow Up (Resubmit)

Choose future date



SAP AG 2007, SAP 54

Follow Up – Task for Resubmission

Item gone

Pull the itemback tocurrent time



SAP AG 2007, SAP 55

Manage Attachments



SAP AG 2007, SAP 56

Summary

Business Task Management enables you to have central

access to all your tasks via NetWeaver.

The tasks can include alerts, business workf low items,

knowledge management notif ications, collaboration

tasks, and guided procedures tasks.

The Universal Workl ist can be customized via XML and

personalized for each user.



SAP AG 2007, SAP 57

Q

Questions?



SAP AG 2007, SAP 58

Please complete your session evaluation.

Be courteous — deposit your trash,

and do not take the handouts for the following session.

Feedback

Thank You



Business Task Management

Introducing Universal Worklist

Collaboration Tasks





F f t d i T hEd S i



SAP AG 2007, SAP 60

For reference, not covered in TechEd Session

This information in this appendix is for student reference. This

information wil l not be covered during the TechEd session.

P i it f C fi ti



SAP AG 2007, SAP 61

Prerequisites for Configuration

Before configuring UWL ensure that:

You have administration r ights for the Portal

Each person who will be using UWL must have a user

account defined on the portal and in the backend system.

They must have access to transaction code SWK1 and

access to funct ion group SWK1.

Users should have current work i tems in their Business

Workplace on the backend system.

R i d t t fi UWL



SAP AG 2007, SAP 62

Required steps to configure UWL

1. Define your SAP system

2. Create a System Alias to uniquely identify the system

3. Define exact settings for technical connections

4. Define how users are mapped

5. Test system connections

6. Add the new system to UWL configuration

7. Register work item types

D fi SAP t (1)



SAP AG 2007, SAP 63

Define your SAP system (1)

1

2

3

4

D fi SAP t (2)



SAP AG 2007, SAP 64


Type of sys tem. For UWL

this will normally most li kely

be a Load Balancing system.We will use a dedicated

application server.

5

Define o r SAP s stem (3)



SAP AG 2007, SAP 65


6

8

7




SAP AG 2007, SAP 66


9

10

Create a System Alias



SAP AG 2007, SAP 67

Create a System Alias

NOTE:

System Alias links SAP

system to UWL. UWL will not

work correctly without the

System Alias.

Update Connector Information (1)



SAP AG 2007, SAP 68


Example of fields for

“ Dedicated Appli cation Server”

Example of fields for “R/3

system with load balancing”




SAP AG 2007, SAP 69

1

2

3

4

5


Transaction code SCC4

1) Select to edit the Object.

2) Select Connector.

3) Provide the actual host name for the

backend system.

4) The Logical System name MUST be the

exact same as the backend logical

system name.5) Provide the exact backend Client,

System ID, and System number.

Update the WAS Information: WAS Host Name



SAP AG 2007, SAP 70

Update the WAS Information: WAS Host Name

iwdf9004.wdf.sap.corp:1081

Transaction code

SMICM

Update the WAS Information: WAS Host Path



SAP AG 2007, SAP 71

Update the WAS Information: WAS Host Path

Transaction code

SICF

Update the ITS Information



SAP AG 2007, SAP 72

Update the ITS Information

Update the User Management Information



SAP AG 2007, SAP 73

Update the User Management Information

USIDPW means each Portal

user must be mapped to abackend user.

Map Portal User to System User



SAP AG 2007, SAP 74

Map Portal User to System User

1

23

4

5

6

Test System Connections



SAP AG 2007, SAP 75

Test System Connections

System Administration -> System Configuration ->System Landscape -> Portal Content

1

2

3

4




SAP AG 2007, SAP 76



Workflow

AdhocSystem is for

collaboration tasks.

ActionInbox is for KM

notifications.




SAP AG 2007, SAP 77



Workflow




SAP AG 2007, SAP 78


Web Dynpro Launch System: Enter System Alias for a system definition with J2EE port

defined in the WAS system attribute.*

User Roles: Delimit who can get work items via the user role. For example, you canassign a portal role here, such as “ buyer” . Only users with the role “buyer” will see items

from B7QCLNT000 in UWL.*

System Configuration Groups: Option to have various tabs that point to UWL. UWL items

for B7QCLNT00 will onl y appear in portal navigation tabs that are mapped to a specific

configuration group.

Pull Channel Delta Refresh Period: How often we should check to see if new items have

entered the users inbox.*

Snapshort Refresh Period: How often we should retrieve all items from the backend

system.*

Asterik items (*) deno te items that are new in NW2004s.




SAP AG 2007, SAP 79


Look at each workflow step and ask “ How

should I launch this step”

TS30000016 = SAPGui for HTML

TS99700023 = ITS MiniApp

TS99700034 = BSP TS99700087 = URL

B7QCLNT000

End User Personalization Choices



SAP AG 2007, SAP 80

End User Personalization Choices

Columns: Which columns and the order

Sorting preferences

Data properties

How many items per page

How often to refresh the page

Date range of items

Warnings for Ad Hoc due dates

Create their own custom filters with in custom views

View Personalization



SAP AG 2007, SAP 81

End user creating views with filters (1)



SAP AG 2007, SAP 82

g ( )

User requires custom fil ter to only see requests from

the Athletic Department

2

1

To add custom view with a filter

1.Select Personalize View

2.Select Duplicate

End user creating views with filters (2)



SAP AG 2007, SAP 83

g ( )

3To add custom view with a filter

3.Name your custom view

4.Add your fil ter criteria

4

End user creating views with filters (3) - Result



SAP AG 2007, SAP 84

g ( )

User now has a custom view, MyOwnApprovals

User also has a custom fil ter, myOwnFilter

Only requests from the Athletic Department appear

Launch Work Transaction



SAP AG 2007, SAP 85

Parameterized launching for

• BSP

• iView

• URL

• Web Dynpro (Java or ABAP)

• SAP GUI (for HTML)

Launch Customization: ITS MiniApp for SRM



SAP AG 2007, SAP 86

pp

Launches

a MiniApp

XML Example

<Action

name=“ launchSAPAction”

handler=“SAPMiniAppLauncher”

>

Launch Customization: BSP for Business Workflow



SAP AG 2007, SAP 87

Launches

a BSP

XML Example

<Action name=“ launchWsHandler”

handler=“XhandlerLauncher”>

Launch Customization: ABAP Web Dynpro



SAP AG 2007, SAP 88

XML Example

<Action name=" launchWebDynProABAP"

handler="SAPWebDynproABAPLauncher“ >

Launches an

ABAP Web

Dynpro

1

2

3

Details of XML for Web Dynpro Launch



SAP AG 2007, SAP 89

<ItemTypes><ItemType name="uwl.task.webflow.TS65507956" connector="WebFlowConnector"

defaultView="myABAPWebdynpro" defaultAction="viewDetail"executionMode="pessimistic"><ItemTypeCriteria externalType="TS65507956" connector="WebFlowConnector"/>

<Actions>

<Action name="launchWebDynProABAP" handler="SAPWebDynproABAPLauncher"><Properties>

<Property name="WebDynproApplication" value="ZTECHED2005FORM_ENTRY"/><Property name="WebDynproNamespace" value="sap"/><Property name="DynamicParameter" value="WI_ID=${item.externalId}"/>

</Properties></Action></Actions></ItemType>

Important details: TS number , action handler, actual web dynpro application,

work item ID, and system (if web dynpro wi ll be called on a different system)

Copyright 2007 SAP AG. All Rights Reserved



No part of this publication may be reproduced or transmitted in any form or for any purpose without th e express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, O S/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i 5, System p,

System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of th e Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trad emark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license f or technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.Data contained in this d ocument serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any f orm or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to th e implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This

limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of t hird-party Web pages nor provide any warranty whatsoever relating to third-party W eb pages.

introduction to universal worklist

Documents