Retrieve User Actions on Multiple Binders

Retrieve all available user actions on specific versions of multiple binders.

POST/api/{version}/objects/binders/lifecycle_actions

Headers

Name	Description
`Content-Type`	`application/x-www-form-urlencoded`
`Accept`	`application/json` (default) or `application/xml`

Body Parameters

Name	Description
`docIds` required	The `id` and version numbers of binders for which to retrieve the available user actions. Include a comma-separated list of binder IDs and major and minor version numbers in the format `{binder_id:major_version:minor_version}`. For example, `22:0:1`.

Request

curl -X POST -H "Authorization: {SESSION_ID}" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "docIds=152:0:1,153:1:0,154:1:0" \
https://myvault.veevavault.com/api/v26.1/objects/binders/lifecycle_actions

Response

{
    "responseStatus": "SUCCESS",
    "responseMessage": "Success",
    "lifecycle_actions__v": [
        {
            "name__v": "read__c",
            "label__v": "Read",
            "lifecycle_action_type__v": "workflow",
            "lifecycle__v": "job_processing__c",
            "state__v": "draft__c",
            "executable__v": true,
            "entry_requirements__v": "https://myvault.veevavault.com/api/v26.1/objects/binders/lifecycle_actions/read__c/entry_requirements?lifecycle=job_processing__c&state=draft__c"
        }
    ]
}

Response Details

The response lists all available lifecycle actions (lifecycle_actions__v) that can be initiated on the specified versions of multiple binders.

Name	Description
`name__v`	The lifecycle action name (consumed by the API). These vary from Vault to Vault and may be text, numeric, or alphanumeric values.
`label__v`	The lifecycle action label. This is the "User Action" label seen in the UI.
`lifecycle_action_type__v`	The `workflow` (legacy) and `stateChange` types are the most commonly used and are available in all Vaults. Others may exist.
`lifecycle__v`	The binder lifecycle the action belongs to. For example, `general_lifecycle__c`.
`state__v`	The state of the binder.
`entry_requirements__v`	The endpoint to retrieve the entry requirements for each lifecycle action. If no entry requirements exist, the endpoint returns an empty list.

Lifecycle actions are not returned for binders which are currently in an active workflow.