Recilient saves for dataValues

[danielskovli]

Description

As a service owner, after I configure dataFields, I need total confidence in the existence of dataValues for all submitted instances. This information is vital for the processing of instance data at my organisation.

Additional Information

Through a reported issue, we have discovered that in certain (unlikely) scenarios dataValues may not be properly saved on the instance object.

On Slack we have briefly discussed the possibility of forcing a dataValues write before allowing the process state to change in the process/next handler.

Tasks

No response

Acceptance Criterias

• If configured to used dataValues, it is impossible for an instance to be submitted without the values having been saved properly