Wednesday, August 17, 2022

#925 - OCI Process Automation - Dynamic Processes

As in real life, many of your business processes won't follow a structured or sequential path. They might have many possible activities that experts could act on as needed, given the situation. Think of an insurance claims case, where experts could be brought in as necessary to examine documents, pictures of damaged vehicles etc. Based on their findings, we could find ourselves dealing with a case of possible fraud etc. OPA allows us to create such processes, so let's away!



Activities: the actions taken within the process, e.g. review claim, ask for fraud check etc.

Stages: Your dynamic process can be divided into stages. Think of a stage as a bucket for related activities, activites that must be completed inorder to achieve a Milestone e.g. 

Stage 1 - Initial Investigation includes tasks such as validate claim report, review pictures of damaged vehicle. Our milestone, the outcome of this stage, we could call "Initial Investigation Completed". Depending on the outcome, this could result in Stage 2 - Fraud Investigation - being triggered.

You get the idea!

Here is my simple dynamic process - the prep work included defining a Claim Business Type - 


A Form with 3 presentation types - for claim entry, initial investigation and fraud checking.



Two structured processes - 


RequestDocsProcess simply emails the claimant requesting more documentation related to the accident etc.

SettleClaimProcess emails the repair shop to confirm they can start repairing the vehicle.

I also added the following roles - 


Let's now orchestrate the dynamic process, now that we have all of the pieces -



 

Note, each stage can have it's own set of activities. Also note the Activities section below the Stages. Here one can define common activities, invokable  at every stage. An example could be activity to ask for more documentation from a claimant. 

Before we get into the different activities one can have in stages, let's look at how we can kick off this claims case - 























As you can see, the case can be initiated via a form or the arrival of a message. I choose the form option. 


Here are the different types of activities available - 



The Initial Investigation Stage includes 1 Human Task Activity. Let's look at its configuration - 



























As you can see, the properties allow for great flexibility. The Initial Investigation stage, in our use case, is mandatory and can only happen once. The task is assigned to the Claims role.

Further properties include -






















Note the Task Outcome - I needed to create this variable - very easy to do - 

















I created an outcome variable for the fraud check as well as one for the claim object itself. More about them later.

Now to the Fraud Check Stage - I only want this triggered when the initial investigation rejects the claim.


 










I can specify this through an activation rule - 




The Fraud Check human task is configured analogue to the InitialInvestigation human task, so I will not go into the details here.

Now to the common activity - 











Only structured processes with a None start event can be included here. So the next question is - how to I pass parameters to this process?

Simple - You define these within the process. 

Here is the process - 


 
























Now to the Data Mapping - 



The same procedure is used for the Settle Claim Stage activity, so I will not go into detail about it here.

Now we are ready to process a claim - 





Here I see the different stages and their individual status. I see 2 activities available - InitialInvestigation and RequestDocs(the repeatable common task). Let's activate the latter - 













The Claimant receives the email - 












In the meantime, let's do the initial investigation - 


What does the case status look like now?


The Fraud Checker takes over - 


No fraud here, so let's settle the claim and inform the repair shop - 





Summary

Granted, a simple example - but the goal was to show you the mechanics of implementing such in OCI Process Automation. I hope you can extrapolate and see the business value add Dynamic Processes offer you and your customers. By the way, the vehicle registration plate details I used - HMI 819 - were from a Renault 8 my parents bought in the late 1960s - they don't make care like that anymore - 


  

Sunday, August 14, 2022

#924 Oracle Integration 3 - More than simply a New look and Feel

 There are a host of compelling new UI features in this release which OIC developers will love - 

Redwood Look and Feel

Yes, a new award winning look and feel, more functionality and salient information at hand, compelling presentation and less clicking to navigate. 



 Note, this initial release of Oracle Integration 3 includes Integration and Insight. Process, Visual Builder and B2B will be included in a future release.

Check out the new menu structure, Monitoring is now Observability.

The About box shows the version nr - the format is YY.MM.



Kicking the Tyres

I will begin a simple integration - as you can see, we have converged on the following 2 styles- 


 









So let's get going - 








Here I define a REST trigger, as you can see, we have a new UI for this task -



 







I am essentially entering the same data, just in a more ergonomic way.

The result -














Let's check out the 4 icons top right -










I - Identifier - click here to specify your tracking field(s) 















The first icon is for Keyboard shortcuts - 






The cog icon is for Primary Info -














The final icon, the warning triangle, is for accessing the Global Fault Handler - 











The Actions remain the same - 






Using the Mapper

Again, the same modus operandi as in OIC gen2, however, there are some cosmetic changes - 
















The 3 icons above -
Design, Code and Test.
In OIC gen2 we had - 




The icons on the right are as follows - 






The first 2 speak for themselves, the 3rd is the View option.
The 4th is the filter. So, net, net - no changes here.

Now to some key new features -

Expand and collapse Actions

e.g. SWITCH Action - 















Cut & Paste Support






















New Share Button - Export and Print

Now before we activate, note the new button - Share -


 

Export downloads the .iar file.
Print - does what it says!


Note, this is the outline view of the integration.

New Search Functionality

Extremely useful, especially when you have a large model - 


The selected action, in my case, invoke OrderApproval - is then highlighted in the canvas -























Now to deployment - here the icon has changed slightly -



















Note the options available above - 

Production - Shows all activities bar LOG and Loop activities - data retained for 32 days
Audit - wire payloads logged and data retained for 8 days
Debug - All payloads and activities inside of loops logged - data retained for 24 hours. 


Wire payloads are the integration entry and exit payloads 

Now to testing the integration - note, there is no run icon, one selects Run from the menu -





















Note, the Instance Id is now alphanumeric - 
















This may be of interest to any developers who use this id for other purposes, e.g. store it in a DB table in a column of type NUMBER. 

Let's check out the Monitoring -







Clicking on a section in the activity stream results in the highlighting of the relevant flow action - 


 

Click on the eye icon to see the actual payload -























The next section looks at Oracle integration 3 monitoring in more detail.

Observability / Monitoring updates

From a top level menu perspective Monitoring is now Observability -









Again, check out the new look and feel - 






The Dashboard is less cluttered - salient information is available up front, with the ability to drill down, for example - from 










to







Also inline - e.g.


Nice new feature is the ability to navigate to child instances - 


















Oracle Integration 3 Documentation




Check out the What's New page to check out the new features. There is also a section on deltas vis-a-vis OIC Gen2. Please note, Oracle Integration 3 currently does not include Process, Visual Builder and B2B; however, you can expect these to be available as part of the new service very soon.

Summary

Oracle Integration 3 is our next generation enterprise iPaaS service. Expect lots of compelling new features in the coming months and years. It will be available in all Oracle data centers soon, so make sure you try it out!