/api/helpdesk/processes/{processId}/activities/{activityId}/transitions

Exposes one transition leaving an activity.

The URL identifier is a SHA-256 fingerprint, not a persisted model value. Clients should use the identifier returned by the collection GET and supply a fresh identifier for later PATCH requests. Conditions are replaced as one collection; conditions in the native model are evaluated as an AND expression. The conditionData property is serialized as a JSON string. Action identifiers and condition dependencies must be obtained from the process editor metadata endpoint and from the process detail graph.

Example of an automatic transition with two dependent conditions. The first identifier must be an activity in this process. The second field key and operator must be compatible according to editor metadata. Replace every placeholder with an identifier returned by the API:

 PATCH /api/helpdesk/processes/{processId}/activities/{activityId}/transitions/{transitionId}
 {
   "actionid": 1234,
   "nextActivityId": "activity-finish",
   "conditionsForAutoTransition": [
     {"type":"activityFinished",
      "conditionData":"{\"itemId\":\"activity-review\",\"ignoreIfNoLongerReachable\":false}"},
     {"type":"ticketHasValue",
      "conditionData":"{\"referencedTicket\":null,\"ticketFieldKey\":\"priority\",\"operator\":\"EQUALS\",\"value\":\"2\"}"}
   ],
   "autoTransitionText": {
     "text": "Finish after review", "htmlContent": false, "duplicatedContent": []
   }
 }
 

Lists transitions leaving an activity.

# Request
GET /api/helpdesk/processes/<processId>/activities/<activityId>/transitions HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>

# Response
HTTP/1.1 200 OK
Content-Type: application/json

[
    {
        "transitionId": "string",
        "nextActivityId": "4ga372jupg3i4eykhmbayesxn",
        "actionid": 0,
        "actionLabel": "string",
        "conditionsForAutoTransition": [
            
        ]
    }
]

The status codes 400, 403, 404, 405, 406, 409, 413, 415, and 500 use the same ApiError JSON error format:

{
    "status": 404,
    "code": "route_not_found",
    "message": "The requested API route does not exist.",
    "details": []
}

Request and response schemas used on this page.