Question


Realvalue Consulting
CH
Last activity: 9 Jul 2016 10:00 EDT
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.
Thanks
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution


Pegasystems Inc.
IN
Hi Genta, Good morning!
- Most of the tables are covered in Kevin's post. again copying the tables just to draw the final list using both the posts.
Smart Investigate WorkObject Table Delete Script
DB2
Delete from si_work@
Delete from si_index_workparty@
Delete from research_links@
Delete from paf_work@
Delete from paf_index_workparty@
Delete from paf_index_txn@
Delete from paf_index_original@
Delete from paf_entry@
Delete from pc_assign_workbasket@
Delete from pc_assign_worklist@
Delete from pc_data_workattach@
Delete from pc_index_workparty@
Delete from pc_link_attachment@
Delete from pc_link_folder@
Delete from pc_history_work@
Commit@
Oracle
Delete from si_work;
Delete from si_index_workparty;
Delete from research_links;
Delete from paf_work;
Delete from paf_index_workparty;
Delete from paf_index_txn;
Delete from paf_index_original;
Delete from paf_entry;
Delete from pc_assign_workbasket;
Delete from pc_assign_worklist;
Delete from pc_data_workattach;
Delete from pc_index_workparty;
Delete from pc_link_attachment;
Delete from pc_link_folder;
Delete from pc_history_work;
Commit;
User Note
Hi Genta, Good morning!
- Most of the tables are covered in Kevin's post. again copying the tables just to draw the final list using both the posts.
Smart Investigate WorkObject Table Delete Script
DB2
Delete from si_work@
Delete from si_index_workparty@
Delete from research_links@
Delete from paf_work@
Delete from paf_index_workparty@
Delete from paf_index_txn@
Delete from paf_index_original@
Delete from paf_entry@
Delete from pc_assign_workbasket@
Delete from pc_assign_worklist@
Delete from pc_data_workattach@
Delete from pc_index_workparty@
Delete from pc_link_attachment@
Delete from pc_link_folder@
Delete from pc_history_work@
Commit@
Oracle
Delete from si_work;
Delete from si_index_workparty;
Delete from research_links;
Delete from paf_work;
Delete from paf_index_workparty;
Delete from paf_index_txn;
Delete from paf_index_original;
Delete from paf_entry;
Delete from pc_assign_workbasket;
Delete from pc_assign_worklist;
Delete from pc_data_workattach;
Delete from pc_index_workparty;
Delete from pc_link_attachment;
Delete from pc_link_folder;
Delete from pc_history_work;
Commit;
User Note
- Execute the above script to delete Exception & Message cases (work objects) to de-link the transactions from work objects.
- If cache is deleted - first user might notice a slow response from application and we might need to run static assembler before user run through the application.
Thank you!
psahukaru


Pegasystems Inc.
US
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
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;


Pegasystems Inc.
US
Hi Kevin
Due to some reason, I did not receive an email notification from mesh on this thread. I just found this item today when I was going through my mesh inbox.
I am copying, Srikanth Tadi who can help you on your Smart Investigate query.
Thanks
Elisha
Accepted Solution


Pegasystems Inc.
IN
Hi Genta, Good morning!
- Most of the tables are covered in Kevin's post. again copying the tables just to draw the final list using both the posts.
Smart Investigate WorkObject Table Delete Script
DB2
Delete from si_work@
Delete from si_index_workparty@
Delete from research_links@
Delete from paf_work@
Delete from paf_index_workparty@
Delete from paf_index_txn@
Delete from paf_index_original@
Delete from paf_entry@
Delete from pc_assign_workbasket@
Delete from pc_assign_worklist@
Delete from pc_data_workattach@
Delete from pc_index_workparty@
Delete from pc_link_attachment@
Delete from pc_link_folder@
Delete from pc_history_work@
Commit@
Oracle
Delete from si_work;
Delete from si_index_workparty;
Delete from research_links;
Delete from paf_work;
Delete from paf_index_workparty;
Delete from paf_index_txn;
Delete from paf_index_original;
Delete from paf_entry;
Delete from pc_assign_workbasket;
Delete from pc_assign_worklist;
Delete from pc_data_workattach;
Delete from pc_index_workparty;
Delete from pc_link_attachment;
Delete from pc_link_folder;
Delete from pc_history_work;
Commit;
User Note
Hi Genta, Good morning!
- Most of the tables are covered in Kevin's post. again copying the tables just to draw the final list using both the posts.
Smart Investigate WorkObject Table Delete Script
DB2
Delete from si_work@
Delete from si_index_workparty@
Delete from research_links@
Delete from paf_work@
Delete from paf_index_workparty@
Delete from paf_index_txn@
Delete from paf_index_original@
Delete from paf_entry@
Delete from pc_assign_workbasket@
Delete from pc_assign_worklist@
Delete from pc_data_workattach@
Delete from pc_index_workparty@
Delete from pc_link_attachment@
Delete from pc_link_folder@
Delete from pc_history_work@
Commit@
Oracle
Delete from si_work;
Delete from si_index_workparty;
Delete from research_links;
Delete from paf_work;
Delete from paf_index_workparty;
Delete from paf_index_txn;
Delete from paf_index_original;
Delete from paf_entry;
Delete from pc_assign_workbasket;
Delete from pc_assign_worklist;
Delete from pc_data_workattach;
Delete from pc_index_workparty;
Delete from pc_link_attachment;
Delete from pc_link_folder;
Delete from pc_history_work;
Commit;
User Note
- Execute the above script to delete Exception & Message cases (work objects) to de-link the transactions from work objects.
- If cache is deleted - first user might notice a slow response from application and we might need to run static assembler before user run through the application.
Thank you!
psahukaru


Capgemini
SE
Is it advisable to create a copy of the si_work table for storing implementation specific work objects?


Pegasystems Inc.
IN
yes. ideally when application extended for implementation app express/DCO will create implementation specific work table.