FOUR-21670: Screen is empty if the request was started by start signals

[danloa]

Issue & Reproduction Steps

Steps to Reproduce

• Create a process with start signal
• Configure the start signal with create record in collection
• Go to Collection
• Create a new record
• Go to Cases
• Open the process started by signal
• Open the task

Current Behavior
The screen of the task is empty if the process was start by start signal event

Solution

• Signal start events were started so that the request user_id column was set to null. Now, if no authenticated user exists in the context, the Anonymous user is used.

Related Tickets & Packages

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

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]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube