101-std-fea-004

101-std-fea-004 #101 #fea004 #fea #stdfea #std

Govern Search
Overview | Predefined Searches | Search Pane Command Buttons | How to Search | What’s New | Related Topics
| …Last Modified June 5, 2018

Overview

Table of Contents

Overview
Predefined Searches
Search Pane Command Buttons
Begin the Search
Select / Deselect All
Clear
Load Selected Parcel(s)
Clear and Save to External Tables
Append to External Tables
Print
Export to Excel
Export Search Query Results to a Microsoft Excel File
Search Command button grouping
How to Search
Search Criteria
Search Result Pane
Transfer Individual Files to the Treeview
Sorting Search Results by Column Heading
What’s New
Quick Search (Govern 6.0 Suite release 6.0.1707 / 6.1.1707)
Hide Search Toolbox (Govern 6.0 Suite release 1503.341)
Related Topics

Searches are preset queries that are submitted to the database. The search process is one of the key functions in Govern. The search function allows you to retrieve datasets from the database. Further actions such as creating permits, attaching messages, generating licenses, generating mailing lists, etc. can then be performed on the records in these datasets. The Predefined Searches pane is the main user interface for performing searches on the database.
See Also Quick Search and Saved Datasets.

Predefined Searches

Predefined Searches are queries that have been preset for the user. When a search is performed, you are querying the database based upon your specified criteria. For example, a search by Parcel ID (P_ID) will return all records with a P_ID or a P_ID that matches a specified parameter. As searches can produce numerous results, these results can be controlled with the value specified in the Max. Records parameter in the User Registry. For example when the Max. Records parameter is used, i.e. a value of 25 is specified, only the first 25 records are used. If there are more records, they are discarded. Additional sorting can occur, but only on the records obtained. See Sorting Search Results by Column Heading for details.

Search Pane Command Buttons

Begin the Search

Click this icon to perform your search based upon your selected criteria.

Select / Deselect All

When search results are obtained, they are listed in the search pane. By default the results are all selected. Click the Deselect All icon to deselect all results; this will allow you to select only select records.
NOTE: The Select All and Deselect All icons alternate depending on whether all search results are selected, or deselected.

Clear

Click Clear to clear the Search Results pane of all records.

Load Selected Parcel(s)

When this icon is selected, the search results records are transferred to the Dataset Treeview pane.
TIP: When you enter information into any of the search parameters, clicking Enter will start the search and automatically load results to the Treeview.

Clear and Save to External Tables

Click to save the search results to one of the three (3) External tables (i.e. PM_EXTERNAL, NA_EXTERNAL, and PC_EXTERNAL).

Append to External Tables

To add or append the currently listed search results to the results that are listed in the Dataset Treeview pane, click this icon.

Print

Click Print to display the Print dialog box and print out the results of your query to your default Windows printer.

Export to Excel

Click to export the results of your query to a Microsoft Excel file that has not been formatted. See Export Search Query Results to a Microsoft Excel File below for details.

NOTE: This feature will only work when Microsoft Excel is installed on the system that Govern for Windows is installed on. Users must have a valid license for Microsoft Excel.

To restore the search form…

  1. Click the View tab in the Ribbon.
  2. Under the predefined Searches section select one of the Groups or Styles searches.
  3. When the search form appears, it will not be in auto-hide mode. Click the Auto Hide (Pin) icon to restore the form to auto-hide mode.

Export Search Query Results to a Microsoft Excel File

After performing a search query, you may want to perform further analysis on the records that were retrieved, e.g. review the tax map numbers or certificate numbers, etc.

To save search query results to a Microsoft™ Excel file…

  1. Move your pointer over the Predefined Searches auto-hide pane.
  2. Complete the necessary parameters and click the Search icon to perform a search.
  3. Click the Export to Excel button.
  4. When the save dialog box appears; specify the name of the Excel file and the location that it will be saved in.
  5. Once a name has been given, click Save to save the file.
  6. Next you will be given the option to open the file immediately in Excel; click Yes to open the file in Excel.

The records that are exported to Excel will not be formatted, i.e. only default fonts and alignments will be used.

NOTE: This feature requires that a version of Microsoft Excel must be installed on the same system that Govern for Windows is installed on. Users must obtain a valid license for Microsoft Excel.

