[MGNLWORKFLOW-302] Provide Configurable E-Mail based workflow out of the box: Provide solid replacement for openWFE e-mail sending workflow. Created: 28/May/15  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Workflow Module
Component/s: jBPM
Affects Version/s: 5.2.2, 5.3.5, 5.4.5
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Won't Do Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLWORKFLOW-321 Email support for the OOTB workflow Closed
relation
is related to MGNLWORKFLOW-320 Allow simple workflow changes be done... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

IN 4.5 we had a OpenWFE workflow, where the customers were able to have Emials send by the single steps very simply. All they had to do was uncomment a part in the workflow definition.

I'm aware that JBPM workflow is much more powerful, but also less flexible as it needs to be compiled and so on.

But the simple use case "sending an EMail" is so widely common, that it can't be that every client needs to create their own workflow implementation just to sent a email.
It just sending an email, and almost everybody would like to have/use this.

I am aware of this:
https://academy.magnolia-cms.com/display/MA/M3+Custom+workflows+in+5.3+plus
But its not really helping. T mail addresses to use are simply coded in the Java code, not a real help for a real use case in a project.
Usually the ones triggering a workflow and the once getting it assign should receive a email, and not a hardcoded mail in the code.

Its a big time loss for customers to implement it by them selves, for such a simple use case that was possible within minutes in the past.

Suggestion:
Please investigate if there can't be provided a simple solution, where you can configure where to send mails to. So that a workflow step can use this config in a generic way, just to send a email within a workflow step.
Just the simple use case:
The triggering person of a workflow can get a mail.
The group and|or person that gets the workflow's human task assigned to gets a e-mail



 Comments   
Comment by Erich Ruf [ 28/May/15 ]

Our customer has exactly this simple requirement:

  • Sending an E-Mail to publishers in case of a new publication task
  • Sending an E-Mail to editor when the publication task was approved or rejected.

A simple standard solution for this problem is very welcome!

Comment by Espen Jervidalo [ 09/Jun/15 ]

There is a very easy way to implement this. Register an event-listener to the system EventBus like this:

@Inject
public MyClass(final @Named(SystemEventBus.NAME) EventBus eventBus) {
  eventBus.addHandler(new TaskEventHandler() {
    ....
  }) 
}
Comment by Richard Gange [ 17/Feb/16 ]

That's not easy for most users. I would agree with christian it need to be able to be configured.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 10:08:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.