Correspondence Management DataDitionary provides a representation of the underlying data structure of a complex backend enterprise system in a simple and user-friendly manner which business users can easily understand.
In any enterprise implementation of Correspondence Management usually middle ware developers work on creation of data dictionary.
We get requests from our customers to understand the best practices for creation of DataDictionary.
The answer is try to Keep It Simple.
- Do not try to create a single Data Dictionary with tens of thousands of elements to cater to the needs of all the correspondences
- If there is a possibility to create multiple data dictionaries by logically separating the correspondences based on business units / business needs , prefer to create multiple data dictionaries.
- If a single complex data dictionary is created (even if there isn’t a real need) , there would be some trade-off in the form of performance for some operations like Publishing the datadictionary and preview of letters that use this data dictionary.
- Do not try to over complicate the data dictionary by creating too many levels down the hierachy and do not even use a DD which is completely flat.