I am getting an error in our PEGA logs that reads:
(Commons_Data_Interface_.Action) INFO gbautilwas1.corp.bcbsal.org|XX.XX.XX.XX|SOAP|CGBACTI|Event|AgentCallNotification|AB6A8EA7934A1AF91FCAF24383BA5B810 - LogServiceInOutTime*Application:CC*ID:151641000006927*InTime:20160307T213925.282 GMT*OutTime:20160307T213925.300GMT*TimeDifference:18.0*Msg:ScreenPop2016-03-07 15:39:33,168 [ WebContainer : 12] ( rd.resolve.SqlReportResolver) ERROR gbautilwas1|gba10004548.corp.bcbsal.org - An error occured during resolving the report definition - InvalidReferenceException .pyRuleName Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException .pyRuleName Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking
Hi Mark, The PDN post you referred explains about the CPM related data properties as need to remap the database table for few data classes after upgrade to CPM 713.
But your issue seems to be with PRPC OOB property .pyRuleName. In one of the report definiiton, it is trying to retrieve the .pyRuleName column from the DB table where the property is not optimized/existed.
As per my analysis, i could see that, Data-Rule-Locking is associated with pwbv4_rule_lockingDB table. A column name called pyrulename is present in the DB table. Can you check whether the column is available in the above table.