Page History

...

Brief about the data model:

1. ProductStoreTelecomSetting:
   This entity will be used for associating all gateway related setting with the product store. The details of each field in the entity are as below:
   -- productStoreId: will hold the value of the Product Store to which gateway settings need to be applied.
   -- telecomMethodTypeId: will hold the value of the type of telecom method user wants to use. for ex. SMS, MMS, WhatsApp etc. This entity will have relatioship with TelecomMethodType entity.
   -- telecomMsgTypeEnumId:  will hold the value of type of telecom message user wants to send. for ex. ORDER_SMS, INVOICE_SMS, USER_REGISTRATION_SMS, OTP etc. This entity will have relatioship with Enumeration entity.
   -- telecomCustomMethodId: will hold the value of custom method which needs to be called to send the telecom message. This entity will have relatioship with CustomMethod.
   -- telecomGatewayConfigId: will hold the value of which gateway configurations need to be used.
2. TelecomGatewayConfig:
   This entity will hold the value of telecomGatewayConfigId and bridging the ProductStoreTelecomSetting with the custom entity specific to the telecom gateway. i.e. here it is Msg91GatewayConfig.
3. TelecomMethodType:
   This type entity will hold the values of the type of message user wants to send. for ex. ORDER_SMS, INVOICE_SMS etc.
4. Msg91GatewayConfig:
   This will be the custom entity specific to the telecom gateway which will hold all configuration related values of the gateway.

At service level, we will be writing one common generic service to send SMS as like sendEmail in OFBiz. The user/developer will need to write the custom service, specific to the API provider/vendor to prepare vendor specific parameters or data which will be needed for calling SMS APIs.