Question
IN
Last activity: 29 Mar 2018 4:56 EDT
Error appears in tracer but not on screen
Hi Team,
I created a section which is embedded in a harness and on click of a button in section an activity is triggered.
The primary page is pylanding. Now upon clicking a button in section i validate and set error in activity using page set messages,the error appears on pylanding in tracer but i dont see it in screen. When i screen refreshes a red color error messages appears and dis appears. please help
PFA document.
***Updated by moderator: Lochan to add Categories***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
In Section/Harness try to include OOTB pyDisplayErrors(@baseclass) and let me know the outcome. The issue you are seeing is probably because refresh section/harness is getting called.
Also, check in tracer what is the steps executed after fail messages in tracer.
IN
I did it you can see in my screen shots, there is a empty layout. And yes i kept refresh action on the update button
IN
I tried by removing refresh , its not working still.
J.P. Morgan Services India PVT Ltd
IN
Hello,
In the harness we have the option to always show the error checkbox, can you make that true and check the behavior.
Also is the behavior consistent in all the browser,? pls check,
IN
yes that's enabled . PFA document.
J.P. Morgan Services India PVT Ltd
IN
hello,
is this an upgraded environment?
pls check out this SA Article:
IN
Ahh ok let me try the script mentioned . I will get back to you. Thank you Neha
Pegasystems Inc.
IN
Hi Pavani,
Which version of Pega you are having is it 7.1.7 /8 /9 ?
Check the Harness which you are using , i mean to say the perform harness , just try with the OOTB perform hanress once.
Is the issue is a flickering issue (i.e the error mesage is appearing and then quickly disappears ?)
IN
Hi Sahu,
I am using 7.1.8. I placed the section in my custom harness as shown in above attachment. Yes its flickering issue. Any idea how to resolve this?Please suggest.
Pegasystems Inc.
IN
Hi Pavani,
Seems to be a BUG but not sure . Try the local chnage in the user workform if it is not working then you may raise SR mentiong a BUG id BUG-195424 which closely resemlbes with this .
<script>
pega.u.d. handleErrorAfterPartialSuccess = function (responseObj) {
Hi Pavani,
Seems to be a BUG but not sure . Try the local chnage in the user workform if it is not working then you may raise SR mentiong a BUG id BUG-195424 which closely resemlbes with this .
<script>
pega.u.d. handleErrorAfterPartialSuccess = function (responseObj) {
var errors = false;
var reloadElement = responseObj.argument[0];
var newStream = responseObj.responseText;
var documentFragment = document.createDocumentFragment();
var newElement = document.createElement("DIV");
newElement.style.display = "none";
documentFragment.appendChild(newElement);
/*If the response has PEGA_GRID_DELETE||DELETE_SUCCESS|| delete is successful. So, return false. BUG-46793*/
if (newStream.indexOf("PEGA_GRID_DELETE||DELETE_SUCCESS||") != -1) {
errors = false;
} else {
errors = true;
}
newElement.innerHTML = newStream;
var errorTable = pega.util.Dom.getElementsById('ERRORTABLE', newElement);
/* SE-33005: Additionally check the formErrorType before displaying the form errors */
if (errorTable && pega.u.d.formErrorType) {
pega.u.d.displayFormErrors(pega.util.Dom.getOuterHTML(errorTable[0]), newElement);
return errors;
}
/*Don't check for field errors for custom error section*/
pega.u.d.handleFormErrors(newElement);
var customErrorDiv = pega.util.Dom.getElementsById('pyCustomError', newElement);
if (customErrorDiv && customErrorDiv[0]) {
/*customErrorMsg span is generated only when there are messages on the page. Only in this scenario return true.*/
var errorSpan = pega.util.Dom.getElementsById('customErrorMsg', customErrorDiv[0]);
if (errorSpan && errorSpan[0]) {
return errors;
}
}
return false;
};
< /script>