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 label incorrectly returned under control node for DX API



The label (text on the button) is returned on the label key in the Control node instead of the parent field node of the DX API GET service assignments/{id}.

For example, verify the 'label: setValue-Refresh' under 'control' (incorrect, due to Localization) and 'label: Knop' under the parent type.

The requirement is for the Label key value pair of the  button to be a part of the parent Field node.

Consider another control such as TextInput which is set in the parent field node (Rekeningnummer in Dutch is Accountnumber).

At the minute, the label in the parent node Field for a pxButton is hardcoded to the button and due to Dutch localization is displayed as 'Knop'.

Error Messages

Not Applicable

Steps to Reproduce

  1. Call the DX API GET service that returns an assignment with a button control and a label.
  2. Catch the response of the Pega application.

Root Cause

An issue in  the custom application code or rules.
The DX API responses are designed such that the button labels must be present in the Control node.


Here’s the explanation for the reported behavior:

The buttons have two labels, one label that can appear above the button and the other that can appear in the button (similar to the desktop).

Almost all the elements have a label that can be at the top, left, etc. (that is, the field label) and the elements are populated in the Field node. For elements that have an additional label (button, checkboxes, etc.), they reside in the 'Control' and the 'Control node' because they belong to the control.

Published August 19, 2019 - Updated December 2, 2021

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