Skip to end of banner
Go to start of banner

Lookup Control

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 12 Next »

Lookup Control is a component used for displaying data in a tabular format and comes with various configurations for data manipulation and presentation. It is used for displaying and searching for EmpowerID objects.

To view it in the EmpowerID Web User Interface, you must place it within a workflow.

This is how a lookup control looks in Workflow Studio.

Grid Columns

  • Grid columns are properties of your object.

  • Their labels can be localized strings.

  • You add columns using the “Lookup Designer” menu.

  • Columns can be added individually or as a group by selecting pre-defined “Grid Types” – these are xml definitions stored in SQL for common scenarios.

  • Grid columns can be reordered by grabbing and dragging them.

  • Grid columns can have “Value Formats” assigned to render dates or checkboxes, etc.

When click on Lookup Designer → New Column a Field Selector dialog box will appear.

  • Use the Value Format property to render the field in different formats.

  • Use the Label property to set the column name.

  • Use the Field Name property to show the data in the particular column.

Edit Search Criteria

• Many methods support Advanced Search
• Fields added must be searchable / indexed

IsAdvanced Search Enabled

If this checkbox is checked, then you can do searching on the columns that have been added in the Edit Search Details dialog box see above image. You can add more columns to the search criteria by clicking on the Add New button and can remove any column from the search criteria by clicking on the Remove button.

Use Search Terms

SearchTerms is a “generated” field with advanced logic to aid searching and should be used whenever present.

Enable Custom SQL

When Enable Custom SQL Search what it will do, it will enable advanced SQL Search and it will ignore other search criteria, it will also ignore the method configuration. Assume that the component will have a hardcoded name

Queries must begin by returning the GUID and FriendlyName of the objects or they will fail when compiled.

  • No labels