Customer schema tables - No OoTB columns
From Pega 8.1.0, i see that "CustomerData" is chosen as the schema for the tables of all the data types. Tables created in such way do not have any px, py and pz properties which include pzInsKey, pxObjClass or even pzPvStream. This restricts the data type from holding value other than the exposed columns. Is this a product defect? How to overcome this issue?
Thanks in advance.
Hi Pedel,
Thanks for the quick response. How to have a blob column and px,py, pz columns in a table created for a data type?
Replacing my original response. As of Pega 8.1.3 you can change from CustomerData schema to the PegaDATA at the bottom of the Data Type "Sources" tab before you click Submit.
See attached.
PREVIOUS RESPONSE BELOW (Ignore)
The brute force way would be to NOT use the Data type view and instead manually create a Data class followed by defining its keys.
If Pega does not create a new table for you, you can clone the pr_other table to create a new table in the PegaDATA schema for your class.
You can then create a Data-Admin-DB-Table record to map your class to that table.
Lastly you can add your class to your Application in the Data section below the Case types section.
That should create a new Data-Rule-AppMetadata instance.
But what happened to the good old "Data type having a table with blob column" approach? Is there no way to configure that from now on? All the data types that we create will be associated only with fully exposed external tables? I don't think it should boil down to an extent of cloning tables at the DB level.
Thanks in advance.
Ratan Balaji.
You can change the schema to PegaDATA at the bottom of the Sources tab before clicking Submit.
I totally agree with Ratan on this, why Pega has taken the blob column approach which in turn increases the effort to clone the existing table with blob column.
"We" should also include Business Users.
While Pega 8.1's App Studio does not currently support report authoring, it is on Pega's radar to offer this capability.
Every Property that a user defines in App Studio creates a column in the database regardless the table being defined in the PegaDATA schema or the CustomerData schema.
Reports defined using Relevant Records would not incur BLOB reads.
Obviously this is by design, not a product defect. In 8.1's App Studio there is seamless integration between your Data Type and whatever System of Record is used for that Data Type. You would not fetch a BLOB column from a non-Pega SOR data source.
As we know Pega readily handles case embedded Pages and PagesList sourced to a Data Type using the Data Page reference or snapshot pattern.
Are you wanting to embed a PageList within a Data class not using a Data Page to capture the data? Recall that Savable Data Pages were added in Pega 7.4.
Or are you not wanting to expose every column in your Data class?