Idea
Issues with pre processing limitation on Bulk Actions
pyTransferAssignment is a flow action used in Bulk Processing. pyTransferAssignment section is used to capture user input such as pyReassignType, Workbasket, Operator. The input is captured on reAssignPage of class Data-Reassign. It is stated that pre processing is not supported because work object is not being opened.
Imagine the scenario where the data on reAssignPage and not on work object needs to be manipulated, i.e. business requirement states that some values on reAssignPage (not work object) should be defaulted. How is this feasible to achieve if pre processing Data Transform is not supported?
Thanks for your help
I have been advised to raise this as Product Enhacement as per article below:
https://pdn.pega.com/why-don%E2%80%99t-pre-processing-activities-circum…
***Edited by Moderator Marissa to update categories; add FDBK ID***
I have submitted this as a product enhancement per the original poster's request and updated the Feedback ID in the original post. Please take this to your Account Executive for more information if you would also like this enhancement.
Thank you!
How about calling an activity at preprocessing of flow and then configuring the required manipulation?
You can configure a utility shape in the flow, with an activity having the configuration with altered data set.
Additionally, you can raise an enhancement request with GCS/moderator on PSC to add this functionality, though it's subject to review of the product owner.
Hope it answers your query, kindly notify if it does.
Regards,
Asif