Search Command button grouping

The Search Pane command buttons are grouped for clarity and to accommodate the command buttons for functionality that is related to the mobile version of Govern. There are two (2) groups of command buttons; Search-related, and Output-related buttons.

How to Search

The search process is one of the key functions in Govern. The search function allows you to retrieve datasets from the database.
To perform a search…
1. Click Pre-defined Searches in the Ribbon.
2. In the drop-down menu, click Groups search or Styles search.
3. In the Predefined Searches form, click Property Search to view the drop down menu.
4. Select Property Search (A).
5. Under Property Search are options to select a search criteria; select By Tax Map.

TIP: When using Predefined Searches press the Tab key to quickly move your cursor from field to field for quick entry.

NOTE: Users Accessing Govern Remotely
should note that parameters with field masks that are designed to accept hyphen separated entries entries, e.g. Telephone Numbers, Tax Maps, will display in OpenForms as a parameter with individual fields. These individual fields can be accessed with the Tab key.
The Field Mask for the above would look like the following “XXX-”XXX-XXX-X”, each of the grouped X’s are separated. Users that are accessing Govern over a Remote Link, e.g. VPN should pay attention to the tab sequence when pressing the Tab key to jump to the next parameter. Over a remote connection, in the Tax Map parameter, the tab key will not move the cursor to the next field of the Tax Map number, rather it will jump to Include the Inactive parameter. This behavior only applies to remote connections to Govern.
7. When the search is complete, the results are displayed in the Search Results pane.6. Click the Search icon.
NOTE: When you enter information into any of the search parameters, click Enter to start the search; search results will be automatically transferred to the Treeview.
NOTE: Only a maximum of 25 search results are displayed; this can be modified under Options > Max. Records.

Search Criteria

8. Click the option for Load to the Search Result. The results are loaded into the Dataset Treeview pane; you can also populate the Dataset Treeview automatically by selecting any parameter and clicking on Enter on your keyboard.
The Search Criteria will display the search parameters that have been configured with the Search Type.

Search Result Pane

When a search is performed, the Search Results pane displays the results in a grid below the Search and Search Criteria areas.
TIP: When you enter information into any of the search parameters, clicking Enter will start the search and force search results to automatically transfer to the Treeview.

Transfer Individual Files to the Treeview

At times you may require a single file to be loaded / displayed in the Dataset Treeview. This situation can arise when you have multiple results in your Search Query Results dataset. and the requirement is to look at each record one at a time.

To load a single record into the Dataset Treeview…

  1. Place your mouse pointer over the Pre-defined Searches auto-hide tab; complete the parameters to perform a search.
  2. Click the Search icon (A).
  3. In the Search Result pane (A), double-click on the individual record that you would like transferred to the Dataset Treeview pane (B).

When an individual file is transferred to the treeview, any previous dataset will be overwritten and replaced with the single file that was selected.

Sorting Search Results by Column Heading

Search results can be sorted based upon column headings, and in ascending and descending order.
To sort search results based on the column headings…

  1. Display the Predefined Searches pane.
  2. Perform a search; the results will be presented in the Search Results pane.
  3. Note the column that you would like to sort your results on; click on the column heading (A) to sort in ascending or descending order.

The direction of the arrowhead in the column head will indicate the direction of the sort. When the arrowhead is pointing upward, the sort is ascending, when the arrowhead is pointing downwards, the sort is descending. A click on the column heading will switch between ascending and descending.

The result will be sorted based on the column heading that you are using. When there are empty grids, i.e. NULL characters, those records are presented first when the sort is ascending, last if they are descending.

What’s New

Quick Search (Govern 6.0 Suite release 6.0.1707 / 6.1.1707)

NEW! As of release 6.0.1707 / 6.1 1707, an alternate search interface is available to the Govern user. The Quick Search differs from the traditional search interface in the sense that it bears a closer similarity to the search interface that is often associated with search engines. When correctly configured, this search interface is available through the Govern ribbon. In addition to the Quick Search feature is a new GNA editor. The Quick Search Index Configuration Editor is for configuring the Search Indexes that are used by the Quick Search. Click for Details on the Quick Search or the Quick Search Index Configuration Editor.

Hide Search Toolbox (Govern 6.0 Suite release 1503.341)

