As Cleo Clarify users start using using Clarify’s latest Version/Engine 2
features, there are alot of questions about how to make sure it is done
In an earlier post, we will showed a few differences of a Cleo Clarify Rulesets.
In Part 2 we will review the Business Process Script and Database Adapter we created for the inbound 940 x12 transformation. We also review the mechanics/’guts’ of the ruleset we created in Part 1 of 1st Impressions of Version/Engine 2
Business Process Script
The Business Process (below) is a version 2 (engine 2) BPS. It looks and feels like a BPS that we would normally use.
As users can see there is no reference to version 2, but if users view the Business Process, in text mode, they will see: #content/*bps 2 */
The Database Adapter, being referenced in the Business Process (above), is also version 2/engine 2.
The Guts of a Ruleset
In Part 1 of 1st Impressions of Version/Engine 2, we showed how a ruleset is made and some of the differences. One of the MAJOR differences with Version/Engine 2, is the creation of the JAVA objects.
More 1st Impressions….
In Part 1 of 1st Impressions of Version/Engine 2, we showed how a ruleset is made and some of the differences.
Part 3 will cover Clarify Auditor and the formatting of the errors.
More Info on Cleo Clarify…
For more assistance or information on Cleo Clarify 4.6 or any other related, please feel free to contact our group
By: Sean Hoppe on