Is it possible to set a user or group by default for a process model? Not who starts the process!
I´ve seen that it´s possible select "Run as the person who designed this process model", but I don´t know if this solve the problem.. (I want to use the creator of process, but im not sure the designer is the same person)
In other way, this is a sub-process model box. How can I do it with the father (not sub-process)?
Thanks for your time! Best regards!
Discussion posts and replies are publicly visible
you can define security in horizontal or vertical lanes in process model for achieving your requirement
For an Action or Related Action, the initiator is always the person who starts the process. As far as I know there's no way to override this.
The person who designed is the person who last published it. But not not use this if you don’t need to check initiation privileges of users executing the model.
If you have an input task, it should be possible to assign that to a specific user, and afterward you can use activity chaining with "Override Node Assignment" selected to maintain assignment across all nodes that follow for that process. That should also make the person you chose the initiator of any subprocesses.
If this is fully automated from start to finish, I don't know how you would go about solving this. The other problem is that if you make it a person, it would have to be configured such that this one person alone in all the organization would be able to start this process. That would leave a single point of failure which is quite a bad thing to have.
Can you elaborate further on the use case and why it is so important that the particular person / group you have chosen be the assignee?
What are you trying to achieve? What do you mean by "user or group by default for a process model"?
You also want to be careful about this, because if the person publishes under their own account, then they change jobs or retire, you deactivate them and now no one in the organization can run the process model.
You always want to make sure you upload things to your Prod environment using a standard non-user admin account that will never get deactivated, such as a Model Publisher account.
davidl280 said:because if the person publishes under their own account, then they change jobs or retire, you deactivate them and now no one in the organization can run the process model.
To tack onto this, if there will be any longer-running processes in any particular system, then processes started under a user account that's deactivated later will severely malfunction if they still have processing to do at that point.
One project i've been involved with has had basically nothing *but* super long-lived processes, and we found it necessary to have everything but the top-level actions "run as designer" (and then make sure everything was imported by a non-user system account).
I know this might not be very common with well-designed projects nowadays which hopefully use shorter-lived processes, but it should be a design consideration at least.
© 2020 Appian. All rights reserved.