FOUR-33788 Custom started date in Cases Dashboard

[henryjonathanquispe]

Related Tickets & Packages

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

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:deploy

[cursor]

PR Summary

Low Risk
Single-line boot change; user now consistently comes from setupMain meta-based config instead of a second Blade copy.

Overview
Stops the Cases Main Vite loader from replacing window.ProcessMaker.user with window.temporal.user after setupMain() runs.

setupMain() already initializes the user from page meta tags and applies PHP→Moment datetime/calendar formats via config/user. Re-assigning the raw Blade JSON user was undoing that conversion, which broke custom started-date (and related) formatting on the Cases dashboard. The loader still copies window.temporal.packages onto ProcessMaker; only the user overwrite is removed.

^{Reviewed by Cursor Bugbot for commit c6d6ec9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[decisions-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

[vladyrichter]

QA server K8S was successfully deployed https://tenant-1.ci-bd382c704d.engk8s.processmaker.net