This is a new User Interface feature that will disable the default behavior of a persistent Search Toolbox. Typically, after performing a search followed by a Load action, you have to click on a form, or Tree view pane to hide the Search Toolbox. Now a Load from a Search or a Load from a Saved Data set will immediately hide the Search toolbox. Exceptions that override this feature are, if after performing a search, you Append to the Tree view, the Search pane will not hide. This feature is enabled through a “toggle”, i.e. ON/OFF, button. Options (tab) > Hide Search Toolbox.
NOTE: This feature has no impact when the Search Toolbox pane is docked, i.e. fixed with the pin icon.

Related Topics

Govern Search
Govern Quick Search
Quick Search Index Group Editor
Govern Search Technical Specifications

Saved Datasets
Dynamic Search Objects
Dynamic Search Styles
Dynamic Search Groups

Govern New Administration (GNA)

101-std-fea-005

101-std-fea-005 #101 #fea005 #fea #stdfea #std

Dataset Treeview
Overview | Populating the Dataset Treeview | The Treeview Explorer | Record Edit Confirmation | System Architecture | What’s New | Related Topics
| …Last Modified June 5, 2018

Table of Contents

Overview
Populating the Dataset Treeview
The Treeview Explorer
Record Edit Confirmation
System Architecture
What’s New
Context Menu in Dataset Treeview
Reposition
Hibernate Mode
Load to Treeview and Add (Append)
Hibernate
Enabling “Synchronize Dataset Treeview”
Location of Data
Business Rules
When Parameters Change:
When Opening Govern (Before opening Profiles):
When monitoring Dataset tree view changes:
Related Topics

Overview

Datasets that appear in the Dataset Treeview are populated with the results of searches made through the Search form. Records that are loaded into the Dataset Treeview may be appended to through the Saved Dataset pane, or deleted directly in the Treeview pane.

Populating the Dataset Treeview

To populate the Dataset Treeview with search results…

  1. When the Predefined Searches pane is in its default position, place your mouse pointer over the tab to display the search form (A).
  2. In the form perform a search type; for this example we will perform a property search by P_ID.
  3. Click Search for Result.
  4. Search results will be displayed in the lower portion of the search form.
  5. Click Load to the search result to transfer the search result records to the Dataset Treeview pane.
  6. If the Dataset Treeview pane is not displayed, click its tab at the bottom of the pane.

The Treeview Explorer

The Treeview Explorer displays record information in a hierarchical arrangement. In the Treeview panel, you are able to expand or contract a record by clicking on the arrowhead icons.
For example, on a search that retrieves tax map records, when you double-click on the tax map, it lists name information at the next level. Each item can be expanded to show specific data on the property, such as owner and occupant names, parcel information and location, permits, utility billing and accounts receivable records.
As you select each level of information, the data is displayed in the appropriate OpenForm when it is displayed on the right hand side.

Record Edit Confirmation

When a dataset has been loaded, it is easy to select and begin to edit a record. This ease of selection may at times be a detriment as at times the wrong record may be selected, and the user immediately begins to edit in error. It has been determined that if a secondary confirmation is introduced during the record selection process, there is less chance of erroneously editing the wrong record.

Through the Govern New Administration (GNA), the Record Edit Confirmation option can be enabled to add a secondary confirmation. When Record Edit Confirmation is enabled, after the user selects a record, they are obliged to click on a secondary icon (A), to fully unlock the record for editing.

To enable Record Edit Confirmation…

  1. In GNA, select System Parameters (tab) > General Connection Parameters.
  2. In the General Connection Parameters form, locate the Organization Parameters group and select The user must explicitly enable editing for each parcel option.
  3. Click Save to save the option.
  4. To close the form, click Exit.

When this option is enabled, after loading a dataset, users may still select a record for editing, but the selected record will have an icon beside it. The user must click the icon in order to fully unlock the record for editing.

System Architecture

For all details regarding the Govern Treeview Architecture, refer to 101-std-fea-005-Treeview_Architecture.

What’s New

Context Menu in Dataset Treeview

