I'm in the process of adding a holding step at the very end of one of our processes used for reporting separations of employment. The holding step will allow the submitter to submit the form, but instead of it going straight to the repository, it will instead enter this holding step, allowing for them to potentially change the employee's last day without having to redo the entire form.
The holding step involves a user task, allowing for potential edits to the employee's last day to be made, until one day after the employee's last day, at which point I have set up a Timer Catch Event to bypass that step and save it to the repository.
If an edit is made, however, it sends an email and then loops back to the same user task, allowing for yet another date change to be made, if necessary.
What I'm looking to capture on the form itself is the effective date of the employee's separation as it originally was, as well as what it was changed to. If the form gets corrected a second time, however, I'd like the "original date" field to be updated to the first changed date, and the new date to also now be displayed. Not that this happens often, but I'd like to ability to repeat this process indefinitely. Ex:
First Correction
Original Date: 06/15/2022
New Date: 06/18/2022
Second Correction
Original Date: 06/18/2022
New Date: 06/25/2022
Third Correction
Original Date: 06/25/2022
New Date: 07/01/2022
Below is the relevant portion of the process diagram - hopefully this will help to better explain what I'm trying to do:
I thought setting a default value of "Effective Date" for the "New Date" field would always pull in the current value of the effective date upon loading the form, but it seems to always pull the first date ever entered into that field, never any subsequent updates to it.
Any help would be greatly appreciated! Sorry this got confusing quick :D