Start date filter for modify operation - Documentation #4632
Description
Acceptance Criteria (Required on creation)
Document following in migration guide:
From PR:
When deleting an incident, the incident filters still yield the process instances that had an incident. I think this is generally fine since the behavior is consistent with the standalone batch operation page. However, we should mention this in the migration guide to avoid surprises for users.
From kick-off document:
Articulate the change to the group key for stored modify process instance queries
Articulate the need that administrators communicate this change ahead of the migrations so their users are able to prepare for that. For example: Please let your users know the change regarding of the filters and prepare them to recreate the saved filters.
From incidentIdIn PR:
❓ Do we need to extend to docs that incidentIds are excluded for Or queries here: https://docs.camunda.org/manual/develop/user-guide/process-engine/process-engine-api/#or-queries
Related to PR for feature(engine): add activityIdIn filter to HistoricProcessInstanceQuery
General statement: Runtime query change to historic process instances query
Details about: limitations regarding AsyncBefore, AsyncAfter, and compensation
To consider:
Is the documentation for activityIdIn in HistoricProcessInstanceQuery clear enough?
Hints
Links
Parent: #4586
Breakdown
### Pull Requests
- [ ] https://github.com/camunda/camunda-docs-manual/pull/1689
- [ ] https://github.com/camunda/camunda-bpm-platform/pull/4675