[MGNLWORKFLOW-192] Sending email notifications from workflow missing Created: 17/Jan/14  Updated: 18/Mar/14  Resolved: 17/Mar/14

Status: Closed
Project: Magnolia Workflow Module
Component/s: Base
Affects Version/s: 5.0, 5.2.1
Fix Version/s: 5.3

Type: Improvement Priority: Neutral
Reporter: Rainer Blumenthal Assignee: Espen Jervidalo
Resolution: Not an issue Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLWORKFLOW-191 Workflow launch command doesn't suppo... Closed
relation
is related to MGNLWORKFLOW-401 Pulse should be capable of notifying ... 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:
Visible to:
Rainer Blumenthal

 Description   

In Magnolia 4.x it is possible to configure if emails will be sent to the editors.

In Magnolia 5 this has to be implemented manually. I'd say that 80 % of editors want to get notifications in their email inbox, not only in Pulse.



 Comments   
Comment by Richard Unger [ 17/Jan/14 ]

Hi,

As an idea, might it be possible to implement this in Pulse rather than in the Workflow module?
Perhaps by adding a feature to Pulse that messages can be forwarded by email as well as appearing in the UI?

Regards from Vienna,

Richard

Comment by Jan Haderka [ 20/Jan/14 ]

@Richard I like this proposal.

@Rainer Even in Magnolia 4 it was not "out of the box" you had to modify workflow and enable it. The only difference was that in the xml workflow definition there was commented out section that you could uncomment, while in M5 there is no commented out xml since you are using the eclipse plugin to build workflows visually.

Comment by Rainer Blumenthal [ 20/Jan/14 ]

@Jan: You are completely right. I am fully aware of that, what I want to say is:

In the past this could be solved by configuration (nearly no costs for the customer) - now it has to be solved programmatically: plan, implement, QA, delivery. So I consider this as a step back, that's why we decided to create this ticket for a missing feature.

Hint from my colleague: You still have a workflow notification email in your mail module.

Comment by Espen Jervidalo [ 17/Mar/14 ]

Extending the publication process to send emails is explained as a step-by-step tutorial in http://documentation.magnolia-cms.com/display/DOCS/Creating+a+custom+workflow+process

Comment by Richard Unger [ 17/Mar/14 ]

Hi - I see you have closed this issue.

However, your resolution ignores the inputs from Rainer and myself:

  • we are aware the email notification can be added programmatically by editing the workflow

1) Rainer's point was that most customers using workflow will want this feature, and having to program it into the workflow each time isn't very user friendly. Why not put it in the workflow from the outset, and make it configurable by JCR property.

2) My point was: what about the other pulse messages? Why not add this feature to pulse, on a per-user basis? In this way each user could configure whether they receive their pulse messages also by email...

I don't feel this ticket should be closed yet.

Comment by Rainer Blumenthal [ 17/Mar/14 ]

I am completely with Richard ... each Magnolia project we offer to a customer would be 1-2 days more expensive, just because we would have to:

  • plan, implement, QA, deliver

the workflow mail sending.

Comment by Richard Unger [ 18/Mar/14 ]

I can only comment on this issue, but as the reporter you might be able to reopen it, Rainer...

Comment by Rainer Blumenthal [ 18/Mar/14 ]

No, i can just clone it.

Comment by Espen Jervidalo [ 18/Mar/14 ]

Hi,
I opened a discussion on this issue internally and this should ideally be added as pulse feature in a later release. I will create an issue for it and link it.

If you want a quickfix for this without having to touch the jBPM processes, you can extend the NotificationWorkItemHandlers to send emails after the pulse was notified.

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