Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Track process instances started by a restart batch operation #4201

Open
1 of 4 tasks
yanavasileva opened this issue Mar 22, 2024 · 2 comments
Open
1 of 4 tasks

Track process instances started by a restart batch operation #4201

yanavasileva opened this issue Mar 22, 2024 · 2 comments
Labels
type:feature Issues that add a new user feature to the project.

Comments

@yanavasileva
Copy link
Member

yanavasileva commented Mar 22, 2024 •
edited
Loading

User Story (Required on creation)

As an Operations Engineer, if a "restart batch" is executed accidentally for all "Finished" process instances. It is important to know on which process instances the batch was executed to be able to take counter actions like e.g. roll-back, ... .

Functional Requirements (Required before implementation)

User can find all process instances started by a restart batch by selecting a (deep link) button.

Technical Requirements (Required before implementation)

  • Add restartedProcessInstanceId for historic process instances started by a batch pointing to the completed HPI that has been restarted
  • Add restartedByBatch(#batchId) filter criteria for historic process instance query
  • In Cockpit, add for restart batches a deep link button to the process dashboard where "restarted by batch" filter will be preselect to display the affected process instances

Limitations of Scope

Hints

Links

Breakdown

Tasks
Beta Give feedback
  1. Expose restartedProcessInstanceId for historic process instances #4214
    2 of 2
    scope:core-api type:feature type:subtask version:7.22.0 version:7.22.0-alpha6
    psavidis
  2. Introduce restartedByBatch(batchId) filter criteria for historic process instance query #4212
    scope:core-api type:subtask
  3. In Cockpit, allow to track started process instances by restart batch operation #4213
    scope:cockpit type:subtask
  4. Document trackability of process instances started by a restart batch operation #4226
    scope:documentation type:subtask

Dev2QA handover

  • Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment
@yanavasileva yanavasileva added the type:feature Issues that add a new user feature to the project. label Mar 22, 2024
@yanavasileva yanavasileva changed the title Introduce startedByBatch filter criteria for Process instances Introduce startedByBatch filter criteria for historic process instances Mar 22, 2024
@yanavasileva yanavasileva changed the title Introduce startedByBatch filter criteria for historic process instances Allow to track process instances started by restart batch operation Mar 22, 2024
@yanavasileva yanavasileva mentioned this issue Mar 22, 2024
Closed
1 task
@yanavasileva yanavasileva changed the title Allow to track process instances started by restart batch operation Track process instances started by a restart batch operation Mar 25, 2024
@yanavasileva yanavasileva mentioned this issue Mar 26, 2024
Open
3 tasks
@adisin17
Copy link

Hi @yanavasileva , I am new here and would like to take this up.

@yanavasileva yanavasileva mentioned this issue May 17, 2024
Open
2 tasks
@yanavasileva
Copy link
Member Author

Hi @adisin17,

Thank you for your interest.
This ticket depends on #4205 which is not scheduled yet. However, a community member has raised a pull request for it.
Before starting work on this item, I suggest you either to wait for the implementation of #4205 or pick another topic that doesn't have task dependency.

Let me know if you need any support to make a contribution.
Also, please have a look at our contribution guidelines: https://github.com/camunda/camunda-bpm-platform/blob/master/CONTRIBUTING.md

Best,
Yana

@yanavasileva yanavasileva mentioned this issue Jun 12, 2024
Open
psavidis pushed a commit that referenced this issue Sep 12, 2024
@punitdarira
feat(engine, engine-rest): Expose restartedProcessInstanceId
0509c7b 
Context: This commit introduces restartedProcessInstanceId for historic process instances.
Why: To be able to track the originating process instances in restart - batch operations.

Db-Migration: The commit introduces

- RESTARTED_PROC_INST_ID_ column in ACT_HI_PROCINST table
- ACT_IDX_HI_PRO_RST_PRO_INST_ID index on the above

Unit-tests: Adds a unit test for verified the population of the column for completed and restarted process instances

Related-to

- #4214
- #4201
hauptmedia added a commit to hauptmedia/operaton that referenced this issue Nov 4, 2024
@hauptmedia
feat(engine, engine-rest): Expose restartedProcessInstanceId
731e32d 
Context: This commit introduces restartedProcessInstanceId for historic process instances.
Why: To be able to track the originating process instances in restart - batch operations.

Db-Migration: The commit introduces

- RESTARTED_PROC_INST_ID_ column in ACT_HI_PROCINST table
- ACT_IDX_HI_PRO_RST_PRO_INST_ID index on the above

Unit-tests: Adds a unit test for verified the population of the column for completed and restarted process instances

Related-to

- camunda/camunda-bpm-platform#4214
- camunda/camunda-bpm-platform#4201

Backported commit 0509c7b114 from the camunda-bpm-platform repository.
Original author: punitdarira <[email protected]>
@hauptmedia hauptmedia mentioned this issue Nov 4, 2024
Merged
javahippie pushed a commit to operaton/operaton that referenced this issue Nov 5, 2024
@hauptmedia @javahippie
feat(engine, engine-rest): Expose restartedProcessInstanceId
db0f12d 
Context: This commit introduces restartedProcessInstanceId for historic process instances.
Why: To be able to track the originating process instances in restart - batch operations.

Db-Migration: The commit introduces

- RESTARTED_PROC_INST_ID_ column in ACT_HI_PROCINST table
- ACT_IDX_HI_PRO_RST_PRO_INST_ID index on the above

Unit-tests: Adds a unit test for verified the population of the column for completed and restarted process instances

Related-to

- camunda/camunda-bpm-platform#4214
- camunda/camunda-bpm-platform#4201

Backported commit 0509c7b114 from the camunda-bpm-platform repository.
Original author: punitdarira <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:feature Issues that add a new user feature to the project.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yanavasileva @adisin17