Skip to content

Conversation

@pru46423
Copy link
Contributor

@pru46423 pru46423 commented Oct 9, 2025

Purpose of this pull request

This pull request (PR) is for introducing Journaling API with a simple commerce use case

Affected pages

New pages being added

Links to Magento Open Source code

Copy link
Collaborator

@rojoangel rojoangel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice one!

## Reading Through Adobe I/O Journals
Adobe I/O Journaling API acts as a queue that holds events temporarily. Each event has a position marker that serves as a cursor. The fetchEvent() function retrieves events from the journaling URL provided in the parameters.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spelling Consistency: both Journalling and Journaling are used interchangeably in this pull request. I will recommend reviewing these instances and stick to using only one of them.

## Register Commerce Events in Adobe Developer Console for Journaling

Define which Commerce events to subscribe to and register them within the Adobe Developer Console project. Return to the project workspace in the Developer Console, open the Add Service menu, and select Event. On the Add Events page, choose Commerce Events and select Next.
**Insert Image**
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't an image missing here?

Define which Commerce events to subscribe to and register them within the Adobe Developer Console project. Return to the project workspace in the Developer Console, open the Add Service menu, and select Event. On the Add Events page, choose Commerce Events and select Next.
**Insert Image**
In the Configure Event Registration step, select the event provider created earlier in Adobe Commerce. Select Next and review the events available from the provider. For journaling, do not choose any specific delivery method or Runtime Action. The Journaling API renders by default for the integration.
**Insert Image**
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be replaced with an actual image

@github-project-automation github-project-automation bot moved this from 📋 Needs Review to 👍 Approved in Commerce - Pull Requests Oct 23, 2025
@keharper
Copy link
Contributor

@pru46423 Your PR is almost ready to merge. I've made numerous edits, so you'll need to pull in my changes and address the following issues:

  • Add screenshots
  • @rojoangel pointed out that "journaling" vs "journalling" is used inconsistently. I've updated all instances to use one L, except within code samples. If the Journaling developers wrote code where journaling is spelled with 2 Ls, there's nothing we can do about that. If you can fix any of your custom code, please do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 👍 Approved

Development

Successfully merging this pull request may close these issues.

4 participants