NEW! Users of the Dataset Treeview will note that when it is populated with one or more records, there is a description for each record. This description can be a Parcel ID, an Account Number, and so on. A quick method of deleting individual records is to hover the mouse pointer over a record. When the width of the Dataset Treeview pane is wide enough, placing the mouse cursor over the description will display an “x” that can be used to remove the record. Unfortunately when there is insufficient space, i.e. the space is not wide enough to display the full description, the “x” is not visible. To address this situation a context based menu has been added to the interface.
TreeviewContextMenu00.png
To display this menu…

  1. Right click on the record of interest in the Dataset Treeview.
  2. In the floating menu, you now have option for additional functions that appear beside the record when the entire line is visible.

By default, there will be an option to “[x] Remove”. When there are other options, e.g. Edit, they will also be presented in the menu.
This feature is available in the following releases: 6.0.1611.0067 / 6.0.1702.0080 / 6.1.1611.0060 / 6.1.1702.0121

Reposition

Previously, when performing a search of records with the same NA_ID but multiple ST Account numbers, when you copy the record to the Treeview, the system would only select the first account. Now the selected record will be sent to the Treeview. (Available in release 6.0.1503)

Hibernate Mode

This behavior of selecting only the first account also applies to the Hibernate process. As Govern is restored from a hibernation if a second or third account is selected before hibernation, when the application is restored, although the NA_ID is correct, only the first account will be displayed.

Load to Treeview and Add (Append)

As data is loaded or appended to the Treeview from the Search, or the Saved Datasets form, the following rules apply:

  • When a record is selected for append, only new files will be loaded. If previously loaded, the file will not be reloaded into the Treeview.
  • If no search result is selected, the Add to Search Results button will be disabled.

Hibernate

Previously the Hibernate would store the NA_ID of the records displayed in the various panes that are opened in the interface. Now to maintain the fidelity of the hibernated user environment, all Govern ID’s are used; i.e. NA_ID, P_ID, ST_ID, and so on.

NOTE: User Hibernate information is stored by user in (Table: USR_HIBERNATE). The following query will display the hibernation information for “userName”

SELECT *
FROM USR_HIBERNATE
WHERE USR_ID = ‘userName’;

Treeview Synch
In Govern for VB6, external tables (PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL), were used by external applications and reports to automatically know the current recordset and currently viewed parcel. In Govern release 6.0 and upwards, these external tables are being phased out and the functionality provided by them will need to be reproduced.

NEW! The Treeview sync. feature saves the contents of the current profile in (Table: USR_SAVED_DATASETS) with a “Saved Dataset” name of “AUTOSAVE” under (Column: USR_SAVED_DATASETS.SAVED_SET_NAME). Should a profile be changed, the dataset loaded in the Treeview will be automatically synchronized to (Table: USR_SAVED_DATASETS).
This feature recreates the functionality provided by the three (3) external tables that were used in Govern for Windows, (Tables: PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL). For example users could run a batch process on a saved external dataset as opposed to a set range.

NOTE: In release 6.0 a simultaneous save will be made to (Table: PC_EXTERNAL) and (Table: USR_SAVED_DATASETS), Tables NA_EXTERNAL and PM_EXTERNAL are no longer supported.
In release 6.1, all three (3) tables PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL will not be supported.

  • PC_EXTERNAL (Supported in release 6.0; not supported in release 6.1)
  • NA_EXTERNAL (Not not supported in release 6.0 and 6.1)
  • PM_EXTERNAL (Not not supported in release 6.0 and 6.1)

Enabling “Synchronize Dataset Treeview”

This feature is enabled in the User Registry through the User Registry Manager. The Options button is located below the Govern suite button in the Govern User Interface.

  1. Click the Options button; click Options.
  2. In the Registry Manager form, verify that the Registry Filter is set to User ID.
  3. Under the Section Name column, locate Synchronize Dataset Treeview; click to select the option under the Key Value column.
  4. Click Save to save your changes.

When you return to the Govern interface, the Treeview Sync. icon will be enabled. This is a toggle, i.e. ON/OFF button that will enable or disable the feature.

Location of Data

As indicated above, all data will saved in (Table: USR_SAVED_DATASET). Associated columns are as follows:

COLUMN DESCRIPTION
USR_ID User ID
SAVED_SET_NAME By default will be AUTOSAVE
REF_TYPE “P_ID”, “NA_ID”, etc. Based on the profile Key Type
SORT_SEQ Order in the Treeview
IS_CURRENT TRUE if the current item in the Treeview

