Discussion

Need help/Info about PC_INDEX_WORKPARTY TABLE

I know that PC_INDEX_WORKPARTY should contain workparties for a work object. But, when I look in the table it shows only the current or most recent assigned workparty and doesn't show all workparties involved in the work during the entire life of that work.

Can any one know what PC_INDEX_WORKPARTY table actually contains?
Please Help.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

December 21, 2010 - 3:40pm

It's exactly as you described it. It contains a list of all work parties currently associated with a work object. If you want to keep track of all parties involved over the entire lifecycle of the work object, you'll need to create your own method.

Rob Dunie

quote:


Originally posted by KAMRANI2

I know that PC_INDEX_WORKPARTY should contain workparties for a work object. But, when I look in the table it shows only the current or most recent assigned workparty and doesn't show all workparties involved in the work during the entire life of that work.

Can any one know what PC_INDEX_WORKPARTY table actually contains?
Please Help.


December 21, 2010 - 4:44pm

Thanks for the reply Rob.

Yes, I would like to keep track of all parties involved. I have to provide to my business a way of reporting all work object by all workparties been involved with a work. I can't use the PC_INDEX_WORKPARTY table because of the problem mentioned above that it lacks the record of all workparties.

Is there a way to accomplish that?

December 22, 2010 - 7:03am

We copied the Rule-Declare-Index PartyURI rule to our custom ruleset and also set up a MyCO-Party-Account class for the custom properties for this rule. We then are able to store all of the party roles for a case.

December 22, 2010 - 9:31am

Thanks for reply LAVSAK

As I am a Pega newbie can you please give a little more detail about how you setup/used MyCO-Party-Account.

Your suggestion is to create a Declarative Index based on the copy of
pega's standard Rule-Declare-Index PartyURI which is used by Index-WorkPartyUri class which maps to PC_INDEX_WORKPARTY.

I understand the part of creating a declarative index based on PartyURI. But tell me if I am wrong, Is the MyCO-Party-Account is your applications work class or class group?

Thanks.

December 22, 2010 - 9:43am

How is your declarative index created>
Are you using the following settings:

Under INDEX CLASS DATA section:

Source Page Context: .pyWorkParty()

Source Page Context Class: MyCO-Party-Account

December 22, 2010 - 9:49am

We set up our work parties back with 4.2 SP6 with SmartAdjust so it probably isn't the "standard" used today. Our MyCO-Party-Account is not part of our class group, it's part of our data structure which inherits up to our abstract class of MyCo-.

Source Page Context = .pyWorkParty(Customer)
Source Page Context Class = MyCO-Party-Account
Index Class To Write = Index-WorkPartyUriAccount (custom class copied from Index-WorkPartyUri into our own ruleset)

June 22, 2016 - 5:18am
Response to robert.dunie

"It contains a list of all work parties currently associated with a work object."  - As defined by the current workparties currently associated with a work object? Sometimes current workparties are not reflected in the table.

March 14, 2013 - 8:25am

I currently have over 50 million rows in PC_INDEX_WORKPARTY.  Any Ideas on how to purge the old data from this TABLE.  Its taking up a lot of space without true use.

 

June 2, 2016 - 7:45am
Response to RITSCHEW

In our application, there is no real use of this data.

Is there any way suppress writing data to pc_index_workparty table?