Wondering if this is a bug, or if this is the intended behavior?
We're on Forms 11, Update 5 (11.0.2311.50556).
Here's the scenario:
A form is submitted. The initiator then exits our organization, their account is disabled, and they are marked as "No" in the License column on the Participants tab under System Security. Then... at a later step in the process, the form is returned to "Initiator" for correction. At this point, we would expect the instance to suspend, since the account tied to "Initiator" is no longer active, but that's not happening. Instead, the task assigns to that user, despite them no longer working here. We only notice it at some point later by chance.
We reached out to our VAR for support, and it was recommended we give approvers an option to "Reject and Cancel" in addition to just rejecting, leaving it to them to know if the initiator has exited. We could do that, of course, if the system is truly working as intended.
Can anyone confirm?