Thursday, July 4, 2019

#714 OIC & Autonomous Transaction Processing CS (ATP) - A Compelling Combination

Leading on from the previous post -

We now have the ATP adapter in OIC integration, how can we leverage this from the other OIC components?

ATP as the Business DB for Process Automation

Process comes with its own Archive and Purge Functionality

You could, conceivably, use this for compliance purposes. But there are some pre-requisites/caveats -

1. You need Storage Cloud Services

2. You will need to consider the format/level of detail of what is archived.

So one should consider using an external DB for this purpose.
Benefits include -
1. Full control of what data is stored.
2. Full access to that data, in a format that you have decided upon.
3. All of the benefits of ATP - highlighted in the previous post.

So it is very easy to add a call to the integration, created in the previous post.
That integration updated an Order Approvals table in ATP.

Note the StoreCompliancyData activity above. This called the aforementioned integration.

Now to a test - I enter an order and approve it


and above you see the salient data in ATP.

ATP as the Business DB for Visual Builder Apps

Similar modus operandi here - leverage the Integration in VB CS

Here is a simple example - check out the Order Business Object I have
defined in in Visual Builder 

I have created the following simple flow -
Browse Orders - Create Orders - Approve Orders

Let's use the ATP Integration for the "Approve" functionality -
I can add a connection to the aforementioned very easily -

This I do via Visual Builder Service Connections

I select the appropriate integration -

I can easily add a service call to the following page  - via Events

So what's the value add of ATP here?

1. VB CS has its own persistence layer. Business Objects are persisted,
but can only be accessed via the Business Object REST APIs.

2. The VB CS persistence layer has a fixed size. You cannot change this.

ATP addresses both of the above.

No comments: