Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Technical Problem

intl-packages:

1 - Option (used in this refinement)

  • We should create a new secret (crm-events) to save settings.

  • Update CRM Event (mparticle) to use secrets and send message to another markets.

2- Option

...

POC: https://github.com/rbilabs/intl-packages/pull/938/

...

  • New User

    • We must add two new fields to be sent to the particle trigger.

      • email_subscribe

      • push_subscribe

  • Update User to call logCrmEvents

  • The user update routine is done via HTTP request, here we must integrate it with CRM Events, currently, it only updates in DynamoDB

  1. Option 2

POC: https://github.com/rbilabs/intl-user-service/pull/294/files#diff-16c30acb1319788d9f98e57369f216f74b1ef5017c6c7b73c5c9ff675e12d7e1

API - User Update - To test

...

  • Should create a new definition secret to crm-events

  • Should We must check to work to PLK and BK brands and countries all markets and not only ES and PT.

...

Task 4 - Change mparticle-service.ts to replicate message to mparticle

...

More information

  • In the SignUp to accept the marketing to EMAIL and PUSH you need to enable this flag in Launchdarkly - Platform:

Code Block
enable-push-notifications-on-signup
  • It is fundamental that on DynamoDB with the table rbi-account-secrets with the item rbi/dev/YOUR_BRAND/crm-events (rbi/dev/plk/crm-events) there are the valeus for this, is required there are at least one URL and the ACTIVE field must be true

  • In case of problems in register user, in the moment of validate OTP code, you can to see the logs of on CloudWatch AWS, the lambdas that you need to analyze are dev-plk-user-new-user and dev-plk-user-api, you need just to change the brand.

  • We have a feature flag to control this feature, enable-cross-brand, for work we need to enable this flag, and we can customize with the email and country, this way we have more control about this feature.

...