Grid layout - Presentation tab

Specify a style for the grid. You can select from:

• Default:
• Spreadsheet:
• Transparent:
• Other:

Select one of the following container formats:

• None:
• Default:
• Other:

You can create and modify accordion formats in the skin. See Skin form — Components tab — Layouts — Grids.

Select this check box if you want to set a fixed pixel size for the grid. Specify the grid width and height in the fields that display.

Displays when you select Fixed (pixel) size grid.

Specify the grid height in the field that displays.

Select if you want to sequentially number the rows in the grid.

Select if you want an OnHover style for rows, changing the appearance of a row when the cursor hovers over it. You can set the hover text and background color in the Skin rule.

The UI Gallery contains working examples of Row Hover. To view and interact with samples, select > User Interface > UI Gallery. In the Tables & Grids area, select Grid. In the See Also column on the right, select Row Actions.

Select this option to make your grid responsive. Once this property is set, you can specify which columns of the grid should be displayed when the available screen width is reduced, according to the responsive breakpoints you set in the skin. In this section or harness, after closing this panel, you should specify the importance of each column. See the Column Properties Importance settings (below).

You set the responsive behavior for your grid columns in the skin. Skin form - Components tab - Layouts - Trees & grids

Check this box to override the default presentation when a grid is empty. You can:

• Select the Section option and enter the name of your custom section.
• Select the Field Value option and enter the name of your custom field value.

Alternatively, you can save a customized version of the pyGridNoResultsMessage section or GridNoResultsOnLoad field value into one of your application rulesets.

Check this box to override the default presentation when your filter criteria yields no matching results. You can:

• Select the Section option and enter the name of a custom section.
• Select the Field Value option and enter the name of a custom field value.

Alternatively, you can save a customized version of the pyGridNoResultsMessage section or GridNoResultsOnFiltering field value into one of your application rulesets.

These are the properties for your grid columns that you open by selecting the small circle in a column instance.

• Width — Specify a column width in pixels.
• Inline style — Optional.
  As a best practice, define custom styles in the skin.
• Importance — The options are:
  • Primary — Only one column can be marked as Primary, and this column must be to the left of all secondary columns. The primary column of a grid is always displayed.
  • Secondary — You can mark as many columns as you want to be Secondary. They are all appear right of the primary column. If the grid is reduced to a one-column flat list, the secondary column contents appear in their respective primary column cells.
  • Other— This is the default setting for a column. The Other columns can appear left or right of the primary and secondary columns. These columns are dropped from the grid or hidden (depending on your skin settings) when the screen size is less than a responsive breakpoint.

When you plan to localize the application using this rule, so the application can support users in various languages or locales, choose the text carefully and limit the length to no more than 64 characters. When practical, choose a caption already included in a language pack, to simplify later localization. A field value rule with this text as the final key part is needed for each locale. See About the Localization wizard.

Optional. Clickto open the Image Library landing page and select an image to include on the left side of the header.

If you want to display a tooltip when the user hovers the mouse pointer over the icon, type a text string within quotations, for example, "Select to view list".

Optional. Leave blank to present the body always. To control visibility of the body, enter or select one of the following:

• The When Name key part of a when condition rule. Click() to review or create the rule.
• Simple expression based on the comparison of a pair of constants, properties, or both, combined by Boolean operators, such as .Color="Red". You can combine the expression with a when condition rule or another expression using the && and || operators.

As a best practice, use the Condition Builder to edit this field. Click( ) to open the tool. See Using the Condition Builder to configure dynamic UI actions.

Appears when you select Conditional Visibility and enter a simple expression in the field that displays.

Select the Run visibility condition on clientcheckbox to cause dynamic execution of the condition each time the value of a property stated in the condition changes.

Conditions are automatically re-evaluated when the user updates a property value. By default, controls that allow typing, such as Text Input, are evaluated when the user leaves the field. To re-evaluate conditions as the user types, use the Apply Conditions action with a Keyboard event. See Control Form — Completing the Control tab.

Optional. Choose this option to delay loading at runtime of the section content until the user clicks the header. Deferring enables users to start using other parts of the page rather than waiting for this section to load.

To enable users to take actions, such as submit, on a work item while other content is still being loaded, configure sections to use defer loaded asynchronous declare pages. See PDN How to configure non-blocking UI using Asynchronous Declare Pages (ADP).