Restriction on entry of SMS records into SMS Corr table
Hello Team,
I am using pega 8.7 CDH and we are trying to send SMS to customer by storing SMS details in our own customized table.
We are not using OOTB capability to send SMS by configuring SMSC account.
We are storing SMS records into customized table based on out requirement. A job scheduler will run and push all the records to kafka topic and 3rd party will consume those records and will process the sms to send to the customer.
As we are using our own customized table to store SMS details we do not want the entry of SMS records into Pega OOTB table SMS Corr.
As we are using Send SMS shape in our offer flow, we are not able to restrict entry of SMS records into SMS Corr table.
Can someone please provide some suggestion to avoid entry of sms records into SMS corr table.
Thanks in advance!
Pegasystems Inc.
GB
@TaniyaD3 To avoid the entry of SMS records into the Pega OOTB table (SMS Corr) while using the Send SMS shape in your offer flow you can consider customizing the Send SMS shape or creating a custom activity that bypasses the default behavior. Since Pega does not provide an out of the box feature to directly prevent entries into the SMS Corr table you might need to implement a custom solution. One approach could be to create a custom activity that handles the SMS sending logic and updates your customized table instead of the OOTB table. This custom activity can then be called from your offer flow instead of the standard Send SMS shape.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.