FOUR-15510: [Summer24] Actions By Email V2

[pmPaulis]

Issue & Reproduction Steps

Increased user engagement: Users are more likely to stay engaged with the system when they receive timely notifications about relevant activities.
Improved responsiveness: Users can promptly respond to important updates or tasks, enhancing overall efficiency.
Enhanced user experience: Providing email notifications seeking to respond to tasks directly from the email to avoid the user having to access ProcessMaker.

Prd

https://processmaker.atlassian.net/wiki/spaces/PM4/pages/3341647873/Actions+by+Email+V2

Figma

https://www.figma.com/design/RiBfT37iExrySseqYZuLg3/Summer-2024?node-id=103-17&t=EZjsN3lxFW9jiFGb-0

Solution

• New control was created in the Email Screen

How to Test

• Create a new Email Screen
• We can use a new control Submit button

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-15510

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.

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube