Queue method to invoke an activity from another activity

Queue method to invoke an activity asynchronously, can be an alternate to SpinOff a flow. However few configurations are required with "Queue" which are not required with "SpinOff" in flows.

When using "Queue" to invoke an activity, the activity is invoked by the master agent in the context of "Batch" requestor's access group. So, the default context is setup using the access group "PRPC:Agents". In order to make the system locate the activity which is queued, either update this access group to access your application or update the requestor type "Batch" to have access to your application's access group.

Note: If there are multiple applications are hosted on the same Pega Instance, then changing the requestor type to access your application specific access group, might impact other applications, hence it’s not suggested in that setup.

As an alternate, use the method "Queue-For-Agent" to invoke an activity configured in Standard / Advanced agent where access control is handled in the custom Agent instance and not at the broader level.

**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.


Keep up to date on this post and subscribe to comments

October 17, 2018 - 2:25am

Hi Saurabh,

Thank you for sharing on PSC.


Lochana | Community Moderator | Pegasystems Inc.