Table of Contents:
What are Appian's policies for third party libraries in plug-ins?
Plug-ins are permitted to use open source third party libraries as part of the plug-in, provided that they have full rights to use and distribute all code or libraries contained or used by the plug-in. Plug-ins must have the right to copy, distribute, and deploy all source code contained in the plug-in, and must comply with the terms of any open source libraries used or incorporated into the plug-in.
For more information on plug-in policies, see AppMarket Submission Policies for Plug-ins and the AppMarket Submissions Agreement.
Why has Appian requested a license notice file in my plug-in?
Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests NOTICE.txt or NOTICE.html as the standard to achieve consistency among plug-in submissions. Appian informs plug-in submitters when additional work may be required to maintain compliance with applicable license terms, in order to allow submitters to reconfirm their license obligations.
How do I add a license notice file to my plug-in?
For more information on how to build a license notice file, see Apache docs which include an example NOTICE.txt. The name and format of the file required will vary depending on the applicable license terms.
What if my plug-in does not need a notice file?
If a notice file is not required by any licenses in use by your plugin, return the plugin submission to Appian with confirmation of this to proceed through the review process.
This article applies to all versions of Appian.
Last Reviewed: February 2025