Versions Compared

Key

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

...

Scope/ Outcome

Work Required

Available on staging

Status

  • Add configurable time period of storing the Guest Order data in the database. Configure to 10 year for DE

  • Preventing the guest user from seeing app content dedicated for registered users only

  • Add a security layer limiting actions allowed for the orders with Guest token. Actions allowed for example: priceOrder, validateCommitOrder, commitOrder, getOrder, etc

  • Add a guard that allows to use of the Guest Token only for the allowed actions

  • Creating Guest Token- To place an order as a Guest users require to have be authenticated on our platform/ In order to do that we need to create a Guest Auth token. We can’t follow the current path for collecting it because Guests don’t have accounts in Cognito and in the User DB entries.

  • Save Card Option Removed at the Payment step

    Image Removed
  • Added Modal to continue as a guest

  • Adjusted data on the confirmation page

  • QA Testing

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-908
F

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-949959
F

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-959941
F M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-941947
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-947957
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-957956
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-956912
M W
Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-9121010
W

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-10101053
W

Status
colourBlue
titleWork in Progress

  • Accommodate new transactional email communication with AWS SES instead of Braze

  • Decide and execute when guest token should be removed, so no other order can be made with that token to guarantee anonymity

  • Prevent error appearing on the success page due to loyalty account request and price call which does not exist for guest users

  • Review the tracking event coverage and naming conventions

  • QA Testing

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1006

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-880

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-962

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1040

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1052

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1057

Status
titleTo do

  • Create a new static page for guest terms and conditions and link it in the flow

  • Change copy to “choose payment' instead of “add payment” at the /cart/payment page

  • Save Card Option Removed at the Payment step

    Image Added
  • Implement tracking events to flow to Amplitude

  • E2E QA Testing

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-948

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1015

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-949

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1003

Status
titleTo do

...