Skip to content

Commit

Permalink
CEXT-3214: Fixing missing header and typos
Browse files Browse the repository at this point in the history
  • Loading branch information
ryanjcohen committed Jun 17, 2024
1 parent d91334d commit 864bd38
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -87,4 +87,4 @@ You can retrieve the `consumerKey`, `consumerSecret`, `accessToken`, and `access

You can now add the order's extension attributes retrieved from Commerce to the order event payload, and send the payload to a third-party Enterprise Resource Planning (ERP) system using a custom module.

After creating a runtime action using this code, you can create an event registration can to subscribe to the `observer.sales_order_save_after` event, and configure the new runtime action to receive the event notifications.
After creating a runtime action using this code, you can create an event registration to subscribe to the `observer.sales_order_save_after` event and configure the new runtime action to receive the event notifications.
4 changes: 3 additions & 1 deletion src/pages/events/consume-events.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ keywords:
- Extensibility
---

# Consume Events

You can consume events sent from Adobe Commerce to Adobe I/O events in several ways. The following options for consuming events are available when adding events to your App Builder project and creating an event registration:

* [Using the Journaling API](#using-the-journaling-api) (enabled by default)
Expand All @@ -15,7 +17,7 @@ You can consume events sent from Adobe Commerce to Adobe I/O events in several w

## Using the Journaling API

When you create an Adobe I/O event registration, the subscribed events added to an ordered list, referred to as the journal, by default. You can consume these events using a journaling endpoint URL that is unique to the registration. For more information on reading events from the journal, see the [Introduction to Journaling](https://developer.adobe.com/events/docs/guides/journaling_intro/).
When you create an Adobe I/O event registration, the subscribed events get added to an ordered list, referred to as the journal, by default. You can consume these events using a journaling endpoint URL that is unique to the registration. For more information on reading events from the journal, see the [Introduction to Journaling](https://developer.adobe.com/events/docs/guides/journaling_intro/).

You can also consume events from the Journaling API using the [Adobe I/O Events SDK](https://github.com/adobe/aio-lib-events). See [Subscribe to Events Using Journaling](https://developer.adobe.com/events/docs/guides/sdk/sdk_journaling/) for details and sample code.

Expand Down

0 comments on commit 864bd38

Please sign in to comment.