feat(api-mapping): add Camunda 8.10 mapping guide - #2559
Open
bojtospeter wants to merge 16 commits into
Open
Conversation
Add the released Camunda 8.10 API specification and publish the 7.23-to-8.10 mapping guide, including the new suspension, batch job update, and job priority mappings.\n\nCloses #2164\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
There are a few confirmed documentation/mapping-table defects (duplicate row mapping and grammar errors) that should be corrected before merge.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR extends the code-conversion/api-mapping web experience with the released Camunda 8.10 Orchestration Cluster API specification and publishes the corresponding Camunda 7.23 → 8.10 mapping guide, including updated endpoint mappings and version-specific documentation links.
Changes:
- Added a new 7.23 → 8.10 mapping entry and wired it into the mapping selector.
- Introduced a new 8.10 mapping guide (intro + endpoint mappings) under
mapping_details_7_23_to_8_10/. - Updated type-escape allowlist to account for the new 8.10 OpenAPI spec content.
File summaries
| File | Description |
|---|---|
| code-conversion/api-mapping/src/mappings/mappingIndex.jsx | Registers the new 7.23 → 8.10 mapping in the UI index. |
| code-conversion/api-mapping/src/mappings/mapping_7_23_to_8_10.jsx | Adds the new 7.23 → 8.10 mapping guide configuration and mapping aggregation. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/index.js | Exports the per-endpoint-group mapping arrays for the 8.10 guide. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/version.jsx | Adds mapping guidance for the version/status endpoint. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_variable.jsx | Adds/updates user-task variable mappings for 8.10. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_local_variable.jsx | Adds/updates user-task local-variable mappings for 8.10. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_identity_link.jsx | Adds identity-link mapping guidance via user-task retrieval/patch endpoints. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_comment.jsx | Documents lack of task comment APIs in 8.10. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_attachment.jsx | Maps task attachments to documents APIs and links to 8.10 docs. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/external_task.jsx | Maps external-task APIs to 8.10 job search/activation/failure/completion endpoints. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/job.jsx | Adds/updates job mappings including batch retry updates and priority changes. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/process_definition.jsx | Adds/updates process-definition mappings including suspension-related guidance. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/process_instance.jsx | Adds/updates process-instance mappings including suspension state and job retry batch updates. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task.jsx | Adds/updates task/user-task mappings including suspension-state notes. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/authorization.jsx | Adds 8.10 authorization mappings aligned with Identity APIs/docs. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/batch.jsx | Placeholder mapping group export for batch endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/condition.jsx | Maps condition evaluation to 8.10 conditional evaluation endpoint. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/decision_definition.jsx | Placeholder mapping group export for decision definition endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/decision_requrements_definition.jsx | Placeholder mapping group export for decision requirements endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/deployment.jsx | Placeholder mapping group export for deployment endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/engine.jsx | Placeholder mapping group export for engine endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/event_subscription.jsx | Maps event-subscription APIs to message-subscriptions search in 8.10. |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/execution.jsx | Placeholder mapping group export for execution endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/filter.jsx | Placeholder mapping group export for filter endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/group.jsx | Placeholder mapping group export for group endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_activity_instance.jsx | Placeholder mapping group export for historic activity instance endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_batch.jsx | Placeholder mapping group export for historic batch endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_decision_definition.jsx | Placeholder mapping group export for historic decision definition endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_decision_instance.jsx | Placeholder mapping group export for historic decision instance endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_decision_requirements_definition.jsx | Placeholder mapping group export for historic DRD endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_detail.jsx | Placeholder mapping group export for historic detail endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_external_task_log.jsx | Placeholder mapping group export for historic external task log endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_identity_link_log.jsx | Placeholder mapping group export for historic identity link log endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_incident.jsx | Placeholder mapping group export for historic incident endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_job_log.jsx | Placeholder mapping group export for historic job log endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_process_definition.jsx | Placeholder mapping group export for historic process definition endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_process_instance.jsx | Placeholder mapping group export for historic process instance endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_task_instance.jsx | Placeholder mapping group export for historic task instance endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_user_operation_log.jsx | Placeholder mapping group export for historic user operation log endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/historic_variable_instance.jsx | Placeholder mapping group export for historic variable instance endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/history_cleanup.jsx | Placeholder mapping group export for history cleanup endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/identity.jsx | Placeholder mapping group export for identity endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/incident.jsx | Placeholder mapping group export for incident endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/job_definition.jsx | Placeholder mapping group export for job definition endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/message.jsx | Placeholder mapping group export for message endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/metrics.jsx | Placeholder mapping group export for metrics endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/migration.jsx | Placeholder mapping group export for migration endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/modification.jsx | Placeholder mapping group export for modification endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/schema_log.jsx | Placeholder mapping group export for schema log endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/signal.jsx | Placeholder mapping group export for signal endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/telemetry.jsx | Placeholder mapping group export for telemetry endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/tenant.jsx | Placeholder mapping group export for tenant endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/user.jsx | Placeholder mapping group export for user endpoints (currently empty). |
| code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/variable_instance.jsx | Placeholder mapping group export for variable instance endpoints (currently empty). |
| code-conversion/api-mapping/scripts/type-escape-allowlist.txt | Allowlists a new “explicit-any” hit introduced by the 8.10 OpenAPI spec content. |
Review details
- Files reviewed: 55/56 changed files
- Comments generated: 3
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
It introduces a large generated OpenAPI spec plus broad mapping-guide content changes that warrant final human verification for correctness and consistency.
Review details
Suppressed comments (2)
Previously missed (2) — in code that hasn't changed since the last review.
code-conversion/api-mapping/scripts/type-escape-allowlist.txt:3
- This allowlist entry is suppressing a false positive from the type-escape regex matching
: anyinside an OpenAPI description string; add a short note so future spec regenerations know why this line is here.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/external_task.jsx:600 - Grammar: "there is not additional" should be "there is no additional".
- Files reviewed: 55/56 changed files
- Comments generated: 0 new
- Review effort level: Lite
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
bojtospeter
commented
Sep 4, 2026
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
There are actionable security and maintainability issues in the new files (missing rel on target="_blank" links and a brittle line-based allowlist for generated OpenAPI content).
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 55/56 changed files
- Comments generated: 2
- Review effort level: Lite
Exclude generated OpenAPI sources from type-escape checks and secure documentation links opened in new tabs.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
There are user-facing guide text issues (field-name mismatch and punctuation whitespace rendering) that should be corrected before publishing the 8.10 mapping guide.
Review details
Suppressed comments (4)
Previously missed (2) — in code that hasn't changed since the last review.
code-conversion/api-mapping/src/mappings/mapping_7_23_to_8_10.jsx:180
sortis the actual Camunda 8 request-body field name (and is referenced earlier in this guide), but this section labels it assorting, which is inconsistent and can mislead readers.
This issue also appears on line 345 of the same file.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_identity_link.jsx:75
- The period is on its own line after the
<code>candidateUsers</code>element, which will render as an extra space before the period ("candidateUsers ."). Move the period onto the same line as the code element.
This issue also appears on line 108 of the same file.
code-conversion/api-mapping/src/mappings/mapping_7_23_to_8_10.jsx:347
- This section refers to the Camunda 8 request-body
sortfield, but the text sayssorting. Align it with the actual field name to avoid confusion.
<h5>
Fields of <code>sorting</code> list of objects:
</h5>
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_identity_link.jsx:112
- Same whitespace-before-period issue as above: the period is on its own line, which will render as "candidateUsers ." in the UI.
- Files reviewed: 55/56 changed files
- Comments generated: 0 new
- Review effort level: Lite
Correct the Camunda 8 sort field labels and keep candidate user punctuation adjacent in the 8.10 guide. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
bojtospeter
commented
Sep 4, 2026
bojtospeter
commented
Sep 4, 2026
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The change set is large and content-heavy (new spec + many mapping entries) and needs a human pass to validate semantic correctness against the released 8.10 APIs.
Review details
- Files reviewed: 55/56 changed files
- Comments generated: 0 new
- Review effort level: Lite
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Several mappings describe invalid request shapes or semantics, and the batch-retry details currently render empty.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 55/56 changed files
- Comments generated: 10
- Review effort level: Balanced
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Several mappings currently produce invalid filters, duplicate variable results, or incorrect identifier and endpoint guidance.
Review details
Suppressed comments (11)
Previously missed (7) — in code that hasn't changed since the last review.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/external_task.jsx:282
- These query objects are not directly assignable to
JobFilter: common C7 fields are renamed (externalTaskId→jobKey,topicName→type,workerId→worker), need advanced-filter operators, or have no C8 equivalent. Please list the supported field transformations and classify unsupported criteria separately; otherwise the documented object-to-object mapping produces rejected or incorrectly scoped batch updates.
This issue also appears on line 359 of the same file.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/process_definition.jsx:1302
- This endpoint is not redundant: C7
submit-formstarts a process instance for the specified definition, and C8POST /process-instancessupportsprocessDefinitionKey, variables, andbusinessId. The guide already maps both key-based submit-form variants this way, so marking only the ID-based variant discontinued hides a valid migration path.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task.jsx:57 processInstanceIdIncannot be sent as the scalar mapping shown here. The C8 filter supports the list throughprocessInstanceKey.$in; without documenting that transformation, following this row produces an invalid filter for the array variant.
This issue also appears on line 91 of the same file.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task.jsx:103
elementInstanceKeyis scalar-only in the 8.10 user-task filter, but the C7 source accepts a list. As done fortaskIdInabove, this must use$orwith oneelementInstanceKeyclause per ID (or separate searches); mapping the array directly to this scalar loses the list semantics.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task.jsx:942- This is not a direct replacement for C7 form variables. C7 applies form-field types/defaults and returns one property per effective variable, while this endpoint returns raw scope occurrences (including duplicate shadowed names) and ignores form metadata. Use effective-variable search as the closest target and explicitly mark the form-field behavior as discontinued.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_attachment.jsx:91 - A Camunda 7
attachmentIdis not a Camunda 8documentId; uploading the attachment content to C8 creates and returns a new document ID. Presenting this as a direct field rename will make delete requests target a nonexistent document unless the migration first persists the returned ID mapping.
This issue also appears on line 165 of the same file.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_variable.jsx:15
- This C8 endpoint returns every scope occurrence of a visible name, so a shadowed variable appears multiple times; the C7 endpoint returns an object keyed by name and therefore exposes only the effective value. Map this read to the effective-variable search endpoint, which explicitly deduplicates names using the innermost scope.
This issue also appears on line 112 of the same file.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_variable.jsx:112
- A name filter on the ordinary variable search can return multiple values when the variable is shadowed in nested scopes, whereas C7 returns the single effective visible variable. Use the effective-variable search endpoint here as well; it supports the same
filter.namefield.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task.jsx:91 - The array-valued
processDefinitionKeyInneeds the advanced C8$infilter rather than the scalar field shown here. Document bothprocessDefinitionIdfor the singular source value andprocessDefinitionId.$infor the list so the resulting request matches the 8.10 schema.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_attachment.jsx:166 - The source attachment ID cannot be used directly as the C8 document ID. A migrated attachment must first be uploaded and the returned
documentIdretained; otherwise this download mapping leads users to request an unrelated or missing C8 document.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/external_task.jsx:364 - As above, neither C7 query schema can be copied into
JobFilter; field names, key formats, and supported predicates differ substantially. Document concrete translations and unsupported fields for the async source endpoint instead of marking both whole objects as direct, or migrated retry updates will use invalid/wrong filters.
leftEntry: <pre>(object) externalTaskQuery</pre>,
rightEntry: <pre>(object) filter</pre>,
},
{
leftEntry: <pre>(object) processInstanceQuery</pre>,
rightEntry: <pre>(object) filter</pre>,
- Files reviewed: 55/56 changed files
- Comments generated: 0 new
- Review effort level: Balanced
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
bojtospeter
commented
Sep 7, 2026
bojtospeter
commented
Sep 7, 2026
bojtospeter
commented
Sep 7, 2026
bojtospeter
commented
Sep 7, 2026
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Lock extension loses worker-ownership fencing, and resumption branches lack their corresponding endpoint links.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (3)
Previously missed (1) — in code that hasn't changed since the last review.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/process_instance.jsx:796
- This Camunda 7 operation handles both boolean values, but the endpoint panel always links to the suspension operation. When
suspendedisfalse, the prose names resumption without linking its 8.10 documentation, so the mapping's published link is for the wrong branch. Link the resumption operation explicitly (or support multiple targets).
This issue also appears in the following locations of the same file:
- line 927
- line 1338
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/process_instance.jsx:931
- This asynchronous Camunda 7 operation also handles both boolean values, but the endpoint panel always links to suspension. For
suspended: false, add an actual 8.10 resumption documentation link (or model both targets), rather than leaving users with the suspension link only.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/process_instance.jsx:1341 - The rendered Camunda 8 endpoint links only to suspension, although this Camunda 7 operation maps
suspended: falseto a separate resumption API. Make “Resume process instance” an explicit 8.10 documentation link (or support both target endpoints) so the false branch does not direct users only to the wrong operation.
- Files reviewed: 55/56 changed files
- Comments generated: 1
- Review effort level: Balanced
Preserve leased-job fencing and link both suspension states. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Peter Bojtos <peter.bojtos@camunda.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The guide is published before the stable 8.10 release and two bulk-variable mappings incorrectly imply that wrapped Camunda 7 values can be sent directly.
Review details
Suppressed comments (3)
Previously missed (3) — in code that hasn't changed since the last review.
code-conversion/api-mapping/src/mappings/mappingIndex.jsx:15
- This publishes the 8.10 guide before the release required by #2164. As of 2026-09-07, Camunda's official release notes still mark 8.10 as unreleased and schedule the stable release for 2026-10-13, so this exposes preview APIs and versioned links as though they were final. Keep this entry out of the public index until release, then import the released specification and revalidate the links.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_local_variable.jsx:60 - This is not a direct object-to-object mapping: Camunda 7
modificationsvalues areVariableValueDtowrappers (value,type, andvalueInfo), while the Camunda 8variablesobject expects raw JSON values. Following this row literally stores the wrappers as local-variable values. Document that every entry must be unwrapped/converted before sending it.
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task_variable.jsx:58 - This is not a direct object-to-object mapping: Camunda 7
modificationsvalues areVariableValueDtowrappers (value,type, andvalueInfo), while the Camunda 8variablesobject expects raw JSON values. Following this row literally stores the wrappers as process-variable values. Document that every entry must be unwrapped/converted before sending it.
- Files reviewed: 57/58 changed files
- Comments generated: 0 new
- Review effort level: Balanced
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Three variable-update mappings omit the required conversion from Camunda 7 value wrappers to raw Camunda 8 JSON values.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 57/58 changed files
- Comments generated: 3
- Review effort level: Balanced
Comment on lines
+1423
to
+1426
| { | ||
| leftEntry: <pre>(object) modifications</pre>, | ||
| rightEntry: <pre>(object) variables</pre>, | ||
| }, |
Comment on lines
+58
to
+61
| { | ||
| leftEntry: <pre>(object) modifications</pre>, | ||
| rightEntry: <pre>(object) variables</pre>, | ||
| }, |
Comment on lines
+56
to
+59
| { | ||
| leftEntry: <pre>(object) modifications</pre>, | ||
| rightEntry: <pre>(object) variables</pre>, | ||
| }, |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Several search mappings document invalid top-level filter fields, and the synchronous suspension mapping omits its asynchronous C8 behavior.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
code-conversion/api-mapping/src/mappings/mapping_details_7_23_to_8_10/task.jsx:252
withoutDueDateis a boolean in the bundled Camunda 7.23 specification, not a date-time. The displayed type is misleading for users translating this query parameter.
- Files reviewed: 57/58 changed files
- Comments generated: 6
- Review effort level: Balanced
| ), | ||
| rightEntry: ( | ||
| <> | ||
| <pre>(string) processDefinitionKey</pre> |
| leftEntry: <pre>(string[]) processInstanceIds</pre>, | ||
| rightEntry: ( | ||
| <> | ||
| <pre>(string*) processInstanceKey</pre> |
Comment on lines
+809
to
+813
| The Camunda 8.10 request body must be{" "} | ||
| <code>{"{ filter: ... }"}</code>. With{" "} | ||
| <code>suspended: true</code>, the suspension endpoint | ||
| updates only active process instances. With{" "} | ||
| <code>suspended: false</code>, use the resumption endpoint |
| ), | ||
| rightEntry: ( | ||
| <> | ||
| <pre>(string) userTaskKey</pre> |
| }, | ||
| { | ||
| leftEntry: <pre>(string) varName</pre>, | ||
| rightEntry: <pre>(string) name</pre>, |
| }, | ||
| { | ||
| leftEntry: <pre>(string) varName</pre>, | ||
| rightEntry: <pre>(string) name</pre>, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
cd code-conversion/api-mapping && npm run buildCloses #2164