OOTB BulkAction not supporting standard P7 UX
The out-of-the-box BulkAction functionality is implemented in the scripted single section "pyMyProcessActions" which is not P7 UX-like, doesn't match with the other OOTB harness UIs and shows a poor UX in comparison to the P7 standard UI rules.
Furthermore to customise this is only possible via scripting again - is this by intention?
***Updated by moderator: Lochan to add SR Exists group tag***
Pegasystems Inc.
IN
This is definately not by intention and not a best practice at all.
We are actually not using this section anymore in OOTB manager portal. Could you tell me where are you exactly noticing in Pega 7 this section being used?
Thanks :)
Accepted Solution
Pegasystems Inc.
US
As Rawap alluded to, the "pyMyProcessActions" section was deprecated in 7.x, and replaced with the newer "pyBulkActionsWrapper" section. If you've upgraded your application to Pega 7.x from a 6.x or earlier version, your portals may still be referencing the deprecated section.
You can review a sample implementation of pyBulkActionsWrapper by logging in as the OOTB administrator@pega.com operator, launching the CaseManager7 portal, and selecting "Bulk Actions" from the operator menu in the upper right.
Hope this helps!
-Kurt
Pegasystems Inc.
GB
Thanks for the input.
Running PRPC 7.2.1 with PEGA SI 7.11 we can see that all portals refer these very old versioned sections in the navigation panel.
The version from the standard P7 portals is fine– the issue was that the SI portals are not updated with the new version.