Adobe's integration starter kit uses Adobe Developer App Builder to improve real-time connection reliability and reduce the time-to-market for integrations between Adobe Commerce and other back-office systems, such as ERPs, CRMs, and PIMs.
Apache License 2.0
9
stars
2
forks
source link
INTERNAL - make `sales_order_save_commit_after` sample event compliant with validation schema #19
Make sales_order_save_commit_after sample event compliant with its JSON schema.
Currently, it yields a validation error caused by not matching the JSON validation defined in the runtime action code.
Related Issue
N/A
Motivation and Context
The sample event should be compliant with the JSON schema defined by the action that will process it, otherwise, if triggered from the Adobe Developer Console, it'll yield an HTTP/400 response related to invalid event format
How Has This Been Tested?
The fix has been tested in a fresh deployment of the starter kit.
Screenshots (if appropriate):
The new sample event as displayed on the Adobe Developer Console:
The new sample event is processed by the corresponding registration. The processing still yields an HTTP/400 error, but now it is not related to the event validation.
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Description
Make
sales_order_save_commit_aftersample event compliant with its JSON schema. Currently, it yields a validation error caused by not matching the JSON validation defined in the runtime action code.Related Issue
N/A
Motivation and Context
The sample event should be compliant with the JSON schema defined by the action that will process it, otherwise, if triggered from the Adobe Developer Console, it'll yield an HTTP/400 response related to invalid event format
How Has This Been Tested?
The fix has been tested in a fresh deployment of the starter kit.
Screenshots (if appropriate):
The new sample event as displayed on the Adobe Developer Console:
The new sample event is processed by the corresponding registration. The processing still yields an HTTP/400 error, but now it is not related to the event validation.
Types of changes
Checklist: