Creating new columns on pc_assign_workbasket table
Due to business requiment, we want to include 6 new columns to optimize the search on pc_assign_workbasket table. Actually we use a join with pc_work table to filter this columns on the assignment report definition, but the performance is very poor, due to amout of records and custom columns on pc_work table.
Is there any restriction to update the pc_assign_worklist data model?
***Edited by Moderator: Pallavi to change content type from Discussion to Question***
Updated: 30 Jun 2020 8:45 EDT
Pegasystems Inc.
FR
Hello,
I don't think there is no. But if this is just for report purpose I would create a new VIEW maybe and report on it.
ABC Bank
BR
Hi Marc,
This report will be used to load the table in the section that displays the assignments contained on the workbaskets, on case worker portal.
Thank you,
Fabio Assuncao
Ford Motor Company
US
@FabioA35 First of all you should consider mapping to a different table than pc_work table. Your work table can be a clone of pc_work table, but not the actula pc_work table. Once you have your own work table, you have freedom to drop the columns in the work table, which are not being used, then joining with pc_assign_worklist/basket should be faster.
If you examine the various alerts in AES/PDC/PLA you should be able to identify the problematic area's which are inefficient.
ABC Bank
BR
Hi Gumudavelly,
Sorry, our work table is already a custom table, but have a lot of exposed properties on it (> 500), due to a bad implementation. That's the reason we want to customize the pc_assign_workbasket table, to improve the performance on search using this report definition. It will be used to retrieve the assignments on the workbaskets, using a search.
Thank you,
Fabio