<?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/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/discussions/f/plug-ins/14576/content-expressions-v1-0-8-plugin</link><description>We are currently upgrading to 19.1 and ran into several process errors in our DEV environment due to the finddocumentsbyname() function that was included in the Content Expressions (v1.0.8) plugin. I searched for this plugin less than 2 weeks ago and</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/67598?ContentTypeID=1</link><pubDate>Fri, 21 Jun 2019 10:05:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:eb20880e-5ad1-48e7-aab4-e8d72f606978</guid><dc:creator>jits</dc:creator><description>&lt;p&gt;Is it back?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65516?ContentTypeID=1</link><pubDate>Fri, 29 Mar 2019 21:40:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4d96aa6f-911a-43b6-98ab-9b0f9a781f15</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65515?ContentTypeID=1</link><pubDate>Fri, 29 Mar 2019 19:59:29 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0e4cdd31-7d7c-417b-bc42-aa1d362b3d65</guid><dc:creator>Sanchita Gupta</dc:creator><description>&lt;p&gt;We removed the plug-in listing from the AppMarket because there was a reported issue with deploying it.&amp;nbsp; We are working to get the issue corrected and re-listed.&amp;nbsp; We will also include some clarifications on its use.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Once it is re-listed I&amp;#39;ll post back on this thread.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65512?ContentTypeID=1</link><pubDate>Fri, 29 Mar 2019 15:39:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b7c124ca-9f6f-4a0a-9a97-5554b7756665</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;I&amp;#39;m really curious what&amp;#39;s going on with the Content Tools plug-in... it was supposed to be this big comprehensive future-proof replacement, and now it&amp;#39;s completely unavailable, just days(?) later...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65502?ContentTypeID=1</link><pubDate>Fri, 29 Mar 2019 12:24:41 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f6236745-2386-439c-9940-edb1662cb2ee</guid><dc:creator>judym598</dc:creator><description>&lt;p&gt;It appears as if this plugin is no longer available. Based on our experience, it is not supported on 19.1 which is why we had to update process models that used the finddocumentsbyname() function. We changed these to findcontentsbyattribute() which worked. However, once we get all our environments on 19.1, we are going to remove the deprecated Content Expressions plugin and install the Content Tools plugin.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65485?ContentTypeID=1</link><pubDate>Fri, 29 Mar 2019 02:18:05 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4e2b5672-5266-44df-bde2-f36d5251f55f</guid><dc:creator>Joshua F</dc:creator><description>&lt;p&gt;I can not find this plug in, or get to the link you posted about it. Do you know if it is supported on 19.1?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65356?ContentTypeID=1</link><pubDate>Fri, 22 Mar 2019 18:44:51 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c0780c68-fae6-4708-953b-525cdab9bd4e</guid><dc:creator>judym598</dc:creator><description>This did not work - I tried searching for finddocumentsbyname() and got nothing; then tried a known function, findcontentbyattribute()), and got nothing.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65353?ContentTypeID=1</link><pubDate>Fri, 22 Mar 2019 17:19:08 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:67bffb18-dce4-45a7-8e37-7fa1919f08c9</guid><dc:creator>judym598</dc:creator><description>I should be able to use the findcontentbyattribute() function to locate a document vs the finddocumentsbyname(), right? It appears to still exist in 19.1 but that may be because it exists in the Content Tools plugin. We are not in a position to deploy the updated plugin, Content Tools until we finish our upgrade to 19.1. I&amp;#39;m hoping I can figure out how to use the findcontentbyattribute() function to temporarily resolve this issue...then work on deploying the Content Tools plugin.  I will definitely use the select expression option to search for the function(s) I need to update. I&amp;#39;m surprised the Health Check didn&amp;#39;t pick this up.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65350?ContentTypeID=1</link><pubDate>Fri, 22 Mar 2019 16:49:21 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7618a8e0-0796-453f-a36f-da9ea3448a76</guid><dc:creator>paulc919</dc:creator><description>Oh and the Content Tools plug in page (&lt;a href="https://community.appian.com/b/appmarket/posts/content-tools)"&gt;community.appian.com/.../content-tools)&lt;/a&gt; has been updated ( I think ) to state : NOTE: This Plug-in replaces the Content Details by UUID and Custom Content Functions Plug-ins. - which usually means you&amp;#39;d need to remove the old plug in before deploying the new.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Content Expressions (v1.0.8) Plugin</title><link>https://community.appian.com/thread/65349?ContentTypeID=1</link><pubDate>Fri, 22 Mar 2019 16:45:58 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:44c4c048-ddba-44ae-a4ea-4aeeae57cea0</guid><dc:creator>paulc919</dc:creator><description>Hi Judy - you can use the Designer search feature - select expression and then search all objects for the two functions you want to find (one at a time obviously) - it should bring back a match to highlight where you&amp;#39;re using that function. &lt;br /&gt;
&lt;br /&gt;
If there are smart services you want to find then its a bit more convoluted as there is a HC file on the root directory of the System Logs - hc-process-nodes.csv. &lt;br /&gt;
&lt;br /&gt;
If you download and open the CSV, the heading Activity Class Local ID will list the namespace of the plug ins you&amp;#39;re using. Filtering in Excel might help highlight the process model UUIDs that may need to be refactored.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>