[COMMENTING-27] Add a configurable notification when a comment is created Created: 03/Jun/20  Updated: 20/May/21  Resolved: 20/May/21

Status: Closed
Project: Commenting
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.1.1

Type: Improvement Priority: Neutral
Reporter: Adrien Manzoni Assignee: Riste Drangovski
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Core

 Description   

Plug a webhook at then end of the commenting creation process.

https://git.magnolia-cms.com/projects/INCUBATOR/repos/webhooks/browse

 



 Comments   
Comment by Riste Drangovski [ 12/Apr/21 ]

@tmiyar
currently we have configurable magnolia commands that can be called when comment is added/updated/deleted.
for this commands to be triggered we need to set key: ebean.listeners.enabled=true in magnolia configuration.
When ebean.listeners.enabled=true  is set, magnolia will check in commenting-core module configuration, in "comment" catalog, if there are commands with names:
prePersist, postPersist, preUpdate, postUpdate, preRemove, postRemove. In case any of these commands exists it will be called with comment object passed command context.

Is this OK or should we implement some additional logic here ?

Comment by Teresa Miyar [ 16/Apr/21 ]

rdrangovski we will need to update the documentation with this information,

Comment by Riste Drangovski [ 11/May/21 ]

I don't have privileges to update wiki pages, so we added readme (markdown) file in the git repository describing triggers configuration, file is named "triggers.md" 

Generated at Mon Feb 12 00:01:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.