Thank you! Great question!

I chose to use a JSON-based system property over checklist templates mainly for flexibility and control. My use case required both the automation of checklists for specific catalog tasks and the ability to designate certain checklist items as mandatory. Checklist templates have limitations here:

1. Mandatory Field Control: Checklist templates don’t provide a way to set specific items as mandatory, which was essential to ensure that certain tasks couldn’t close without meeting critical requirements.

2. Maintainability: With a JSON structure in a system property (or perhaps a custum table), it’s easier to update or customize checklist configurations centrally without needing to adjust templates. For large-scale environments with many checklists, this approach also allows for a more scalable and governance-friendly setup, making it easier to manage checklist data and updates across environments.

I hope this helps clarify!

Agreed. In case of having the event dynamically distributed to multiple event queues your way is the best. Just in case one custom event queue would be enough it is easier to use the field “queue” on the registry and skip the fifth parameter in the code. This makes maintenance more efficient and might be easier to use. I just wanted to make sure this was mentioned in the otherwise very informative article.

Hi Christoph! Thanks for reading through the article and commenting. You are right, there is a Queue field that could be used, but if you take a look the code that is generating the events, you’ll notice that it is distributing the same event to N different queues. Using the Queue field instead of the code-driven distribution would mean that we would need N amount events, that will be tied to N different queues.

When the event is triggered “gs.eventQueue(‘event.name’,…” you don’t need to specify the fifth parameter as these events will always go into the queue specified on the “Event Registration”.

Maybe an information that might be added in the article.

Thanks! We are working to bring the best content to our audience.

Thanks Rodrigo!!