Deprecated Plugins

Creating a new plugin, but calling the functions/smart services inside the plugin the same name will be considered new functions/smart services. The plugin-key is the unique identifier.
forum.appian.com/.../Appian_Plug-ins.html

Hope that is what you were asking and that helps!

I believe it should not break the code. In case, you do not find an alternative for the plugin with deprecated APIs, you can replace the deprecated APIs with the alternative APIs that Appian suggests, increment the version number in appian-plugin.xml file and deploy after removing older version plugin.

Hi, Kumara,

It all depends on what kind of plugins you are using. There are few plugins published in Appian forum might have used some Appian API stuff which can give them better way to provide solutions very easily as the Java version grows bigger few parts of Appian API's might get deprecated due to some performance issues or the other ways.

As per the Appian best practices if the plugin version get's updated it's better to reconfigure the nodes. For instance there were few plugins related to excel tools in the forum got deprecated and instead of all of them they have introduced one excel tool plugins so if the excel tools plugin version changes then it is good to change the plugin in configuration.

Coming to you question, it is better to reconfigure if the health check says that plugin is using some deprecated API's in the background and try for the new one and can go for alternatives. If the new functionality may impact your code then you can use the old plugin which is still in the local memory then you can gradually move to the new version as soon as you are updating any objects as part of new enhancement.

Thanks.