Versions Compared

Key

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

...

Zenuml sequence macro lite
uuid6b1e5f66-1cf0-42a2-b0fc-0b8fb97ceebd
customContentId4808409158
updatedAt2024-06-18T16:36:01Z

Braze

Proposal

Solution 1 - Add isBlocked field in User DynamoDB item

...

Zenuml sequence macro lite
uuidb71e9351-b423-4ec1-ba13-9349ce24c6aa
customContentId4810997767
updatedAt2024-0607-19T0101T13:5624:16Z18Z

Blocked user attempts login

Zenuml sequence macro lite
uuid9e561ae4-39d8-4c19-81ba-99e914394741
customContentId4810997776
updatedAt2024-06-19T02:01:46Z

User is blocked while logged in WL → Add getMe query when user goes to cart page

Zenuml sequence macro lite
uuid5495a0ee-0cbb-4042-8755-8a716fa406f1
customContentId4810965031
updatedAt2024-06-19T02:08:58Z

User is blocked while logged in WL → Validate blocked user on gateway

Zenuml sequence macro lite
uuidee40a82d-c05d-4041-a5ed-e235ab9900cd
customContentId4836786181
updatedAt2024-07-08T04:37:55Z

Task breakdown

Changes in intl-whitelabel-cms

...

Expand
titleintl-admin-app
  1. Create block status card on customer page

    1. Update users package

    2. Add isBlocked to user details type in graphql

    3. Add isBlocked to customer query in frontend

    4. Create card to display user status

  2. Create mutation to block the user

    1. Use blockUser exposed in the user package (instantiated insider the user provider)

    2. Create auditLog for the customer blocking

      1. Create new audit action block-user

      2. Example of audit log

      Check if the agent has permission to block

      TBD: which permission is needed
    3. Create block customer permission

      1. Permission: “RBI.supportActions.customer.block”

      2. Add “RBI.supportActions.customer.*” to rolePermissionMapping in agent role for BK,PLK,TH and FHS

  3. Implement block user in front end

    1. Create confirmation modal

    2. Check if agent has permission to change customer status

      1. TBD: which permission is needed

    3. Trigger block mutation on confirmation

  4. Create mutation to unblock the user

    1. Use unblockUser exposed in the user package (instantiated insider the user provider)

    2. Create auditLog for the customer unblocking

      1. Create new audit action unblock-user

      2. Example of audit log

    3. Check if the agent has permission to unblock

      1. TBD: which permission is neededPermission: “RBI.supportActions.customer.block”

  5. Implement unblock user in front end

    1. Create confirmation modal

    2. Check if agent has permission to change customer status

      1. TBD: which permission is needed

    3. Trigger unblock mutation on confirmation

...