Workflows; An invalid allocated User prevents saving, even if the User has not changed

Where a Workflow Type previously allowed a User to be assigned to Workflows of that type, but no longer do, any attempts to edit a Workflow with a now invalid User assigned would fail, even if it wasn't the User being updated.

For example, If a Workflow Type allowed User A, B and C to be assigned to a Workflow, and a resulting Workflow assigned User A to it. After this, User A is removed as an allowed User on the Workflow Type. If the Workflow is subsequently edited, it can never be saved until the allocated User is changed, which may not be desirable.

Now, if an existing User is already assigned to a Workflow when they are no longer allowed Workflows of that type, the Workflow can still be edited without error.

Note: As before, finPOWER Connect will prevent the now-disallowed User being assigned to any new Workflows, or any existing Workflow not currently assigned to them. It is only changing the behaviour for Workflows where the User was previously allocated to the Workflow.