If a second data destruction request is submitted for the same person, the derived variable 883668444 get changed in a way that is not expected. See example below from dev:
Step1: request DD in SMDB
Step2: sign form in PWA. Data looks like the following
If the DD form is already signed in PWA and then another data destruction request is submitted, the derived variable 883668444 should not revert from 704529432 (Requested and signed) to 111959410 (Requested but not signed). It should stay 704529432.
If a second data destruction request is submitted for the same person, the derived variable 883668444 get changed in a way that is not expected. See example below from dev:
Step1: request DD in SMDB Step2: sign form in PWA. Data looks like the following
359404406: 353358909 119449326: 2024-08-07T15:20:53.036Z 883668444: 704529432 269050420: 2024-08-07T14:59:21.030Z
Step3: re-request DD in SMDB. Data looks like the following
359404406: 353358909 119449326: 2024-08-07T15:20:53.036Z 883668444: 111959410 269050420: 2024-08-07T15:32:43.620Z
If the DD form is already signed in PWA and then another data destruction request is submitted, the derived variable 883668444 should not revert from 704529432 (Requested and signed) to 111959410 (Requested but not signed). It should stay 704529432.