Peer Review Component Questions
Your questions and suggestions related to the Peer Review Component are welcome here.
FAQ:
Q: What Pega Platform versions are supported?
A: Pega Platform 8.4 is supported at the moment.
Optum
US
Hi,
can we get this feature as a backward compatibility for V81,V82,V83? Thanks,
Ravi Kumar.
MD Cloud
CY
Hi Ravi Kumar,
Thanks for your interest in Peer Review component.
Unfortunately product archive can't be installed to the lower platform version ....
We are checking if there any workarounds available; I'll update you in case of any solution available.
Thanks, Oleg
Citizens Financial Group
US
@lapso Any update on whether a workaround is available for lower versions of Pega 8 ? we are on Pega 8.2 and interested in having a peer review component
WellsFargo
IN
Can we have any kind of notification feature? When a reviewer complete the code review and if there any question/fixes a reviewer should have a option to send a notification to developer and vice versa when developer completes all the fixes.
Today using the peer review component we have to send email manually or reach out to developer that the code review is complete.
Thanks,
Suman
MD Cloud
CY
Hi Suman,
That's a reasonable question and we got number of similar requests already, thus we are implementing email notifications already. It would be available in the next version; I hope it would be released next week. Please subscribe to the anouncement page (https://collaborate.pega.com/discussion/peer-review-component-announcements) to get informed about the release.
Thanks, Oleg
WellsFargo
IN
Awesome. Thanks for the reply.
MD Cloud
CY
Hi Suman,
Please find Peer Review Component Version 8.4.6 on the PegaMarketplace: https://community.pega.com/marketplace/components/peer-review-component
It supports email notification when review process stages change.
Thanks, Oleg
WellsFargo
IN
Hi Oleg,
Chrome is restricting the latest version to download? I am facing the same issue in my office and personal laptop. Could you please check?
Thanks,
Suman
Updated: 9 Oct 2020 14:03 EDT
MD Cloud
CY
Hi Suman,
Thanks for letting know!
It's resolved now.
Thanks,
Oleg
MD Cloud
CY
Hi Suman,
As a workaround you can select "Keep" action on the Chrome warning to complete download.
Thanks,
Oleg
Sun Life Financial Inc
IN
Hi,
Do we ootb reporting for Peer review?
Reporting for:-
What kind of comments are left - is there any report?
What kind of review is done on the rules ?
MD Cloud
CY
Hi Sandeep,
Thanks for the good question.
Component is keeping review data so it's available for the reporting.
There is no OOTB reporting at the moment due to the missing requirements.
Could you please share details about your case? What are you trying to achieve?
Thanks, Oleg
WellsFargo
IN
Hi Oleg,
Regarding reporting below are our requirements
1) Every sprint we need to generate a report of all code review comments and publish it to management
2) Today there are no reports if I have to go back and look the review comments per user story , basically I am looking for a history of all code review comments
3) For a review case , it would be great if we can have additional parameter to hold the sprint name
Thanks,
Suman
Truist
US
@Suman Palukuru - Hi Suman, did you find any solution on this requirement? we do have the same requirement. Please let know if you have any solution around this to get the Report of all code review comments for each Branch before merging into actual ruleset version.
Thanks,
Balaji
ING Bank N.V.
NL
@lapso One question : If a Developer A assigns a review to another Developer B, until the review is complete, A should not be able to do anything with the branch. But I see that the developer can unlock , and merge the code , even if there is a pending review for it.
Can this be addressed in the next release ?
MD Cloud
CY
@VTALUKDAR Hi Victor,
That's an interesting idea, thanks for sharing.
It seems that merging and corresponding restrictions are already covered by Pega Platform:
As you mentioned branch can be locked to reduce a chance for an unwanted change.
Deployment Manager allows to enable check for review completion on a branch:
https://community.pega.com/knowledgebase/articles/devops/85/adding-pipeline-premises-0 (step 15)
https://community.pega.com/knowledgebase/articles/devops/85/check-branch-review-status
Please note, that Peer Review Component would show changed rules even if they were reviewed before the change.
Thanks, Oleg
Self
US
@lapso Firstly I would like to congratulate your team for such a awesome feature which I have been looking for a while. Thanks!
As a reviewer of a rule, I dont see a way to set a review status 'Todo, Ask..etc' - the split button is missing. I am on 8.5.3 platform and 8.5.7 of component. 
MD Cloud
CY
@DhananjayU Hi, thanks for the feedback!
The rule on the screen is checked out and that's probably a reason why the review actions are not available.
Please check in the rule to ensure that review actions would be displayed.
Thanks,
Oleg
Self
US
@_OLAP_ Thanks for the response. I think the root cause was an old branch review existed for that branch before the component application was installed. I tried with a new branch and I see Review split button rightly getting populated even when the rule is checked out/private checked out.
Self
US
@lapso Also wanted to get your thoughts on best practices. The OOTB one looks very minimal and I believe the expectation is that senior resources customize it as per their application. Was looking for some security around the Edit button- can we do something without overriding your section.
MD Cloud
CY
@DhananjayU That's right, it's a tool to capture project specific best practices. The aim is to get rid of external tools like WIKIs and to keep best practices in Pega close to the work context.
Senior resources do provide initial guidelines typically, however best practices are expected to become a common team's responsibility. Common WIKI pages are not restricted typically and we used the same approach keeping snapshots in a history for an incident cases.
I hope this would work for you.
Thanks, Oleg
Empower Retirement
IN
Hi @lapso,
We have added the peer review component in the application and we can see that the Data-Rule-BestPractices datatype instances are empty and the best practices are not showing up in the rules history tab .
Is there any way to get the CSV file for this data type so that we can import in the application.
Pega Version :8.4.4
Thanks
Mithun
MD Cloud
CY
@Manash_LSA hi,
Thanks for the question, Current version is fully compatible with Pega 8.7
Thanks,
Oleg
Truist
US
Are there any updates regarding reporting requirements,
1) Every sprint we need to generate a report of all code review comments and publish it to management for Audit purposes.
2) Today there are no reports if I have to go back and look for the review comments per user story, basically I am looking for a history of all code review comments even after the code review branch has been merged into actual ruleset version.
Thanks in advance!
MD Cloud
CY
Thanks for the follw-up.
Could you please suggest how do you manage what was part of the sprint for audit? Are you using Agile Workbench?
Thanks,
Oleg
Wipro Technologies
GB
When is the peer review component for 8.7.5 version of Pega to be made available?
will the current version of Pega Peer review component be available for use in Pega 8.7.5?