...
The key information required to register a source system to OneList are:
The unique OneList API key for the source system. The OneList adapters of the source system must use this API key to interact with OneList APIs. OneList authenticates the requests by validating the API key and uses it to identify the source system and its adapters to handle the requests.
The mapping between the source system user and OneList user. The user mapping can be created automatically or manually by the user. Automatic user mapping is achieved when OneList and the source system have the same user id, or when the source system adapter can create the mapping via the OneList user sync APIs. If user mapping cannot be resolved, OneList creates the mapping using the standard OIDC and ADFS protocols to request the user id from the source system. This requires user logging on to the source system once to give consent for OneList to retrieve the user's profile information. Once the user mapping is established, the user's tasks are available on OneList.
Configure the task category
...
There are two types of adapter to be registered:
Task adapter is responsible for the task synchronization and the task layout transformation;
Delegation adapter is responsible for the synchronization of task delegation settings. Delegation adapter is optional.
Detail steps of the above configuration are in the following sections
| Child pages (Children Display) |
|---|