Skip to content

FOUR-26848: Improve Message Catch and Throw Events Elements to configure the payload - Modeler - #1948

Closed
rodriquelca wants to merge 12 commits into
developfrom
feature/FOUR-26848
Closed

FOUR-26848: Improve Message Catch and Throw Events Elements to configure the payload - Modeler#1948
rodriquelca wants to merge 12 commits into
developfrom
feature/FOUR-26848

Conversation

@rodriquelca

Copy link
Copy Markdown
Contributor

Issue & Reproduction Steps

Expected behavior:

Actual behavior:

Solution

How to Test

Test the steps above

Related Tickets & 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.

@cypress

cypress Bot commented Oct 2, 2025

Copy link
Copy Markdown

modeler    Run #1698

Run Properties:  status check failed Failed #1698  •  git commit e2d2109e7d: FOUR-26848: Improve Message Catch and Throw Events Elements to configure the pay...
Project modeler
Branch Review feature/FOUR-26848
Run status status check failed Failed #1698
Run duration 02m 00s
Commit git commit e2d2109e7d: FOUR-26848: Improve Message Catch and Throw Events Elements to configure the pay...
Committer Rodrigo Quelca
View all properties for this run ↗︎

Test results
Tests that failed  Failures 6
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 71
Tests that passed  Passing 0
View all changes introduced in this branch ↗︎

Tests for review

Failed  IntermediateMessageThrowEvent.cy.js • 1 failed test

View Output

Test Artifacts
Intermediate Message Throw Event > can render an intermediate message throw event Test Replay Screenshots
Failed  Modeler.cy.js • 1 failed test

View Output

Test Artifacts
Modeler > Create a simple process Test Replay Screenshots
Failed  Pools.cy.js • 1 failed test

View Output

Test Artifacts
Pools > Update pool name Test Replay Screenshots
Failed  MessageFlows.cy.js • 1 failed test

View Output

Test Artifacts
Message Flows > Can connect two pools with a message flow Test Replay Screenshots
Failed  DataObjectDataStore.cy.js • 1 failed test

View Output

Test Artifacts
Data Objects and Data Stores > does not support connecting sequence flows for processmaker-modeler-data-object Test Replay Screenshots

The first 5 failed specs are shown, see all 94 specs in Cypress Cloud.

cursor[bot]

This comment was marked as outdated.

@processmaker-sonarqube

Copy link
Copy Markdown

Quality Gate passed 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

const validId = id.match(/^[_A-Za-z][-._A-Za-z0-9]*$/);
if (!validId) {
return this.$t('Data input ID is not a valid xsd:ID');
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Inconsistent Regex Validation Causes ID Conflicts

The DataInputAssociation component uses two different regex patterns for data input ID validation. One pattern allows only letters, numbers, and underscores, while the other also permits hyphens and dots. This inconsistency can lead to situations where a data input ID is saved but then incorrectly flagged as invalid in the display list.

Fix in Cursor Fix in Web

@rodriquelca rodriquelca closed this Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant