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

Button in repeat layout on refresh section has incorrect DOM ID



Buttons in a repeating layout are meant to have incremental IDs to make them have distinct actions applied per row. However, when a user applies an onClick > "Refresh this section" action, the ID does not recognize that it is in a repeating layout. The ID of the Document Object Model (DOM) that is given after the refresh is no longer distinct. This affects triggering CSS styles. The screen design uses CSS 3 hover and focus styles. After a button's onClick > Refresh this section action, the CSS styling is applied only to the first element. Hovering over the second label will highlight the first label because it is for SamplePropertyName.

Error Messages

Not Applicable

Steps to Reproduce

Apply an onClick > Refresh this section as an action to rows in a repeating layout.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code or rules.

In repeating layout, the field control's ID is not incremental. It points to the property name. Here's a conceptual example of rendered HTML to explain the defect:

<div class="content-item content-sub_section item-1 base_ref=".SampleRecord(Key1)">
<input id="SamplePropertyName" name="$PpyWorkPage$pSampleRecord$gKey1$pSamplePropertyName" data-click="..." />
<label for="SamplePropertyName" data-hover="..." />
<div class="content-item content-sub_section item-2 base_ref=".SampleRecord(Key2)">
<input id="SamplePropertyName" name="$PpyWorkPage$pSampleRecord$gKey2$pSamplePropertyName" data-click="..." />
<label for="SamplePropertyName" data-hover="..." />


Apply HFix-21289.

Published May 25, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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