Constellation Tips: Bulk Transfer Assignment

Assignment level bulk actions are not yet available OOTB in constellation as of v24.2…but Case wide bulk actions are available… This article describes how to implement “bulk tranfer assignment” feature using Case wide bulk action.(Note: This will only work when the case has one open assignment. if there are multiple open assignments for a case, only the first assignment is being transferred.)

  1. Create a wrapper activity to loop through the pxflows and skip the flows where pxSystemFlow = true.

Steps:

Step1-Method Params

Step1-Loop

Step1-When

Step1-Jump

Step2-Method Params

Step2-When

Step3-Method Params

Parameters:

Page&Clasess:

Security:

  1. Customize pyTransferAssignment flow action.

Save a copy of Work-.pyTransferAssignment into your application ruleset… rename it… (e.x.BulkTransferAssignment)…

Action Tab: Specify your wrapper activity as the post “Run activity”

  1. Add “bulk transfer action” to the case type.

Related links

Enabling bulk processing of Cases in Constellation

Constellation 101 Series

Enjoyed this article? See more similar articles in Constellation 101 series.

8 Likes

@Chunzhi_HongHi,how to conditionalize this flow action (BulkTransferAssignment) would be visible only while configured on portal landing pages?

@VenkateswararaoK I am not sure if I really understand your question…do you mean that you want BulkTransferAssignment action only appears when you execute bulk action on the landing page…but you don’t want BulkTransferAssignment appears in the action list on the full page view of a case?

@Chunzhi_HongHong, Yes You are correct. is there any way to conditionalize the visibility to appear only on landing page ?

@Chunzhi_Hong Hello,

Thanks for sharing the article. However, how do we get DestinationType (Workqueue or WorkList) and user id which are selected on model window? How do I pass these parameters to pxTransferAssignment activity?

@Chunzhi_Hong i followed same way. once transfer completed, i can see the assign to field changed to new user but when i open the case still i can see case is assigned old user ? am missing anything here ?

One additional aspect to this. In activity BulkTransferAssignmentPostAction you need a multi part when rule to account for subflows that are not SystemFlow but also don’t have a pxAssignmentKey. Thus when rule condition on step one should be.

Also if you want this to handle multiple assignments on the same case. Putting the pyTransferAssignmentPostProcessing as a child step of the loop will allow this.