Difference between revisions of "Resetting Smart Dispute Data for Journey Re-run"

From PegaWiki
Resetting Smart Dispute Data for Journey Re-run
Jump to navigation Jump to search
m (curator assigned)
Tag: Visual edit
(Minor grammatic edits)
Tag: Visual edit
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{New request
+
{{Design pattern|Title=Resetting Smart Dispute data|Description=Script to reset work object and related data|Version=7.1.1|Applications=Pega Disputes and Payments Exceptions|Capability Area=Financial Services|Owner=Manjusha Gandham}}
|Request to Publish=Yes
 
|Curator Assigned=Manjusha Gandham
 
|Description=Resetting Smart Dispute Data for Journey Re-run
 
|Applications=Smart Dispute
 
|Capability Area=Financial Services
 
|Version=7.x
 
}}
 
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓  '''<big>Please Read Below</big>'''  ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
 
  
Enter your content below. Use the basic wiki template that is provided to organize your content.  After making your edits, add a summary comment that briefly describes your work, and then click "SAVE".  To edit your content later, select the page from your "Watchlist" summary.  If you can not find your article, search the design pattern title.
+
== Resetting Smart Dispute data for Journey rerun ==
 +
To showcase a Smart Dispute journey demo to a new customer, a system without a dispute work object or any associated work object related data is required.
  
When your content is ready for publishing, next to the '''"Request to Publish"''' field above, type '''"Yes"'''. A Curator then reviews and publishes the content, which might take up to 48 hours.  
+
To achieve this, one way is to reset or reinstall the application or delete all the existing work object and the associated data. Resetting or reinstalling the application takes a lot of time and resetting multiple configuration settings to achieve the desired demo scenario. Deleting and resetting the existing data is easy to perform, and is explained below.
  
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ '''<big>The above text will be removed prior to being published</big>''' ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
+
Run the following SQL script by replacing the <PegaData> with the exact schema name and modify the script per the database type to reset the Smart Dispute data:
  
== Resetting Smart Dispute Data for Journey Re-run ==
+
<code>delete from <PegaData>.pc_data_uniqueid;</code>
During the Smart Dispute Journey demo, it is often required to have a system with no dispute work object and no associate data related to work object to showcase proper scenario to new customer.
 
  
To achieve this, one way is to reset the current application and reinstall Smart Dispute or delete all the existing work object and its associate data. The first approach is time taking and the team providing demo must perform lots of configuration setting to achieve the desired demo scenario. The later approach is quite simple and easy to perform, giving the team providing the demo to focus only on the demo scenario.
+
<code>update <PegaData>.pc_data_uniqueid set pylastreservedid=0;</code>
  
== Script to reset Smart Dispute data ==
+
<code>delete from <PegaData>.sd_claim;</code>
Run the following SQL script to reset the Smart Dispute data.
+
 
* delete from <PegaData>.pc_data_uniqueid;
+
<code>delete from <PegaData>.sd_dispute;</code>
* update <PegaData>.pc_data_uniqueid set pylastreservedid=0;
+
 
* delete from <PegaData>.sd_claim;
+
<code>delete from <PegaData>. pc_work;</code>
* delete from <PegaData>.sd_dispute;
+
 
* delete from <PegaData>. pc_work;
+
<code>delete from <PegaData>. pc_assign_worklist;</code>
* delete from <PegaData>. pc_assign_worklist;
+
 
* delete from <PegaData>. pc_assign_workbasket;
+
<code>delete from <PegaData>. pc_assign_workbasket;</code>
* delete from <PegaData>. pc_history_work;
+
 
* delete from <PegaData>. pc_data_workattach;
+
<code>delete from <PegaData>. pc_history_work;</code>
* delete from <PegaData>. pc_index_workparty;
+
 
* delete from <PegaData>. pc_link_attachment;
+
<code>delete from <PegaData>. pc_data_workattach;</code>
* delete from <PegaData>. pc_link_folder;
+
 
* delete from <PegaData>. paf_entry;
+
<code>delete from <PegaData>. pc_index_workparty;</code>
* delete from <PegaData>. paf_index_workparty;
+
 
* delete from <PegaData>. pr_assign;
+
<code>delete from <PegaData>. pc_link_attachment;</code>
* delete from <PegaData>. pr_sys_locks;
+
 
* delete from <PegaData>. pr_sys_queue_sla;
+
<code>delete from <PegaData>. pc_link_folder;</code>
* delete from <PegaData>. pr_sys_queues;
+
 
* delete from <PegaData>. pr_data;
+
<code>delete from <PegaData>. paf_entry;</code>
* delete from <PegaData>. pr_link;
+
 
* delete from <PegaData>. pc_work_social;
+
<code>delete from <PegaData>. paf_index_workparty;</code>
* delete from <PegaData>. pr_index;
+
 
* delete from <PegaData>. pr_Index_PegaCard_Sd_FraudRepo;
+
<code>delete from <PegaData>. pr_assign;</code>
Replace the <PegaData> with the exact schema name. Also, modify the above script as per the database type.
+
 
 +
<code>delete from <PegaData>. pr_sys_locks;</code>
 +
 
 +
<code>delete from <PegaData>. pr_sys_queue_sla;</code>
 +
 
 +
<code>delete from <PegaData>. pr_sys_queues;</code>
 +
 
 +
<code>delete from <PegaData>. pr_data;</code>
 +
 
 +
<code>delete from <PegaData>. pr_link;</code>
 +
 
 +
<code>delete from <PegaData>. pc_work_social;</code>
 +
 
 +
<code>delete from <PegaData>. pr_index;</code>
 +
 
 +
<code>delete from <PegaData>. pr_Index_PegaCard_Sd_FraudRepo;</code>

Latest revision as of 10:24, 25 October 2021

Resetting Smart Dispute data

Description Script to reset work object and related data
Version as of 7.1.1
Application Pega Disputes and Payments Exceptions
Capability/Industry Area Financial Services



Resetting Smart Dispute data for Journey rerun[edit]

To showcase a Smart Dispute journey demo to a new customer, a system without a dispute work object or any associated work object related data is required.

To achieve this, one way is to reset or reinstall the application or delete all the existing work object and the associated data. Resetting or reinstalling the application takes a lot of time and resetting multiple configuration settings to achieve the desired demo scenario. Deleting and resetting the existing data is easy to perform, and is explained below.

Run the following SQL script by replacing the <PegaData> with the exact schema name and modify the script per the database type to reset the Smart Dispute data:

delete from <PegaData>.pc_data_uniqueid;

update <PegaData>.pc_data_uniqueid set pylastreservedid=0;

delete from <PegaData>.sd_claim;

delete from <PegaData>.sd_dispute;

delete from <PegaData>. pc_work;

delete from <PegaData>. pc_assign_worklist;

delete from <PegaData>. pc_assign_workbasket;

delete from <PegaData>. pc_history_work;

delete from <PegaData>. pc_data_workattach;

delete from <PegaData>. pc_index_workparty;

delete from <PegaData>. pc_link_attachment;

delete from <PegaData>. pc_link_folder;

delete from <PegaData>. paf_entry;

delete from <PegaData>. paf_index_workparty;

delete from <PegaData>. pr_assign;

delete from <PegaData>. pr_sys_locks;

delete from <PegaData>. pr_sys_queue_sla;

delete from <PegaData>. pr_sys_queues;

delete from <PegaData>. pr_data;

delete from <PegaData>. pr_link;

delete from <PegaData>. pc_work_social;

delete from <PegaData>. pr_index;

delete from <PegaData>. pr_Index_PegaCard_Sd_FraudRepo;