With Ramp up of Composition Environment (CE)7.1 and its general availability up from December, 14th, with support package SP3, there will be some new key features available in comparison to SAP NetWeaver 7.0. More new functions & features has already been shipped with CE 7.1 SP1 to Rampup Customers as well as to former support packages of SAP NetWeaver 2004s.
Overview of features coming with CE 7.1, shipped back to Support Packages for SAP NetWeaver 7.0:
Feature | Description | CE 7.1 | Sap NetWeaver 7.0 |
Attachments are now supported on activity and process level |
| SP03 | SPS 13 |
Rename Process Instance Title on Process Instantiation |
| SP03 | SPS12 |
Set Due Date on Action Level in Runtime | Realized on API level | SP03 | SPS12 |
Parameter Consolidation: Consolidation Proposal & Filtering also for nested parameters |
| SP03 | SPS13 |
Parameter Consolidation: Expose a Parameter, that is a structure child without exposing the whole sructure |
| SP03 | SPS13 |
"Looping across phases/blocks (Arbitrary jumping between blocks)" | The Looping Framework enables jumps from an action in one phase/block to an action in some other phase/block. | SP01 | SPS11 |
Complete process when one task is completed (n out of m behavior of parallel blocks) | It is possible to model a GP process wherein it completes all the branches if one is approved by the approver. When a parallel assessment of a scenario has been given to two engineers and when one assessment task is completed and the manager is satisfied he should be able to complete the entire process by approving and completing the first assessment | SP03 | SPS12 |
Optional tasks – status set to complete when being “Skipped” | For optional skipped tasks, status comes as “Completed” during runtime. | SP01 | SPS11 |
WebService CO support Remote Procedure Calls (RPC) |
| SP03 | SPS13 |
Possibility to add additional Parameters on Block and Action level |
| SP03 | SPS13 |
New Key features are coming with SP3:
As of the current release (SP3), there are two new callable object types:
1. User Mapping (Conversion between AS Java and AS ABAP Identities)
Use this object to perform bidirectional conversions of AS Java (UME) unique user IDs to their corresponding AS ABAP unique user IDs. As a prerequisite, you must have configured access to an AS ABAP system by creating a system landscape object with a system alias in the portal
2. Pass Through Form
Use this object to transfer instances of composite forms (PDF files) between process steps. The callable object also allows you to download and modify the input form online
Enhanced features are implemented for the following callable object types:
1. WD4VC Application callable object
The wizard for creating the callable object now supports Flex rendering option, in addition to HTML and Complex parameters (clustered data sets)
2. Web Service callable objectWhenever the Web service definition exposed in the object has been changed, you can update the object right from the design time.
3. Portal iView or Page callable objectUse the object to integrate Knowledge Management (KM), Business Intelligence (BI), and SAP System Transactions in Guided Procedures (GP). To do this, you must expose the following iView types:
- KM Documents iView, KM Search iView
- BEx Web Application or Query as iView
- Transaction iView
Please consider that the following callable object types become deprecated: KM Resource, BI Application, SAP Transaction. So you are no longer able to modify, activate or create callable objects of the types listed. However, the change does not affect running process instances that use active versions of the deprecated callable objects types.
You can now use the Copy Wizard to duplicate and reuse all GP development objects created in the gallery.
GP design time tools are now more flexible in creating, configuring, and consolidating parameters to facilitate process data flow.
The current release offers a set of enhancements and new features to help GP design time and runtime users:
1. Defining and Configuring Notifications: available for actions if the notification is not for a due date.
- on assign: You use this type of notification whenever you want to inform a user that a task has been assigned to him or her. The task appears as a worklist item in the portal.
- on deassign: You use this type of notification whenever you want to inform a user that a task has been removed from his or her worklist and assigned to a different user.
The current release offers a set of enhancements and new features to help GP administrators.
Also Consider the Enhancements in documentation: