Hello everyone,
I have a query. in application the processes are running with someone's account it seem...what happens when her/his account is disabled? will the processes stop working in environment ?
Thanks
Discussion posts and replies are publicly visible
The process won't stop working exactly, but certain things that happen in the "initiator" context will start failing (and it can cause a weird error message). This is a core reason why I tend to design subprocess trees to initiate as "publisher", so only top-level process contexts are running as "initiator" (and even this approach is imperfect, but usually "good enough"). If there's a certain initiator who has loads of instances running in their name, then usually the best solution is to not deactivate them, but take certain other approaches when they no longer need access to their account.
Does this mean I need to change the settings of all process that they made? Like changed from running as "publisher" to "initiator"?
The safer option is for subprocesses to execute as "publisher", since when you use direct deployment, you will (hopefully) be importing the process to the target environment under the authority of a high-priveleged Service Account which will never be deactivated.
1. Okay, it means change subprocesses setting to publisher will work if we deploy from low to high environment.
2. Top-level process setting set as initiator. Right?
Will all above cases work if we deactivated the user who created a processes?
manjit.1486 said:Top-level process setting set as initiator. Right
the top-level process has no choice but to be run under the authority of "initiator", since it'll be run as whoever initiated it.
manjit.1486 said:Will all above cases work if we deactivated the user who created a processes?
If there are already-running processes launched by a user you're deactivating, and they need to continue running without error, then you should avoid deactivating them, because there's no way to change the "initiator" property of a top-level process that was launched by an individual user. In cases like this I usually don't deactivate the user, but instead, change their username to something indicating they're no longer active, then add them to the "service accounts" system group, then remove their email address. This way, the active instances can complete naturally without causing issues, and there is no way for that user to login using their account.
Thanks for the information. Mush appreciated. I will keep these instructions in mind.Thanks