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
Hi. I get an error when installing the plugin in version 25.3 "Error: Unable To Deploy Plug-in. Plug-in failed to deploy.". Does anyone else have the same error?
Hi,
The Content Tools (com.appiancorp.ps.plugins.contenttools) plug-in has been flagged in the health check report as high risk. The following private Appian API is being referenced:
[private] com.appiancorp.process.expression.ExpressionEvaluationException.<init>(java.lang.String)
Could you please review this and let us know if there are any plans to address this dependency in future updates?
Thank you in advance!
Hi, we detected that 'Delete Rule/Constant Versions' is not working in Appian v25.2. We are using Content Tools v1.11.3
Hi there. When I run a Health Check it says the following. Is this something you are planning to address?
Content Tools (com.appiancorp.ps.plugins.contenttools) references private Appian APIs [private] com.appiancorp.process.expression.ExpressionEvaluationException.<init>(java.lang.String)
for me the smart service Create Document Version is not working with appian 25.2
The function getcontentobjectswithnumofversions is not working. This happens to us with version 25.1. Does it happen to anyone else with this version? Is there a solution?
The goal is to see the versions of the objects, in case someone has another solution.
Thanks and best regards
According to our latest Appian Health Check, this plugin is using deprecated Appian APIs. Is there a plan to upgrade this plugin to support the newer versions of Appian and cease the use of these deprecated APIs?
We also are experiencing this in our environments with the function. Appian advised us to send an email to appmarket@appian.com regarding the issue since they do not support the plug-in. We did that back in December and have not seen anything.