Hi Appian Community!
Does anyone have good recommendations for replacements for the unsupported plug-in Republish Model as Different User?
My organization uses it in lower environments whenever an individual developer modified a process model and daily, there is a scheduled process that republishes all the modified process models as a service account to prevent issues of process models being "stuck or frozen" when a developer leaves and their account becomes inactive.
TIA
Discussion posts and replies are publicly visible
If it's merely a matter of developers leaving (and the remaining instances of running processes that were started under their account), my current trick is to rename the user account, then add it to the Service Accounts system group. This prevents the account from going stale (until you're very ready to hard-disable it), and also prevents that user from logging in manually.
Higher environments, of course, should automatically have all their objects published by the service account that handles site-to-site deployments.
Hi Mike, thanks for replying my first post and your selfless help on the forum. I also enjoyed your episode with Stefan on his podcast
Nice, thanks for confirming!
We have to republish PM in production environment ? do we have feasible solution ?
Can you re-import under the authority of a Service Account?
reimport should be considered a last resort. Before that, explore alternative ways to handle the situation without releasing the individual application deployment, It is important to maintain th integrity of the source code , especially since some applications have-not been modified in a long time
What is your use case for needing them re-published, exactly?