Web Browser Integration (WBI)

Overview

The OpenForms Application Browser form technology is a form that is based on the Web Browser OpenForms technology. This form can be used as a container for simple, e.g. Web Browser, to complex integrations such as MATIX, a GIS solution from Harris Govern.
An unlimited number of forms can be set up to meet the requirements for displaying spatial, and tabular content of profile users. In addition, an unlimited number of Application Browsers can be configured in a form. Forms can be set up with options that can include the following Key Types, e.g. Parcel ID, Name ID as well as Unformatted Tax Map). Other options include configuration by GIS Server URL, through Synchronization Options, and by Viewing Tabular Data.

Form basic integration, Web Browser Integration (WBI) can be used for adding an interactive website to Govern OpenForms. For example, you could use WBI to add a Geographic Information Services (GIS) web browser interface, such as the Govern GIS Explorer, to a Govern user form and Profile. You could then select records in Govern and view them on the GIS interface. You could also select records on the GIS interface and load them to the Govern Treeview, with the option to set up manual or automatic synchronization between Govern and the website.

The WBI control is added to a custom entity in the Govern OpenForms Designer (OFD). All the configuration is performed in the OFD including any related security settings.

WBI is supported by most websites. It is fully integrated with Govern. It implements predefined commands to add the following functionalities:

Loading all records from the Govern treeview to the website
Loading the active record in Govern to the website
Replacing all records in the Govern treeview with a list provided by the website
Replacing the active record in Govern with a list provided by the website

Configuration

Custom entities are used for adding specific predefined controls to a Govern form. In this case, a custom entity is used for adding Web Browser Integration (WBI) functionality. A custom entity cannot stand alone. It needs to be added to an existing form. The form must be added to Profile.
You can add the same custom entity to multiple forms, and add the forms to multiple Profiles, if required.

You need to select a Parent Entity for your new custom entity. Usually, this is the Root Entity.

The following rules apply:

The WBI control must be added to a custom entity.
The custom entity must be added to an existing form.
The form must be added to a Profile.
The Dataset Type Code for the Profile must be set to Parcel ID (P_ID) or the Name ID (NA_ID), and must correspond to the value set for the SelectedKeyType.
The Dataset Type Code is shown in the following screen shot:

Documentation

Click on the link below to view a .PDF containing details about Web Browser Integration and configuration procedures.
Adding and Configuring WBI

Video Demonstrating Test Tool

A video demonstrating how to test the integration will be be posted below shortly.

Click here to view the How To demo video

What’s New!

Web Browser Integration (WBI) was introduced in Govern 6.0. As of Govern OpenForms version 6.0.1405, it is used for integrating the Govern GIS Explorer with Govern.

NOTE: The WBI control is used for integrating GIS functionality with Govern as of Govern OpenForms 6.01.1405

Troubleshooting

Any issues that may be related to the Web Browser Integration form will be listed below.

No Access to the Wiki (Log In Error)

Symptom

This error displays a Script Error screen which appears on top of a Wikispaces sign in screen.

Resolution

A solution to resolving this error is to log in to the Wiki prior to launching Govern. When you have successfully logged into the Wiki, start Govern and open the form with the Web Browser Integration form.

Application Browser Form – Matix Integration

Overview

Matix leverages the power and flexibility of ESRI’s ArcGIS Server, and web-based mapping services, to provide an everyday tool for performing statistical analysis and visualizations. Matix integration allows the Govern application to leverage the functionality of the Matix plugin in Govern V6 through a custom control. When configured the integration is presented as another “child” of the integration controls, similar to the Govern Web Browser Integration (WBI). Matix Integration has been implemented in GA release 1511 for version 6.0 and 6.1.

For the Matix integration, there are three (3) principal areas of the user interface that are used.

Dataset TreeView – This is used for displaying search results, and expanding the results to access related OpenForms.
Matix Ribbon – This area contains the principal controls that allow users to query and interact with configured base maps.
Matix Map pane – This displays the GIS map as well as the controls to modify the display of the map, layers, and selected parcels. The Dataset TreeView and the Matix Map pane can be configured to update and display information automatically or with manual synchronization.

Configuring the UI for Auto-Synch or Manual Synch operation is achieved through selections made in the Govern User Registry Manager form. See Auto-Synch and Manual Synch Configuration in the Matix documentation for more information.

Features

Matix Integration features include:

Display GIS Map In Govern
Support Multiple Matix Configuration, Different Map / Data per role/user
Ability to Show Selected Parcel (in Govern) on the Map
Support Multiple Selection Mode (Rectangle, Free Hand, point,…)
Ability to add/replace GIS selection to Govern Treeview
Ability to Create PNG / Multimedia Document
Search Govern Parcel and display the result on the map
Search GIS for GIS Data and Intersection
Support Multiple Base Image
Support Theme Map
- Label
- Color Ramp
- Points

User Registry Filter Matix

See Other
AutoZoom to Highlighted (Selected)
AutoZoom to Selected (Loaded)

OFD Setup Controller Setup

Search Group

Documentation

Click to link to the Current Matix documentation.

Videos

Click on this video link to learn more about Govern Matix Integration.