Overview
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.
All functions use the serviceContext of the user account executing the expression at runtime.
Key Features & Functionality
Data Types
Smart Services
Functions
Glad to know this will work with 20.1 - Can you update the information for this plugin? It currently says 'Compatible Version(s): 17.2 +, 19.3 - which is misleading. Perhaps it should say 17.1 - 20.1.
Makes sense! Thanks, Mike!
The plugin will not be affected in any way. The "removed" tag is an internal tag that HC reads - we will be updating the HC. There may be some updates to the Content Tools plugin but always in a backwards compatible fashion. Public APIs that have been truly removed will be called out in release notes.
Thanks! But in health check we see some of the APIs removed. In which way, it will affect?
Yes it will work.
https://docs.appian.com/suite/help/20.1/Appian_Release_Notes.html#removals
Hi Team,
We are using this plugin.
In health check, we received some of the APIs used in this plugin got removed/deprecated. Can we expect any update on the plugin sooner?
We used the below functions in our app. We are going to upgrade to 20.1. Can you confirm that the below functions will work in 20.1?
FindContentByAttribute FindDocumentsByName FindFoldersByName GetContentObjectDetailsByID GetDocumentsFromFolder GetSubfoldersFromFolder
Health check report:
Content Tools (com.appiancorp.ps.plugins.contenttools) references removed and deprecated Appian APIs[removed] com.appiancorp.suiteapi.common.LocalObject.<init>(java.lang.Integer,java.lang.Long)[removed] com.appiancorp.suiteapi.common.exceptions.AppianException.<init>(com.appiancorp.suiteapi.common.exceptions.ErrorCode,java.lang.Object[])[removed] com.appiancorp.suiteapi.common.exceptions.AppianException.<init>(com.appiancorp.suiteapi.common.exceptions.ErrorCode,java.lang.Throwable)[removed] com.appiancorp.suiteapi.content.ContentFilter.<init>(int,int)[removed] com.appiancorp.suiteapi.process.exceptions.SmartServiceException.Builder.<init>(java.lang.Class,java.lang.Throwable)[removed] com.appiancorp.suiteapi.type.TypedValue.<init>(java.lang.Long,java.lang.Object)[deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getContentService(com.appiancorp.services.ServiceContext)[deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getStatisticsService(com.appiancorp.services.ServiceContext)[deprecated] com.appiancorp.suiteapi.content.ContentService.approve(java.lang.Long[])[deprecated] com.appiancorp.suiteapi.content.ContentService.getAllChildren(java.lang.Long, com.appiancorp.suiteapi.content.ContentFilter, java.lang.Integer)[deprecated] com.appiancorp.suiteapi.content.ContentService.getAllChildrenAndVersions(java.lang.Long, com.appiancorp.suiteapi.content.ContentFilter)[deprecated] com.appiancorp.suiteapi.content.ContentService.getExpiredIds(java.lang.Long, java.lang.Integer, com.appiancorp.suiteapi.content.ContentFilter)[deprecated] com.appiancorp.suiteapi.content.ContentService.getInactive(java.lang.Long, com.appiancorp.suiteapi.content.ContentFilter)[deprecated] com.appiancorp.suiteapi.content.ContentService.getPendingPaging(java.lang.Long, com.appiancorp.suiteapi.content.ContentFilter, int, int, java.lang.Integer, java.lang.Integer)[deprecated] com.appiancorp.suiteapi.content.ContentService.getVersions(java.lang.Long[], java.lang.Integer)[deprecated] com.appiancorp.suiteapi.content.ContentService.unexpire(java.lang.Long[])
Hi nagashankarn0001
Yes 1.1.3 is the current version.
We are using content functions plugin in our apps
com.appiancorp.ps.plugins.contenttools-1.1.3.jar (Last updated Nov 8, 2019) is the replacement of content functions plugin as we didn't find any official statement on it.
Thanks
Yes, this will continue to work. That being said I would recommend that you move over to the OOTB folder expression to pull out childDocuments.
we are preparing to upgrade our platform to New version 20.1 .we are using this ( content tools ) plugin & its functions ex : getdocumentsFromFolder() in our existing rules. Can you please confirm this plugin would support to 20.1 version or Can we get upgraded/replacement of this plugin