flowable / flowable/flowable-engine
completionCondition---Even if the conditions are not met, it can still proceed to the next node
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 7h 8m
- Merged PRs (30d)
- 2
Description
${passCount/totalCount>=0.5}
passCount = 0;totalCount=3;
complete task code :
param.put("passCount", passCount);
param.put("totalCount", totalCount);
processEngine.getTaskService().complete(taskId,param);
All user submissions are disagreeing, The passCount parameter is always equal to 0 ;
1. If the conditions are not met, it should not be executed to the next node
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the multi-instance workflow using the supplied completionCondition and the TaskService.complete(taskId, param) call, with passCount=0 and totalCount=3. Trace how the condition is evaluated after completion and verify whether a false result still advances to the next node. Done means the workflow remains in the multi-instance activity when the condition is not met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100