Skip to end of metadata
Go to start of metadata


Note Number

Short Text               


Sample Implementation



Workflow log: Scenario-specific T100 messages

You want to add scenario-specific log entries to the work item history. These log entries enable a workflow status reporting from the application point of view.




Executing background work items with jobs

You can now execute certain tasks within a workflow using job processing
to preserve tRFC resources and to obtain better distribution of the
existing resources. ATTENTION! Please also apply note 1685032  which provides information about activating and configuring the jobs.




Automatic replacement of work items

If you cancel execution of a dialog work item, the work item remains in status STARTED in the inbox of the canceling user and is still assigned to that user. If the canceling user wants to make this visible for all original processors, they must replace it manually. This manual interim step can be automated with this note. ATTENTION! You must also apply note 1708610 so you can enable this functionality.




Mail send step: Enhancement of mail title to 255 bytes

The title of a mail that is sent with the mail send step has the maximum
length of 50 bytes. You want to increase this to 255 bytes. ATTENTION! You must also apply note 1658491 so you can enable this functionality in transaction SWPA.




Workflow Builder: Dynamic step priority

The priority can also be specified at the time of definition by an expression ("Miscellaneous" tab page). If the expression has a valid value (1...9) at runtime, the step is created with this priority, otherwise, the old response remains




Generic object services for ABAP 00

This note delivers an example implementation for the class CL_SWF_FORMABSENC. The call of generic object services in implemented in the function module SWX_FORMABS_DISPLAY as an example




SWDM: Where-used-list for BOR and class methods

Where-used list for BOR and class methods that are used in workflow tasks




User decision with automatic note

At the time of definition, you should be able to specify whether the user must or should enter a note (reason) for each decision option in a user decision. At runtime, after the user selects the option, the system automatically opens the input screen for notes




Dynamic user decision

Previously, the system always displayed all alternatives defined for a step during a user decision. In future, there is to be an option to hide individual alternatives

Blog 'Dynamic user decisions in SAP Business Workflow'  by R. J. van Looy



Dynamic columns in outbox and resubmission

The dynamic columns, which so far are only available in the workflow inbox, are to be provided in the other workflow-relevant folder areas outbox and resubmission as well




Business Workplace: 12 dynamic columns instead of 6

The number of dynamic columns should be doubled from 6 (currently) to 12




Adaptation of the BOR-editor

The previous editor for BOR-programs is replaced by a new editor which supports additional functions such as syntax Highlighting and code completion. This new editor is available by importing of the corresponding Support Packages. Due to the complexity of the changes it is not possible to deliver via a note



1286336  1705866 

SWIA: New "Logically Delete" function for mass processing

You want to delete a large number of work items logically. This applies
particularly to the ccBPM environment to clear open correlation
instances. Up to now, you could not use standard SAP tools to do this. Without a customer development, the only options are the following two workarounds (1) Using the work item administration to manually delete them individually. (2) Using the report RSWWWIDE to physically delete them.