Issue & Reproduction Steps

This PR refines the data-loading pattern for screens to prevent unnecessary reloads when accessing non-listing endpoints. This update ensures the loading state only triggers for the main screens listing endpoint.

Solution

• Updated the :for data-loading pattern from '/screens/' to'/\/screens\?page/'.
• Prevents reloading when interacting with non-listing screen-related endpoints.
• Aligns with pagination query parameter patterns used in other components.
• Fixes unwanted refreshes when accessing screen-related endpoints.

How to Test

1. Navigate to Designer > Screens.
2. Open the VarFinder Panel (Shift + Space).
3. Go to the "Search" tab.
4. Ensure the selected asset type is "Screen".
5. Type anything in the search box.
6. Verify that the screen listing behind the VarFinder Panel does not reload.

Related Tickets & Packages

FOUR-21890

ci:package-variable-finder:release-2025-spring
.

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.
• This ticket conforms to the PRD associated with this part of ProcessMaker.