Content Expressions (v1.0.8) Plugin

judym598

Certified Senior Developer

over 5 years ago

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 found an updated version, Custom Content Functions [com.appiancorp.cloud.plugins. contentfunctions - 1.1.2.jar] (Last updated Feb 2 2018) at https://community.appian.com/b/appmarket/posts/custom-content-functions# Just tried to go to this link and it is no longer there. It appears as though the functions/smart services are now in the Content Tools plugin. (https://community.appian.com/b/appmarket/posts/content-tools). Was the other one removed? No longer available for use? We use the finddocumentsbyname() and findcontentbyattribute() functions in many process models. Should we update to the Content Tools plugin? How do I find ALL the places that use a deprecated function. I just did a health check in our DEV environment and this was not identified.

Discussion posts and replies are publicly visible

Top Replies

Sanchita Gupta over 5 years ago in reply to Mike Schmitt +1
Appian Employee

We removed the plug-in listing from the AppMarket because there was a reported issue with deploying it. We are working to get the issue corrected and re-listed. We will also include some clarifications…

0 paulc919 over 5 years ago

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're using that function.

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.

If you download and open the CSV, the heading Activity Class Local ID will list the namespace of the plug ins you're using. Filtering in Excel might help highlight the process model UUIDs that may need to be refactored.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 paulc919 over 5 years ago

Oh and the Content Tools plug in page (community.appian.com/.../content-tools) 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'd need to remove the old plug in before deploying the new.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 5 years ago in reply to paulc919

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'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'm surprised the Health Check didn't pick this up.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 5 years ago in reply to paulc919

This did not work - I tried searching for finddocumentsbyname() and got nothing; then tried a known function, findcontentbyattribute()), and got nothing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Joshua F
Certified Lead Developer
over 5 years ago in reply to paulc919

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 5 years ago in reply to Joshua F

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Schmitt
Certified Lead Developer
over 5 years ago in reply to judym598

I'm really curious what's going on with the Content Tools plug-in... it was supposed to be this big comprehensive future-proof replacement, and now it's completely unavailable, just days(?) later...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sanchita Gupta
Appian Employee
over 5 years ago in reply to Mike Schmitt

We removed the plug-in listing from the AppMarket because there was a reported issue with deploying it. We are working to get the issue corrected and re-listed. We will also include some clarifications on its use.

Once it is re-listed I'll post back on this thread.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Schmitt
Certified Lead Developer
over 5 years ago in reply to Sanchita Gupta

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jits over 4 years ago in reply to Sanchita Gupta

Is it back?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel