PIYUSHA6661 Member since 2016 2 posts
Posted: June 14, 2016
Last activity: June 23, 2016
Posted: 14 Jun 2016 16:25 EDT
Last activity: 23 Jun 2016 4:34 EDT

Reusable nested class structure design to support BIX

For one of my customer when the original Pega platform was built on v 6.1 SP2 one of the business requirements was MI function must have access to each and every information we are keeping in Pega Work DB. In absence of detailed MI requirements project team didn't give additional consideration for efficient MI while designing the Work data structure. In the last stage of project life cycle team configured the BIX Extract rules to pull the information into the staging DB to support business MI function outside Pega. Although the application was designed using reusable nested class structure across work types, the BIX tool generated 500+ DB tables in the destination database which created a big problem for Business MI team to understand the data.

Now the same scenario is repeating itself for other client and we want to prevent it in design stage. Is there any configuration available in Pega 7.x to map the nested class structure of Work type to the normalized DB tables so that the extracted information is immediately ready for reporting.

Many thanks in advance for your invaluable recommendations.

Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.