'GETNEXT' is not pulling any work even though the WB has work
A work basket has more than 100 cases for SKILL A and SKILL B users. When the USER with SKILL B hits the GETNEXT, the screen indicates there is no work.
The SQL that selects the work appears to restrict the results prior to applying the Skill filter. This prevents large work baskets from being processed.
Steps to Reproduce
- When the first 50 of the most urgent work items in a work basket which do not have any work for a specific skill.
- Click "Get Next"
- The query returns no rows, resulting the message ‘no work available’
This is the expected behavior for the legacy configuration of GetNextWork.
For help configuring GetNetWork on the Product Discovery Network (PDN) see:
0% found this useful