Workflow Plus - Browse and Reference Field

In the request, in the Browser section, there is a new button that redirects you to the application where you can create your own browser.
Go to Workflow > Requests > Request types and select the required request type, for example Checked task.

• In the Fields section, click Add to add a new field, and click Add (Section) to add a new section.
  
• To add the browser field, select a field type according to your needs, for example Free: GUID.
  
• Scroll down to the Browser section and click the new button to create a new browser for this field.
  
• Alternatively, you can link an existing browser to the current view by selecting it from the list of available browsers, for example ExactSynergyProjects then click the Save button.
  
• When you create a new Checked task request, you will see the browser field in the request form.
  
• When you open the browser field, you are redirected to the browser view that you created or selected.
  

When you create a new browser, fill in the following fields:

Field	Description
Name	The technical name of the browser. It is used in the source code and repository to define which browser to use.
Caption	The text displayed as the browser title.
TermID	The term ID associated with the caption.
Query	The SQL query used by the browser. You can use parameters; if you do, you must also fill the Query parameters field.
Column info	The definition of how the columns are displayed in the browser. This can be filled automatically by choosing Save + Edit column info.
Result columns	The columns returned to the calling code (key and description). The columns are separated by commas, for example: c.cmp_wwn,c.cmp_name.
Query parameters	The list of columns that require a parameter in the query, for example: h.res_id.
Table list	The list of tables used in the query, including aliases if applicable, separated by commas, for example: cicmpy c,humres h.
Security level	The minimum security level a user must have to use this browser.
Maintenance Application	The maintenance application that starts when the user presses the New button in the browser.
Enterprisesearch entity	The entity used for Enterprise Search, if applicable.
Security provider	The security provider definition for the browser.
Security provider parameters	The parameters used by the security provider.

After you have entered the Query, Column info, and other main fields, click Save + Edit column info to open the column configuration screen.

• In the left list box, you can change the order of the columns.
• On the right side, you configure the properties for the selected column. Make sure you select the column from the column drop‑down first.

For each column, you can configure the following properties:

Field	Description
Header / TermID	The column caption and its term ID.
Header – Suffix / TermID	The suffix caption and suffix term ID.
Visible	Sets the column to be visible or hidden.
Sorting	Enables sorting on this column.
Quick search column	Enables the column for searching in the browser’s quick search.
Checkmark	Converts a 0/1 value from the database into a checkmark in the browser.
Domain	The repository domain used by the column. The domain determines how the column is displayed and the maximum length for the related input field.
Scale / Currency column	Defines which currency to display for an amount when the currency is stored in another column.
Selection values	Predefined selection values for this column (used in the quick search).
Selection columns	Defines the column that contains the selection values (for example, for status codes).
TermID column	The term ID for the value in the result. Useful for status fields like A (Active), P (Proposed), where the database value is A but the browser displays “Active”.
Suffix / TermID column	The suffix and suffix term ID for the value in the result.
Right aligned	Right‑aligns string fields.
Human id	Displays the value as a Human ID. For example, database value 15367 is displayed as 15.367.
Date/time format	The display format for date/time fields.
Search option	Configures the search operator used in quick search (for example “Contains” or “Starts with”).

After the query and browser definition are created:

• You can select the browser in a free field whose key type matches the browser key type.
• Example: if the browser is built on table cicmpy with key cmp_wwn of type guid (uniqueidentifier), the browser is only available in request free GUID fields.

This browser shows all accounts where the person in the request is the account manager.

• Name: AccountManagers

• Caption: Accounts

• TermID: 9 (for “Accounts”, found via: System > Setup > Terms > Search).

• Query:

  SELECT c.cmp_wwn,
         c.cmp_name,
         h.res_id,
         h.fullname
  FROM cicmpy c
  INNER JOIN humres h ON c.cmp_acc_man = h.res_id
  WHERE h.res_id = ?
  ORDER BY c.cmp_name

  The ? parameter is the person (resource) taken from the request.

• Column info (initial): c.cmp_wwn;c.cmp_name;h.res_id;h.fullname After you click Save + Edit column info, you can refine it to:
  c.cmp_wwn,,,,,,2;c.cmp_name,,Name;h.res_id,,Resource Id;h.fullname,,Full name.

• Result columns: c.cmp_wwn,c.cmp_name (key and description used in the browser).

• Query parameters: h.res_id.

• Table list: cicmpy c,humres h.

In the Save + Edit column info screen:

• For column c.cmp_wwn

  • Visible: No (the GUID does not need to be shown).

• For column c.cmp_name

  • Header: Name
  • TermID: 206 (term for “Name”).

  

• Select the AccountManagers browser in a suitable free GUID field.

• Because the browser has a parameter, an additional field Dependency: h.res_id appears with a drop‑down of available request fields. Select the Person field as the source for the parameter.

• Leave Result columns empty in the free field, because they are already defined in the browser.

• Reference URL: CRMACcountCard.aspx?BCAction=1&ID= This link is shown after the browser. It opens the Account Card, and ID is filled automatically based on the selected account.

