Best Practice for Deploying Patches

Indeed, that's exactly what I want to achieve. In the beginning I was just little bit confused because in our case the getProcessModelDetailsByUUID function didn't return "Last Published By" but of course I found out we had an old version of the plugin deployed :)
So now I have no other blocking issue ahead of me, so there will be no problem to complete this functionality.

Thank you

If you're interested, I've created a generic export of my process model republisher app.  It requires the two plug-ins mentioned here, as well as the common Appian Common Objects rules (APN_isBlank, APN_isEmpty, APN_arrayLength, and APN_displayUser), but otherwise has no precedents.  I will attach it here so you can try it out.

1362.Process Model Republisher - 2018-11-13.zip

This also requires a .properties file - the generic value is as follows, and you would need to supply your own custom admin user username proor to import:

## Constant: PMR_ENVIRONMENT_ADMIN_USER
## Type: Text
##
## Text values will be displayed in Appian exactly as they are
## specified here. No spaces are trimmed. Values do not need to be
## encased in quotation marks.
content._a-0000dab0-812b-8000-9ba2-011c48011c48_193261.VALUE=admin.username

Perfect, thank you very much, Mike.

One last question regarding e.g. expression rules or interfaces.
We want the process models to be published by service account so the users who created/published those PMs and left the company could be deactivated, right?
I am just wondering what happen to expression rules or interfaces when the user, who created them or modified them last, is deactivated.

Thank you

As far as I know, users leaving / becoming deactivated does not affect rules / interfaces / other system objects, as long as security is properly set up by group (and not defined by individual users). The main reason I know of that we need to worry about process models is because old running instances will start breaking if their "initiated by" user is deactivated.

Thanks for confirmation, Mike.

Hi Judy,

Deployment in the prod environment should be done only by service accounts in order to avoid chaos that may be created if the user is deactivated.

You can build a utility model to republish the process models which were not deployed using the service account. While doing so please take of any scheduler processes.

The creator of the process model cannot change. As far as security is concerned, you can the setting to "who started" as opposed to who created.
If you really need the creator of the process model to change, you would have to select the process models, then SAVE AS a new process model with the required user