Batch requestor in NBAM offer processing defaults to two
NBAM hotfixes HFix-9953 and HFix-9999 introduce a regression issue where the number of requestors used by the offer processing infrastructure is always 2.
N/A - performance issue
Steps to Reproduce
Regardless of the value set on the NBAM batch topology landing page NBAM offer processing still uses 2 requestors.
The root cause of this problem is a defect in Pegasystems’ code/rules.
HFix-10075 resolves this issue.
Published January 31, 2016 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.