[MGNLWORKFLOW-135] after execution of workflow, pulse message should be removed Created: 02/Sep/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Boris Kraft Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

once a publication was successful, the message in pulse should be removed. Instead add a message that the page has been published. Thats what I expect from Pulse : stream of information of what has happened in the system.



 Comments   
Comment by Daniel Lipp [ 03/Sep/13 ]

AFAIK it was conciously decided that the pulse is kind of a mailbox - everything is collected, no automated removal. Changing this "strategy" has a lot of consequences that should be listed/discussed/analyzed first.

Comment by Boris Kraft [ 03/Sep/13 ]

good point. And the "message stream" idea supports that. But maybe we can change the status of a message to something like "done"

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:07:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.