Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Overview

In this document, we are going to focus on “Search” control and how this functionality allow us to search elements created in DB through the Stored Procedures by checking values in a table or query.

How to create a new “Search” control?

Preconditions

To create a new control, we need to enter on the page that we are going to include this object. Also it’s necessary to connect with out DB through any Stored Procedure previously generated in order to set the parameters in “Search” Control.

Steps

Navigate through the Project’s main dashboard and click on page hyperlink.

Page’s details form page is displayed and we can observe all the Datasets, Controls and Actions associated to the page previously created.

Under the “Controls” section, choose the “Search” option. Wayfast refreshes the screen with the buttons associated to this control.

Click “New” button and popup will prompt with the details to fill in regarding “Search” control. In “General” tab, complete the field name and description.

Turn to “Data Binding” tab and take a look on the settings that you can set to make this new control accurate on what the application needs. This is the most important set of values that we need to establish for this new control.

Field

Description

Dataset

This option gives the ability to load the page with results from a previous query in the Search control

Default value

We can set a default option to search and this should match with the value in the associated Stored Procedure (SP)

AutoSearch

If select “Yes”, we set the Control as parameter in the SP to establish the connection with DB. We make the search shorter by establishing a “SELECT TOP 150” using LIKE % in the SP.

Type

We can choose between the following options:

  • Table: connect with DB

  • Stored Procedure: connect with DB

  • Free: set the SQL query on the fly (not recommended)

  • Cursor Reference: TBD

Fields

Normally we set the first 3 columns on the SP as variables and taking into consideration that AutoSearch required that the Control name itself is set at the first one. Then we can retrieve the description and other value to show in Search.

Columns to Display

In case that the query contains multiple columns, we can select which ones we want to display in Search control

Instance

This will show the instance where the Project is connected to DB.

Execution Type

We can select between the following options:

  • Pre: Recommended

  • Post

  • Ondemand

Data Refresh Binding

In this option, we can establish a relationship with other control that can trigger the Search. For example, we select an option from dropdrown list and then we can display the Search field to make other selection.

On “Layout” tab, we can indicate which is the place, order and alignment for the new control in the Page.

Recap

  • No labels