Ansicht
Dokumentation
Business Workflow (Enhanced) ( RELN640BCBMTWFM_1 )
General Material Data TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Short text
Business Workflow (Enhanced)
Use
Correlations (New)
A correlation enables you to identify objects that belong together, for example, a quotation and the relevant sales order. This involves correlating the objects by using one or more common elements, for example, the quotation number. You define a correlation by using the correlation editor (Environment -> Development -> Correlation Editor). The correlation is activated by a control step and then used in a wait step.
Step Types (Enhanced)
Block (New)
The new step type Block enables you to group together steps that are to access the same local data. The local container contains the elements of the Workflow container and can be enhanced with local elements. You can also define the following for a block:
- Latest end
- Exception handler
- Table-supported ParForEach (Parallel For Each)
A new work item type Block Work Item (abbreviation X) is created at runtime for a block.
Multiple Condition (Enhanced)
A multiple condition can now also be of type Switch. A switch enables you to define multiple processing branches and to define a separate condition for each branch. However, it is still possible to define multiple conditions. In this case use type Case.
Activity (Enhanced)
In an activity with a ParForEach, it is now possible to define an end condition for the ParForEach.
To make this function clearer, the tab pages have been rearranged. The new tab page Details contains details that were previously included on the Control tab page, for example, information about the work item procedure (Advance with Dialog and so on).
Fork (Enhanced)
You can now define an end condition in a fork with dynamic parallel processing.
Wait for Event (Enhanced)
You now have the following new options for the step type Wait for Event:
- Wait for Condition: The step waits until the specified condition returns true.
- Wait Using Workflow: The event is initially received by Workflow and is then transferred to the step once it is active.
For the options Wait for Event and Wait Using Workflow you can define that a correlation is to be used to define the event.
Local Workflow (New)
It is now possible to define local Workflows. Contrary to a Sub-Workflow, a local Workflow has full access to the data in the Workflow container. In the local container you can define additional container elements. A local Workflow is started by a local event. You can use a local Workflow, for example, to model reactions to business exception situations. For example, if you model how an order is processed in Workflow, you can use a local Workflow to model how you want exception handling to function should the order be deleted. This local Workflow can be started by a local event Order Deleted and, for example, trigger a notification to be sent to the administrator.
Process Control (Enhanced)
It is now possible to use a process control to activate a correlation or throw an exception.
User Decision (Changed)
To make this function clearer, the tab pages for the step type User Decision have been rearranged. The new tab page Details contains details that were previously included on the Control tab page, for example, information about the work item procedure (Advance with Dialog and so on).
Form Step (Enhanced)
In the form that is used for the form step you can now make the following adjustments:
- Adapt function texts (function module SAP_WAPI_FORM_SET_FUNC_TEXTS)
- Adapt the label of the Form Fields tab page (function module SAP_WAPI_FORM_SET_TAB_TITLE)
Local Events (New)
The tab page Local Events is now available in the version-specific basic data of a Workflow. A local event can start a local Workflow.
Event Creation Using ABAP Classes (New)
You can now also trigger events by using ABAP classes. You use the ABAP class CL_SWF_EVT_EVENT for this purpose.
Binding (Enhanced)
Functional Methods in Expressions (New)
You can use a functional method within an expression on the source side of a binding row. You can use a function method to execute calculations or data transformations, for example.
Implicit Support for GET_ Methods
GET_ methods of an object are now displayed as additional attributes of the object (for example, GET_ADDRESS is displayed as ADDRESS). The prerequisite is that the GET_ method does not have any import parameters and only gets one return value (parameter Result or Returning). You can use the attributes that are made available by GET_ methods in expressions as usual, for example, in a binding (on the source side) or in work item texts. The support for GET_ methods applies for both BOR objects and ABAP-OO. This enables you to access attributes of persistent ABAP-OO classes for the first time. Using GET_ methods, BOR objects can now offer structured attributes for the first time.
Programmed Binding (New)
You can now also implement a programmed binding as an ABAP class. A binding that is implemented as an ABAP class is displayed in the list of binding statements as an enhancement and is visible in all Workflows. An enhancement such as this is completely integrated in the binding editor. You can implement you own checks for the class and choose the names and symbols to be used to display the enhancement in the binding editor.
Binding Editor (Enhanced)
The options for binding statements have been enhanced.
ABAP Classes in Workflow (New)
In the definition and runtime components of SAP Business Workflow you can now use ABAP classes that support the IF_WORKFLOW interface. This means that all public attributes of a class can be accessed. A class that implements the IF_WORKFLOW interface can be used in any workflow. The class is automatically released for use in workflows when the interface is implemented.
The interface uses the following methods:
- BI_PERSISTENT~FIND_BY_LPOR: Converts a persistently saved representation of an object to an instance of the relevant ABAP class.
- BI_PERSISTENT~LPOR: Provides the persistent display for an existing instance of an ABAP object.
- BI_PERSISTENT~REFRESH: Ensures that all values of the object are valid and are identical to the persisted representation of the object.
- BI_OBJECT~DEFAULT_ATTRIBUTE_VALUE: Gets the display name of the object.
- BI_OBJECT~EXECUTE_DEFAULT_METHOD: Default method of the object and is executed when, for example, the object is called in the Business Workplace.
- BI_OBJECT~RELEASE: Signalizes that the instance of the object is no longer required.
Top-Down Modeling (New)
The options in the Workflow Builder now enable you to use top-down modeling. Top-down modeling allows you to create workflow definitions taking into account block orientation without knowledge of the individual tasks used. At an early modeling stage, it is therefore possible to create incomplete but consistent workflow definitions.
Structure of Workflow Builder UI (Enhanced)
In the Workflow Builder, messages, check results, and search results are now displayed in a separate screen area. The individual screen areas now have separate titles.
The list view is no longer used. You can continue to use the graphical modeling or tree modeling functions.
Furthermore, you can now also move or copy a block and its corresponding steps by using Drag&Drop. To do so, select the Quick Block Operations icon.
E-Mail Notifications (Enhanced)
The e-mail notification functions for SAP Business Workflow (Report RSWUWFML) have been enhanced. They now offer the functions that were previously only available with Microsoft Outlook Integration or Lotus Integration (without the calendar synchronization of Microsoft Outlook Integration). The new functions replace the SAP MAPI Service Provider and SAPforms, which were previously used for the integration of Microsoft Outlook and Lotus Notes.
Groupware Support
Notifications can be sent in the form of e-mail notifications (HTML and Text-Only). E-mail notifications are displayed in the user's default mail inbox. This means that the rules defined by the user also apply for e-mail notifications. Messages can also be sent to a dispatcher to support further Groupware functions. Only the HTML format for Microsoft Outlook is supported for HTML messages at present.
Message Structure and Delivery
One notification is created for each work item and user. You can define which notifications are sent individually as e-mails and which are grouped together in a collective message. You can control when exactly messages are delivered by using schedules. A message can contain a URL or an attachment to enable you to either display or execute the work item directly. The work item is displayed or executed in one of the following front end applications:
- SAP GUI for HTML, based on the Internet Transaction Server (ITS)
- SAP GUI for HTML, based on the SAP Web Application Server (Web AS) Release 6.40 or higher
- Web browser for work items that are based on Web technologies such as WebFlow Services, Business Server Pages (BSP), WebDynpro and so on
- SAP GUI for Windows
Installation and Configuration
E-mail notifications are configured centrally by administrators by using a transaction. If SAP GUI for windows is used for displaying and executing work items, then the standard installation of the SAP GUI for Windows is sufficient. No user-specific configuration settings need to be made in the client software.
User Management and Authorizations
The e-mail notification function can be implemented for an unlimited number of users. If Single Sign-On is activated, a user can navigate from an e-mail notification directly to the relevant SAP system by selecting the link to an executable work item. You do not need to log on separately when using Single Sign-On.
Deprecated Features
In the future, the following functions will no longer be supported:
- Microsoft Outlook Integration for SAP Business Workflow, Lotus Integration for SAP Business Workflow (also known as SAP MAPI) and SAPforms (see also SAP Note 627397)
- Step type While loop
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Deadline Monitoring (Changed)
Previously, it was possible to monitor a deadline over a period of time or to monitor a deadline just once. It is now only possible to monitor deadlines periodically. As a result, you must change any non-periodic monitoring settings.
Define Metadata for Visualization (New)
In transaction SWFVISU, you can specify parameters for different visualization types such as WebDynpro, People Centric UI, iViews, and so on. These parameters are required by the UWL (Universal Worklist) to start the corresponding application.
Monitoring and Alerts (Enhanced)
Business Workflow is now integrated in CCMS.
Work Items with Deleted Users (New)
The new report Work items with Deleted Users under Administration -> Workflow Runtime fetches the work items that are assigned to an agent whose user has been deleted.
Effects on Customizing
See also
General Material Data ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 13515 Date: 20240508 Time: 164210 sap01-206 ( 232 ms )
