Versions Compared

Old Version 4

changes.mady.by.user ashwini.athani

Saved on

compared with

New Version 5

changes.mady.by.user Hina Makhija

Saved on

Key

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

...

After connection activation or legacy connection, user can disconnect the connection either temporary or permanent. This process based on defined workflow. Any action is based on defined roles on the action level. For disconnecting the connection, user needs to send extra parameters in the RequestBody as below :

  1. disconnectionReason - to add the reason for disconnection

  2. isDisconnectionTemporary - Whether the disconnection is temporary or permanent (if disconnection is temporary then isDisconnectionTemporary will be true else false)

  3. disconnectRequest - This will always be true for disconnection application.

  4. disconnectionExecutionDate - This is the date when the application is disconnected.

...

Code Block
{
   "format": "SW_AP/[CITY.CODE]/[fy:yyyy-yy]/DC-[SEQ_SW_APP_[TENANT_ID]]",
   "idname": "sewerageservice.disconnection.id"
}
Info

This new feature is developed using the same existing base apis for new and modify connections.
The changes for disconnection follows similar approach as that of New Connection.
The config and persister changes required are mentioned below.

Persister configuration:
https://github.com/egovernments/configs/blob/qaUAT/egov-persister/sewerage-persist.yml

Workflow config for edit connection:

...