Page Comparison

/onelistserver/api/datasync/SyncTasks

This API synchronises OneList tasks with source workflow tasks.

• The ActiveTasks array contains new or updated task detail. OneList reads this array to add or update the tasks to its task cache;

  • The supported task actions must be defined in the EnabledActions field.

    • For each action, specify the type of action in the ActionType field:

      • Action - the action is a task level action.

      • LineAction - the action is a line-level action. Actions of this type can be bound to a Section in the OneList Task Configurator.

      • ForwardTask - the action is to forward the task to a different user. OneList ensures a forwarded user is selected when executing this action.

    • For each task level action, specify the ApplyLineAction field:

      • true - apply line-level actions;

      • false - do not apply line-level actions.

  • The TaskDetail field is mandatory and it must be assigned the full detail of the task (JSON). It can contain hierarchical data structures and there is no limit to the number of levels of hierarchy. This is the source data for the OneList task engine to layout the task for presentation.

  • The meta data of the task attachments should be included in the Attachments field. The attachment files are posted to OneList separately using the /onelistserver/api/datasync/SyncAttachments API.

  • If the HasValue field is not set then OneList uses the TaskDetail field to calculate the hash.

• The DeletedTaskId array contains the id of the tasks that are completed by the source workflow. OneList removes these tasks from its task cache;

/onelistserver/api/datasync/

GetUserSync

This API returns the list

of

users that are requiring user accounts created in OneList. The adapter looks up the user profile information and calls the SyncUsers API to

update

OneList. This API returns the list of:

• Source system user name, or

• OneList user id.

/onelistserver/api/datasync/GetActiveUsers

This API returns the profile of active OneList users. It can be used to compare with source system user information to detect outdated OneList user profile.

• The UserName field is the source system user id;

• The OneListUserId field is the OneList user id;

• The other fields are the current OneList user profile information.

/onelistserver/api/datasync/SyncUsers

This API adds or updates OneList user account with the source system user information. It also creates the user mapping between the OneList user account and the source system user account.

• The UserName field is the source system user id;

• The OneListUserId field is optional, if not specified then the UserName is used as the OneList user id;

• The other fields are used to populate the OneList user profile.

/onelistserver/api/datasync/SyncAttachments

This API synchronises OneList task attachment cache with source system files.

• The Attachments array contains the current version of the files for the task;

• The DeletedAttachments array contains the source system document id that is removed from the source system document repository.

/onelistserver/api/datasync/GetActionRequests

This API returns the list of user task actions. The source system should perform the requested task action in the workflow.

• The UserId is the source system user id who performed the action in OneList;

• The Task field contains the key information of the task to be actioned;

• The TaskAction field contains the detail of the task action including user input such as approval comment;

• The LineActions array is only populated for task supporting line-level action;

• The Token field may contain the refresh token for source system to impersonate the user.

/onelistserver/api/datasync/PostTaskActionOutcome

/onelistserver/api/datasync/PostLineLevalTaskActionOutcome

Source system calls this API to notify OneList of the requested task action.

• The OneListRequestId is the identifier of the action request;

  • The Messages array is optional for posting any status or error messages to OneList.

/api/DataSync/GetDelegationRequests

This API returns the list of new or deleted delegation requested by the user. The adapter should add or remove the delegation records in the source system accordingly.

• The Operation is either New or Delete;

• The OneListRequestId is the OneList request id. It should be passed back in the PostDelegationOutcome API for OneList to update the status of the request;

• The SourceSystemRecordId is used for identifying the delegation record in the source system for deletion. This field is null when the Operation is New;

• The DelegateFromUser is the delegator’s user id in the source system;

• The DelegateToUser is the delegate’s user id in the source system;

• The WorkflowType is used for identifying the delegation subsystem or subcategory for which the request is targeting;

• The Scope is used for identifying the profile or scope for which the request is targeting;

/api/DataSync/PostDelegationOutcome

The adapter calls this API to post the outcome of each delegation request.

• The OneListRequestId is required and must be assigned with the OneList request id;

• The SourceSystemRecordId is required when the outcome is successful;

• The IsError is a boolean value indicating if the request was processed successfully or not;

• The Message is an array of string for the adapter to return success or error information to OneList;

/api/DataSync/SyncDelegations

The adapter calls this API to post the full list of current delegation records of the source system to OneList

• The SourceSystemRecordId is required and has the unique id of the source system delegation record;

• The DelegateFromUser is the delegator’s user id in the source system;

• The DelegateToUser is the delegate’s user id in the source system;

• The WorkflowType is the delegation subsystem or workflow of the delegation;

• The Scope is the profile or scenario of the delegation;

/api/DataSync/GetBusinessObjectRequests

The adapter calls this API to get the list of id of the business objects requiring the updated snapshots. The API returns the following:

• The task type;

• The id of the business object;

• The hash value;

• The last workflow task id for the business object. Adapter can use this id to identify the workflow and retrieve the workflow history.

/api/DataSync/SyncBusinessObjects

The adapter calls this API to post the snapshot of business objects. The information posted are:

• The task type;

• The id of the business object;

• The hash value;

• The title of the business object.

• The full name of the requestor.

• Whether it is the final snapshot based on the status of the business object.

• The detail field must be the same task JSON as the TaskDetail JSON for the SyncTask API.