Skip to main content
July 17, 2024
Solved

Replacement for Republish Model as Different User

  • July 17, 2024
  • 7 replies
  • 0 views

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

Best answer by mikes0011

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.

7 replies

mikes0011
mikes0011Answer
Brainy
July 17, 2024

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.

July 17, 2024

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

mikes0011
Brainy
July 17, 2024

Nice, thanks for confirming!