Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

PUIC: Harness error messages are displayed with empty space

SA-3682

Summary



1. When there are any validation errors on the screen, these error messages are displayed along with empty white space underneath that errors table.
2. In the harness on ‘Display Options’ tab, ‘Always show form-level errors’ checkbox is unchecked. Hence, it is expected that harness errors are not displayed where there is validation failed.
3. It is observed that ERRORTABLE table/div is getting created after submit and when there are error messages irrespective of whether the "Always Show" checkbox is checked or unchecked.

Error Messages



No error messages.

Steps to Reproduce

  1. In the perform harness, uncheck "Always show" checkbox under Form level errors. 
  2. Select Top of Harness option for Display errors. 
  3. On submit, set any error messages either by validation rule or Page-Set-Messages.
Observe, these errors getting displayed with white space underneath the Error-Messages table. Space increases if error messages increases as table height will be increased.

Root Cause



This problem occurs because the position of form-error-marker's div is set to static. 


#FormErrorMarker_Div.yui-overlay { 
position:static; 
}


Removing position static fixes this issue. Already fixed in ML7 with same code.

Resolution



The modified code is patched inside HFix-10348. This hotfix is tested and it resolves the issue of extra empty space generation below the error messages table.

Before applying the hotfix (Empty space below error-message table):




After applying the hotfix (No empty space below error-message table):



 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us