The following smart services are provided in this plug-in.
The plug-in supports:
Hello, Mike! Thank you for your response; yes, we intend to upgrade the version. Smart Services 1.1.2 is our version.
Thanks,
Per the listing, this plugin is "archived" and not downloadable. It needs to be updated with newer libraries.
Are you looking to update (don't worry about it) or use for the first time (which self-managed SP version is it?)
Hello -
we are trying to downloads the latest version. Could you please direct us how to?
The necessary runtime dependencies are included in the project - the plugin would not run without them. They are in the meta-inf/lib folder inside the jar.
The compile time dependencies are - (these should not be included in the packaged jar):
appian-plug-in-sdk, appian-suiteapi, og4j:1.2.17, commons-codec:1.15
Hello,
Thank you For reply , From the JAR file, we got the source code. However, there are still other Jar file dependencies that are being references.
Would it be possible to share the rest of the Jar files / complete dependencies?
We are trying to make a simple change to allow a certificate to work properly from Appian cloud to internal/on premise SharePoint site
Trusted server certs apply only to OOTB functionality. https://docs.appian.com/suite/help/21.4/Appian_Administration_Console.html#trusted-server-certificates
You will need to customize the plugin for it to take in a self-signed cert as a parameter and use it when initiating the connection.
We are trying to use the plugin from appian cloud to On-prem SharePoint. Certificate is there in admin console trusteed but still we are seeing below , anyone faced it ?
"PKIX path building failed: error when attempting to make a call to an external server"
Thanks
Plugins do not have access to the self signed certificates uploaded via the admin console. If you want to use a self signed cert with a plugin, you would need to update the plugin itself and take a cert as an input.
I just try this plug-in but I receive a certificate error. Certificate is well trusted in Appian. We suspect that the certiciate is read from another source (JVM?). Have you already use it with https ?