[MGNLHOOK-19] Configure events definition based on Content Types Created: 12/Apr/22  Updated: 22/Jul/22  Resolved: 06/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: Fixed 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
depends upon MGNLHOOK-18 Extend registry for webhook definitio... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLHOOK-51 Get available content types on Webhoo... Technical task Completed Javier Benito  
MGNLHOOK-52 Handlers for Content type events (cre... Technical task Completed Javier Benito  
MGNLHOOK-53 Testing on Magnolia instance Technical task Completed Javier Benito  
MGNLHOOK-54 piQA Technical task Completed Milan Divilek  
MGNLHOOK-55 Code review Technical task Completed Jaroslav Simak  
MGNLHOOK-56 PR submitted Technical task Completed Javier Benito  
Team: DeveloperX
Epic Link: Configure a Webhook event
Sprint: DevX 9
Story Points: 3

 Description   

SP: 3

 

This task depends upon MGNLHOOK-18.

In this step, we need to add to the existing webhook definitions registry, support for entities = Content Types.

For example, we should be able to load webhook definitions like this (note that the entity is tour, which is declared as a Content Type):

events:
  - name: p2
    eventType: unpublish
    entity: tour #You can use an existing contentType

Validation should be taken into account, to ensure that an event must not provide a not existing Content Type. Error should be reported on the Definitions App.


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