A Rules Test Harness has been built as part of the Rules Engine solution. This was initially built for Basis Technologies internal use to help our Development and QA team test the Rules Engine, however it is also an extremely useful mechanism for our customers to validate how a particular transport will behave within the ActiveControl workflow as a result of their Rules Engine configuration, or indeed to troubleshoot any unexpected behaviour resulting from their Rules Engine setup.
The Rules Harness is accessed via program /BTI/TE_RURE_TEST_HARNESS in the Domain Controller.
Figure: The Rules Harness
|Data Entry|| Single Entry : Should be used when you want to evaluate a specific transport against a Rule.
Mass Entry : Should be used if you want to evaluate a spreadsheet list of transports against a Rule
Used Stored Data : This can be used if you want to analyse a historical Validation run
|Transport||The Transport against which you want to validate against a Rule|
|Target||The target against which you want to validate a Rule|
|Location||The location of the target defined above, against which you want to validate a Rule|
|Step ID||The Rule against which you want to validate a Transport|
|File Path (location||Used in conjunction with the ‘Mass Entry’ mode. Please refer to this FAQ for instructions on how to use this data entry mode.|
|Run IDs||Used in conjunction with the ‘Use Stored Data’ mode. This mode is primarily for Basis Technologies internal usage.|
|Run Version||Used in conjunction with the ‘Use Stored Data’ mode. This mode is primarily for Basis Technologies internal usage.|
Thanks for your feedback.
Post your comment on this topic.