Skip to main content

Automate Loading Priorities - Low Level design(LLD) & High Level Design(HLD)

UI Changes:

  • From portal, user will not be able to edit rolling protection irrespective of the role.

Assign Relationships API:

  • Assign Relationships API upon receiving request should validate the request upon below parameters
    • Params
      • Source System
      • User
      • Brand
      • Customer Code
      • Customer Segments (SegmentationsType)
        • Segments (SegmentType)
          • SegmentType
            • Brand ( Brand code, Brand name)
            • Segment Classification ( Segment Classification Code, Segment Classification Value, Segment Classification Name, Segment Classification Description)
            • Unassign Segment Flag
  • Upon successful validation, if segment value is Attractiveness(SERV) and segment value is KeyClient(KEYC) then update ROLP segment value to A1.
  • Upon successful validation, if segment value is Attractiveness(SERV) and segment value is Runway(NEXT) then update ROLP segment value to A2.
  • If the Key Client is deleted, then the loading priority will be null.
  • All the customers within the same concern must have the same Attractiveness value.

Ingest Customer API:

  • If segment value is Attractiveness(SERV) and segment value is KeyClient(KEYC) then update ROLP segment value to A1 and also update vip non roll flag as A1.
  • If segment value is Attractiveness(SERV) and segment value is Runway(NEXT) then update ROLP segment value to A2 and also update vip non roll flag as A2.
  • Any changes to the rolling protection/loading priority must reflect in the VIP non roll flag field.
  • After then do elastic sync and publish.

BBU:

  • From BBU, validation message should be thrown while trying to add ROLP segment value. (Error message will be decided once Vinesh confirms it.)

High Level Design:

Was this page helpful?