All of the sudden a client appears be getting this error when trying to start processes. "The Process Model cannot be started. There is no published version". This happened in a test environment. upon inspection of the process model it seems like the PM was missing the latest versions as if someone came in and deleted them and now there were only a few old unpublished versions. A quick solution was to save and published the PMs in the dev environment and deploying them again. However, I don't know what might have caused this problem?
Has anyone run into this problem and found the cause for it?
Some pointers would be helpful to ensure that this doesn't happen again. Is there a log registry I can look that would information about this issue?
Discussion posts and replies are publicly visible
Hello Jose,
There are some ways you can get into that situation. As you mentioned maybe someone can go and delete the last version which was published. Maybe the last use who published it left the company? Here are multiple ways to prevent this to happen.
1) if it is dev , well that is normal and the rule should be to publish again in case we ever need to remove a version
2) let’s say it is in test or prod environment, here the situation is completely different and you can be more strict on who makes changes here. For example don’t make everybody
sys admin, setup your application security properly and make everybody read only access.
3) when deploying in an environment like test or prod make sure you make the deployment using a service account which can never be deactivated,
4) if possible use the automatic deployment tool or user the OOTB compare/deployment available in the last versions
Please find below some References for the automatic deployments
* deployment automation manager
*
Hope this helps
Thanks
Jose P