FOUR-26374: The name in the properties of a "Start event" does not work correctly.

[rodriquelca]

Issue & Reproduction Steps

Expected behavior:
As in previous versions, it should display the name of the selected start event.
Actual behavior:
The object name doesn't change; it remains Email start event

Solution

• remove keepOriginalName migrate validations

convert_issue.mov

How to Test

Test the steps above

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-26374

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.

[cypress]

modeler    Run #1666

Run Properties:   Passed #1666  •  41687a2ede: FOUR-26374: The name in the properties of a "Start event" does not work correctl...

Project	modeler
Branch Review	bugfix/FOUR-26374
Run status	Passed #1666
Run duration	05m 45s
Commit	41687a2ede: FOUR-26374: The name in the properties of a "Start event" does not work correctl...
Committer	Rodrigo Quelca
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	83
Skipped	0
Passing	280
View all changes introduced in this branch ↗︎

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube