Link to a Page and Add Page Bindings

Link to a Page

You can add a link to a Construct page within the same or different WebApp using the Link to Page Name property in the column input types mentioned below, enabling users to access the required page with a click. By default, when linking from one page to another, Cloud Construct links the pages using the key fields.

Currently, the following column input types supports the Link to Page feature:

• List

• Number

• Text

• Button

When using the Link to Page setting with column input types other than button, the display text in the field displays with an underline.

Use an existing column in a view, or a count, or a NULL and assign an alias so a Button column type can be added to the page in the Cloud Construct. Buttons can display text or a counter to indicate the number of records on the linked page. You can also execute an event using Buttons. Refer to Construct Events for more information.

Note

• It is recommended to implement the page links in column properties prior to building additional page properties. Testing additional properties on pages that have not been linked within the WebApp cannot be performed during implementation, leaving possible errors undiscovered until later.

• A NULL column with an alias must be added to the underlying view to add a button to a column that does not contain data. The view must be modified before a link from a button can be added.

To link to a page on the above mentioned column input types, complete the following steps:

1. On the Cloud Construct’s home page, edit the required WebApp. The WebApp configuration page is displayed.

2. Access the Grid’s or Form’s node of your required construct page.

3. In the Fields node of the Grid or Form, access the required the column input type mentioned above.

4. From the Link to Page Name list, enter the name of the required Construct page.

5. In the Display Text field, enter the required display text if this field links to another page.

6. To open the link in a new browser tab, turn on the Open in New Tab toggle.

7. To display NULL values as 0 when this column has a link, turn on the Display NULLs as Zero toggle.

8. To add a link to page binding criteria, refer to the Add Link to Page Bindings section below.

9. To pass additional data to the linked page’s container events or list boxes, refer to Add Link to Page Shared Fields section below.

10. Click Save.

Add Link to Page Bindings

Link to Page only links the pages using key fields. However, if the key fields are different between linked pages, identity the key fields on the required views and use the Link to Page Bindings property to link between the pages.

Note

Page bindings pass data values from the source page to the target page, allowing for filtered views when navigating between pages.

For instance, a user clicks a button on a Country page listing country records to access a Region page listing the selected country's regions. If the Country field (the key field) does not have the same name on both pages, the field on the linked from page (the Country page) must be included as part of the page binding criteria. Otherwise, the Region page displays regions for all countries.

Use the table below as a reference to add the required link to page bindings. Either the Source Data Record Field Value or Fixed Value field must be specified.

Click Add to create multiple page binding criteria.

Add Link to Page Shared Fields

Link to Page Shared Fields allows you to pass additional data between grids/forms, list box fields, and the events configured in the linked (target) container. Unlike Page Bindings, Page Shared Fields do not filter records on the target container.

Note

Ensure that the event task configured in the target container includes a variable to store data from the shared source column or value.

Using Shared Fields with List Box Filters

For list box fields, you can use the Dynamic Field option to reference shared field values from a linked page to filter the available options dynamically.

How it works:

1. Define the shared field: Configure a shared field to pass a value from a source page (or parent container) to a target page (or child container). The shared field acts as a bridge between contexts.

2. Configure the filter: In the list box filter configuration, specify a Dynamic Field that references the shared field by name (for example, Country).

3. Runtime filtering: When you navigate from the source page, the system looks up the value of the shared field from the page context at runtime. If the shared field exists and has a value, it is used to filter the list box options. If the shared field is not found or has no value, the filter is not applied.

For example, to filter a State list box on the Region page by passing the Country field that was selected on the Country page:

1. Configure the shared field:

   • Add the Country field as a Source Column in the Link to Page Shared Fields for the target Region page

   • Set the Region page's Country field as the corresponding Target Column

2. Configure the list box filter:

   • On the Region page, in the State list box configuration, add a List Box Filter with the following settings:

     • List Dataset Field: Country

     • Comparison Operator: Equals

     • Dynamic Field: Country (the target column from the shared field)

3. Runtime behavior:

   • When you click a country on the Country page, the Regions page is displayed. Clicking the State list box automatically displays only the states that match the country value passed from the Country page.

Note

You can also use Shared Fields within the same page to pass values from a parent container to filter list boxes in child containers.

Use the table below as a reference to add the required link to page shared fields. Either the Source Column or Fixed Value field must be specified.

Click Add to include multiple shared fields.

Related Articles

• Add a List Box

• Build Assist

• Configure Column Properties

• Working with the JSON Editor