Appian reviews all component plug-ins to ensure they meet our standards and those of our customers. This page explains the review process and the steps you'll go through to get your component plug-in approved for use in applications.
Allowing developers to extend Appian by creating new components is an incredibly powerful concept that lets customers build even more powerful applications. We've put a lot of effort into creating an extensible platform, and we want to make sure our developers and our customers succeed.
We also want to make sure that Appian continues to be the fastest way to create enterprise software. That means we don't expect you to build a new component for every application. In fact, it should be the exception. By reviewing every component plug-in we want to help you make the most of your time, developing only the most valuable components that add broad capabilities to the growing Appian ecosystem.
You don't have to tell us what you plan to build, but if you do we'll let you know if it's something that might violate our review guidelines. While we can't guarantee final approval until you submit your completed plug-in, this is the best way to make sure you're on track before you start.
You can request a pre-approval from the AppMarket Submissions Site.
Once you've built and tested your component, you'll submit it for review. Use the following checklist to help the review process go as smoothly and quickly as possible:
When you're ready to submit your plug-in, use the AppMarket submission form. Make sure to provide:
If your component plug-in is approved you'll receive a copy of your plug-in signed by Appian. Your plug-in will then be able to run on any Appian instance (Cloud or on-premises).
Your plug-in will also be listed in the Appian AppMarket so that customers can download it and use it in their applications.
If your component plug-in is not approved, we'll send you a detailed report explaining why. You can use the report to update your plug-in and resubmit.
If we believe we would never approve your component because of fundamental design violations the submission will be rejected. Make sure to get your idea pre-approved to avoid this situation!
Once listed in the AppMarket, customers will be able to use your component in their applications, and you'll start hearing feedback when they do. When you decide to release a new version make sure to read our guidance on what type of version change to make. New versions will need to be built in your developer instance and submitted for review using the same process as your initial release.
We'll also be monitoring feedback on your component plug-in as it's used by customers. We may reach out to you to address any concerns, such as:
Our goal is to work with you to ensure your component is available and provides value. However, Appian reserves the right to remove your plug-in from the AppMarket at any time and for any reason.
On This Page