Apply BehaviorPromoCode to CustomerBehaviors in rapid identification#42
Merged
Conversation
Per Omeda's API docs, PromoCode on the Customer Behavior element has been deprecated in favor of BehaviorPromoCode. The resolver now sets BehaviorPromoCode on each behavior, using a per-behavior override if provided (new optional behaviorPromoCode field on the behavior input), falling back to the top-level promoCode value. The top-level PromoCode field is preserved for backwards compatibility. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
zarathustra323
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PromoCodeon theCustomer Behavior Elementhas been deprecated in favor ofBehaviorPromoCodeBehaviorPromoCodeon each behavior in theCustomerBehaviorsarray, using the top-levelpromoCodeas the value (with optional per-behavior override via a newbehaviorPromoCodefield on the behavior input)behaviorPromoCode: StringtoRapidCustomerIdentificationBehaviorInput— callers can pass a behavior-specific promo code; if absent, falls back to the top-levelpromoCodePromoCodefield is preserved for backwards compatibilityTest plan
omedaPromoCodePrefixconfigured and confirm the promo code appears on the resulting customer behavior in the Omeda portalbehaviorPromoCodeon input) still correctly falls back to top-levelpromoCode🤖 Generated with Claude Code