In some scenarios it is a need for several people will be involved in reporting on different parts in the same form.
Example scenario.
Reportee fill out some data in the form
Auditor fill out some additional fields in the same form
One option to solve this is to make it possible to fill out the same data element over two different tasks and allow to have a different form layout for this.
This is partially supported, at least on the form layout level, but this needs to be investigated. At least the locking of dataelements is not defined.
Flow could be
Data -> Data -> Confirmation
or
Data -> Data -> Confirmation - > Sign -> End
Or any other functional flow that makes sense.
Services where this functionality is required is
KRT-1008, KRT-1009 and KRT-1010 for finanstilsynet
Screenshots
Considerations
Locking/unlocking of form when the data is gone be modified before
What when the form is sent backward in the process?
Ops requirements
Acceptance criteria
Possible to have a different design for the same data element type in two different tasks
Data created should be resued in the next step
data created and updated Task 1 should be editable in Task 2.
Should be possible to send from Task 2 to Task 1 if the flow is defined in the process.
Possible to define different authorization requirements for the two different tasks
Specification tasks
[ ] Development tasks are defined
Development tasks
Test
Definition of done
[ ] Documentation (docs.altinn.studio) is updated (if relevant)
[ ] Technical documentation
[ ] User documentation
[ ] QA
[ ] Manual test is complete (if relevant)
[ ] Automated test is implemented (if relevant)
[ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)
Description
In some scenarios it is a need for several people will be involved in reporting on different parts in the same form.
Example scenario.
One option to solve this is to make it possible to fill out the same data element over two different tasks and allow to have a different form layout for this.
This is partially supported, at least on the form layout level, but this needs to be investigated. At least the locking of dataelements is not defined.
Flow could be
Data -> Data -> Confirmation
or Data -> Data -> Confirmation - > Sign -> End
Or any other functional flow that makes sense.
Services where this functionality is required is
KRT-1008, KRT-1009 and KRT-1010 for finanstilsynet
Screenshots
Considerations
Ops requirements
Acceptance criteria
Specification tasks
Development tasks
Test
Definition of done