Oracle Policy Automation and Siebel Innovation Pack 16 #4
Welcome back to part four of our ongoing series about Oracle Policy Automation and Siebel Innovation Pack 16 . This post continues with the setup and testing that began three posts ago. For reference here are the links to the previous parts of the series:
- Oracle Policy Automation and Siebel Innovation Pack 16 #1
- Oracle Policy Automation and Siebel Innovation Pack 16 #2
- Oracle Policy Automation and Siebel Innovation Pack 16 #3
This particular article continues working on the core data transfer operations, namely Load and Save. I also have a tendency to call the Save operation Submit, because it reminds me that not only must the request be submitted to Siebel to save any mapped out data, but a response needs to be sent back from Siebel to Oracle Policy Automation to, for example, display a message in Oracle Policy Automation confirming that the save was a success (or whatever).
This need for a two step approach (Save in Siebel and Respond to Oracle Policy Automation) means your Workflow Process is likely to have both typical Siebel Operations to update the database but also typical transformation and response creation like the previous operations.
The example Workflow Process for Save will require, therefore, quite a bit of work before it is fully functional. In the video I try to highlight this, but it is worthwhile mentioning the key issues again here:
- You will need to extract any data from the hierarchy sent to your by Oracle Policy Automation
- You might well need to use scripting if the hierarchy you receive has multiple entity instances (for example, the Oracle Policy Automation Project infers multiple vehicles and you want to save each of them in Siebel).
- You will need to make sure that you create a Response that updates one of the input mapped, load after submit attributes to show it in the Interview.
In this video which follows on from the previous set of SOAP UI tests, build and troubleshoot your Save operation with Siebel CRM to check for errors. There are lots of places where you will need to put in a bit of work on the example Workflow Processes (since they do not actually save much at all) and more complex (and therefore more interesting) business requirements may require a Business Service approach, namely to iterate through multiple instances of data returned to Siebel.
Whilst the videos cannot give you all the details, they definitely will put you in the right direction!
Oracle Policy Automation and Siebel Innovation Pack 16 Load and Save Testing in Siebel
Remember you can find the White Paper and associated files (at time of writing) at this Oracle Website location.
In the next part of this series, we look at two supplementary operations, GetCheckpoint and SetCheckpoint : whilst a Connection does not have to support these operations, if you plan on allowing users to stop and resume their interview before it is finished then you definitely need these operations. See you next time!