The activity model should be changed to reflect the new dialog aggregate version
Description
Some renames and validation changes should be performed on the dialog activity model. This includes using the model in #851 as performedBy, changing the valid types and chaning the validations
The "description" (localizationtext) property should still be available, but only allowed (and required) if type is "information". The other types should not allow for a textual override, as the type itself should provide a non-ambiguous semantic.
See #851 for performedBy model.
### Tasks
- [ ] #851
- [x] Rename fields and fix relations
- [x] Update type values
- [x] Update validations
- [x] Prepare documentation (if relevant - either update working document, or add a new file in `docs`)
- [x] Add e2e-test (if relevant)
### Threat modelling
- [x] Does this change introduce any potential security issues?
Introduction
The activity model should be changed to reflect the new dialog aggregate version
Description
Some renames and validation changes should be performed on the dialog activity model. This includes using the model in #851 as
performedBy
, changing the valid types and chaning the validationsImplementation
The model should look something like this
Valid types should be:
The "description" (localizationtext) property should still be available, but only allowed (and required) if type is "information". The other types should not allow for a textual override, as the type itself should provide a non-ambiguous semantic.
See #851 for performedBy model.
Acceptance criteria
GIVEN ... WHEN .... THEN ...
GIVEN ... WHEN .... THEN ...