Hi Team,
We need to restrict the automation to move jobs that are in inactive status.
EG, the below deactivated job was pulled from correct 0360 status back to 0300 when the job e-form was required to be amended retrospectively. This seems to only happen where the user has the relative permissions to override the workflow. There should be a lock on this as a job that is inactive should not be allowed to move status – same as adding an SOR etc where this cannot be done to a job that is inactive. We’ve now had this happen quite a few times so would appreciate it if we can get this corrected as it causes unnecessary time within the business trying to work out why jobs have moved when they shouldn’t be. Note; the attached file shows examples of another 14 jobs where the same movement has applied.