Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SendSMSTreatment error and outbound SMS not working

SA-8470

Summary



Developer has noticed that SMS are not sent to the recipients when they run the program in NBAM 7.11.1

Error Messages



Error occurred in SendSMSTreatment - - Send SMS treatment aborted.
157 [fault (self-tuning)'] [ STANDARD] [ ] [ DEMO:01.01.01] (cessBatch.System_Queue_.Action) ERROR - ProcessBatch error on commit.
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties Data-BatchOutPR77 RT_AREA.BatchOutPR77 ExternalMKTData CustomerID
From: (BD287C45A5E3C0C1C8D19896DD35B2948:(Child Requestor))
at com.pega.pegarules.data.internal.access.PageDatabaseMapperImpl.fillInExternalSaveStatement(PageDatabaseMapperImpl.java:1665)
at com.pega.pegarules.data.internal.access.Saver.saveExistingInstanceWithNoDeletedColumnNotOnlyIfNew(Saver.java:1269)
.
.
.
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:509)
at com.pega.pegarules.internal.etier.mdb.PRAsyncBoot.onMessage(PRAsyncBoot.java:91)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:575)
at weblogic.ejb.container.internal.MDListener.run(MDListener.java:874)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)


Steps to Reproduce

  1. Create a Program.
  2. Map a Strategy which contains an Offer having Send SMS shape.

Root Cause



CustomerID property was missing from the Key mapping of the Customer class.

Resolution



CustomerID must be mapped as the key in the Customer class and also in the external mappings of the Customer class. Developer did not have a CustomerID column and they were keeping the CustomerID data in the AccountID column. Developer is advised to make another column in the customer table which has AccountID data and then map the AccountID to CustomerID property.

Developer created another class inherited from the their current Customer class and mapped the CustomerID. This Local-change has resolved the issue.

Published April 20, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us