The OSP provides a consolidated view of the AAI APIs used with also the ability to create workflows that can call other AAI APIs and execute the defined business rules. The UI provides a way how to define the business process (workflow) which executes these calls.

Each defined process in the OSP yields an API definition for the instantiation of the process. This definition is visible within the Developers → API Test section in the OSP. E.g.

The workflow is intended to be defined in the OSP by the Risk officers and then only instantiated by the consuming teams (such as Onboarding).

That being said, it’s expected that the consumer teams of OSP will only receive an API which the teams will call, without having much information about the business logic executed within the workflow. It is expected that the defined workflow will either synchronously finish with a result, or it will be provided with a callback endpoint which it should call once the results are ready.

Accesses

Environment

URL

Username

Password

Note

Dev

https://oop-id.advai.net/

Demo-tenant11@advancegroup.com

Demo-tenant11

Not to be used - Running in Indonesian region

Dev

https://oop-id.advai.net/

SAFI-test2@advancegroup.com

a1234567

Running in Philippines region

Stage

https://oop-id.advai.net/

SAFI-test1@advancegroup.com

a1234567

Running in Philippines region

Docs

Document

Date

File

OSP Workflow API

OSP CaseDetail API

OSP CaseDetailCallBack API

OSP Private API

Logging & Caching Integration Guide_v1.1

OSP SaFi integration guide

Comment from AAI Nan Gao 高楠 (Gary) :

We will include the reference ID as a workflow input parameter and return it back to you in both the API response and logging events. You can use that to pass on your customer ID so you can join the responses back"

Integration

OSP Workflow API integration

https://safibank.atlassian.net/wiki/spaces/ITArch/pages/138150063/OSP+Customer+Deduplication+Setup

OSP Onboarding Decision Tree

Known issues

found:

fixed

documentation and implementation differ: https://github.com/Onestop-advanceAI/APIRepostiroy/blob/master/open_apis/workflow_query_result.md

  • inconsistency in API: GET parameter:

    • Request → Parameters: transId Transaction Id returned when you submit a task.

    • curl --location --request GET 'https://api.advai.net/intl/openapi/journey/v1/query?transactionId=19d1fa4666fad51b'

found:

documentation and implementation differ: https://github.com/Onestop-advanceAI/APIRepostiroy/blob/master/open_apis/workflow_event_callback.md

  • WORKFLOW_EVENT

    • documentation: status Enum: Optional values: APPROVE, REJECT, REVIEW or null.

    • implementation: we received PENDING instead of REVIEW, ERROR instead of null