Question

1
Replies
275
Views
Close popover
Herbert Thevasagayam (thevh)
PEGA

Pegasystems Inc.
US
thevh Member since 2015 1 post
PEGA
Posted: November 16, 2016
Last activity: November 18, 2016
Closed

Work History Table and pyLinkedObject and pyLinkedObjectClass properties

While I was implementing inbound email work processing I ran into an issue.

I observed a DB commit error execution of Activity Work- pyCreateAndManageWorkFromEmail

2016-10-19 18:39:04,311 [    EMAIL-Thread-130] [  STANDARD] [                    ] [        NPI:01.01.01] (nageWorkFromEmail.Work_.Action) ERROR EMAIL.ProcessEmailReply.Listener|from(Herbert.Thevasagayam@labatt.com)|sub(Email Appr)|Email|NPIEmail|ABI-NAZ-CA-NPI-Work-NPPA|CreatepyStartCase|AAFC326E7BBEFEF374AFD79FA2F416873  - Error in commit() 
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties	History-ABI-NAZ-CA-NPI-Work	pegadata.pc_History_ABI_NAZ_CA_NPI_Work	PegaDATA	pyLinkedObjectClass , pyLinkedObject 
From: (AAFC326E7BBEFEF374AFD79FA2F416873:NPIEmail)  
	at com.pega.pegarules.data.internal.access.PageDatabaseMapperImpl.fillInSaveStatementWithoutStream(PageDatabaseMapperImpl.java:1650) 
	at com.pega.pegarules.data.internal.access.Saver.getStatementWithPrepValues(Saver.java:1707) 
	at com.pega.pegarules.data.internal.access.Saver.addBatch(Saver.java:975) 
	at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:866) 
	at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:777) 
	at com.pega.pegarules.data.internal.access.Committer.performOps(Committer.java:243) 
	at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2751) 
	at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2400) 
	at com.pega.pegarules.data.internal.access.DatabaseImpl.commit(DatabaseImpl.java:2127) 
	at com.pegarules.generated.activity.ra_action_pycreateandmanageworkfromemail_3a45813c4a6a1bf69258af9a1b387721.step42_circum0(ra_action_pycreateandmanageworkfromemail_3a45813c4a6a1bf69258af9a1b387721.java:3500) 
	at com.pegarules.generated.activity.ra_action_pycreateandmanageworkfromemail_3a45813c4a6a1bf69258af9a1b387721.perform(ra_action_pycreateandmanageworkfromemail_3a45813c4a6a1bf69258af9a1b387721.java:838) 
	at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3510) 
	at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:646) 
	at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:466) 
	at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.runActivities(ServiceAPI.java:1896) 
	at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:390) 
	at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source) 
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
	at java.lang.reflect.Method.invoke(Method.java:606) 
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1277) 
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1015) 
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:848) 
	at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:331) 
	at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.handleStandardRequest(EmailListener.java:3671) 
	at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.handleRequestContents(EmailListener.java:4033) 
	at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.handleRequest(EmailListener.java:3901) 
	at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.emailProcess(EmailListener.java:3493) 
	at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.oneIteration(EmailListener.java:2816) 
	at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.run_(EmailListener.java:2676) 
	at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:454) 
	at java.lang.Thread.run(Thread.java:745) 

The class and DB table mention above (History-ABI-NAZ-CA-NPI-Work & pegadata.pc_History_ABI_NAZ_CA_NPI_Work) were generated through Case Designer (add case type).

I opened an SR and I was advised to expose these columns (pyLinkedObjectClass , pyLinkedObject) on the work history table.

Just out of curiousity I have the following questions:

  1. What do these properties (pyLinkedObjectClass , pyLinkedObject) do exactly?
  2. And because these properties being exposed is a dependency for the OOTB activity (Work- pyCreateAndManageWorkFromEmail) why isn't it exposed at the time when they are generated (by Pega)?
  3. I don't see these properties mentioned in the ER diagram below.  Is this ER diagram outdated?

Thanks in advance!!

***Updated by Moderator: Vidyaranjan| Tagged SRexists***

Low-Code App Development Data Integration Java and Activities Case Management Support Case Exists
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.