Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix/FOUR-12661: [34966 - 35021] Process Not Sending Email Notifications #5729

Merged
merged 2 commits into from Nov 30, 2023

Conversation

agustinbusso
Copy link
Contributor

@agustinbusso agustinbusso commented Nov 30, 2023

Issue & Reproduction Steps

IMPORTANT: be sure you are using Nayra micro service

  • Create a process with the following controls:
  • An Star event, 2 tasks, and a End event.
  • Create a screen with your desired controls and assign them to both tasks.
  • In the second task, configure the Email Notifications, and in the Recipient Type, choose Email Address and enter the desired email. Also, ensure that your server has its Email Default Settings configured.
  • Assign a user to the start event.
  • Run a request and route it to the second task.

Current Behavior:
As you can see, you will not receive a notification email that was configured in the second task. For more details, please watch the video in the ticket https://processmaker.atlassian.net/browse/FOUR-12661.

Expected Behavior:
The sending of email notifications should work seamlessly when using it.

Solution

  • Emit event activity activated to trigger email notification.

Working video

Screen.Recording.2023-11-30.at.15.16.25.mov

How to Test

  • Follow 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.

Copy link

@caleeli
Copy link
Contributor

caleeli commented Nov 30, 2023

Tested with events:

  • Activity Activated: Notify email Task Assigned
  • Activity Completed: Notify email Task Completed
  • Gateway Event: Log in comments
  • Activity Exception: Log error

@ryancooley ryancooley merged commit 3744805 into develop Nov 30, 2023
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants