[MAGNOLIA-1949] Default workflow definition should allow sending emails upon activation Created: 10/Dec/07  Updated: 23/Jan/13  Resolved: 12/Dec/07

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 3.5 RC3
Fix Version/s: 3.5

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Vivian Steller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1947 MgnlUserManager does not take realm i... Closed
depends upon MAGNOLIA-1948 MgnlMailFactory can't read e-mail add... Closed
relation
is related to MAGNOLIA-1953 activation workflow can not send e-ma... Closed
supersession
is superseded by MAGNOLIA-1953 activation workflow can not send e-ma... Closed
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   

Indeed, the first instruction is assigning the item to the group-publishers, whereas users will tend to uncomment the part sending emails in the "to-publishers" subprocess. It seems delegating to the "to-publishers" subprocess immediately would not have any negative side-effects.



 Comments   
Comment by Vivian Steller [ 12/Dec/07 ]

was fixed with MAGNOLIA-1953

Generated at Mon Feb 12 03:31:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.