Skip to main content

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.

Question

6
Replies
347
Views
 Ganesan Senthilkumaran (Ganesan_Vizient) Vizient, Inc.
Vizient, Inc.
US
Ganesan_Vizient Member since 2016 1 post
Vizient, Inc.
Posted: March 16, 2018
Last activity: June 18, 2019
Posted: 16 Mar 2018 16:13 EDT
Last activity: 18 Jun 2019 16:00 EDT
Closed

Bug fix for Existing requestor retrieved?

Report

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****

System Administration
Posted: 5 years ago
Posted: 16 Mar 2018 18:15 EDT
Susan Liu (SusanLiu_GCS) PEGA Senior Principal Engineer, Technical Support, Runtime Engine
Pegasystems Inc.
US
Report

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

 
Posted: 4 years ago
Posted: 15 May 2018 15:43 EDT
Shreshta Vinayak (vinas) Technical Solutions Engineer
Pegasystems Inc.
IN
Report

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
Posted: 4 years ago
Posted: 12 Feb 2019 16:50 EST
Sreekanth PeddyReddy (SreekanthReddy2010) FaceBook
FaceBook
US
Report

Hi Shreshta,

How do we resolve this issue? 

Thanks

Sreekanth

 

 
Posted: 4 years ago
Posted: 18 Feb 2019 1:54 EST
Maurice Boer (MAURICEBOER) Nationale Nederlanden
Nationale Nederlanden
NL
Report

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
Posted: 3 years ago
Posted: 18 Jun 2019 16:00 EDT
Vipin Kumar (DHEER_GCS) PEGA Director, Technical Support, Cloud Service
Pegasystems Inc.
US
Report

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. 

We'd prefer it if you saw us at our best.

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.

Close Deprecation Notice