[MGNLHOOK-21] (Event System) Events data definition (eventId, date, etc) Created: 12/Apr/22  Updated: 22/Jul/22  Resolved: 11/May/22

Status: Closed
Project: Magnolia Webhooks
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.0

Type: Story Priority: Neutral
Reporter: Javier Benito Assignee: Javier Benito
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLHOOK-20 (Event System) Support for default tr... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLHOOK-73 Detected data added to events (Publis... Technical task Completed Javier Benito  
MGNLHOOK-74 Testing data is added on events Technical task Completed Javier Benito  
MGNLHOOK-75 Submit PR Technical task Completed Javier Benito  
MGNLHOOK-76 piQA Technical task Completed Jaroslav Simak  
MGNLHOOK-77 Review Technical task Completed Milan Divilek  
MGNLHOOK-78 QA Technical task Completed Jaroslav Simak  
MGNLHOOK-79 Rebase master into the PR Technical task Completed Javier Benito  
Team: DeveloperX
Epic Link: Configure a Webhook event
Sprint: DevX 9, DevX 10
Story Points: 3

 Description   

SP: 3

 

We need to declare what data is going to be detected and published to the queue, when Published and Unpublished events are detected (Content and Content Types).

These typically could be some POJOs (ContentPublished, ContentUnpublished, ContentTypePublished, ContentTypeUnpublished, etc), for example, with the following data (only a proposal):

  • eventId (automatically generated, maybe by the Event System?)
  • eventDate
  • name (page, content type that changed)
  • nodeType
  • path
  • workspace

 

These POJOs should be in the webhooks part of the module, not in the events side. Events part should provide an interface with the main data an event should have, for the webhooks part to implement it.


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