We are working on a data migration effort prior to bring our system into production. We need to migrate millions of records and turn them into work objects. In order to speed throughput, we have implemented the use of queuebatchactivity() to spawn multiple requestors to run our migration activities. We have come across an issue where various property fields are being set incorrectly, only when running our activities using queuebatchactivity(). If we run the activites manually in a single requestor we do not see the same issue.
Does anyone have suggestions on how to troubleshoot this issue? We are using PRPC 6.3 SP1
***Updated by moderator: Marissa to close 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.
I might not be right but I doubt that child requestors do not have the proper access to the rules used. Which, in case of stand alone run from the developer portal is accessible.
In the case of queue, the activity for child requestor, the "pzInheritRulesetList" or "pzUseCurrentAccessGroupForChild" has to be explicitly set to true in the parameter page. So that thsese values can be passed down to the child requestor.
Please let me know if you have already tried that and it is still not working. In that case, I think you should raise an SR.