FOUR-13969: Allow user to decide what to do with the Screen Interstitial when importing assets

[estebangallego]

Issue & Reproduction Steps

When following the guided template process, it has been noticed that the interstitial screen does show within the TemplateAssets check and it's been duplicated multiple times.

Interstitial screens should be part of the initial existing assets check, so the user can decide if they’ll be updated, replaced, or if a new version should be created

Solution

• Allow Screen Interstitial to display within the TemplateAssets table.

How to Test

• Navigate to Processes
• Navigate to Guided Templates
• Select the Guided Invoice Approval
• Follow all the steps
  Please ensure that the user has the option of what to do with the Interstitial Screen.
  Please make sure that each selection works as expected. (Update | Keep Previous | Duplicate)

Related Tickets & Packages

• Ticket: FOUR-13969
  ci:next

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.

[eiresendez]

Awesome 👍

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube