Fix data update before to start a webentry

[caleeli]

Issue & Reproduction Steps

When a request is started using webentry when it is started with the new engine it is started in background. This could cause a collition because in the same controller action the data of the request is changed after the request was started.

Solution

• Update the request data (change the file uploaded ids) before to send the startEvent to the engine.

How to Test

Run the attached process as a webentry.

• Upload a file
• Submit the form
• See the interstitial get properly the next screen.

webentry.zip

Related Tickets & Packages

• Link to any related FOUR tickets, PRDs, or packages

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.

[processmaker-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

0.0% Coverage
0.0% Duplication