Adding links to IQA results

IQA lets you design search results that contain live hyperlinks within the items that it returns. Using the Link feature on the Display tab, you can create hyperlinks for multiple columns in your query results. These links let users immediately click through to the records and content that they are seeking. In this example, users can click links to open specific contact profile and product pages.

You add the links while you are editing a query. In Advanced mode on the Display tab, populate the Link field with parameters to generate the custom link. The link must have one of the forms listed in the guidelines below.

Combining Link strings with Alias variables lets you create powerful queries that open the details that your users need. This is how Alias and Link values relate to the query results:

For steps to set up a similar query, see Example: Display completed orders.

Note: Where contact ID links go differs by platform. On your site, contact ID links open that contact’s page (~/Core/AccountManagement/Impersonation.aspx).

  • To build a link, you must first indicate whether it should point to a shortcut URL, a content record (ContentCode), a navigation item (NavigationCode), or an ASPX web page. Shortcuts and content record links display the published content record within an iMIS website, regardless of the sitemap definition. Links to a navigation item take the user to a particular page within an iMIS sitemap.
    • ~/MyShortcut – For the given property, a link is established to the shortcut specified (shortcuts are defined in Site Builder > Manage shortcuts). For example, if you want to link query results to a Products shortcut you have defined, then enter ~/Products.
    • ContentCode=MyContentCode – For the given property, a link is established to the content identified by the ContentCode value. For example, if you want to link query results to a product page content record that has a Content Code of Specials, then enter ContentCode=Specials. To define or edit a Content Code, go to Page Builder > Manage content, edit a content record, and expand the Properties tab. 
    • NavigationCode=MyNavigationCode – For the given property, a link is established to the navigation item identified by the NavigationCode value. For example, if you want to link query results to a profile page’s navigation item that has a Navigation Code of ProfilePage, enter NavigationCode=ProfilePage. To define or edit a Navigation Code, go to Site Builder > Manage sitemaps, edit a navigation item, and expand the Properties tab.

      • Note: If the Link includes both a ContentCode and NavigationCode, only the ContentCode is used to build the link.

    • ~/Webpage.aspx – For the given property, a link goes to an ASPX web page, relative to the root of your website. By default, the root corresponds to C:\Program Files\ASI\iMIS\Net. For example, ~/Party.aspx. For more information, see Using redirector pages.

      • Note: Party.aspx is a sample redirector page shipped with iMIS that checks the user’s permissions to determine which content record to display. To see a sample query that uses this functionality, from IQA open $/ContactManagement/DefaultSystem/Queries/Directory/People search.

  • Using URL parameters, you can control the data displayed on the target page if it contains a content item that accepts such a value. The URL parameter can either be hardcoded to a specific value or it can be dynamically generated based on the value of a particular Property or Alias of the query. You can add multiple URL parameters to the Link, separated by ampersands (&). URL parameters should be in the following form:
    • &URLParameter1Name=[PropertyName] – Dynamically builds the link based on the value of the specified query property. When referencing a query property, do not include any spaces. For example, if you want to set the URL Parameter iProductCode (used by the General Product Display content item) to the Product Code property value, enter &iProductCode=[ProductCode] (no space between Product and Code). By combining this example with the Shortcut example, you can build a link that opens the shortcut populated with the product in the query results. The full Link would look like: 
      • ~/ItemDetail?iProductCode=[ProductCode]
    • &URLParameter1Name=[Alias Name] – Dynamically builds the link based on the value of the specified Alias. If you want to create a link for a query property and you have given it an Alias, then you must reference the Alias name in the Link, not the Property name. For example, if you want to set the URL Parameter ID (used in several contact content items) to an ID property value in the query results, and you have given that property an Alias name of iMIS User ID, enter &ID=[iMIS User ID]. By combining this example with the NavigationCode example, you can build a link that opens a particular user’s profile page. The full link would look like:
      • NavigationCode=ProfilePage&ID=[iMIS User Id]
    • &URLParameter1Name=URLParameter1Value – Sets the URL parameter to a hardcoded value in all of the results.
  • Any properties used to build links must be selected for display in the query (Display tab). However, you may not want a user to see values for all of the properties required to build the links. You can hide columns from a user by giving the property an Alias prefaced with code_. In the previous example screenshot , the Full Name column uses the value of an ID property to build the links, but the ID property is hidden by giving it an Alias of code_ID.
  • If you get an error message after clicking a link in your query results, check your link entry for the following:
    • If you have an opening bracket, you must also have a closing bracket [  ].
    • If you provide an Alias for a property, then the original property name is no longer usable in the Link field. The Alias always overrides the original field name and will be the only column name available for reference in the results.
  • If your query result links do not work as expected, try the following troubleshooting techniques:
    • If possible, find a place in iMIS where the target page is correctly displayed and compare the URL parameters that appear for that page to the ones you have identified in the Link text field.  Are there additional parameters required that you have not provided? 
    • Add the query to a content record in your website, so that you can view the query results like an end user would. After clicking a linked query result, examine the URL in your browser. Compare it to the Link you have built in IQA to determine if the URL is incomplete and if it contains everything you intended.