Closed
Solved
Exposing custom properties in pr_sys_queues table
Could you, please, tell me if it is possible to expose custom properties as a database columns in internal Pega table pr_sys_queues without any negative impact on all agents' processing and all other OOTB functionalities?
We developed a report which retrieves data from pr_sys_queues table using custom properties as a columns source, but its execution performance is severely limited by the lack of "report's optimization" in terms of these custom properties. We are not sure if exposing these properties will not have a bad effect on application stability and functioning.
I would appreciate your answers.
Posted: 8 years ago
Pegasystems Inc.
Pegasystems Inc.
IN
Hi Lukasz, Good Morning!
- exposing columns (as the table is added with additional columns - custom properties) shouldn't have any negative impact on the system.
- but we should be careful during upgrade/migration scenarios to reflect this schema change (System-Queue-).
- creating a RAP rule for DATA-ADMIN-DB-TABLE SYSTEM-QUEUE- would help in auto extracting the table schema.
- but we should be careful during upgrade/migration scenarios to reflect this schema change (System-Queue-).
Please share your thoughts/comments, Thank you!
psahukaru