These functions extend Appian content and offer document/folder search, directory listing, and the ability to get/set the searchable attribute of a folder.
Functions are designed for and only work on Appian content, not the local filesystem. All search functions assume the root folder and all subfolders are searchable. Search functions will not return results contained within non-searchable objects.
Useful to identify rules/constants with large number of versions when investigating high memory usage in the Collaboration engine. See https://community.appian.com/support/w/kb/441/kb-1226-content-collaboration-engine-consumes-high-memory for more information.
All functions use the serviceContext of the user account executing the expression at runtime.
NOTE: This plug-in should NOT be used in conjunction with Custom Content Functions as they are not compatible.
If we are already using Custom Content Functions, and replace it with this plugin, will there be any impact?
Is there any way this can be enhanced to add a function that given a UUID it returns the application containers the object is part of?
If we want to deploy this plug in is the recommendation to remove the existing Content Details by UUID and Custom Content Functions Plug Ins first ? Presumably all the functions / smart services in those two plug ins have been replicated under this new Content Tools plug in ?
The function list is not accurate, the v1.0.1 of this plugins does not include getconstantsbyname but includes the function FindFoldersByName.
This plugin should not be used in conjunction with Custom Content Functions as it is a replacement for that plugin.
If you are currently using Custom Content Functions, do not also deploy this plugin.
I'm a bit confused - does this Plug In replace the existing Custom Content Functions plug in ? If it does replace / supersede then I presume it would be advisable to remove the existing Custom Content Functions plug in before deploying this new one ?
Deploying the latest version of "Custom Content Functions" plugin fixed our issue in 19.1.
Its confusing why both "Content Tools" and "Custom Content Functions" have a function with the same name getdocumentsfromfolder
If any of you already have "Custom Content Functions" plugin deployed in your environment and face an error post upgrade to 19.1, please redeploy "Custom Content Functions" plugin to fix the error. Thats from my experience
I faced an issue trying to deploy "Content Tools" plugin into our Appian cloud environment upgraded today to 19.1
I see that the function getdocumentsfromfolder was present in the Plugin "Custom Content Functions" (shown in Admin screen as Custom Expressions) and it looks like the issue we are facing (i.e getdocumentsfromfolder shown as being unavailable ) must be due to this change. I shall try upgrading the "Custom Content Functions" to latest version to see if it helps and report
We are using this plugin and the function getdocumentsfromfolder is being indicated as not available after we upgraded to 19.1 earlier today. No change in the plugin itself was made. Kindly help asap!
Luckily we only upgraded our Dev and Test and not Prod as we wanted to rule out any issues before we upgrade Prod. But we need this addressed asap so we can upgrade Prod. Your help is much appreciated!
I received a descriptor error when deploying installing this plug-in in both 18.3 and 19.1. Looks like it might be an case issue in the appian-plugin.xml file for getFilesLargerThanSize and getFilesOlderThanDate as the classes start with G not g
© 2019 Appian. All rights reserved.