FOUR-27977: [48377] DevLink does not import Data Connector dependencies inside PM Blocks

[eiresendez]

Issue & Reproduction Steps

When using “Save as PM Block”, the Select List inside the cloned Screen loses its Data Connector selection: the dropdown shows no selected connector/endpoint.

Repro: create a process with a Screen containing a Select List bound to a Data Connector; click “Save as PM Block”; open the generated PM Block’s Screen in the Screen Builder—Data Connector and End Point are unselected.

Solution

• Allow PM Block Data Connectors (asset_type = PM_BLOCK) to be included in the nonSystem scope so they are returned by /api/data_sources and visible in the builder.
• Ensure the Select List import remaps selectedDataSource as an integer ID so the builder pre-selects the cloned Data Connector.
• Added targeted tests to prevent regressions for both the scope change and the Select List remap.

How to Test

1. Create a process with a Screen that has a Select List configured to a Data Connector and save it as a PM Block.
2. Open the PM Block’s Screen in the Screen Builder: the Data Connector should already be selected and the End Point set to GET.
3. API check: GET /api/1.0/data_sources should list both regular and PM Block Data Connectors.

Run package-data-sources tests.

ci:package-data-sources:bugfix/FOUR-27977
ci:deploy

Related Tickets & Packages

• FOUR-27977
• Package Data Source PR

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.

---

Note

Filters the Data Connector list based on the screen’s asset_type, resolving it from the current screen and passing it to /data_sources (PM_BLOCK maps to all).

• Inspector Select List (src/components/inspector/options-list.vue):
  • Add resolveAssetType() to determine asset_type from current screen (/screens/:id) using URL, with caching flags (assetTypeResolved, screenId).
  • Update getDataSourceList() to be async and send asset_type param to /data_sources (PM_BLOCK => all), then map results and endpoints as before.
  • Add new reactive fields: assetType, assetTypeResolved, screenId.

^{Written by Cursor Bugbot for commit 6b68bef. This will update automatically on new commits. Configure here.}

ci:k8s-branch:disable-verify-ci-ping

[cypress]

screen-builder    Run #2103

Run Properties:   Passed #2103  •  6b68bef938: FOUR-27977: [48377] DevLink does not import Data Connector dependencies inside P...

Project	screen-builder
Branch Review	bugfix/FOUR-27977
Run status	Passed #2103
Run duration	09m 45s
Commit	6b68bef938: FOUR-27977: [48377] DevLink does not import Data Connector dependencies inside P...
Committer	Eleazar Resendez
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	19
Skipped	0
Passing	389
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

[vladyrichter]

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