Properties

Summary

In dialogs many input validation rules are used. Some (input) validations will be defined within the domain layer and used within dialogs (interface layer), others are only defined and used within dialogs (e.g. correct birthday, telephone numbers, etc.). Validation rules defined within the domain layer will cause coupling between dialogs and business rules which will leads to many undesirable effects.

Context

Input validations and suport attributes.

• op een plek definieren zodat onderhoud eenvoudig is. Weinig werkt.
• Validatie service

Different rules exists in every layer within the clean architecture.

• (Input) validation rules; can we process this value? Is it required.
• Product rules; Are the various choices compatible?
• Underwriting rules; Is this application acceptable?
• Process rules; What is the next step? Do we need X?
• Authorization rules; Can this user (role) see/modify this? Can they overrule these warnings?

Problem

Content of a value list changes more often compared to the application which uses the value list. Seperating application behaviour from maintenance of value list content which could be depend on external resources.

Solutions

Voor de oplossing wordt rekening gehouden met de kenmerken die benoemd zijn in de tabel onder "Context".

Er zijn verschillende oplossingen mogelijk waarbij de bovenstaande kenmerken in meer- of mindere mate gerealiseerd kunnen worden. Per geval dient de best passende oplossing te worden gekozen. In de tabel hieronder worden de belangrijkste eigenschappen getoond en hoe elke oplossing daarop scoort.

characteristic

Solution 1

Solution 2

Issues and considerations

Related patterns