SA-22986

Summary

When trying to set up Oracle Virtual Private Database (VPD) custom properties following a PDN article, an exception occurred. The link to the article is given below.
https://pdn.pega.com/passing-custom-properties-oracle-database/passing-custom-properties-oracle-database

Error Messages

[MSG][Exception][STACK][com.pega.pegarules.pub.clipboard.WrongModeException: The property D_VPDInfo.pyCustomPropertyList.pyValue was of mode String while com.pega.pegarules.data.internal.clipboard.ClipboardPropertyStrMinFeatureImpl.getPageValue() was expecting Page mode. Details: (none) at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getPageValue(ClipboardPropertyImpl.java:3495) at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getPageValue(ClipboardPropertyImpl.java:3486)
.
.

Steps to Reproduce

1. Create a data page for custom properties.
2. Stop the server.
3. Configure a new schema or database in the prconfig.xml file that specifies the database details for the classes identified in Step 2.
4. Start the server.
5. Create a new Data-Admin-DB-Name instance that connects, by using configuration preferences.
6. Open the db-name instance, and click Test Connection.

Root Cause

This is a Pegasystems' product defect.

Resolution

Perform the following local-change:

1. Prepare data transform.




2. Prepare a data page with List of Embed-NameValuePair.


The referenced PDN article will be updated to reflect the solution here. BUG-246708 is scheduled to be fixed in Pega 7.2.1 to resolve this issue.