Validation Interfaces
If our validation algorithms are the engine of our features, Validation Interfaces are their fuel. They contain the specifications that are applied when checking a data set. They guide your data senders towards a compliant participation in your business processes. And they give you transparency about your data flows. Tailor-made validations
To give your partners a simple overview of where they need to make improvements, we display the errors directly in the source message. There they will find a representation of the structural and logical errors. The logic tests require an explanation of how the individual components are connected. With detailed descriptions of the rules and their components, you can give your partners the explanations that used to require conference calls and long emails. Experience has taught us that a Validation Interface must not overstrain the partners. Syntax checks or validation rules that do not apply to a partner will only distract him. To avoid this, you can separate a Validation Interfaces into multiple Sub-processes. Sub-processes of a Validation Interface share a common core of syntax checks and validation rules. However, each Sub-process can have its own validations that deviate from others. In this way, you can divide your Validation Interface into suitable sub-units. Your partners only have to process the checks that are really relevant to them.