Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new a custom event that allows webhooks/integrations to be triggered manually. This is useful when we want to to set up a webhook/integration that shouldn't be triggered automatically by the system when one of the default entity events present in this bundle takes places such as
CREATE
,UPDATE
,DELETE
.The following code shows how to make use of this functionality by creating a custom event that would trigger a webhook when an Oro payment transaction is completed.
1. Create a webhook custom event
services.yml
WebhookCustomEventPaymentTransactionComplete class
messages.en.yml
2. Once the above has been implemented, you should see your new custom event as a option in the event dropdown
3. Listen to payment transactions
4. Trigger webhook custom event