The LOCK_NODE action applies a lock to a file or folder in Alfresco Content Services (ACS).
Use this action to prevent unauthorized or unintended modifications while content is being reviewed, processed, updated, or managed by a workflow. Locks can be configured with different lock types and durations, allowing organizations to control how content can be accessed and modified during specific business processes.
During the operation, the connector identifies the target file or folder. ACS applies the specified lock type, the duration and expiration of which were configured.The locked content remains available in the repository but can only be modified according to the selected lock configuration.
The input parameters of the action are:
| Parameter | Type | Required | Description |
|---|---|---|---|
| file | Array<json>, JSON | Optional | ACS file to lock. If multiple files are provided, only the first file is processed. |
| folder | Array<json>, JSON | Optional | ACS folder to lock. If multiple folder references are provided, only the first folder is used. |
| lifetime | String | Required |
Lifetime of the lock. Supported values:
|
| lockType | String | Required | Lock type to apply. Supported values:
|
| nodeId | String | Optional | Node ID of the file or folder. For example: a6a977a6-c728-4038-8dbc-d914c4d8cfb3. |
| path | String | Optional | Location or relative path of the file or folder to lock. |
| timeToExpire | Integer | Required | Time, in seconds, after which the lock expires. For example: 1200. |
The output parameters of the action are:
| Parameter | Type | Required | Description |
|---|---|---|---|
| response | Array<json> | Optional | Response returned by ACS for the lock request. |