• Reference SQL: Leave this empty initially so it is generated automatically. If you get a query error with a standard browser, you can define your own query, for example:

  SELECT c.cmp_name
  FROM cicmpy c
  WHERE c.cmp_wwn = @P1

  @P1 is automatically replaced by the selected account ID.

• Show inputfield: Automatically unchecked because the browser key is a GUID; users select the value via the browser only. In the request, when the Person field changes, the browser results update accordingly.

This browser shows purchase orders directly from the Exact Globe/Macola back‑office database.

• Name: PurchaseOrderBO

• Caption: Purchase order list

• TermID: 490 (for “Purchase order list”, found via System > Setup > Terms > Search).

• Query:

  SELECT po.ord_no,
         po.vend_no,
         v.vend_name
  FROM poordhdr_sql po
  INNER JOIN apvenfil_sql v ON v.vend_no = po.vend_no
  ORDER BY ord_no

  This query reads purchase orders from the Macola purchase order table and joins the vendor table to show the vendor name.

• Column info (initial): po.ord_no;po.vend_no;v.vend_name After Save + Edit column info, you can set: po.ord_no,,PO No.;po.vend_no,,Vendor number;v.vend_name,,Vendor name.

• Result columns: po.ord_no,v.vend_name (key and description).

• Table list: poordhdr_sql po,apvenfil_sql v.

In the column settings screen:

• Quick search column Set to Both. If this is not set, manually typed purchase order numbers cannot be found in the browser.

• Domain Set to bkstnr_sub. The domain determines the field length; here, the length is 8, so the order number field is also length 8. If no domain is set, the length falls back to the default free text field length.

Because the key ord_no is a text field, this browser can be selected in any free text field.

Additional configuration:

• Division Set to Creator (division). The purchase‑order browser will use the creator’s division.

• Result columns (in the free field) po.ord_no,po.ord_no,v.vend_name

  • First po.ord_no is the key.
  • The second po.ord_no and v.vend_name are used in the reference/link.

• Reference URL ICEMPoOrder.aspx?OrderType=N&Division=@Division&OrderNo= This link opens the InterConnect purchase order application.

  • @Division is automatically replaced by the creator’s division.
  • OrderNo is filled automatically based on the selected order.

• Reference SQL

  SELECT ord_no,
         v.vend_name
  FROM poordhdr_sql po
  INNER JOIN apvenfil_sql v ON v.vend_no = po.vend_no
  WHERE LTRIM(RTRIM(ord_no)) = @P1

  @P1 is automatically replaced by the order number.

• Show inputfield Checked. Users can type the order number manually or select it from the browser.

In the request, the browser shows purchase orders and a link to the back‑office application. When the value changes, the reference and displayed data are updated accordingly.

A new free text field is added to the request, and the standard SalesOrder browser is selected for this field. The division used by the browser is based on the division of the person in the request. When you open the browser, you can only view the information; you cannot change the browser details because this is a standard browser.

By default, the standard SalesOrder browser returns the ordernr column as the result. In this example, we change the behavior by setting Result columns in the request field definition to ordernr,refer. Without this change, the reference/link will display only the order number; after the change, it displays the sales order description instead.

Set the Reference URL to:

LogOrderBO.aspx?Type=V&Division=@Division&Number=

This URL opens the sales order from the Exact Globe back office in Synergy, using the selected division and order number.

In the request, the browser field will show the adjusted description based on the result and reference settings.

You can add a standard Item request field with a fixed selection option. However, this standard selection cannot depend on other request fields. To make the item list depend on another field (for example, an assortment), you can use the browse field option.

In addition to free fields having a Browse section (to link your own browser), standard browse request fields such as item1, item2, person, and project also have this Browse section. When you link your own browser there, it will replace the standard browser.

In this example, we create an item browser that depends on an assortment free field. When users browse, only items linked to the selected assortment will be shown.

• Use Free number field 1 as the assortment field, with the standard reference selection Assortments.

• For the standard Item field, create a new item browser named ItemAssortmentsDependency. This browser will replace the standard Item browser. Configure the browser as follows:

• Query

  SELECT ItemCode, Description
  FROM Items
  WHERE Assortment = ?
  ORDER BY ItemCode

  The ? parameter will be replaced by the value of the reference field, in this case Number field 1 (the assortment field).

• Column info ItemCode;Description This can be further edited via Save + Edit Column info.

• Result columns ItemCode,Description These define the key and the description shown in the browser; the fields are separated by a comma.

• Query parameters Assortment This is the column used with ? in the WHERE clause. It must be linked to the field that the browser depends on (the assortment free field).

• Table list Items This is the table used in the query, including any aliases if required.

After you save the browser and open the Item request field, the Browser section will show a Dependency: Assortment field with a drop‑down list of available request fields. Select Free number field 1 (labeled “Assortment” in this example). Once saved, the Item browser will depend on the assortment field, and only items belonging to the selected assortment will be displayed.