How to identify process models which has depreciated plug-ins in use

RE: How to identify process models which has depreciated plug-ins in use

Gerry McGreevy — Thu, 24 Oct 2024 19:14:31 GMT

All this link does is point back to this thread. There is no other discussion visible.

RE: How to identify process models which has depreciated plug-ins in use

Robert Shankin — Thu, 10 Jan 2019 14:41:32 GMT

mayurm168
ref: community.appian.com/.../find-all-process-model-uuid-of-an-application-by-plugin

RE: How to identify process models which has depreciated plug-ins in use

Srinivasa Kommanaboyina — Tue, 21 Aug 2018 16:41:46 GMT

Thanks Robert.

RE: How to identify process models which has depreciated plug-ins in use

aloks0189 — Mon, 20 Aug 2018 22:57:58 GMT

Agreed to @Robert statement, there no such direct/automated way to search/find for a plugin used inside the process model.

As of now, the best option is to, search for the plugin name using Notepad++ or any other text editor inside list of exported XML files of your process models.

Currently we can only search for the expressions used within the objects but not the plugins.

Hence you need to put some manual efforts to achieve this.

RE: How to identify process models which has depreciated plug-ins in use

Robert Shankin — Mon, 20 Aug 2018 21:31:10 GMT

The way I've always done this is by creating an application or a patch containing all the processes I wish to inspect.

The export zip contains a folder called "processModel"

If you know one model that contains the deprecated smart service, you can export the model on its own to find the plugin's signature in the XML file that represents that process.
For example :

That indicates that the send file over SFTP smart service (NOT ACTUALLY DEPRECATED, just an example) is in this process model.

Once you know what you are looking for, you can export several process models and use your favorite text editor to perform "find in files" search. You should then be able to quickly find all the processes.

The friendly name of the process can be found in the "process-name" tag as shown here:

This process has the (lazy) name "process with a plugin node"

This is not terribly elegant, I know. But, it gets the job done.