In Share the Document Library defines a number of “action groups” which determine the actions shown to the user. What would determine the action…

In Alfresco Share, the selection of an "action group" for the Document Library is primarily determined by the context of the user interface and the fundamental nature of the content item. The current view (e.g., Detailed, Simple, Gallery) directly maps to specific action groups like doclib-details or doclib-browse in the configuration. Concurrently, the type of node (e.g., a cm:folder versus a cm:content document) dictates which set of actions within that group is relevant. For instance, a folder has an "Upload" action, while a document does not. These two factors establish the base set of actions to be considered.

B. The aspects applied to the node typically enable or disable individual actions within a group (e.g., versioning actions), but do not select the entire group.

C. The mime type of the node is used by evaluators to control specific actions (e.g., "Edit in Google Docs"), not to determine the overall action group.

D. The status of the document, often managed by workflows, influences action availability via permissions or specific conditions, rather than selecting a different base action group.

E. The current user's permissions filter which actions from the selected group are ultimately displayed and executable, but do not determine the initial group selection.

1. Alfresco Content Services 5.2 Documentation, Share Extensibility, Actions: This section details how actions are configured. It shows that action groups are defined within a component configuration, such as the Document Library. The examples and structure implicitly and explicitly tie action groups to UI views and differentiate actions based on node characteristics. (See Developing -> Share Extensions -> Share Extensibility -> Actions).

2. Default Share Configuration (share-documentlibrary-config.xml): Examination of this core configuration file for Alfresco 5.x reveals the defined action groups. For example, and directly correspond to the Document Library views (supporting option F).

3. Default Share Configuration (share-documentlibrary-config.xml): Within the action groups, individual actions use evaluators like evaluator.doclib.action.isContainer to differentiate between folders and documents, confirming that the node type is a primary determinant for the set of applicable actions (supporting option A).