Closed
Bug fix for Existing requestor retrieved?
Do we know when we can expect the fix for Bug-311189, as mentioned in SA-39642?
***Edited by Moderator Marissa to update platform capability tags****
This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.
Do we know when we can expect the fix for Bug-311189, as mentioned in SA-39642?
***Edited by Moderator Marissa to update platform capability tags****
HI,
I just checked it for you.
Bug-31189 issue was found in Release Pega 7.2.2 and it is fixed in Pega 7.3.1.
If your application is on Pega 7.3.1, it should have the fix.
Thanks,
Susan
Hi Susan,
Do we have a hotfix for this issue in 7.2.2?
Hello Anoojit,
There is no available hotfix for this in Pega 7.2.2. This has been fixed in Pega 7.3.1 as an enhancement.
Thank you,
Shreshta
Hi Shreshta,
How do we resolve this issue?
Thanks
Sreekanth
Hi Shreshta,
same question here. Will the fix be ported to 7.2.2? I assume more customers are working on 7.2.2.
Regards,
Maurice Boer
Please note that a Hfix is not available for this Bug since Hfixes are for serious product defects whereas this Bug fix is cosmetic in nature. "Last input" field is typically populated with useful information that helps end user to analyze where the issues lie. This field does not hold value in the context of PEGA0069 alerts and hence contained "existing requestor retrieved" message. Therefore, to resolve this bug, we will not output any data for the "lastInput" field for any PEGA00069 alerts.
Question Solved
Question Solved
Question Solved
Question Solved
Question Solved
Question Solved
Question
Question Solved
Question
Question
Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.