Smart Investigate - Production Environment Cleaning
Our Project is expected to Go-Live in ten days and, since we're now in Business Simulation in the Production Environment, we have to clean the whole database (all cases, cache, etc..) in order to have a clean situation for the users to start the actual business adoption of the new Platform.
The Platform is based on PEGA PRCP 7.1.9 + Smart Investigate for Payments 7.11.
Any kind advice or best practice you may provide in order to reach the clean environment status for the Go-Live is more than welcome.
As a startup, I copied what Elisha Tanikonda for early version of smart investigate running on 61sp2 - let's wait for SMEs to provide insights. But I believe for the most part, the list below is still valid. If necessary, create a SR for further investigation.
Provided the below suggestions to the customer.
For BIX ======== pr_extract_time
For PRPC =======
pc_work — Primary work object record pc_history_work — Audit trail details pc_assign_* tables — Incomplete assignments pc_link_attachment — Associates a work object with attachments, optional files, e-mail messages, or images. pc_link_folder — Support folders, an optional facility for grouping multiple work objects pc_data_workattach — Holds work object attachments pc_index_workparty — Cross-references work objects by an identifier for each party (participant), such as an account number, Social Security Number, e-mail address, or telephone number. pc_data_unique. — Supports unique work object numbering pr_data — Holds unsent correspondence for work objects [don't truncate the whole table!] pr_assign - external assignments go here
For Smart Investigate and SWIFTNet (E & I) ============================ delete from si_work; si_index_workparty; research_links; paf_work; paf_index_workparty; paf_index_txn; paf_index_original; paf_entry; pc_assign_workbasket; pc_assign_worklist; pc_data_workattach; pc_index_workparty; pc_link_attachment; pc_link_folder; pc_history_work;