FOUR-25827: Fix launchpad import to refresh screen references after process import #8697
+7
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.





Issue & Reproduction Steps
When importing a process with launchpad settings, the stored screen_id in process_launchpad.properties can point to a non‑existent screen in the new environment, causing a 404 on GET /api/1.0/screens/:id when opening /process-browser/{processId}.
Solution
How to Test
Related Tickets & Packages
ci:deploy
Code Review Checklist
Note
Ensures launchpad screen references are valid after import.
ProcessLaunchpadExporter::import(), now setsscreen_uuid,screen_id, andscreen_titlefrom the importedscreendependentProcessLaunchpadExporterTestto assert launchpad properties point to the new process cancel screen and that saved search IDs are remappedWritten by Cursor Bugbot for commit eb782c5. This will update automatically on new commits. Configure here.