actions

/actions — Action Executor Generator

In-Process SDK only — deploys inside the ACS JVM as a Platform JAR.

Generate Alfresco action classes.

Input

Read REQUIREMENTS.md to identify action requirements and resolve the Platform JAR project's Root path from Section 2 (Project Architecture).

• If Section 2 contains no Platform JAR project, stop and explain that /actions only applies to the in-process repository addon project.

Output Files

1. Action Class

{platform-project-root}/src/main/java/{package}/action/{Name}ActionExecuter.java

• Extend ActionExecuterAbstractBase
• Implement executeImpl() method
• Define parameters via addParameterDefinitions()

2. Spring Bean Registration

Add to {platform-project-root}/src/main/resources/alfresco/module/{module-id}/context/service-context.xml:

<bean id="{prefix}.{actionBeanName}" class="{package}.action.{Name}ActionExecuter" parent="action-executer">
    <property name="nodeService" ref="NodeService"/>
    <!-- additional service references -->
</bean>

The bean id is the repository action identifier used by Share, rules, and the Action REST API. Follow Spring Beans and Share UI Model → Repository action wiring in AGENTS.md.

Action Reference

Synchronous vs asynchronous execution

Actions can run inline or in a background thread. Asynchronous actions run in their own transaction after the current one commits.

// Programmatic invocation
actionService.executeAction(action, nodeRef, checkConditions, executeAsynchronously);

• Set executeAsynchronously=true for long-running or external-integration work so the caller's transaction is not held open.
• An action can also declare a default by overriding getAdhocPropertiesAllowed() / setting the executer's executeAsynchronously bean property.

Parameter constraints (dropdown-style values)

To constrain a parameter to a fixed set of values, reference a registered parameter constraint in getParameterDefinitions():