-
Couldn't load subscription status.
- Fork 29
[DO NOT MERGE] CEXT-5400: Add origData to the event payload #459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| </config> | ||
| ``` | ||
|
|
||
| ## Trigger events on specific field changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we also add an example when the events need to be triggered once qty or price is being changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem here is that we don't have OR rules, all rules are processed as AND.
By adding the next rules:
<rule>
<field>quantity_and_stock_status.qty</field>
<operator>onChange</operator>
<value />
</rule>
<rule>
<field>price</field>
<operator>onChange</operator>
<value />
</rule>
The event will be triggered only if both price and quantity are changed.
Currently, it's possible to resolve by creating a separate subscription with an Alias name, one for price change and one for quantity change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should we state somewhere that OR rules aren't supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have the next definition at the beginning of that page.
If one or more rules evaluate as false, the service sends neither the parent event nor the conditional event, unless the parent has been subscribed separately, without any rules.
Should we mention it one more time?
| </config> | ||
| ``` | ||
|
|
||
| ## Trigger events on specific field changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should we state somewhere that OR rules aren't supported.
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
Co-authored-by: Kevin Harper <[email protected]>
- commented out ACCS example
- added release notes
- added information about 64 KB limit
Purpose of this pull request
This pull request (PR) adds information about new functionality, such as original data in the event payload and a new onChange operator based on original data.
Affected pages
Links to Magento Open Source code