Question
Pegasystems Inc.
NL
Last activity: 8 Aug 2018 10:10 EDT
Managing so many optimized properties
Dear all,
I am supporting on an application which is expanded heavily in years and cannot handle current status.
We have more than 900 properties on the application and some of them are exposed.
The column size of our work table is around 360 and still increasing as a result of new requests of search and reporting.
The column population job is not working properly as I heard some issues about our "Work" table which causing some issues on DB. The problem is seems all about the number columns on the table.
Do you any solution for me to solve this issue while keeping the existing architecture?
Thank you
Pegasystems Inc.
US
For reporting, the only options are to use UDFs or to expose columns. The use of UDFs is not recommended for production, so your only other option is to expose them. If you have columns exposed that you no longer need, I think you may be able to drop the column from the table, then resave the class and that should tell Pega to stop trying to populate it. I would test this before trying in production.
If you're trying to expose and populate more properties and it's failing within Pega, that may be something we can assist with if an SR is entered, depending on what the underlying problem is. Could you provide more details about what is preventing the column population job from working properly?
Aaseya IT Solutions
IN
BIX , Declare Indexes , Data classes
You need to look at all these properties and see if they really belong to case life cycle or not.
Are they related to the data models or work object?