Skip to end of banner
Go to start of banner

LOC Analysis or Rough Breakdown

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

UXPROD-4663 - Getting issue details... STATUS

Option 1. Online registration Tier 1, Tier 2

Sequence Diagram Step no

TIER

API

Module

ESTIMATION

Return

Description

Question/Comments/Doubt

2

TIER-1

GET:/Patron-registration-status

edge-patron

mod-patron

3SP

  1. 200: if Active

  2. 404: if inactive (with error code or msg)

  3. 404: if not found (with error code or msg)

To check if email is already exist in USER table.

4

TIER-1

POST/UPDATE/UPSERT: /patron

edge-patron

mod-patron

6SP

  1. 201 if record created or update.

  2. 4XX/5XX: if something else (???)

Create or update patron Tier-1 data in Staging table.

Where should be create the table in mod-patron or mod-user module?

What will be exact table name? staging, user-staging or staging-user?

Will there be jsonb column like mod-users?

10

TIER-1

POST/UPDATE/UPSERT: /activate-patron

edge-patron

mod-patron

3SP

  1. 200: if updated

  2. 4XX: if something else (???)

To activate the patron.

Record still be there in staging table after activated?

Patron will activated even before T2 registration flow?

15

TIER-2

POST/UPDATE/UPSERT: /patron

edge-patron

mod-patron

4SP

  1. 201 if record created or update.

  2. 4XX/5XX: if something else (???)

To store patron Tier-2 data.

Will this be stored in staging table only?

Onsite registration completion

Sequence Diagram Step no

TIER

API

Return

Description

Question/Comments/Doubt

TIER-1

TIER-1

TIER-1

TIER-2

  • No labels