SAP Business Workplace

Since a work item is created for each activity, the SAP Business Workplace can be used to process the activities or work items. However, the actual tasks are part of ProProcess and can therefore only be processed using the ProProcess task widget.

Executing a work item in the SAP Business Workplace automatically navigates to an activity using role-based navigation in ProNovia. This must be set up because the SAP standard does not know the object ProProcess Activity and no transaction can be determined for it.

If no corresponding navigation has been set up, the following message appears when a work item is executed:

The setup of role-based navigation is part of ProObjectLib and is described in Role based Navigation . Specifically, the following settings must be maintained:

Navigation target

A target must be defined for navigation. This consists of a unique ID in the customer namespace (e.g. Z_BPFActivityDisplay), the navigation handler for AFW applications and a name (e.g. ProProcess Display activity). Within the destination, the APPLICATION parameter must be used to define the AFW application to be launched.

Navigation

In order for the navigation target to be started, navigation must be set up. Basically, a separate role can be assigned to each activity, which allows the start of different applications depending on this role. However, it is recommended to set up a cross-role navigation in any case. It is still possible to configure a role-specific, deviating navigation. The following values must be maintained for a role-independent navigation:

Field	Value

Field	Value
Navigation role
Object type	BPF_ACTIVITY
Action	Display
Navigation target	Previously defined target (see above)

When a work item is executed via the SAP Business Workplace, it is locked. This means that events (e.g. completion of the work item) cannot be processed as long as the work item is locked. This may mean that the process cannot be continued until the user navigates back to the SAP Business Workplace. If the user closes the window without navigating back to the Business Workplace first, the process will not continue until the events are processed by the corresponding workflow job.

It is therefore recommended that no applications are set up as navigation targets in which the user remains after the activity has been completed (e.g. worklist applications), as this can significantly delay the execution of individual processes.