deploy-process
Operations addressed under /deploy-process — 2 operations.
deploy-process-request
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
deploy-process-request › Request Body
canPreviousUserApprovecanStarterUserApproveoperationTypepathresourceContentresourceNametenantIdusageTypePermitted values — validated against the usage_type parameter. The service rejects any other value.
| Value | Token | Labels |
|---|---|---|
1 | Service | en: Service · ar: خدمة |
2 | BPM | en: BPM · ar: معدل ضربات القلب |
4 | Rule | en: Rule · ar: قاعدة |
3 | Formula | en: Formula · ar: الصيغة |
5 | DistributedQuery | en: Distributed Query · ar: استعلام موزع |
6 | Keycloak | en: Keycloak Service · ar: خدمة كي-كلاوك |
7 | Camunda | en: Camunda Service · ar: خدمة كاموندা |
8 | TaskList | en: Task List · ar: قائمة المهام |
waitForResponsedeploy-process-request › Responses
Success. The catalog declares this returns a single record. Of 25 operations in this state with a probeable route, 8 answered and 6 returned a single record — the other two returned a collection and a bare boolean.
keydeploy-process-by-process-definition-id
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Response body, read from the service source
The route declares its response as DeployProcessByProcessDefinitionIdDto.
| Field | Declared type | Nullable |
|---|---|---|
BpmnProcessId | string | no |
ProcessDefinitionKey | long | no |
Version | int | no |
Resource | string | no |
EditedResource | string | no |
Elements | IEnumerable<Element> (collection) | no |
Member names are the service's declaration names.
Error codes this operation is known to raise
| Code | Status | Meaning | Message |
|---|---|---|---|
ERR_BPM_21 | 400 | PROCESS_DEFINITION_IS_NOT_FOUND | Process definition cannot be found. |
ERR_BPM_38 | 400 | DEPLOY_HAS_ERROR | Deploy has error. Error: {0} |
path Parameters
processDefinitionIddeploy-process-by-process-definition-id › Responses
Success. An exact, uniquely bound route registration classifies this response as a single-record.