FOUR-28520 Reassign > The imported process does not list all reassign… #8664
Conversation
… user list ## Description When Assignment type=process variable and variable Name (groups) is set with a correct value then when reassign button is pressed, only the process manager is listed. ## Related tickets https://processmaker.atlassian.net/browse/FOUR-28520
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
… to extract user IDs from form data (assignedUsers/assignedGroups variables). Uses Process::getConsolidatedUsers() to get users from groups recursively. Validates array inputs and filters invalid IDs. Includes PHPUnit tests.
|
QA server K8S was successfully deployed https://ci-c42676abcc.engk8s.processmaker.net |
| } | ||
| if ($assignmentRule === 'process_variable' && $request->has('form_data')) { | ||
| $include_ids = $processRequestToken->getUsersFromProcessVariable($request->input('form_data')); | ||
| } |
There was a problem hiding this comment.
Rule expression filtering removed when config disabled
High Severity
The rule_expression assignment logic was moved inside the reassign_restrict_to_assignable_users config check block. Previously, when this config was false, the rule_expression check would still execute and filter assignable users accordingly. Now, when the config is false, neither rule_expression nor process_variable filtering occurs, causing users with rule_expression assignment rules to see all users instead of filtered results. This is a regression in existing functionality.
| const response = await getReassignUsersApi( | ||
| filter, | ||
| this.task?.id, | ||
| this.task?.request_data, |
There was a problem hiding this comment.
Mixin uses stale request_data instead of current formData
Medium Severity
The mixin's getReassignUsers method now uses this.task?.request_data instead of this.formData. In tasks/edit.js, the show() method directly calls this.getReassignUsers() from the mixin, and the component has its own formData property that holds the user's current form edits. The change means rule expression and process variable evaluation will use the task's original stored data rather than the user's current form modifications, potentially showing incorrect assignable users if the form data affects assignment rules.
|
QA server K8S was successfully deployed https://ci-c42676abcc.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://ci-c42676abcc.engk8s.processmaker.net |
|
… user list
Description
When Assignment type=process variable and variable Name (groups) is set with a correct value then when reassign button is pressed, only the process manager is listed.
Related tickets
https://processmaker.atlassian.net/browse/FOUR-28520
..>
Note
Improves reassignment user listing to honor process variables and complex rules.
UserController@getUsersTaskCount(POST) now evaluates assignment rules, includingrule_expressionand newprocess_variable, usingform_data; filters results to assignable users.ProcessRequestToken::getUsersFromProcessVariableto collect direct users and users from groups (including subgroups) and validate IDs.getReassignUsersinresources/js/tasks/api/index.jsto POSTusers_task_countwithform_data, and excludes the current assignee; updatesreassignMixinandTaskPreviewAssignmentto use it and passformData/currentTaskUserIdfromTasksPreview.getUsersFromProcessVariablecovering direct users, groups, combined, empty, non-array, and invalid IDs.Written by Cursor Bugbot for commit 745cc92. This will update automatically on new commits. Configure here.
ci:deploy