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

Image not getting disabled in grid when condition is set



User has added Disabled When Expression in grid for Add Item icon. When condition is met, image is not getting grayed out though Add Item Action functionality is working as expected.

Error Messages

Not Applicable

Steps to Reproduce

1.Add Icon with image source in grid action button.
2.Put Disable When Expression as when rowno = 3 disable the icon.
3.Run case.
4.Add three rows.
5.Observe though user is not able to add more rows, but still image is coming as if enabled.

Root Cause

A software use or operation error :

User has replaced Out-of-the-box (OOTB) Pega7 icon that is "pyGridIcons.png" with pzAddIcon png to get pre-pega7 AddItem look and feel.

With OOTB configuration it is using position value to find correct image from the source png and display same.

Since user has hardcoded AddIcon, though disable attribute is appended to DOM at runtime, also user is unable to add new row at this point of time (expected behavior), but image is not grayed out making an impression that it is still clickable.


Perform the following local-change:

Instead of hard-coding the addicon image in Icon source use "pyGridIcons.png" with position 1 for pega7 icon or use "pzmainiconsprite.gif"" with position 34, to get Pega6 style add item.

With this based on disable option, appropriate image will be rendered (that is the grayed out one).

Published August 22, 2017 - 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