Has anyone tried to use BIX DB to restore the case data
Hi tEam,
We know Pega has OOTB archival functionality which requires us to configure the filesystem / to archive the data but it comes with cost for storage and need to address PHI concerns. Has anyone tried the possibility of using other repositories like BIX to either restore the data back into the case table or use this as a secondary lookup for the data, thereby avoiding to archive data into file respositories or creating another source of archival altogether?
Pegasystems Inc.
CA
BIX DB will have incremental case information. In other words, there could be multiple records for the same case because the latest snapshot will be sent to BIX tables periodically during the case workflow.
Accenture LLP
US
@RameshSangili Thanks for the reply,
I already know BIX and already implemented that in my project for storing information for reporting. My question was related to case archival. We are already aware of Pega's OOTB Archival functionality defined at the case level, but we are reviewing other alternate archival strategy as well and thought if we can leverage tables extracted from BIX...
The approach we are looking into is archive case data into BIX tables, purge those cases in original table, when user want to fetch archived data, system pulls data from BIX tables instead of case tables. Reason why we want to do this is because data is already being extracted in BIX table, why not leverage that?
Pega OOTB uses repositories to store data but that is associated with costs and we have to solve issues with PHI information.
Updated: 4 Jan 2024 9:31 EST
Pegasystems Inc.
CA
Thanks for the clarifications.
My 2 cents.
OOTB solution:
- Pega OOTB archival stores the data in the File repository and it uses elastic search to retrieve the information from the Archival storage.
- Data retrieval from Archived storage is faster with Elastic search.
- OOTB solution stores all the Work, History, and associated(Index table for example) tables in Archived storage.
BIX
- Leveraging BIX tables may require more custom solutions to retrieve the Archival data from BIX tables.
- There could be performance impacts when BIX tables grow significantly.
- You may require custom solutions for the history table and do join at run time if we are leveraging BIX table
Are you hosted on Pega Cloud or On-Premise?
Thanks,
Updated: 4 Jan 2024 16:29 EST
Accenture LLP
US
@RameshSangili Hi Ramesh
We are seeing that Pega Archival Job scheduler indexes the archived data - I have a question - Does PEga uses the elastic search to get data from indexed files itself thereby not needing the zip files. or does it open those archived csv files (Stored as zip) when a user clicks on archived case from the search results?
With OOTB solution, is it possible to restore the case back into the original table?
I am wondering why Pega has not created a solution to archive the data into a secondary DB table (which would be a replica of the original case and related tables)? Rather archiving into a file system.
There is also another solution int he market to use DB reference partition concept to archive data into diff. sub-parts based on date (for e.g. diff part table for each year). Does PEga recommend any of these or hass come across any client which successfully implemented this?
I do agree, BIX would be more difficult to leverage.
To answer your question, we are hosted on Pega on-Prem.
Pegasystems Inc.
CA
With OOTB solution, is it possible to restore the case back into the original table?
Yes, with a custom solution. We had a similar requirement in my previous project because we had to reopen once after archiving if there were legal complaints. Clone the information from the Archived case and save it back to the original table.
To my knowledge, DB Partition is no longer supported for Pega On-Cloud customers.