i have a requirement to process the higher purchase amount first when user hit the Get Next work button. I customized list view - getnextwork by adding purchase amount as the part of sorting.
my question is, by pega 7, the getnextwork list view has been marked "deprecated". For this requirement, Do we continue to use the customization on list view OR there is another approach that is "pega 7 preferred" ?
Hoping you circumstanced the ListView to be specific to the Actors, for example workgroup(s), who would use this particular implementation of GNW so does not affect everyone.
You can define a Property on Data-Admin-Operator-ID named "PrimaryRole" set with an R-D-E defined as @whatComesAfterLast(AccessGroup.pyAccessGroup,":").
If your GNW requirement does not require skills matching you can circumstance the ListView on OperatorID.PrimaryRole = <Actor's primary role>.
In that circumstanced version you can replace getContentForGetNextWork with getContent.
Or you could move upstream and circumstance FindAssignmentInWorkBasket.
In that circumstance you can do whatever you want including calling ReportDefinition.pxRetrieveReportData to populate a Code-Pega-List named "WorkBasketPage" that contains Assign-Workbasket instances that meet your requirements.
Within a subreport it is possible to duplicate the logic for how skill matching is implemented. The tricky part though is what to do when there are no assignment skills to match whatsoever. You could invent an Assign-WorkBasket property named ".NumSkills". Either .NumSkills is zero or .NumSkills equals the number of skills on the assignment that matched by the Operator's pySkills PageList.