We've used this setting in Process Models being used as sub-processes

skumar over 11 years ago

We've used this setting in Process Models being used as sub-processes at many places.

Problem occurs when person who has designed the process models leaves the organization & we deactivate his account as it is no longer required.

In this case, we start receiving user account related errors whenever a new instance of such process model is started from his account.

The only workaround that we found so far is to keep such user accounts active to run the processes without error.

Doing this also raises our costs as we have to pay for one extra license which is not needed.

Please suggest a solution as it is causing dual problem to us.

Thanks in Advance....

Discussion posts and replies are publicly visible

0 sonias over 11 years ago

Hi,
You can have a System Account (which is not tied to any user) in Production and use that user account for importing Application packages to Production. This user should never be deactivated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 skumar over 11 years ago

Thanks for the suggestion to work with a single System Account for importing Application packages to Production.

But I wonder how this will prevent throwing errors in process instance that was started & still running by the user account which is no longer required and has been deactivated by us.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sonias over 11 years ago

There probably isn't a direct/simple approach to get all running instances to run under a different user's context. What has been suggested for similar situation is to keep the user active in the sytem until all old instances are completed (that said, publishing under a system account does help with new instances atleast running as admin account). Here is a link to a thread on the same topic where Annelise and others have also provided very good explanation - forum.appian.com/.../b-14987
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 helmuta over 11 years ago

The way we solved this problem is that we created a generic account that we use to do all of our application deployments beyond development. That way the processes are owned by that generic user.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 skumar over 11 years ago

Thanks #sonias and #helmuta

It seems to be a good solution to keep that account active until all running instances complete.

Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel