Allow edit on suspended customer-High level Design(HLD)

High-level Design:

This diagram shows the very high-level flow of edits on suspended customers.

Technical Flow Diagram:

The below diagram shows end to end flow of edits on suspended customers.

• While user is login into the portal based on his role automatically enabled the edits on the suspended customer.
• If the customer is suspended with Difficult collections, we will not allow edits. If not, we will allow edit on suspended customer.
• Edits are allowed only at the same time when customer status is being changed from Suspended to Active. Standalone updates on customer are not allowed if the status is not being changed to Active as part of same edit.
• User can edit the address info like city ,name etc. and will not be allowed to edit CBU, segmentation, web billing and concern details.
• By Default without changing any value if user is tried to edit and save it will generate the Reactivation**(SUSPENDED-ACTIVE)** workflow.
• Upon updating any other details Workflow will be triggered with SUSPENDED-ACTIVE+(Any Other workflow).
• If workflow will rejected by ADS approver, customer will be stay with previous status.
• If ADS approved the task , then Apply the customer info changes to write DB along with this we need to update the customer is concern member of concern group.

→ If a suspended customer is a existing concern member of a concern group, it should inherit all the segmentation values per the parent code (IS_CONCERN) - Attractiveness, Rolling protection flag / Loading Priorities, Value Proposition, Industry, Vertical.

→ If a suspended customer is a concern member of a concern group, any segmentation changes to the IS_CONCERN (parent code) must reflect on the suspended concern member.

• After completion of change update in write Details we need to perform Autosync and publish the customer.