You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
When running an async runtime modification (see steps) the batch job is executed for all instances, including finished and unfinished ones, which is not correct and not what is displayed in the Cockpit migration popup.
Steps to reproduce (Required on creation)
Create process definition. You can put a start event, a user task, and an end event.
Start like 5 PI-s. Complete 3 PI-s by assigning the task and completing it
For the remaining 2 PI-s go to the modify tab, drag and drop the token from the USER TASK to the end event
Go to Select Instances button, and click the Query radio
Remove the filter criteria "Activity_ID=..."
You will see the "Modify all Instances in filter (2)" button, click on it
Leave the async checkbox enabled, you can still see the label under Summary: "You are about to modify 2 instances in the following way:"
So we are expected to modify only 2 queries
Click proceed
Go to batches page: You will see in the "In Progress Batch Details" that the totalJobs count is 5
Observed Behavior (Required on creation)
Batch runs for all the 5 instances, including finished & unfinished.
Expected behavior (Required on creation)
Batch runs only for the 2 unfinished instances, as it was shown in the popup.
Root Cause (Required on prioritization)
With #4586 we replaced the query with historic query. During the modification popup, the list and count display instances with the unfinished: true parameter, which is correct.
However, for the actual batch query we don't include this property anymore.
Solution Ideas
Use the unfinished: true in the batch modification, too.
Environment (Required on creation)
Version 7.22, any environment.
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
When running an async runtime modification (see steps) the batch job is executed for all instances, including finished and unfinished ones, which is not correct and not what is displayed in the Cockpit migration popup.
Steps to reproduce (Required on creation)
So we are expected to modify only 2 queries
Observed Behavior (Required on creation)
Batch runs for all the 5 instances, including finished & unfinished.
Expected behavior (Required on creation)
Batch runs only for the 2 unfinished instances, as it was shown in the popup.
Root Cause (Required on prioritization)
With #4586 we replaced the query with historic query. During the modification popup, the list and count display instances with the
unfinished: true
parameter, which is correct.However, for the actual batch query we don't include this property anymore.
Solution Ideas
Use the
unfinished: true
in the batch modification, too.Hints
Links
Breakdown
Pull Requests
Dev2QA handover
The text was updated successfully, but these errors were encountered: