...
- Next, add an entry for the process you want to integrate between SAP and OneList. If you are integrating OneList with an SAP Workflow, you will need to know the Standard Task ID (use the Workflow Builder (SWDD) or transaction PFTS to get this information) that contains the processing steps. Alternatively, if you are integrating a Fiori App Builder application with OneList, you will need to know the FAB Form name. For completeness, the screenshot below contains an example of both options - although we will only look at the Workflow integration below (the same steps will be followed for integration with a FAB App):
- OneList Job Configuration
Highlight the User integration entry (configured above, and remember this is only done once):
Then double-click the 'OneList Job configuration entry in the tree structure. Configuring this step allows the Adapter framework to communicate with the OneList instance, specifically for user integration. IQX has provided a standard user integration Adapter class (/IQX/CL_OL_SYNC_USERS), but in rare circumstances your organisation may need to alter the behaviour of this class. In that case, you will have to create a subclass of this class (see step 1 above, under SAP Development tasks) and override the relevant methods to suit your needs. in that case, instead of /IQX/CL_OL_SYNC_USERS, use the name of your subclass in the below configuration steps.
You will need to define entries for the SYNC_USER_REQUEST and SYNC_USER_REQUEST_DELTA OneList User Integration APIs/Actions. For each entry, specify:- Adapter Class name: /IQX/CL_OL_SYNC_USERS,or your or your user subclass
- Frequency in minutes: how often the background job calling this OneList API should run. We recommend between 5 and 30 minutes.
- Active - A flag to set whether this job should run. During specific scenarios (shutdown, data take-on, etc.) you may want to disable individual API calls. Normal value will be ticked.
The end result should look something like this:
Now highlight the process integration point for which you want to configure the background jobs ("SAP WF Process" in this example):
Then double-click the 'OneList Job configuration entry in the tree structure. Configuring this step provides a link between your SAP Adapter class (for example ZCL_OL_PO_ADAPTER, created above) and the IQX OneList SAP Adapter framework. For each entry defined here, the Adapter framework will create a background job at the specified frequency, thereby pushing / pulling data to and from OneList. You will need to define entries for the following 4 OneList Integration APIs/Actions:- SYNC_ACTIONS
- SYNC_ATTACHMENTS
- SYNC_CHANGED_TASK_LIST
- SYNC_DELTA_TASK_LIST
For each entry, specify:- Adapter Class name: your class created above, for example ZCL_OL_PO_ADAPTER
- Frequency in minutes: how often the background job calling this OneList API should run. We recommend between 1 and 5 minutes at most.
- Active - A flag to set whether this job should run. During specific scenarios (shutdown, data take-on, etc.) you may want to disable individual API calls. Normal value will be ticked.
The end result should look something like this:
- Next, add an entry for the process you want to integrate between SAP and OneList. If you are integrating OneList with an SAP Workflow, you will need to know the Standard Task ID (use the Workflow Builder (SWDD) or transaction PFTS to get this information) that contains the processing steps. Alternatively, if you are integrating a Fiori App Builder application with OneList, you will need to know the FAB Form name. For completeness, the screenshot below contains an example of both options - although we will only look at the Workflow integration below (the same steps will be followed for integration with a FAB App):
...