Can we create a plug-in and use it for our own Appian instance only?

Hi Sudipta Biswas if you are planning to write a plugin to deploy into your own Appian Cloud Instance, then you need to consider the following factors:

1. When you are creating a plugin, then it's your's or your client/organization decision whether they want to make this plugin available to all(public) or only for their organization (private).

2. Make sure that there shouldn't be any existing way to achieve your requirement in Appian, and if it's already available then you must have a valid reason why you want to write a custom plugin. This is because, you will be asked by the Appian team when you raise the request for the plugin deployment.

3. Make sure to include the various internalization files (.properties) because if that doesn't exist, your plugin wont be approved for the deployment by the Appian Team.

4. Your code should meet the java standards including exception handling and you must enclose the source code while sending it to Appian support, and if your code qualifies the code quality check then only your plugin will be deployed into the environment.

5. You should mostly use open source API's and if there are some features which is already exist in Appian jars then you should avoid adding the jar for those, explicitly. e.g. For Servlet API, JSON manipulation etc..

Hope this will help.

Hi Sudipta Biswas if you are planning to write a plugin to deploy into your own Appian Cloud Instance, then you need to consider the following factors:

1. When you are creating a plugin, then it's your's or your client/organization decision whether they want to make this plugin available to all(public) or only for their organization (private).

2. Make sure that there shouldn't be any existing way to achieve your requirement in Appian, and if it's already available then you must have a valid reason why you want to write a custom plugin. This is because, you will be asked by the Appian team when you raise the request for the plugin deployment.

3. Make sure to include the various internalization files (.properties) because if that doesn't exist, your plugin wont be approved for the deployment by the Appian Team.

4. Your code should meet the java standards including exception handling and you must enclose the source code while sending it to Appian support, and if your code qualifies the code quality check then only your plugin will be deployed into the environment.

5. You should mostly use open source API's and if there are some features which is already exist in Appian jars then you should avoid adding the jar for those, explicitly. e.g. For Servlet API, JSON manipulation etc..

Hope this will help.