Is there a way to get the process model ID from its UUID?...

Hi Jason Ruvinsky . I have to implement the same. can you let me know what approach have you choose?

Mike Schmitt said:

Any reason you don't create constants of type "Process Model", which are fine being exported/imported to different environments and can be used directly in the smart service?

I think this is still a valid question.

Our use case is special because we have one shared development environment, but two separate production environments that house different applications. The constant was part of a common object (LDAP Sync post sync processes) that goes to both environments, but needed to call different processes depending on which production environment it lived on. I had to create multiple versions of this application, with the settings for each target environment. I renamed the app for each with the environment name in it, so it is easy to tell them apart. When making changes, I need to import into dev each, make the changes to the process model constants (and other changes that have dependencies on different apps), and then export again / re-import the dev version. This is all very closely tied to our setup and use case, however, and may not apply to you.

Our use case is special because we have one shared development environment, but two separate production environments that house different applications. The constant was part of a common object (LDAP Sync post sync processes) that goes to both environments, but needed to call different processes depending on which production environment it lived on. I had to create multiple versions of this application, with the settings for each target environment. I renamed the app for each with the environment name in it, so it is easy to tell them apart. When making changes, I need to import into dev each, make the changes to the process model constants (and other changes that have dependencies on different apps), and then export again / re-import the dev version. This is all very closely tied to our setup and use case, however, and may not apply to you.