Configure Browse Sequences

This instruction explains how to configure specific browse panels.

M3 contains three browse options that can be used for fields with user-defined values:

This instruction covers the 'Configurable browse' option, which supports all the capabilities of the 'Custom list' in (CMS010) including related tables, virtual fields etc.

Outcome

A user-defined browse panel is created for a specific scenario. This is displayed when function key F4='Prompt for searching' is used in that scenario, instead of the classic browse panel.

Follow these steps

Configured browse functions are configured through (MNS175) and uses the list defined in 'Information Browser Category. Open' (CMS010).

Note: For best performance, avoid using too many related tables and virtual fields to retrieve information.
  1. Launch (MNS175). This setup defines the scenarios in which the configured browse panel replaces the classic browse panel.

  2. Complete these fields:

    • Table: Must match the table used by the classic browse. Normally the 00 version of the table is used. Use function key F5 in classic browse to see the table used in the browse. See details in step 3.
    • Program: The specific program to be used by the configurable browse function.
    • User: The specific user able to use the configurable browse function.
    • Field Browse Variant: Enables multiple configurable browse functions to be used. The user can toggle between them by using the Function key F7 in the browse panel.
    • Description: The description of the browse function. For example, 'Search for items with warehouse filter'.
    • Name: The name that identifies the browse function.
    • Information category: This must have the 'Used by program' field in (CMS010) set to 'CMS990-Search browser'. The Information category has no relation or validation to the table defined for when it is to be used. For example, a browse function could be set up to browse the item master, but the browse itself could be set up to display information based on the item/warehouse. This means that any information can be used in the browse function, so long as relevant information can be returned to the calling program, for example, the item number. Another example might be using order statistics to browse for sold items.
    • Sorting order: Defines possible filters to be used as well as the columns to be displayed.
    • View: Defines the columns to be displayed.
    • No. filters: Optional. Normally, filters are preset to a value, but they can be defined. For example, a warehouse can be filtered by the standard warehouse from the user master table for the currently logged-in user.
    • Return field: The field to be returned in the search, for example, 'Item number'.
  3. The classic browse function can be used to simplify the setup when deciding which table to use in (MNS175), as follows:

    1. Launch the classic browse in the program and field where the new browse is to be used.

    2. Click Refresh in the classic browse panel.

    3. The table used by the prompt is displayed as either a popup message, or at the bottom of the screen, depending on the UI settings.

    4. Use this table reference number in the (MNS175) record.

Using the Configured Browse Panel

When a user-defined browse panel is created for a specific scenario, it is automatically displayed unlike the classic browse panel where the function key F4 is used.

Using search in the Configured Browse Panel

The full search functionality available throughout M3 BE can be used in configured browse.

An additional search is also performed, based on the value sent from the program when selecting the browse feature. This search always adds a wildcard to the entered value. This enables you to start typing a search query in the field in which you are browsing.

For example, a browse is configured on the 'Item number' field in the function for the item master table in 'Item. Open' (MMS001). To find items for parmesan cheese, type 'parme' in the 'Item number' field and then click 'Browse'. The panel displayed is automatically filtered as per the query 'parme*'.

Related topics