You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alfresco by default only provides category / tag management capabilities as part of the Alfresco Share application. If a customer does not intend to use Share and instead opt for either a 3rd party or ADF-based client, they would still have to use Share for any administration of these elements, or develop the capability in their own client using the public ReST API, which actually does not provide any 1st-level support for categories at all (actually d:nodref/d:category properties have consciously not been supported in some key APIs).
A basic category / tag management capability should be an integral part of an administration UI, and barring any (known) plans of Alfresco to develop such capability on the Repository-tier administration console, we should look to add this to fill the gap, and allow greater flexibility in how Alfresco is deployed and used by customers / community members.
The text was updated successfully, but these errors were encountered:
FEATURE / ENHANCEMENT
Alfresco by default only provides category / tag management capabilities as part of the Alfresco Share application. If a customer does not intend to use Share and instead opt for either a 3rd party or ADF-based client, they would still have to use Share for any administration of these elements, or develop the capability in their own client using the public ReST API, which actually does not provide any 1st-level support for categories at all (actually d:nodref/d:category properties have consciously not been supported in some key APIs).
A basic category / tag management capability should be an integral part of an administration UI, and barring any (known) plans of Alfresco to develop such capability on the Repository-tier administration console, we should look to add this to fill the gap, and allow greater flexibility in how Alfresco is deployed and used by customers / community members.
The text was updated successfully, but these errors were encountered: