In EXTOL EBI 2.6, users can debug ruleset errors via the validation icon. The type reportable errors are limited to the type mismatches, missing values, and etc.

With Clarify, users will be presented with these types of exceptions plus more. Utilizing EXTOL/Eclipse's Ruleset Text-based Editor, Clarify users are transformed into power users.
The Ruleset Text-based Editor users can identify changes outside the ruleset that would cause exceptions in the ruleset. Furthermore the Text-based Editor allows users to make changes to the ruleset 'behind-the-scenes' without corrupting the structure/codebase of the ruleset. Unrecoverable errors that occured in EBI 2.6 are now a thing of the past.

Below are examples of errors we can identfy/modify with the Ruleset Text-based Editor :

• Name changes in dependant objects, ie SQL Actions, Code tables.
• Schema mismatches

Identifying Errors Ruleset Editor

There are two types of notifications in the Ruleset Editor. YELLOW and RED annotations. YELLOW annotations are warnings and RED annotations are errors.

Click on in the sidebar of the schema or rules pane to indicate location of the error. Clicking on this annotation will take you directly to the rule which also has an error icon displayed

Identifying Errors Ruleset Editor Example

In the example below we clicked on the EYE GLASS ICON, and we see there is an error with rule #6. This warning causes the parent rules #3 and #4 to also turn into warnings too.

In the lower Properties Panel we see that the 'From' Property is null. This is the root problem.

Identifying Errors Ruleset Text-based Editor

Another way to review errors is by RIGHT-CLICKING on the ruleset and choosing "Ruleset Text-based Editor".

Identifying Errors Ruleset Editor Example

In the error below, we see there is an issue with the formula (action): com.shg.Inbound850FlatFileActions.NormalizedInputNENormalizedValueFOR


When we mouse over the RED 'X', we see the following: