delete icon missing in System Runtime Context
Hi,
Delete icon is missing in System Runtime Context gadget in Dev Studio. I am using 8.6.0. However, I have seen other system screen (8.6.4) and delete icon was there. Are there any conditions for the icon to appear? Or, is this simply a bug? If this is a bug and already fixed in a patch release, can anyone indicate the item in the Resolved Issues (https://docs-previous.pega.com/pega-platform-patch-releases-resolved-issues-download)?
Thanks,
***Edited by Moderator Marije to add BUG Details; ***
Accepted Solution
Updated: 3 Aug 2022 11:43 EDT
Pegasystems Inc.
JP
You are correct, this is a bug. And it is already fixed by patch release (8.4.6, 8.5.4, and 8.6.1). Your workaround is completely valid, but it is also a good practice that you apply the latest patch release.
Updated: 2 Aug 2022 7:30 EDT
Infosys Limited
IN
Please check if your access group has the access role: PegaRULES:SysOpsAdministrator / PegaRULES:SysAdm4 which has the Rule-Access-Role-Object to the class: Pega-Landing-System-RuntimeContext with the privilege: pzCanEditSRC.
Also check if the when rule for the visibility on the delete icon: pyIsNotMTOrIsShared is returning true with the mentioned conditions in it.
Updated: 2 Aug 2022 19:57 EDT
IT Solution Service
SG
I do have both PegaRULES:SysOpsAdministrator access role and PegaRULES:SysAdm4 equivalent role. I have an access to pzCanEditSRC as well. So isn't this a bug?
IT Solution Service
SG
No, this is not about visibility. Even when I private edit pyIsNotMTOrIsShared when condition to return always true, delete button won't appear.
If I give pzCanEditSRC privilege in Embed-AppInfo class, it works. Last time I gave pzCanEditSRC privilege in Pega-Landing-System-RuntimeContext class but that one does not work.
In summary, neither of SysAdm4 and SysOpsAdministrator has pzCanEditSRC privilege in Embed-AppInfo class in 8.6.0. This is a bug, isn't it?
Thanks,
Accepted Solution
Updated: 3 Aug 2022 11:43 EDT
Pegasystems Inc.
JP
You are correct, this is a bug. And it is already fixed by patch release (8.4.6, 8.5.4, and 8.6.1). Your workaround is completely valid, but it is also a good practice that you apply the latest patch release.
IT Solution Service
SG
Thank you!