Integrating Visual Composer Model with UWL
SAP EP 7.31 SP9, ERP 6 EHP4.
You have a workflow, for instance a basis workflow defined in SAP ERP 6 backend.
This workflow triggers work item creation.
SAP EP is set up and Universal Work List (UWL) is connected to the backend system.
Workflow work items appear in UWL as tasks.
You want to trigger a Visual Composer model to handle the UWL task instead of launching a HTML SAP Gui windows.
This blog will be split in several parts:
- Visual Composer Model
- SAP ERP 6 (or other backend) set upIntegrating Visual Composer Model with UWL Part 2/3
- SAP EP Page linked to VC model Integrating Visual Composer Model with UWL Part 2/3
- UWL Configuration Integrating Visual Composer Model with UWL Part 3/3
- Other references and remarks Integrating Visual Composer Model with UWL Part 3/3
Visual Composer Model
This model will receive the work item id and then retrieve backend data.
Then, depending on the business object you want to handle, appropriate RFC or BAPI will need to be used.
Starting point need to have a text data named WI_ID.
WI_ID will be filled from the UWL task.
Others data are mainly used to unit test the VC model.
RFC SAP_WAPI_READ_CONTAINER is used to read the work item container.
Start is mapped to the data source, WI_ID is linked to INPUT input port.
Depending on your business object you will have to use the work item container accordingly to retrieve the business object key.
In my case I used QM notification tasks, Business Object BUS2078.
A filter operator is used
The Form view is defined as follow:
NUM_DEMANDE and NUM_TASK are my business object keys.
In order to test the model you can map to the start work item default value.
Result (work item is ‘hard coded’) :
Final model with Business objet call (BAPI_QUALNOT_GETDETAIL)
Remark: In my example, I used SAP_WAPI_READ_CONTAINER to read data. If you already have everything in the container and have these attributes available in the UWL, you can directly call the RFC or BAPI by passing for example the object key.