Skip to content

FOUR-25224: [STORY] Notifications should be driven by standard email notification configuration #1930

Merged
pmPaulis merged 2 commits into
epic/FOUR-25223from
story/FOUR-25224
Jul 24, 2025
Merged

FOUR-25224: [STORY] Notifications should be driven by standard email notification configuration #1930
pmPaulis merged 2 commits into
epic/FOUR-25223from
story/FOUR-25224

Conversation

@pmPaulis

Copy link
Copy Markdown
Contributor

Issue & Reproduction Steps

Notifications should be driven by standard email notification configuration

As a user or administrator,
I want notifications to be driven by the standard Email Notification configuration in the Modeler, so that I can ensure consistent delivery settings.

Solution

  • What needs to be built? The system needs to ensure that email notifications for processes and tasks within the Modeler are configured and driven by a standard, default email notification setting. Users should also have the ability to override or update this default configuration.

How to Test

  • Create new FORM TASK
  • Set to FORM TASK

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.

henryjonathanquispe and others added 2 commits July 11, 2025 14:37
FOUR-25228: Create default email notification config when task is created in Modeler
@cypress

cypress Bot commented Jul 21, 2025

Copy link
Copy Markdown

modeler    Run #1645

Run Properties:  status check passed Passed #1645  •  git commit e25daf87eb: FOUR-25224: [STORY] Notifications should be driven by standard email notificatio...
Project modeler
Branch Review story/FOUR-25224
Run status status check passed Passed #1645
Run duration 05m 26s
Commit git commit e25daf87eb: FOUR-25224: [STORY] Notifications should be driven by standard email notificatio...
Committer Paulis
View all properties for this run ↗︎

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

@pmPaulis pmPaulis changed the base branch from develop to epic/FOUR-25223 July 21, 2025 19:35
@processmaker-sonarqube

Copy link
Copy Markdown

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

@pmPaulis pmPaulis merged commit 7845624 into epic/FOUR-25223 Jul 24, 2025
42 checks passed
@pmPaulis pmPaulis deleted the story/FOUR-25224 branch July 24, 2025 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants