Bugfix/FOUR-16548: Drafts being lost after renaming the screen

[agustinbusso]

Issue & Reproduction Steps

• Create a new screen.
• Add some elements to the screen
• You can refresh your screen to validate that your changes are still there.
• Go to the screen configuration and change the name of the screen.

Current Behavior:
All the changes will be lost

Expected Behavior:
The draft with the recent changes should still be there after renaming.

Notes for QA:
The information lost only occurs on unpublished versions. However, these changes exist in the version history as drafts before renaming the screen.

Solution

• When saving in configuration, now we get the last version of the screen and we update the BPMN.
• The button in configuration changed from Save to Save and publish
• If a draft exist for the screen, when clicking in Save and publish, we show a confirmation modal to let the user decide if must continue.

How to Test

• Create a screen.
• Go to screen builder and do some changes (add elements), wait the autosave
• Go to the screen configuration and change the screen name and save

Ensure the confirmation modal shows in the configuration when saving if the screen is draft

Related Tickets & Packages

• FOUR-16548

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.

ci:next

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

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

See analysis details on SonarQube