Question
AIG
US
Last activity: 6 Apr 2016 8:00 EDT
Move Workobject from PROD to NON Prod for debugging
Hi
How to move the work object from PROD to non prod for debugging.
Assumptions:
The pyid has no conflicts on non prod.
it the same application work object that has to be exported to non prod.
same user id ,flows exist.
Pega version : Pega 62 sp2.
Accepted Solution
Pegasystems Inc.
US
Hi Ranjith,
The Package Work wizard should be able to do this for you. You can find more information about it in the following developer help article:
https://community.pega.com/sites/default/files/help_v62/procomhelpmain.htm?
To move just a single work object, you can select the Work ID range to encompass just the target object.
Hope this helps!
-Kurt
GovCIO
US
Hello Ranjith,
There are 2 ways to work on this.
1) Take the help from DBA to copy the WO from prod to non-prod
2) Give a try to create an RAP and mention the pzInskey of that WO in the RAP under "INDIVIDUAL INSTANCES TO INCLUDE" and import that RAP into destination.Not sure if the whole data will be migrated in this option or not. But, no harm to give a try.
Thanks,
Ravi Kumar.
Accepted Solution
Pegasystems Inc.
US
Hi Ranjith,
The Package Work wizard should be able to do this for you. You can find more information about it in the following developer help article:
https://community.pega.com/sites/default/files/help_v62/procomhelpmain.htm?
To move just a single work object, you can select the Work ID range to encompass just the target object.
Hope this helps!
-Kurt
Pegasystems
US
If you do attempt to move the work with a rule-admin-product (RAP) instead of the tool, make sure you include all of the following (unless you don't care that some of it is missing on your target system). /Eric
- work object
- assignment objects
- attachment link objects
- attachment data
- history records
Did I miss some ? /Eric
Pegasystems Inc.
IN
Hi, Package Work is definitely an option, but it would take considerable amount of time for each of the object and related data to get imported. You can even think of doing a direct DB level move / copy which would be much faster.