Peer review component- pyID and pzInsKey are missing when Notification "pyAddReviewer" is sent
HI Team, @MARIK1
We are trying to use Pega peer review component version 08.83.09 as part of our POC. There is a issue we are facing with notifications as below.
steps to reproduce:
1. Create a branch with few rule.
2. Create a code review task for the branch by selecting one reviewer.
3. Login with the reviewer operator, and check for notifications in the notification gadget.
4. Click on the notification and try to open the branch review workobject from portal. It throws error unable to open work object due to missing pzInsKey.
Analysis:
On tracing we found that the pzInsKey and pyID is missing in the Primary page when pxNotify is called from pzSendEmailToReviewers activity. All the rules are final and we are not able to extend this.
Can some recreate this scenario and let me know if its a known issue and will be fixed in upcoming release?
Thanks .
Khusbu choudhary
Pegasystems Inc.
DE
@KhusbuC , hi! thank you for using Peer Review component. As far as I can tell, the scenario you describe was implemented out-of-the-box and wasn't alternated by the component. We have tested the email notifications, but never looked at the notification widget.
Could you elaborate the use scenario? Why and how are you using notification widget in the Dev Studio? Which process it supplements and how it normally flows? We might add this scenario to the backlog for the next release if we understand it better.
PS: sorry for the delayed reply. It is due to the vacation period :)
Aaseya IT Services Pvt Ltd
IN
@MARIK1 Thanks for your response. I have sent you an email with all the necessary details.
Regards,
Khusbu Choudhary