Skip to content

Dispatch consequence in an rules consequence event if schema type is not eventHistory#1148

Merged
timkimadobe merged 2 commits intoadobe:feature/historical-consequencefrom
timkimadobe:event-history-fix-consequence
Jun 12, 2025
Merged

Dispatch consequence in an rules consequence event if schema type is not eventHistory#1148
timkimadobe merged 2 commits intoadobe:feature/historical-consequencefrom
timkimadobe:event-history-fix-consequence

Conversation

@timkimadobe
Copy link
Copy Markdown
Contributor

Description

Restore existing behavior of dispatching consequence in a rules response content event for schema type if the detail is not of type https://ns.adobe.com/personalization/eventHistoryOperation

Related Issue

Motivation and Context

For non event history write cases, we still need to dispatch the consequence so Messaging SDK can use it to display in-app message or content card

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • 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)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@timkimadobe timkimadobe force-pushed the event-history-fix-consequence branch from a103cbc to 0956acf Compare June 11, 2025 21:28
@timkimadobe timkimadobe merged commit 0432b5f into adobe:feature/historical-consequence Jun 12, 2025
17 checks passed
@timkimadobe timkimadobe deleted the event-history-fix-consequence branch June 12, 2025 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants