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.

How to include a property value in a layout tab

Suggest edit Updated on May 3, 2020

Summary

 

Optionally, in a work object form, you can present the value of a property in a tab, in addition to the text label of the tab.

Suggested Approach

  1. Open the Harness rule. Access the Layout tab. Select and drag the Tab control ( Tab control) from the Layout group.
  2. Click the SmartFrames wireframes tool (Wireframes ) to make wireframes visible. Click the magnifying glass next to the tab to open the Container panel.
  3. On the Container tab, set the Header value to StandardHeader. On the Header tab, confirm the Layout type is Tabbed. Enter a caption for the tab in the Title field.

Container

  1. Complete other Container panels as desired. Click Apply.
  2. Determine which property value you want to appear in the tab. Select a control (for example, Input Field) from the Basic group. Drag and drop it into the single cell to the right of the tab caption text.
  3. Click the magnifying glass icon next to the control you dropped. Complete the Cell Properties panel to identify the property and its presentation. On the Conditions tab, select the Read Only check box. Click Apply. In this example, the property pyAgeFromDate is presented using the Date-Short HTML property rule. Click Apply to close the Cell Properties panel.

Cell Properties

  1. If your harness rule will contain multiple tab containers, repeat this process to add properties to other tabs, if desired.
  2. Complete other parts of the harness rule. Save the rule form.
  3. Test. At runtime, the property value appears in the tab.

Runtime

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us