Rely on a cleaner, standardized correspondence engine
Also listed as: Core engine refactor to standards
What is it?
The engine that produces Xelence correspondence has been restructured to follow consistent coding standards, making it easier to read, maintain and extend.
Why does it matter?
Fewer surprises when generating correspondence and quicker delivery of future letter-related improvements.
Getting it into your solution
- Arrives automatically with the release
Start thinking about
- How many letter and notice templates do you maintain, and which could be consolidated?
- What accessibility and plain-language standards must your correspondence meet?
- How will you provide translated correspondence, and who will check the translations?
- Who must approve legal or policy wording before a template is used?
- Which records-retention rules apply to the correspondence you generate and send?
- Which existing templates would you convert or modernize first when adopting new releases?