NOTE: All data will be saved based on the Key Type of the profile. This is done so as to support multiple Key Types at the same time.

  • The data is not saved by profile, so the synchronization for a Key Type will be done on the last active profile using that key type.

The desired behavior when there is more than one Treeview dataset for the same ID Type is to perform a reload when the user switches from one instance to another.

Business Rules

Programmers should note the following Business Rules.

When Parameters Change:

  • From TRUE to FALSE – Delete all SAVED_SET_NAME that have a status of “AUTOSAVE” and replace the value with the current USR_ID
  • From FALSE to TRUE – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with the current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
    – Starts monitoring Dataset tree view changes

When Opening Govern (Before opening Profiles):

  • Starts monitoring Dataset tree view changes if Flag is on

When monitoring Dataset tree view changes:

  • If Active profile changes – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
  • If Treeview is replaced (By eSearch / QueryTool / Matix/…); i.e. a Load
    – Delete All SAVED_SET_NAME equal to “AUTOSAVE” for current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the Treeview data
  • If an item is added into the Treeview (By eSearch / QueryTool / Matix /…); i.e. Add Or AddAndReposition
    – Insert the new item into USR_SAVED_DATASET
  • If an item is removed from the Treeview (using the X button); i.e. Remove
    – Delete the new item into USR_SAVED_DATASET
  • If the active item changes in the Treeview; i.e. Reposition()
    – Update IS_CURRENT in USR_SAVED_DATASET
    NOTE: This is done by setting the current id to -1 and setting the prior id to 0

NOTE: Always hide AutoSave SAVED_SET_NAME from saved dataset functions

  • V6.0 (only) – PC_EXTERNAL will need to be maintained at the same time
  • V6.1 – All three (3) tables, PC_EXTERNAL, PM_EXTERNAL, and NA_EXTERNAL are to be removed.

Related Topics

Forms Explorer
Reports Explorer

History Toolbox

History Toolbox

Overview

The History pane, or panel, allows for quick navigation of historical data records (Years and Frozen ID’s) that are associated with the currently selected record (Table: MA_MASTER, TX_RE_ASSESSMENT). Historical data allows you to view data from previous years, however, you cannot modify or delete the data. For Property Control, this can include Split/Merge/Remap data, as well as CAMA and Tax data. This pane can be displayed with a click on its icon under the View tab on the Govern Application Ribbon.
Alternatively, as an auto-hide pane, it is displayed by placing the mouse pointer over the tab on the default left hand side (LHS) of the interface. In the auto-hide pane, users will see the following:

  • Parcel ID (P_ID) – A numerical value.
  • Parcel Description – A Description of the parcel, e.g. Tax Map number.
  • Parcel Location – An address.

Below the above is a data grid displaying columns containing information from (Table: MA_MASTER), and (Table: TX_RE_ASSESSMENT).

NOTEUsers will have access based upon the alternate ALT security settings that have been established for viewing alternate data in the GSM rel. 6.0. If specific settings are required, Administrators should ensure that they are configured in the Govern Security Manager (GSM). Refer to the Access to Alternate or Historical Data section of the GSM Release 6.0 for details about setting access rights to Historical data.

Read More...

Change Fiscal Year

Change the Current Year

Unlike previous releases, the Fiscal Year can no longer be changed in the govern Ribbon. The Fiscal Year can be changed in the History Panel.
To change the Fiscal Year in Release 6.0 and greater,

  1. Perform a query; for example, in the Property Control profile perform a search based on P_ID and copy the results to the Dataset Treeview.
  2. Click to select the Dataset Treeview pane at the bottom of the interface.
  3. In the Ribbon, click the current year; the Auto-Hide History pane will slide out.
  4. In the year column, double click on the desired year in the Year column.

Command Buttons

The following are the History Pane Command Buttons.

Set History Year & Frozen ID

Click this button to set the Year and Frozen ID to that of the record that is selected in the grid.
To set the Year and Frozen ID to the Current Record…

  1. In the History Pane grid, click to select a record.
  2. Click Set Year and Frozen ID.

The Role Year and Frozen ID will now be set to that of the selected record. Alternatively, a double click on the record in the History pane, will also set the Year and Frozen ID.

