Hi all,
in PEGA 8.5.4 Cloud Platform, Client asked to collect data on a temp context starting from Portal dashboard and, after all required data are collected, to create a new work object. Since temporary cases feature is deprecated, I moved to a custom solution composed by:
-
A new harness launched by user’s portal on click of a navigation menu item.
-
The harness is based on an editable data page where all data are temporary stored.
-
On click of a “Create case” button, a custom js function is launched (see attachments for js code): this function validates all required data and, if validation succeeds, invokes a custom activity to create a new work object and then opens the first assignment.
-
Add custom js style sheet to pega_ui_harness_deferred static bundle.
I used similar configurations to launch activities from js also in other situations with lower PEGA versions and it worked properly. In 8.5.4 it works fine in dev environment, but when I move to a pre-production environment the script doesn’t work (unless i use an admin user from Dev Studio). In the browser console I find the message: “Failed to load resource: the server responded with a status of 403 ()”. I tried to encrypt URL and also supposed the problem could be “Require authentication to run” flag into activity (since I used some non-SSO logged test users), but the problem still exists.
Referring to some documentation I found on PDN, the problem is in the pyBlockUnregisteredRequests when rule that, staring from 8.5.4 version, checks if current environment level is lower than 4 (in lower versions it was evaluating to “Never”). Effectively, performing a test with pyBlockUnregisteredRequests evaluating to never the function works as expected.
Does anyone know another way to let it work without modifying pyBlockUnregisteredRequests when?
Thank you for your support,
Danilo
CustomJS.txt (882 Bytes)
