Page History
Properties
Property | Description |
|---|---|
Decouple category | Front-end (4) |
Complexity | Low |
| Related patterns/solutions |
| Table of Contents | ||
|---|---|---|
|
Summary
In dialogs many input different types of 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 This article only focus on input validation (e.g. correct valid birthday, telephone numbersnumer, etc.) . Validation rules defined within the domain layer will cause coupling between dialogs and business rules which will leads to many undesirable effectswhich is only defined within the dialog. This kind of validation rules won't create coupling with the domain layer. Different solutions are possible which are discussed. Depending on the context a Blueriq validation rule or a support attribute should be used.
Context
Different kind of rules are used within an application. Business rules do have a special
- 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.
Interface layer (front-end) | Application layer | Domain layer | |
|---|---|---|---|
Input validation |
| ||
| Authorization/authenticatie rules | Can this user (role) see/modify this? Can they overrule these warnings? | ||
| Process rules |
| What is the next step? Which activity is not allowed? | |
Deducation/integrity/calculation rules e.g. Product/underwring/policy/law rulesdeclarative rules |
|
|
| Eigenschap | Omschrijving |
|---|
| Knowledge | Implicit vs explicit call | |
| Simple/Complex parameter | ||
| Truth maintenance |
| Implementation properties |
| Testability | Front-end and business rules are independently testable. |
| Maintainability | Business rules are easy to maintain. Front-end and domain logic are not intertwined. | |
| Out of the box |
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.
Pim:
Validatieregels
| Property | Support attributes | Validation service | rule | |||
|---|---|---|---|---|---|---|
| Knowledge | Implicit Implicite vs explicit explicite call | implicit | explicit | implicite | explicite | |
| Simple/Complex parameter | ||||||
| Truth maintenance |  |  | ||||
Implementationproperty | Testability | | * | |||
| Maintainability |  / |
| ||||
| Out of the box | | |
*Business rules implemented in code, not in Blueriq.
Support attributes
Validation
servicerule
Issues and considerations
Related patterns
Overview
Content Tools