...
The adapter is a daemon service. It needs permission to query all user’s tasks, as well as the business objects and attachment files related to the tasks. You need to decide whether it should use the running serivce service account or an explicit account to access source system data and make sure that account has sufficient permission to query the soource source data.
The adapter may need to impersonate the approver to perform task action in the source system. Impersonation requires permissions such as to run SAP background job as the approver, or to request access token using the approver’s refresh token.
...
the source system user id and the OneList user id are the same;
the adapter can automatically map the source user id to the OneList user id.
The user sync process invovles involves calling the /onelistserver/api/datasync/GetUserSyncRequests to get the list of user ids to be sync’d and calling the /onelistserver/api/datasync/SyncUsers to post the user profile and user mapping to OneList. The adapter should query the user information from either the source system or the identitify identity management system, e.g. internal AD or Azure AD. In response to the Sync Users API, OneList will create user accounts and send email notification to the new users inviting them to start using OneList.
If there is no relationship between the source system user id and the OneList user id then the adatper adapter does not implement the user sync process. OneList will prompt users log in to the source system with the source system user credentials in order to complete the user mapping process. The prerequisites of this manual mapping are:
...
What level of detail in the task is required?
In order to provide sufficent sufficient detail for users to make approval decisions directly within OneList, the adapter will need to retrieve comprehansive comprehensive information for the task, such as
details of the business object associated to the task, e.g. the purchase order detail, the SharePoint list item properties;
the key and value of master data look ups;
priror prior approvals and comments from the workflow history;
documents attached to the task or the business object;
What is the selection
...
criteria for the initial load?
When integrating with an existing workflow, it is important to identify the selection criteria for the initial load to avoid outdated and invalid tasks being posted to OneList. Fields like task id, creation date and status are commonly used as the selection criteria. The adapter should efficiently perform the initial push of tasks to OneList. Consider HTTP connection and request size limits imposed on the OneList APIs, paging of data may be required to handle large volumn volume of data.
Event-based integration process
...