As a business rules consultant for Caesar group and Progress Partner, I have many clients for whom I implement Corticon solutions.
To circumvent parsing the response back into Rollbase screens, one could use Datadirect Cloud to create an EDC connection from Corticon to the Rollbase database and persist the results from the decision service. After the decision service terminates, a Rollbase screen refresh can be done to show updated/changed data. This Corticon EDC connection is slow and therefor Rollbase triggers - which enable calling Corticon - time out a lot. For an on premise Rollbase/Corticon client, it is also unacceptable that data from Rollbase must be retrieved via a Cloud connection. One would expect an on premise JDBC connection.
Clients that request a fast response between Rollbase and Corticon are therefor usually disappointed that the request and response for Rollbase to Corticon and back can easily take up to more than 15 secs (using EDC).This is of course not acceptable to clients.
When can we expect a tighter, more user friendly integration (e.g. mapping functionality between Rollbase screens and the request/response of the decision service) between the two solutions which is responsive and agile?
We are looking at tighter integration between Rollbase and Corticon.
Meanwhile I suggest you do the follwoing
Instead of using SOAP request, use REST with JSON to invoke Corticon Server (documentation.progress.com/.../index.html