Versions Compared

Key

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

...

In order to update the users there are certain notification which have been configured at various steps in the application process which can be changed/ configured based upon the requirements.

Data Table

...

Sr.No

...

Module

...

Code

...

Message

...

1

...

Property Tax

...

pt.property.en.create

...

Dear user, Thanks for creating an application for your property assessment. 

...

2

...

Property Tax

...

pt.payment.online

...

Dear user, Your property assessment application has been processed, please pay the required fee online through the link in order to complete the process.

...

3

...

Trade License

...

tl.renew.en.counter.approved

...

Dear user, Your application for renewal of Trade License has been approved.

**Please note: The above table is given for reference only and these are neither the actual message nor the exact codes, these are just for reference.

Procedure

The configuration of various notifications/ SMS can be achieved by following the below methods:

  1. It is more or less a localization configured procedure.

  2. The localization keys are placed at code level at all the junctures where the notification is to be sent.

  3. Then the messages are to be configured in the ' message ' table at the db level.

Data Definition

Following is the explanation of the columns that are mentioned :

  1. Module : The service for which message is being generated.

  2. Code : Localization code for which the message has to be generated.

  3. Message : Notification content that has to be sent to the user in the message.

Validations

Below mentioned are validations which should be taken care of:

  1. Please make sure the module name is correct.

  2. Code must always begin with the abbreviated form of the module.

Attachments

Below attached is the template file in order to get the data.

...

Currently we have the vendor MSDG* integrated for our accounts and the below details are provided by them for us to be configured in our system:

User Id

Password

Sender Id

Secure key

 

 

 

 

*Please note: This vendor has been chosen by our previous clients but the clients are free to chose other vendors keeping in line with the validations.

Procedure

Steps

Since the SMS service is a a vendor delivered service for which the below steps would have to be followed:

  1. Client has to finalize a vendor.

  2. The vendor would ask/ give certain details and code level changes would have to be made in order to achieve the functionality.

  3. At last the IP has to be whitelisted in the vendor’s server.

Data Definition

  1. User Id: Username for us to enter the information.

  2. Password: Password for authentication.

  3. Sendor Id: The sendor’s name for which the information has to be sent.

  4. Secure Key : Another level of encryption in order to secure the details.

Validations

Whenever a vendor is chosen please make sure that the vendor should support “ Multiple Language functionality ” and specially the local language of the state.