Reset Default History Year & Frozen ID

Click to reset the profile and the fiscal year to the default current. Use this option to quickly return back to the original state of the interface.

Refresh History

Click to refresh/update the data in the history grid.

History Pane Columns

The columns in the History pane grid are as follows:

Year

This column will display all historical years of the record.

Frozen ID

The frozen ID status of the record. Refer to the Frozen ID Data Type grid below.

Data Type

The data type of the record, e.g. Current, Audit, Sales, etc.

CAMA

Information that is taken from the (Table: MA_MASTER). When there is no Mass Appraisal history data, there will be no check mark in the column.

TAX

The Tax column will contain information that has been taken from the (Table: TX_RE_ASSESSMENT). If the system does not contain any Tax history data, there will be no check mark in the column.

Frozen ID Data Types

Frozen ID Data Type
0 Current record
1, 2, 3, 4… Sales Information (Property Control or
Mass Appraisal Sales)
-1 Original certified record
-32 766 Split Merge data (Inactive)
32 767 Simulation Data
-2 or less, i.e. -3, -4, -5, etc.. Audit Record (Tax or Mass Appraisal)
1 or greater, i.e. 2, 3, 4, etc. Sales

 

History Results

Applying Filters to History Records

The results displayed in the History pane can be filtered, i.e. selectively control the information that is displayed in each column. For example to filter out all other Frozen ID’s and display only records with a -2 Frozen ID.

  1. With your cursor, click the column heading. Beside the heading, an arrowhead will appear (1).
  2. Click the arrowhead to display a list of all records within the column; in the case of Frozen ID’s, e.g. -2, -1, 0, 1
  3. Select the Frozen ID types that you would like to display (2).
  4. Once you have chosen items to filter for, click outside of the selection area to automatically apply the filter.

The filters will remain in place, until they have been manually altered or cleared, or the session has ended and the application is restarted.

Clearing History Record filtersFiltered data in the History pane can be cleared in the same manner that they were enabled.
To clear filters…

  1. Click the column heading, beside the arrowhead used to display filter options is a filter icon.
  2. Click the (Clear Filter) button (2).

Any filters set for the column will be cleared. If additional filters exist for other columns, they will remain until they are also cleared in the same manner.

Grouping by Column Headings

As with other specialized grids in the Govern suite of applications there is the drag and drop feature that allows for grouping of the results in the grid. The space above the columns is referred to as the Grouping Area (B). This space expands to accommodate column names as they are added.
In order to Group by Columns in a pane that is set to Auto-Hide, click the Pin icon in the upper right hand corner (A) to temporarily disable the Auto-Hide mode.

Grouping History Pane Columns by Headings

History data can be grouped to obtain different perspectives about the data. For example a grouping by year will allow you to see the number of records that are available within each year. History Pane columns can be grouped by any of the following, Year, Frozen ID, Data Type, CAMA, and TAX. For example, to group by Year, we would do the following:

  1. Click and drag the Year column into the Grouping Area above the columns; when empty this area is marked” Drag a column header here to group by that column”. Drop the column heading on the Grouping Area.
  2. You will observe that the data has now been grouped according to the Year column. You will see a heading that indicates the column grouping, the item that it is being displayed under, and the total number of items under that grouping. Click on the “^” beside the column grouping (C) to expand or contract the content listed.

Multiple columns or attributes can be grouped by dragging and dropping them into the Grouping Area. Additional columns will appear as subgroups within the original group.

Removing Column Groupings

To remove column groupings from the Grouping Area:

  1. Click and drag the grouped or title to an area outside of the Grouping Area.
  2. When an ‘X’ appears, release the mouse button to drop the object. The grouping or sub-grouping will be removed.

 

Related Topics

Standard Navigation & User Interface

 

 

101-std-fea-007

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

 

 

Trace Utility Feature

Trace Utility

Overview

The functionality of the GNA trace utility was expanded in Release 6.0. In previous releases, trace logs were generated by setting individual keys for sections that a log was required for; e.g. General, DAB, GIS, Mobile, and so on. In the current Release 6.0 and greater, all trace activities are managed through the Configuration Diagnosis console.

Default Trace Log Settings

Read More...

