Documentation

When you validate data against a domain, the API first checks if the exact member already exists. If this member is found, it is returned as a valid value. If the member is a synonym and thus assigned to a ...
Read More

Our primary focus with the HEDDA.IO WEB API is to provide a full validation API. With this API you have the possibility to integrate the validation of your data, whether single Domain or Composite Domain, into your applications and have ...
Read More

With the HEDDA.IO staging process, your knowledge base will learn and develop itself further, by simply being used.When validating your data, if you specify a type of “Run” within the SSIS Component, then all the data that is not recognized ...
Read More

With Business Rules you have the option of checking data in addition to fixed values. If, for example, you want to save article numbers from an old system together with article numbers from your current system in a domain and convert ...
Read More

A Composite Domain is a logical grouping of individual Domains. Often single Domains cannot be validated alone or need additional context for an exact validation. If, for example, you want to validate a postal code for Germany, you can work with different rules such as ...
Read More

A domain contains all values that are relevant to it. First and foremost, of course, these are the values defined correctly for this domain and within the company.In a domain, however, you can also define values that are considered synonyms ...
Read More

The Knowledge Base is the central starting point if you want to start quality assurance within your data. The various functions of HEDDA.IO are logically grouped or thematically combined in the Knowledge Base.A Knowledge Base can consist of any number of Domains as well ...
Read More