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.
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 which does not exist for guest users
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1006
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-909
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-962
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-1006
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-909
Jira Legacy
server
System JIRA
serverId
255417eb-03fa-3e2f-a6ba-05d325fec50d
key
TRX-962
18
Status
title
To do
3
Identify areas for authenticated users only that guest users should not have access to
Prevent Guests from accessing the aforementioned areas for registered usersCreate 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