Decouple Events from Users
If User X creates an event on a job and then User X has their account disabled or removed in OpCon, that internal event will no longer work correctly, but it fails silently (the job won't fail and raise a notification). It would be great if events weren't dependent on the status of the users who created them. Meaning, even if a user's account was removed, their events wouldn't need to be modified and they would still run correctly.
Collecting community feedback OpCon Security Suggested by: Hidden identity • Upvoted: 10 Feb • Comments: 1
If a user account is removed then the events user account default to "ocadm". I'm not sure about an account becoming disabled. The reason its coupled is to ensure the user performing the action has permissions to do so (think Self Service buttons/events) and so that a user cannot bypass normal security assignments.
I think what would be more prudent would be an Events Manager, so that these could be updated in mass if needed.