-
Notifications
You must be signed in to change notification settings - Fork 242
FOUR-28520 Reassign > The imported process does not list all reassign… #8664
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.
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
base: develop
Are you sure you want to change the base?
Changes from all commits
4568f9a
854e16c
509b855
06cf51e
7ec8046
f686269
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,5 @@ | ||
| import { getReassignUsers as getReassignUsersApi } from "../tasks/api"; | ||
|
|
||
| export default { | ||
| data() { | ||
| return { | ||
|
|
@@ -21,32 +23,28 @@ export default { | |
| this.allowReassignment = response.data[this.task.id]; | ||
| }); | ||
| }, | ||
| getReassignUsers(filter = null) { | ||
| const params = { }; | ||
| if (filter) { | ||
| params.filter = filter; | ||
| } | ||
| if (this.task?.id) { | ||
| params.assignable_for_task_id = this.task.id; | ||
| // The variables are needed to calculate the rule expression. | ||
| if (this?.formData) { | ||
| params.form_data = this.formData; | ||
| delete params.form_data._user; | ||
| delete params.form_data._request; | ||
| delete params.form_data._process; | ||
| } | ||
| } | ||
| async getReassignUsers(filter = null) { | ||
| try { | ||
| const response = await getReassignUsersApi( | ||
| filter, | ||
| this.task?.id, | ||
| this.task?.request_data, | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Mixin uses stale request_data instead of current formDataMedium Severity The mixin's |
||
| this.currentTaskUserId | ||
| ); | ||
|
|
||
| ProcessMaker.apiClient.post('users_task_count', params ).then(response => { | ||
| this.reassignUsers = []; | ||
| response.data.data.forEach((user) => { | ||
| this.reassignUsers.push({ | ||
| text: user.fullname, | ||
| value: user.id, | ||
| active_tasks_count: user.active_tasks_count | ||
| if (response?.data) { | ||
| response.data.forEach((user) => { | ||
| this.reassignUsers.push({ | ||
| text: user.fullname, | ||
| value: user.id, | ||
| active_tasks_count: user.active_tasks_count | ||
| }); | ||
| }); | ||
| }); | ||
| }); | ||
| } | ||
| } catch (error) { | ||
| console.error('Error loading reassign users:', error); | ||
| } | ||
| }, | ||
| onReassignInput: _.debounce(function (filter) { | ||
| this.getReassignUsers(filter); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rule expression filtering removed when config disabled
High Severity
The
rule_expressionassignment logic was moved inside thereassign_restrict_to_assignable_usersconfig check block. Previously, when this config wasfalse, therule_expressioncheck would still execute and filter assignable users accordingly. Now, when the config isfalse, neitherrule_expressionnorprocess_variablefiltering occurs, causing users withrule_expressionassignment rules to see all users instead of filtered results. This is a regression in existing functionality.