[MGNLUI-2618] Work item messages are not extendible in Pulse Created: 23/Jan/14 Updated: 06/May/14 Resolved: 03/Mar/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | pulse |
| Affects Version/s: | 5.2.1 |
| Fix Version/s: | 5.2.3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Frank Sommer | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support, workflow | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| 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)
|
||||
| Release notes required: |
Yes
|
||||
| Date of First Response: | |||||
| Visible to: |
Rainer Blumenthal
|
||||
| Description |
|
I want to show some additional information (e.g. version) in work item messages in Pulse. But I find no configurable way to extend the message. |
| Comments |
| Comment by Espen Jervidalo [ 27/Jan/14 ] |
|
info.magnolia.ui.admincentral.shellapp.pulse.message.MessagePresenter#start |
| Comment by Rainer Blumenthal [ 20/Feb/14 ] |
|
Is it planned for 5.2.3? ... the referenced issue says so |
| Comment by Espen Jervidalo [ 24/Feb/14 ] |
|
Yes, this should be shipped with 5.2.3. |
| Comment by Andreas Weder [ 28/Feb/14 ] |
|
Rainer, work on this improvement has started. It might not make it into the 5.2.3 bundle release (planned for end of next week), however, which would mean we would deliver it in a separate release of the workflow module shortly after that. |
| Comment by Federico Grilli [ 03/Mar/14 ] |
|
Custom message properties, whether they come from extending the Message class or from adding properties to the Message object itself via addProperty(name, value) are now available for rendering in the Pulse message detail view. Only thing to do is to add the fields named after the new properties in the message view form configuration. See attached example: foo and bar have been added to the publish message view. If the message coming to the pulse contains such properties or has public getFoo() and getBar() methods, those will be rendered in the message detail view. |