Several enhancements have been made to the Rule Manager for Release 3.0a.
1. The diagnosis fuction is easier to activate.
2. Substitution exits for individual fields are available.
3. A report is available to check the syntax of all the conditions used in validations, substitutions and rules.
In addition, an example of a CO validation and substitution is delivered with the system. The example validation and substitution have the same names ('0_CO_1').
The trace function allows you to check validations, substitutions and rules in the transaction that calls the routine. You can use this function when the rule does not behave as expected. The trace function displays the values of the fields and the results of the different parts of the rule.
In contrast to Release 2.2, you do not need to change the rule in order to perform the trace.
To activate the trace function:
> Display the rule that you want to check in the Rule Manager.
> Menu 'Details' -> 'Switch on trace'. (If 'Switch off trace' is active, the trace has already been activated.)
You can activate and deactivate the trace in an alternative session.
The trace function will only be activated for yourself; other users are not affected. You cannot activate the trace function for more than one substitution at the same time, but you can activate the trace function for a substitution and a validation simultaneously. The same applies to validations and rules.
Note
: You cannot use the trace function in matrix validations and substitutions. ( validations)
You can create user exits which accept a field as one parameter and return the changed value in this parameter. This allows you to create a user exit which can be used independently of the field and table name. These user exits are contained in the same form pool as the other substitution exits, but a catalog entry must be created in the form routine 'get_exit_titles' at the beginning of the form pool.
This type of user exit cannot be used in the 'Exit only' entry in the list of values to be substituted; it can only be used in conjunction with a field name.
An example of this type of user exit is contained in form pool RGGBS000.
The report RGUGBR19 checks the syntax in all validations, substitutions and rules.
Check syntax of all rules