How to Create Smart service plugin in appian

1. How to get smart services plugin Jar files except appian-plug-in-sdk.jar.
* The appian-plug-in-sdk.jar is the only plug-in Jar file you need for your suite APIs. 
* The Integration SDK is also available for other types of plug-ins such as Connected Systems or Interface Component plug-ins, but the appian-plug-in-sdk only requires that one JAR file. 

2. How to include Public Api with these Smart service plugin.

* Using Maven, just put the sdk Jar in the build-tools/lib/appian/17.2.0/_admin/sdk folder and list the dependency in your POM.xml file as 

      <dependency>
        <groupId>com.appiancorp</groupId>
        <artifactId>appian</artifactId>
        <version>17.2.0</version>
        <scope>system</scope> 
        <systemPath>${basedir}/build-tools/lib/appian/17.2.0/_admin/sdk/appian-plug-in-sdk.jar</systemPath>
      </dependency> 

3. please give any appian  smart service plugin example using Eclipse IDE.
*     The Execute Stored Procedure plug-in includes source code you can use as an example. 

https://community.appian.com/b/appmarket/posts/execute-stored-procedure#

Hope that helps! 

Hi Jim,

 How to connect one application with another application using UUID.

Thanks ,

Thirumurugan

Please elaborate on what you mean with "connect one application with another application using UUID".

Hi Stefan Helzle,

     I need to connect  appian application A with another appian application B using its UUID. Also I need to create customize groups and folder in application B with the help of Application A process model.

Thanks,

Thirumurugan

OK. Now we know that you want to create groups and folder. But what about "connect  appian application A with another appian application B using its UUID"? What does this mean? What is your goal?

Something to keep in mind is that, generally speaking, in Appian each application has access to any other objects in other applications according to the user rights assigned to those objects that you create. Most instances, therefore, have a library of utilities and common objects that everyone shares. That's just how objects work in Appian. However, with regard to plug-ins specifically, if other applications need to access your plug-in, they'll be able to incorporate that plug-in within their objects as often as they like while they're creating their process models and/or expression rules and interfaces (depending on what type of plug-in you create) once your plug-in is deployed into the environment. 

Something to keep in mind is that, generally speaking, in Appian each application has access to any other objects in other applications according to the user rights assigned to those objects that you create. Most instances, therefore, have a library of utilities and common objects that everyone shares. That's just how objects work in Appian. However, with regard to plug-ins specifically, if other applications need to access your plug-in, they'll be able to incorporate that plug-in within their objects as often as they like while they're creating their process models and/or expression rules and interfaces (depending on what type of plug-in you create) once your plug-in is deployed into the environment.