Data Connector uses incorrect Collection ID at runtime causing 500 error

[marcoAntonioNina]

Issue & Reproduction Steps

The host is not recognizable in the API call

Solution

• Enhance URL validation in MakeHttpRequests trait to ensure a host is present. If the URL lacks a host, prepend the base URL from configuration or fallback to the app URL.

How to Test

• Create a Collection
• Use the DC generated with the collection
• In a screen, use the DC; the call should work correctly and not give a 500 error.

Related Tickets & Packages

• FOUR-29133

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

[vladyrichter]

QA server K8S was successfully deployed https://ci-d4f1b2e798.engk8s.processmaker.net

[vladyrichter]

QA server K8S was successfully deployed https://ci-d4f1b2e798.engk8s.processmaker.net

[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