Support Article
Use correct class order and searchability in pyCaseWorker portal
SA-90
Summary
pyCaseWorker portal doesn't allow searching and listing work from all classes listed on Rule-Application (rule-app) details tab. Only items in base-a are returned in searches.
Error Messages
Not Applicable
Steps to Reproduce
1) Install hfix-9525, which makes sure that the new-work dropdown of pyCaseWorker portal shows order that matches the order specified in rule-app details tab.
2) Have work classes base-a, base, and base-b, listed in that order in rule-app details tab.
3) Notice that when you use pyCaseWorker portal, only work objects in base-a are shown in my-worklist and only work objects in base-a are searchable.
Root Cause
For PRPC 6.3 SP1, the internal code seeds the pyCaseWorker search classes and my-worklist classes by appending a wildcard to the end of the first class listed on rule-app details tab. The class listed in that first position needs to be one whose name is a left-anchored substring of the rest.
Resolution
This issue is resolved through the following local change:
In order to allow all classes that may contain starter flows to be in any order in the rule-app details tab list, create a class group named a left-anchored substring of the other items in the list and put that class first.
Using the above example, create a classgroup called bas and list it first on the rule-app details tab list (without the new-work checkbox) so the resultant list is
bas
base-a
base
base-b
Published February 15, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.