By default, when enabled, a trace process will immediately begin to generate data that is written to a Comma Separated Value (.csv) log file in the Trace directory of the deployment folder. The trace file will use the following naming convention:

userName_serverName_ckName_appName.csv
where…

  • userName = users login name
  • serverName = name of the server that the application is installed
  • ckName = the connection key name
  • appName = the application that is being monitored

Ex.: hsolo_JNMTL2_GOVDB_60_JNMTL2_SQL_GovernNetAdmin.csv

NOTE: The trace log file is self maintaining in that it will be deleted when it is older than 30 days. Alternatively, users may opt to delete the file manually, it will be regenerated the next time it is enabled.

Modules option

Target: The Target options allow the selection of how the trace information will be presented. The options are as follows:

  • File – The File option will generate the trace information as a log file. This .csv file can be opened with any application that supports the format, e.g. Microsoft Excel.
  • Console – When Console is selected, a console (output window) titled NLog is launched. The trace information is logged in the NLog window.
  • Console and File – Selecting the Console and File option will display the trace information using both of the above means, the NLog console window will be displayed and the .CSV log file will also be generated.

When the Text option is selected, A text field is displayed. The intent is that any debugging information is pasted into the field.

Min Level

Selecting a minimum level will determine what details are logged.

  • Info – Select the Info option to log general information about the application. This can include a list of the calls that are made by the application
  • Warn – The Warn minimum level will log error messages that are of type Warnings.
  • Error – When a minimum level of Error is selected, the system will log all error messages, that are categorized as type Error. These are errors that will cause the application to halt its current process, but will not cause it to fail. In this situation data loss may occur.
  • Fatal – This option will log all errors that are categorized as Fatal. These are errors that will cause the application to fail, i.e. a crash without the chance of a recovery. In this situation data loss may occur.

Supported Modules

The list of supported modules are presented below the Min Level: option and pertain to the list of installed Govern modules

  • AppXTender – Will log errors generated by the AppXTender application
  • DAB – Selecting the DAB option will log the activities that access the Govern Data Access Block (DAB)
NOTE: When the DAB option is selected, a new field called Trace commands where execution time is longer than X milliseconds will be displayed. See details below.
  • Trace commands where execution time is longer than X milliseconds – Enter a value in milliseconds that will be used a threshold. Any actions or calls that take longer than this value will be recorded in the log file. The default value for this field is 30 milliseconds

Tracing Govern Applications

  • General – When selected will trace the errors generated by installed Govern suite applications; e.g. MSGovern, GovernNetAdmin, BEDesigner, GovernSoftware.Security.UI.Manager, MSGovern.OFD, and so on.
  • GIS – When troubleshooting GIS integrations, select this option to provide related trace information.
  • HummingBird – Use this option to obtain a trace log for Hummingbird Document Management System integrations.
  • Mobile – Selecting this option will provide trace information that is related to the mGovern mobile application
  • Reports – When there are issues with reports, select this option to trace information related to reports.
  • Valcura – Use this option to obtain log information related to the Valcura appraisal system integration.

Text option

The text option is reserved for entering debugging information that is generated by the system. When errors are generated by the system, the debug code can be copied and reviewed for insight into the issue. To further assist, when the “Load configuration from” Text option (A) is selected, the debug code can be copied and pasted into the text field that is displayed. If there is an incompatibility, an error window will be displayed.

 

 

101-std-fea-013

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

101-std-fea-016

101-std-fea-016 #fea #stdfea #std

Jurisdictions & Clusters
Overview | What’s New

Overview

[Discontinued 6.1]
This feature is no longer needed having been replaced by the MASS APPRAISAL LINK GROUP feature.

Jurisdictions and Clusters is a standard feature option in version 6.1. It combines in a cluster or group, property physical characteristics (jurisdiction, neighborhood) with a mass appraisal group for valuation methods and rates (income neighborhood).
Functionality is currently in development.

For more information, see the technical design page.

What’s New

this section will contain any new information that is relevant to Jurisdictions.

BP – Schedule a Report

Batch Process – Schedule a Report

Overview

Standard Batch Process and Definition to execute a query.

 

 

101-std-bp-006

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

BP – Test Batch Process

Batch Process – Test Batch Process

Overview

Standard Batch Process and Definition to execute a query.

 

 

101-std-bp-007

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...