FOUR-21667 | "Edit Template” Link for Screen Templates Does Not Redirect to Edit Page in Screen Builder by mcraeteisha · Pull Request #7959 · ProcessMaker/processmaker

Issue

Ticket: FOUR-21667

When right-clicking on the "Edit Template" link within the Ellipsis Menu for Screen Templates (located on both "My Templates" and "Shared Templates" listing pages), the link incorrectly redirects to the Screens listing page instead of the Screen Builder. This prevents users from editing templates in a new browser tab.

Solution

  • Add screen-template/{id}/edit web route that opens a Screen Template in Screen Builder
  • Add href link to the new route in ellipsisMenuActions.js
  • Remove goToScreenBuilder() method used in navigationMixin.js

How to Test

  1. Go to branch bugfix/FOUR-21667 in processmaker.
  2. Ensure you have Screen Templates in your environment.
  3. Go to Designer → Screens → My Templates.
    • Open the Ellipsis Menu and right-clik on Edit Template to 'Open link in new tab'.
    • Go to the new tab.
    • The new tab should be the Screen Builder page for the selected Screen Template.
  4. Go to Designer → Screens → Shared Templates.
    • Open the Ellipsis Menu and right-clik on Edit Template to 'Open link in new tab'.
    • Go to the new tab.
    • The new tab should be the Screen Builder page for the selected Screen Template.

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