/api/helpdesk/processes/{processId}/parallel-tickets/{parallelTicketId}/startCondition

Exposes one parallel-ticket definition below a ticket process.

Start conditions use native condition data. Clients should obtain valid condition types and field operators from editor metadata. Conditions in one list are combined with logical AND. The conditionData property is a JSON string, not an embedded JSON object.

For example, this definition starts after activity activity-review was visited and the main ticket has priority 2. The referenced activity and field key must exist in the same process; EQUALS must be listed for that field by editor metadata:

 {
   "id": "parallel-security",
   "name": "Security review",
   "startActivityId": "parallel-start",
   "startCondition": [
     {"type":"activityVisited",
      "conditionData":"{\"itemId\":\"activity-review\",\"ignoreIfNoLongerReachable\":false}"},
     {"type":"ticketHasValue",
      "conditionData":"{\"referencedTicket\":null,\"ticketFieldKey\":\"priority\",\"operator\":\"EQUALS\",\"value\":\"2\"}"}
   ],
   "deactivated": false,
   "relativeLatestStart": null,
   "actionOnMainTicketEnd": 42
 }
 

Conditions required before start.

# Request
GET /api/helpdesk/processes/<processId>/parallel-tickets/<parallelTicketId>/startCondition HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>

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

[
    {
        "conditionData": "string",
        "type": "string"
    }
]

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.