<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>KB-2330 Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-2330 Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins</link><pubDate>Sun, 16 Feb 2025 23:33:42 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Maggie Deppe-Walker</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 2/16/2025 11:33:42 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;Why has Appian requested a license notice file in my plug-in?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;How do I add a license notice file to my plug-in?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;What if my plug-in does not need a notice file?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&amp;nbsp;or&lt;strong&gt; NOTICE.html&lt;/strong&gt;&amp;nbsp;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&amp;nbsp;&lt;/span&gt;&lt;span style="font-weight:400;"&gt;The name and format of the file required will vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: February 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/13</link><pubDate>Thu, 13 Feb 2025 14:31:16 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 13 posted to Appian Knowledge Base by Daniel DeVeau on 2/13/2025 2:31:16 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;Why has Appian requested a license notice file in my plug-in?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;How do I add a license notice file to my plug-in?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;What if my plug-in does not need a notice file?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&amp;nbsp;or&lt;strong&gt; NOTICE.html&lt;/strong&gt;&amp;nbsp;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&amp;nbsp;&lt;/span&gt;&lt;span style="font-weight:400;"&gt;The name and format of the file required will vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: February 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/12</link><pubDate>Thu, 13 Feb 2025 05:18:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Maggie Deppe-Walker</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 12 posted to Appian Knowledge Base by Maggie Deppe-Walker on 2/13/2025 5:18:17 AM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;Why has Appian requested a license notice file in my plug-in?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;How do I add a license notice file to my plug-in?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;What if my plug-in does not need a notice file?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&amp;nbsp;or&lt;strong&gt; NOTICE.html&lt;/strong&gt;&amp;nbsp;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&amp;nbsp;&lt;/span&gt;&lt;span style="font-weight:400;"&gt;The name and format of the file required will vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/11</link><pubDate>Mon, 27 Jan 2025 14:33:12 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 11 posted to Appian Knowledge Base by Daniel DeVeau on 1/27/2025 2:33:12 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&amp;nbsp;or&lt;strong&gt; NOTICE.html&lt;/strong&gt;&amp;nbsp;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&amp;nbsp;&lt;/span&gt;&lt;span style="font-weight:400;"&gt;The name and format of the file required will vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/10</link><pubDate>Tue, 07 Jan 2025 22:15:30 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 10 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 10:15:30 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&amp;nbsp;or&lt;strong&gt; NOTICE.html&lt;/strong&gt;&amp;nbsp;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;The name and format of the file required will vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/9</link><pubDate>Tue, 07 Jan 2025 21:39:41 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 9 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 9:39:41 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;The name and format of the file required will vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/8</link><pubDate>Tue, 07 Jan 2025 21:38:10 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 8 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 9:38:10 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;The name and format of the notice file may vary depending on the&amp;nbsp;applicable license terms.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/7</link><pubDate>Tue, 07 Jan 2025 21:36:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 7 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 9:36:43 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;The format of the file may vary depending on the terms&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/6</link><pubDate>Tue, 07 Jan 2025 21:36:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 6 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 9:36:32 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information on plug-in policies, see &lt;a title="AppMarket Submission Policies for Plug-ins" href="https://docs.appian.com/suite/help/latest/Shared_Components.html" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submission Policies for Plug-ins&lt;/a&gt; and the &lt;a title="AppMarket Submissions Agreement" href="/p/appmarket-submission-agreement" rel="noopener noreferrer" target="_blank"&gt;AppMarket Submissions Agreement&lt;/a&gt;.&lt;/p&gt;
&lt;h1 id="main_content"&gt;AppMarket Submission Policies for Plug-Ins&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example &lt;strong&gt;NOTICE.txt&lt;/strong&gt;&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;The format of the file may vary depending on the terms&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/5</link><pubDate>Tue, 07 Jan 2025 21:31:44 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 5 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 9:31:44 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example NOTICE.txt file&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: FAQ, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/4</link><pubDate>Tue, 07 Jan 2025 19:22:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 7:22:34 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example NOTICE.txt file&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: how-to, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/3</link><pubDate>Tue, 07 Jan 2025 19:21:47 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 7:21:47 PM&lt;br /&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#Policies"&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#Why"&gt;&lt;strong&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#How"&gt;&lt;strong&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="#NotNeeded"&gt;&lt;strong&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a id="Policies"&gt;&lt;/a&gt;&lt;strong&gt;&lt;/strong&gt;&lt;strong&gt;What are Appian&amp;#39;s policies for third party libraries in plug-ins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="Why"&gt;&lt;/a&gt;Why has Appian requested a license notice file in my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests &lt;strong&gt;NOTICE.txt&lt;/strong&gt; files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="How"&gt;&lt;/a&gt;How do I add a license notice file to my plug-in?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&amp;nbsp;which include an example NOTICE.txt file&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="NotNeeded"&gt;&lt;/a&gt;What if my plug-in does not need a notice file?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2 id="mcetoc_1ih13a2t50"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: how-to, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/2</link><pubDate>Tue, 07 Jan 2025 19:06:56 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 1/7/2025 7:06:56 PM&lt;br /&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;Some open source licenses explicitly require an artifact declaring the licenses in use to be included with the plug-in. Appian suggests NOTICE.txt files 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;For more information on how to build a license notice file, see &lt;/span&gt;&lt;a href="https://infra.apache.org/licensing-howto.html"&gt;&lt;span style="font-weight:400;"&gt;Apache docs&lt;/span&gt;&lt;/a&gt;&lt;span style="font-weight:400;"&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;&lt;/ul&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: January 2025&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: how-to, plugins&lt;/div&gt;
</description></item><item><title>[DRAFT SUPP-764] Third Party Licensing Requirements for Plug-ins</title><link>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins/revision/1</link><pubDate>Mon, 02 Dec 2024 22:43:05 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:54b1a7c3-2d72-4139-a57f-5a99dc6960be</guid><dc:creator>Daniel DeVeau</dc:creator><comments>https://community.appian.com/support/w/kb/3609/kb-2330-third-party-licensing-requirements-for-plug-ins#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 12/2/2024 10:43:05 PM&lt;br /&gt;
&lt;p&gt;This article serves as a template that you can copy/paste into a new article for use later on.&amp;nbsp;This template should be used to provide extra details about a certain topic. It can either be internal or external.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Table of Contents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="/solution-engineering/w/internal-knowledge-base/724/int-0003-template-faq#HowToFormat"&gt;How should the Q and A be formatted?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;&lt;a id="HowToFormat"&gt;&lt;/a&gt;How should the Q and A be formatted?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Format&amp;nbsp;each question&amp;nbsp;as shown here. The question should be&amp;nbsp;bold with the corresponding answer below.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="/solution-engineering/w/internal-knowledge-base/675/int-1402-forum-accounts-and-user-management-faq"&gt;INT-1402 Forum Accounts and user management FAQ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/support/w/kb/370/kb-1153-saml-authentication-faq"&gt;KB-1153 SAML Authentication FAQ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/support/w/kb/1087/kb-1678-engine-checkpoint-faq"&gt;KB-1678 Engine checkpoint FAQ&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: December 2024&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item></channel></rss>