We are trying to implement the new Bulk-uploading process using queuebatchactivity() to spawn multiple requestors. I want to understand some basic things related to child-requestor, I didn't find good documentation on how we can accomplish them; hence posting here. Any help or approach will be appreciated.
Below are the things I want to understand:
1. How we can debug the child-requestor(s) spawned from queueBatchActivity(). Is it from SMA, I have tried, but in my case, I am unable to see the new requestor in "REQUESTOR MANAGEMENT".
2. Is logging from new child-requestor(s) doesn't log anything in PEGA-LOG(s). I tried doing this using oLog.error() in new PRRequestor, but unable to see any in LOGS. Am I missing something? 3. I think the max limit for child-requestor(s) from a browser requestor is 10. After that it skips requestors instead of queuing them. Am I right? Any approach how we can handle this.
com.pega.pegarules.session.internal.mgmt.base.RequestorChildren has decent amount of debug logs. Regarding your question 3, yes your understanding is right, it is controlled by prconfig setting "services/maxRequestorChildren"
I tried debugging logs for "com.pega.pegarules.session.internal.mgmt.base.RequestorChildren" in Pega Log settings. It prints only the activity the child-requestor invokes and Requestor Track ID. If I try to Log-Messages in the invoked activity it is not showing in LOGS.
sorry to hear that. I suggest you inspect your testing activity in generated java and see which variable is null and go from there. If you are stuck but with reproducible test cases, create a SR if necessary.