Hi Litosh,

For one of the project we have done this which is creation of new queue table.

Steps for that:

Step 1: We created one queue class (System-Queue-MyQueueClassName is concrete). pyItemId is the class key and System-Queue- is the direct inheritance. 

Step 2: Wherever we have to queue to this table we created the temp page of type this class and queued the item in this context.

For example in one of the activity we created the system queue Page of type this. and called the activity "QueueForAgent" and gave the step page as created page.

So whenever this step executes the queue entry will be queued for this class and executed. It works.

We used it as we had requirement of lots of properties to set and track them. Surely it works. 

If you need any help please let me know.

Hi,

Can you please explain below points regarding this post?

1. Have you created a new table similar to Pr_Sys_Queue (structure wise) and mapped that table with the newly created class? 

2. In the activity where we are queuing the item, what parameters are you passing? i understand that you are calling Queue-For-Agent method here on the page of the newly created class.

3. Will standard agent in pega understand at runtime which table it should go for to pick the new item? Generally if we call queue-for-agent it checks in pr_sys_queue table as per my knowledge.

4. Is there any other settings change / development involved in this process apart from what is being written in the post?

I believe that by default it will just point to pr_sys_queues. I haven't seen it create its own database table unlike concrete Pega data tables.

You'll have to create a new table with identical columns as pr_sys_queues and point your new queue class to it.