Issue

Ticket: FOUR-26628

After importing a Process that contains a task with a Rule Expression assignment, clicking the task in the Modeler displays an error message. In the reported case, opening the task triggered a request for a user ID from the source environment that did not exist in the target environment, resulting in a visible 404 error.

The imported pm:assignmentRules data preserved the source environment's numeric user and group IDs. Neither the current nor legacy import flow reconciled those IDs, so the task inspector attempted to load the stale assignees when the task was opened. If the numeric ID belonged to a different user or group in the target environment, the inspector could also display the wrong assignee.

Unresolved rules that still matched at runtime could also bypass a valid Default Assignment and escalate to the Process Manager. Template editing with saveModelOnly skipped reconciliation entirely, so stale IDs remained until a process was created from the template. Inactive-user labels written with a translated $t('Inactive') suffix (for example Spanish inactivo) failed to parse and were incorrectly marked unresolved.

This change affects imported Rule Expression assignments for users and groups. Regular user and group assignments continue to use the existing assignment import behavior.

Solution

processmaker

• Added AssignmentRulesReconciliation to reconcile pm:assignmentRules during import without trusting the exported numeric assignee ID.
• Rebinds user rules by parsing the username from the existing assignmentName value, including values with the - Inactive suffix.
• Rebinds group rules by assignmentName only when exactly one matching group exists.
• Clears the assignee and marks the rule as unresolved when a unique target user or group cannot be found.
• Applied assignment-rule reconciliation to the current import flow through ProcessExporter and to legacy process imports through ImportProcess.
• When an unresolved rule’s expression matches at runtime, throws TaskDoesNotHaveUsersException so execution does not fall through to the Process Manager; the same guard applies in Process, ProcessExecutionRawRepository, and ProcessRequestToken.
• Added modeler Auto Validate coverage for unresolved assignment rules (validateUnresolvedAssignmentRules.js).
• Updated SelectUserGroup so missing assignees do not produce a global 404 alert, do not leave the picker in a loading state, and are handled locally.
• Updated AssignExpression so unresolved assignees are not passed to the user/group picker and instead display “This assignee was not found in this environment. Select a user or group.” under Default Assignment and in the edit card.
• Added feature tests covering username-based rebinding, stale-ID collisions, unresolved users and groups, ambiguous group names, the current import flow, and the legacy import flow.

How To Test

Automated Tests

• php vendor/bin/phpunit --filter AssignmentRulesReconciliationTest tests/Feature/ImportExport/AssignmentRulesReconciliationTest.php
• php vendor/bin/phpunit --filter ImportProcessAssignmentRulesTest tests/Feature/Jobs/ImportProcessAssignmentRulesTest.php
• php vendor/bin/phpunit --filter 'testGetAssigneesFromExpressionThrowsWhen' tests/Model/ProcessRequestTokenTest.php

Manual Tests

1. Import a Process containing a Rule Expression task whose assignment rule references a user or group that exists in the target environment under a different numeric ID, then open the task in the Modeler.
2. Confirm that the task opens without an error and that the assignment rule is rebound to the matching target user or group.
3. Import a Process containing a Rule Expression task whose assignment rule references a user or group that does not exist in the target environment, then open the task in the Modeler.
4. Confirm that no 404 error is displayed, the Default Assignment picker remains usable, and “This assignee was not found in this environment. Select a user or group.” is displayed.
5. Select a valid user or group for the unresolved assignment and confirm that the assignment can be saved.
6. With an unresolved matching expression rule and a valid Default Assignment still configured, start a request and confirm the task does not assign to the Process Manager and instead fails with an incomplete-assignment error until the rule is resolved.
7. Open or import a template with saveModelOnly that contains Rule Expression assignees, confirm the template editor shows the rebound target user/group (not a colliding local ID), then create a process from that template and confirm assignees remain correct.
8. Import a Process whose inactive assignee was saved under a non-English UI (for example Name (username - inactivo)), confirm the user rebinds successfully when that username exists in the target environment.

ci:deploy

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.l
• This ticket conforms to the PRD associated with this part of ProcessMaker.