Find everywhere a rule is used before you change it
Also listed as: Find-reference for X# rule components
What is it?
Developers can find every place a component written in X#, the Xelence rules language, is used across the solution.
Why does it matter?
Safer changes, because teams can see the impact of a change before they make it.
Start thinking about
- Is your written policy kept current enough to serve as the source for your business rules?
- Who in the business confirms that a rule matches policy before it is released?
- How would you show an auditor or appeals officer why a rule produced a particular decision?
- How do you test rule changes today, and where does your test data come from?
- Do you have an approved policy for AI-assisted development, and who owns it?
- How will you plan rule changes driven by new legislation alongside your upgrade schedule?