Not sure what went wrong. because this a general exception which we will get in lot of scenarios.
But if you are not able to access the system completely. Then raise SR ticket to do DB restore, give the timestamp before the deployment (when system was accessible last) to Peag SR team. They will do the complete DB restore and then you will be able to access the system,
Posted: 9 months ago
Posted: 7 Feb 2023 22:47 EST
Mandeep Rawat (MandeepRawat)
Bits in Glass
Senior Software Engineer
Bits in Glass
@Gunasekaran_Baskaran we have fixed the issue. Dev team had modified the default browser requestor with new access group pointing to a application and during the deployment that application rule instance got corrupted(having component mappings which were not in our testing environment). Due to this all the applications in this environment started facing this issue. we resolved this issue by using prpcUtils.sh provided by pega. we corrected the browser requestor type and deployed the code using this utility after that we used another applications dev access to correct the application rule. Now it is working fine.
Posted: 1 month ago
Updated: 1 month ago
Posted: 19 Oct 2023 10:49 EDT Updated: 19 Oct 2023 10:50 EDT
sowjanya seelam (SowjanyaSeelam)
Specialist - Package Implementation
@SowjanyaSeelam we had created a product rule in our dev environment and deployed the zip using the prpcUtils to our effected QA environment. and once we were able to login we corrected other rule level issues.