Page Comparison

...

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 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.

and also user needs to upload some supporting documents and mandatory info.

...

The connection holder will get notification based on a different state of the application. We are pushing the data of the connection holders in the user service too.

Steps to Integration

1. To integrate, host of sw-service module should be overwritten in helm chart.

2.  /sw-services/swc/_createshould be added as the create endpoint for creating sewerage application/connection in the system

3.  /sw-services/swc/_search should be added as the search endpoint .This method handles all requests to search existing records depending on different search criteria

4.  /sw-services/swc/_update should be added as the update endpoint. This method is used to update fields in existing records or to update status of application based on workflow.

Reference Docs

Doc Links

...