103-all-GNA-map

Govern New Administrator (GNA) System Product Map

The product structure is broken down by System Resources, Application modules, Options and 3rd Third Party setup and configuration functions, tools and utilities.

System Resources

Setup and configuration of standard resources, functions, tool and utilities. Categorized by type, based on their menu hierarchy (ED=Editors, SY=System, UT=Utilities, UI=User Interface). The Section # corresponds to GNA’s full pdf manual section.

Section
#
Product Code
Link
Product Description Code
Type
Code
Name
Additional Information Quality Control

Editors

1.2 103-ED-001 Profile Editor ED Editors
1.5 103-ED-002 Field Mask Editor (Global mask)
(previously called Global Mask Validation Editor)
ED Editors
1.4 103-ED-003 Constant Value Editor ED Editors 103-ed-003-TEST 103-ed-003-TEST
1.4 103-ED-004 SQL Query Editor ED Editors 103-ed-004-TEST 103-ed-004-TEST
1.4 103-ED-005 Formula Editor (Discontinued in 6.?) ED Editors
1.4 103-ED-006 Logical Expression Block Editor (Discontinued in 6.1?) ED Editors
1.3 103-ED-007 External Command Editor ED Editors
1.5 103-ED-008 Number Format Editor ED Editors
1.5 103-ED-009 System Validation Table Editor ED Editors
1.5 103-ED-010 User Validation Table Editor ED Editors
1.5 103-ED-011 Data Mapping Editor ED Editors
1.5 103-ED-012 Resource File Editor ED Editors
1.3 103-ED-013 Batch Process Definition Editor ED Editors
1.3 103-ED-014 Dynamic Search Objects ED Editors
1.3 103-ED-015 Dynamic Search Styles ED Editors
1.3 103-ED-016 Dynamic Search Groups ED Editors
103-ED-017 Expression Editor ED Editors 103-ED-017 103-ED-017
103-ED-018 Shared Expression Editor ED Editors (Dev) 103-ED-018 (QC) 103-ED-018
101-std-fea-037 Text Style Editor ED Editors
103-ED-019 Email Template Editors ED Editors
103-ED-020 Mobile Configuration Editor ED Editors 103-UT-006 103-ED-020
103-ED-021 Message Template Editor ED Editors
103-ED-022 Quick Search Index Group Editor ED Editors 103-ED-022
103-ED-023 Bill Messages Editor ED Editors 103-ED-023
103-ED-024 Generic Import Editor (NEW!) ED Editors
103-ED-025 Marshall & Swift (M&S) Valuation Setting Editor (NEW!) ED Editors

System

1.2 103-SY-001 General Settings (SY REGISTRY) SY System
1.2 103-SY-002 General Connection SY System
1.2 103-SY-003 Department Maintenance SY System
1.2 103-SY-004 User Maintenance SY System
1.2 103-SY-005 Name & Address Group Security Grid SY System
1.3 103-SY-006 Report Editor SY System
1.3 103-SY-007 Report Editor Criteria SY System
103-SY-008 User Settings (USER REGISTRY) SY System tbd

Utilities

1.2 103-UT-001 Active Directory Integration Tool UT Utilities
1.6 103-UT-002 Connection Key Management UT Utilities
1.5 103-UT-004 Country Correction in NA_NAMES table UT Utilities
1.6 103-UT-005 Database Verification UT Utilities
1.6 103-UT-006 Initialize Mobile Database UT Utilities
1.6 103-UT-007 Export Data to File UT Utilities
1.6 103-UT-008 Import Data from File UT Utilities
1.1 103-UT-009 Diagnostic Configuration and Trace UT Utilities
103-UT-010 Database Extraction Tool UT Utilities (new)

Conversion

103-ma-cvt-001 Mass Appraisal Parameters
103-ma-cvt-002 Mass Appraisal Tables
103-std-cvt-003 Standard Formula to Expression
103-wm-cvt-001 Workflow Conversion Roadmap (22166)
General
103-GN-001 Field Exclusion (for Roll Forward and Copy to next year

User Interface

1.1 103-UI-ALL User Interface UI Windows
1.1 103-UI-003 Cascade UI Windows
1.1 103-UI-004 Tile Horizontally UI Windows
1.1 103-UI-005 Tile Vertically UI Windows
1.1 103-UI-006 Layout (Std. or Tabbed) UI Windows
103-UI-010 GNA About Box (see roadmap) UI
103-UI-011 GNA Help UI

System Registry

The following parameters are used to configure
Click here to access System Registry Parameters
Accounts Receivable
Miscellaneous Billing

Application Configuration

Standard
Page Link Accounts Receivable Test Plan
103-std-parm-RollFwdExcl 001 Roll Forward Exclusions

Accounts Receivable & Cash Collection

Page Link Accounts Receivable Test Plan
103-ar-parm-General 001 General Parameters
103-ar-parm-Deposit 012 Batch Deposits setup
103-ar-parm-Class 002 Class Codes
103-ar-parm-CC 003 Cash Collection Parameters
103-ar-parm-Priorities 004 Sub-System Priorities
103-ar-parm-ACH 005 ACH Accounts Parameters
103-ar-parm-GL 006 General Ledger Transactions Parameters
103-ar-parm-GLDistr 007 General Ledger Distribution Parameters
103-ar-parm-Trans 008 A/R Transaction Parameters
103-ar-parm-CopyYear 009 Copy to Next Year
103-ar-parm-SubsysPriorities 010 A/R Sub-System Priorities
103-ar-parm-DepositTypes 011 A/R Deposit Types
103-ar-table-cctype CC Type System Table
103-ar-parm-Escrow Escrow Maintenance
103-ar-parm-Calendar 012 AR Calendar

Business Tax (Self Reported Tax)

 

Link Business Tax (ST) + (PM)
103-st-parm-General 001 General Parameters
103-st-parm-CopyYear 002 Copy to Year
103-st-parm-Category 003 Categories
103-st-parm-FormSetup 004 Categories Form Setup
103-st-parm-Periods 005 Periods

Miscellaneous Billing (mb)

 

Link Misc. Billing (mb)
103-mb-parm-General 001 General Parameters
103-mb-parm-Category 002 Categories
103-mb-parm-Item 003 Items
103-mb-parm-Recurring 004 Recurring Entries
103-mb-parm-Templates 005 Misc. Billing Templates
103-mb-parm-CopyYear 006 Copy parameters

Real Property Tax

Page Link Real Property Tax Billing
103-re-parm-General 001 General Parameters
103-re-parm-Levy 002 Levy Codes
103-re-parm-Exemption 003 Exemption Codes
103-re-parm-LevyGroup 004 Levy Groups
103-re-parm-ExemptionGroup 005 Exemption Groups
103-re-parm-Swiss 006 Swiss Code
103-re-parm-Average 007 Averaging Assessment Values
103-re-parm-CapLevy 008 Cap Levy Group

Personal Property Tax

Link Personal Property
103-pp-parm-General 001 General Parameters
103-pp-parm-Levy 002 Levy Codes
103-pp-parm-Exemption 003 Exemption Codes
103-pp-parm-LevyGroup 004 Levy Groups
103-pp-parm-ExemptionGroup 005 Exemption Groups
103-pp-parm-Depreciation 006 Depreciation Tables
103-pp-parm-Category 007 Categories and Items …………
103-pp-parm-Adjustment 008 Adjustments
103-pp-parm-CopyToYear 009 Copy Parameters to a New Year

 

Utility Billing

 

Link Utility Billing
001 General Parameters
002
003
004
005

 

Mass Appraisal

see MA Module Product Map for more information.

Status Page Name Notes Test Plan
103-ma-parm-General 001 GENERAL PARAMETERS
103-ma-parm-General-1 001 General Parameters – Page 1
103-ma-parm-General-2 001 General Parameters – Page 2
103-ma-parm-General-3 001 General Parameters – Page 3
103-ma-parm-General-4 001 General Parameters – Page 4
103-ma-parm-General-5 001 General Parameters – Page 5
[roadmap] 103-ma-parm-General-6 001 General Parameters – Page 6 Marshall & Swift See Roadmap
[to be verified] 103-ma-parm-Appraisers 002 MA APPRAISERS See Roadmap
MA TABLES
103-ma-parm-Tables MA TABLES (Master)
103-ma-parm-Tables-Resequence Table Resequence
103-ma-parm-Shared-Columns Allow Table Sequences to use the same column by model
MA TABLES SINGLE ENTRY
103-ma-parmTables-Single MA Tables – Single Entry (Master)
MA Tables Single – Category ALL
103-ma-tables-nbhd All – Neighborhood
103-ma-parm-Tables-Rounding All – Rounding
103-ma-tables-multdist All – Correlated Values
MA Tables Single – Category LAND
103-ma-parm-landuse Land – Use
103-ma-parm-landschd Land – Schedule
103-ma-parm-plotuse Land – Plot Use Discontinued See Benoit for more information
MA TABLES Single – Category MRA
103-ma-parm-Tables-MRA MRA – Model
MA TABLES Single – Category INCOME
103-ma-parm-income Income – Categories
103-ma-parm-add Income – Added Items
103-ma-parm-incqua Income – Quality Adjustments
103-ma-parm-incadj Income – Overall Adjustments
103-ma-parm-incmodel Income – Model
MA TABLES Single – Miscellaneous Structures Roadmap
103-ma-parm-miscuse Misc. – Miscellaneous Use Codes
103-ma-parm-miscgrad Misc. – Grade
103-ma-parm-misccond Misc. – Condition
103-ma-parm-miscadjt Misc. – Adjustment
103-ma-parm-Tables-BSE 005 Tables – Building Structural Elements
103-ma-parm-Tables-Depreciation 006 Tables – Depreciation
103-ma-parm-Tables-IncExpense 007 Tables – Income Expenses
103-ma-parm-Tables-IncRental 008 Tables – Income Rental Details
103-ma-parm-Tables-LandAdjust 009 Tables – Land Adjustments
103-ma-parm-Tables-MRA 010 Tables – MRA
103-ma-parm-Tables-COMPS 012 Tables – Comparable Sales Elements
103-ma-parm-Tables-Sites 013 Tables – Sites
103-ma-parm-Shared-Lkgroup 014 Tables – Shared Lookupgroup Developer Page 103-ma-parm-Shared-Lkgroup-Test (QC)
103-ma-parm-Shared-Lkgroup-Set 015 Tables – Shared Loookup Group Set Developer Page 103-ma-parm-Shared-LkGroup-Set (QC)
103-ma-parm-ComputeEntity Compute System Entity Configuration
103-ma-parm-Templates-BSE 050 BSE Templates
USER VALIDATION TABLES
103-ma-tables-permadjreason Permanent Adjustment Reasons

Mass Appraisal Tables by Element Type

Status Page Table Element Type Description Developer Information QC /Test Plan
103-ma-parm-Table-Header Header The header type is used to group different elements under a header.
Can be collapsed when not needed
103-ma-parm-Table-Feature Feature The feature is not impact the value calculation but can be used as a
lookup in an element that contributes to value
103-ma-parm-Table-AreaSizeAdj Area Size Adjustment Used to adjust an area for instance when irregular shapes
103-ma-parm-Table-AreaOverride Area Size Override Used to input an area size or override an existing one
103-ma-parm-Table-RateAdj Rate Adjustment Adjust the rate
103-ma-parm-Table-QPoints Quality Points Adjust the rate (add, subtract or multiply) the rate.
Often used in Matrix or Linked Tables
103-ma-parm-Table-CamaAdj Cama Adjustment
103-ma-parm-Table-Depreciation Depreciation Adjustments
103-ma-parm-Table-DepOverride Depreciation Overrides
103-ma-parm-Table-GlobalAdj Global Adjustments
103-ma-parm-Table-OverallAdj Overall Adjustments

 

Workflow Management

See Product Workflow Product Map

SYSTEM OPTIONS / 3rd PARTY

Options

  • e-Government (201)
  • Mobile (202)
  • GIS Integration (203)

 

Link GIS Configuration (System 203)
103-gis-parm-General 001 General GIS Parameters
103-gis-parm-Tooltip 002 GIS Tool Tip
103-gis-bp-Synchronize 003 GIS Synchronize Batch Process
see also [to be verified]
103-ED-011 See Also Data Mapping

 

 

103-all-GNA-map

 

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...

GNA – What’s New

Govern New Administrator (GNA) – What’s New

Version 6.0 and 6.1

Changes to the Govern New Administration are listed below in reverse chronological order. The most recent changes are displayed at the top.

What’s New

RE – Capping Rates

Capping Rates Overview Some municipalities will limit annual increases in assessed value of property with Homestead Exemption to a set

Posted in GNA, Real Property | Tagged , , , , | Leave a comment

MA – M&S Valuation Setting Editor (103-ed-025)

Valuation Setting Editor (Marshall & Swift MVP Interface) Available in release 6.1.2211 – (In Development) Overview Marshall & Swift (M&S)

Posted in Developers, Editors, Feature, GNA, Mass Appraisal, Whats New | Tagged , , , , , , , | Leave a comment

Generic Import Editor (103-ed-024)

Generic Import Editor Available in release 6.1.xxxx – (In Development) Overview The Generic Import Editor is a GNA Editor that

Posted in Developers, Editors, Feature, GNA, Whats New | Tagged , , , , , , | Leave a comment

SSRS – Changes to Handling of SSRS Reports (301-ssrs-util)

Changes to Behavior of SQL Server Reporting Services (SSRS) Version 6.1.2206.0142 / 6.1.1811.2019 Overview The following contains a description of

Posted in Batch Process, Developers, GNA, Reports | Tagged , , , , , , , , , , , | Leave a comment

Old News

Read More...

Mobile related Changes to GNA UI

As a result of the added functionality and enhancements to the Govern Mobile application, changes have been made to the Govern New Administration (GNA) user interface.

Initialize Mobile Database

Verify Database Process

Email Template Editor

Database Utilities

  • [6.0 / 6.1] Support for the extraction of Personal Property (PP) tables in the Mobile Database Initialization process.
  • [6.1] Database Extraction Utility to extract a snapshot of the data along with all parameters for a selected data set.
  • [6.0] Database Verification behavior changes on opening Govern Administrator (GNA)
    • If the connection key is set to an empty database, the Initialize Database process will be launched automatically (see below) and once completed, GNA will be closed and restarted as it is mandatory to run the Verify Database process
    • If their is a major release difference (first 2 digits) between the the program and the database version, it will be mandatory to run the database verification or exit the application. This situation will occur for example, when upgrading from 5.1 to 6.0. A change from 6.1.1503 to 6.1.1511 will not trigger it .
  • [6.0] Database Verification new INITIALIZE Database process to create a Govern Ready Standard System Database.
    • It is no longer necessary to use UPDATA. Tables, fields and views will be created automatically
    • Process is triggered automatically when the table USER_KEY_MASTER does not exist
  • [6.0] Database Verification INITIALIZE Database process – NEW Govern USER and ROLE
    • A new role called “Govern SuperUsers” is created in the GSM. This role will grant access (E)xecute to all GSM and GNA functions.In addition, a User called Govern User belonging to this role will be created.
    • The Govern user password can be changed, the user and role can be deleted after a new Administrator user and role with full access has been successfully created and validated for the organization.
  • [6.0] Database Verification INDEXES
    • All indexes created and used by the Govern applications will be identified as such and will start with the letters GV or PK when the index is a primary key. This will enable the application to manipulate these indexes when needed.
    • An option to delete and recreate indexes was added
    • NOTE: Indexes created by users will not be modified or manipulated in any way. However, it is strongly recommended to delete and recreate them. First they should be reviewed to see if they are still needed (some indexes can impact performance negatively) and for the ones to keep, documented, as they will need to be recreated manually. They can be deleted using the Database Verification Delete Indexes of Type option ALL.

Connection Keys

  • [6.0] A trailer connection key called NOLIMIT will be automatically created and used for lengthy processes that may time out with the preset time limit. For instance, one cause of a time out can be during the rebuilding of an index for an extremely large table. If the time required to rebuild the index exceeds the timeout limit, the system will error out. By default its timeout is set to UNLIMITED. This key can be selected through the Connection Key Manager.

Editors

  • [6.1] External Command Editor has changed
    • It is now expression driven, and all external commands are now written as expressions. The seven combo boxes in the 6.0 version, for adding logical expressions, constants, formulas, etc., have been replaced by one, the Expression Selector.
    • You can now view all the Profiles and user forms to which a selected command is added directly on the External Commands Editor in the Used In list box.
  • [6.1] Constants & Expressions can be overridden by group (year and jurisdiction)
  • [6.1] Queries can be overridden by group (year and jurisdiction)
  • [6.1] Execution Context
  • [6.0] Batch Process are no longer setup by categories and are linked to the Profile
  • [6.0] Reports are no longer setup by categories and are linked to the Profile

User and System Validation Tables

  • [6.1] Generate Data Base View (If checked, will create a view
  • [6.1] Tables can be setup by Jurisdiction
  • [6.1] New flag when tables are Maintained by System
  • [6.1] Added fields can now be created in this function

Application Parameters General

  • [6.1] Roll Forward Exclusion (new functionality to exclude fields from being rolled forward)
  • [6.0] “Owner as of Month” and “+/- Years” in the GNA Department Maintenance form NEW!

Application Parameters

  • [6.1] Mass Appraisal parameters are available on OpenForms
  • [6.0] Accounts Receivable parameters are available
  • [6.0] Cash Collection parameters are available
  • [6.0] Business Tax (SRT) parameters are available
  • [6.0] Personal Property parameters are available
  • [6.0] Real Property parameters are available

User Interface

  • [6.0] The interface for the Govern New Administration has been updated to have a similar look and feel and navigation as other applications in the Govern Release 6.0 suite. Refer to GNA User Interface for interface details.

Troubleshooting

Verify Database – SYS ADMIN rights

Table Change Event Script

  • The first time a verify database is run, a script needs to be executed by a user with System ADMIN rights.
  • IMPORTANT: If your user does not have the required rights, the System DBA will need to execute the following script in each Data Base Server used for Govern deployments.

     

  • Click here for the script CreateCleanupJobForRecentTableChanges commands that can be copied and pasted directly in a query window in MS SQL Server

See Also

For additional What’s New information, refer to the What’s New OpenForms.

For changes that impacts upgrades, see Impact Assessment List

 

 

103-all-gna-wnew

 

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...

GNA – Mobile Configuration Editor

Mobile Configuration Editor

Overview

The Mobile Configuration editor allows administrators of the mGovern Mobile Solution to control aspects of the subset database that is generated for their mobile deployment. The Initialize Mobile Database process is used to create a subset of the main source database. Copies of system resources, i.e. reports, tables, views, and so on are also copied. In addition, general and selected module parameters and tables for given years are created. This process is executed at the initial setup of the Mobile device, or when changes occur in the source database. The Mobile Configuration Editor offers an interface for administrators to manage the tables, views, and functions that are transferred during the initialization process, or the refresh/update process.

Functionality

The Mobile Configuration editor is the user interface for the The Database Objects Exclusion, and the Add and Update User Tables features. This point and click interface simplifies the manual inclusion and exclusion process. For this interface, the following tables were implemented:

  • SY_MOBILE_DB_OBJ_EXCLUSION – This table will contain all object names that should be excluded during the GNA Initialize Mobile Database process.
  • SY_MOBILE_TABLE
  • SY_MOBILE_COLUMN

For more information on manually excluding objects, or adding and updating user table, see the following:

 

User Interface (UI)

The Mobile Configuration User Interface is a grid that allows for the selective exclusion of required database objects in the Mobile deployment database. The grid of the UI displays all system Tables, Views, and Functions. Each Table/View/Function is displayed as a line item in the grid. The database objects that are available for selection are accessed by selecting either the Table, Views, or Functions tab.

Mobile Configuration – Command Buttons

Save – After make selections, click Save to save you changes.
Cancel – Click Cancel [x] to cancel any changes made to the line items, i.e. objects in the grid.

Mobile Configuration grid – Column Headings

Each Table/View/Function is displayed as a line item in the grid.
Name – This column displays the system name of the Table/View/Function.
System – A checkbox is displayed in this column which corresponds to each Table/View/Function.

NOTE: Check boxes under the System column cannot be selected, if not previously selected, or deselected, if previously selected. These are System objects that are not accessible to users.

Exclude from Initialize Mobile Database

In the column heading there is a check box that will allow the selection of all objects in the grid. When the check box beside the line item under this column is selected, the database object on the line will be excluded from the Initialize Mobile Database process.
After selecting or deselecting the database objects, Tables/Views/Functions, required, click Save on the Mobile Configuration tab.

See Also

Initialize Mobile Database
Govern Mobile Technology

Govern Administrator (GNA) System Product Map

 

 

103-ed-020

 

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...

GNA – System Validation Tables

System Validation Tables

Overview

System Validation Tables are used throughout Govern to provide input for a variety of drop-down lists on the forms. Information on specific tables is provided in the documentation on the specific modules. They are similar to user validation tables, but all are maintained by Govern.

This page provides information on the general setup and features.

Documentation

To view this information in pdf format, click on the following link:
SystemValidationTableEditor.pdf

Accessing the System Validation Table Editor

Read More...

To access the System Validation Table Editor:

  1. Launch GNA.
  2. Select Editors > System Validation Table Editor.

System Validation Table Action Buttons

New
Click the New button to create a new System Validation Table. When you click New, the Cancel button is available.
Save
Click Save to save modifications to a table.
Note: The Save button is disabled for the System Validation Tables created by Govern.
Delete
When you click Delete, a confirmation message appears. If you click OK, you delete the table and the codes created for the table.
Note: The Delete button is disabled for the System Validation Tables created by Govern.
Codes
Click the Codes button to view or create

System Validation Table Parameters

Table Name
The table name is unique. Only alphabetical and underscore characters are used. All characters are in uppercase.
English / French Description
Enter a English and French descriptions for identifying the table.

System Validation Table Options

The section describes the options that are applicable to some tables.

Securable

Select this option to enable security on the validation codes for the selected table. The security is applied in the Govern Security Manager.
The following scenario illustrates how to apply security on the Permit Activities validation codes table.

Scenario: Setting Security on the Mailing Index

To enable security settings for the Mailing Index codes:

  1. Launch GNA.
  2. Select Editors > System Validation Table Editor.
  3. Select MAILTYPE – Mailing Index Type in the list of tables on the left.
  4. Select the Securable option.
  5. Click Save.

Follow the next procedure to set restriction on the Mailing Index Type Validation Codes, as required.
The Validation Codes are shown in the following screen shot:

Setting Security Permissions on the Validation Codes

To set security on the Mailing Index Codes:

  1. Launch the Govern Security Manager (GSM).
  2. Select Synchronize All.
  3. Select Applications > Validation Tables > System Validation Tables.
  4. Only the tables with the Securable option selected appear in the list.
  5. Double-click Mailing Index Type to expand the table and view the codes.
  6. Right click on the code on which you want to restrict permission.
  7. Select Exclusions.
  8. Select the users you want to exclude.
  9. Click Save.

For further details on the GSM, refer to the Govern Security Manager (GSM) documentation.

Generate Database View

Select this option to create a database view from the selected table. The view is saved under Views in the Govern database. The format is table name with the prefix V_.
To generate a Database View:

  1. Launch GNA.
  2. Select Editors > System Validation Table Editor.
  3. Select the applicable category.
  4. Select the applicable table in the list on the left.
  5. Select the Generate DB View option.
  6. Click Save.
  7. Select Utilities > Database Verification in the GNA ribbon.
  8. Run the Database Verification procedure.

Added Fields

Added fields are used for some validation tables. In this procedure, you create a new database column for the selected table.

To set up added fields for a user validation table:

  1. Launch GNA.
  2. Select Editors > System Validation Tables.
  3. Select the table.
  4. Select Add Field in the Added Fields tab.
  5. The Database Field Creation form appears.
  6. The existing columns are listed on the right.
  7. Enter the name of the new column in the New Column Name field.
  8. The Description field is automatically populated with the new column name. Modify this if required.
  9. Select a data type, such as currency, date / time, numeric, or text in the Column Type field.
  10. Click Save.

Used In

The Used In section, at the bottom of the form, lists the entities that contain the table.

Creating Validation System Codes

To create validation codes:

  1. Launch GNA.
  2. Select Editors > System Validation Tables.
  3. Select the table.
  4. Click the Codes button on the Validation Table Editor to create codes for the selected table.

The New, Save, and Delete buttons are disabled for the System Validation Codes.
Code
Enter a unique code for the validation user code. This is used for identification.
English and French Short and Long Descriptions
Enter a description to easily identify the validation code in lists and on reports.
English / French Full Description
Enter a longer description in this field. If the Use Rich Text option is selected, then character styles can be applied to the text.
Do not show the validation code on the screen.
Select this option to hide the selected validation code from view.
See Also
User Validation Table Editor

 

 

103-ED-009

 

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...

User Validation Tables

User Validation Tables

Overview

Version 6.1
Maintain the User Validation Tables in this form. These tables are used to validate the information entered in the various fields. Create and maintain the elements of the tables on the Validation Codes form.

To access the User Validation Table Editor, in the Govern New Administration (GNA):

  1. Select Setups /Editors > Editors > User Validation Table Editor…

Adding Rich Text Format to Global Messages

Read More...

You can add Rich Text Format (RTF) to Global Messages. With RTF, you can change the font and font size; add numbers or bullets; add character formatting, such as, bold, italics, or underline; change the alignment to left, center, or right; and add highlights and color to your messages.

Global messages are predefined in the Message Type User Validation Table in GNA They can be updated or modified, as required for the situation, in Govern.

For details on adding rich text format, click on the following link:
Global Messaging

Command Buttons

New: Click New to create a new System Validation Table.

NOTE: When you click on New, the button changes to Cancel ; this will allow you to cancel the creation of the current record. The Cancel button is present until the new record is saved.

Save: Click Save to save any changes to an existing validation table or to save a new table.
Delete: Click to select an existing Validation table from the List of Validation Table list on the left hand column; click Delete to delete the table.
Securable: Select Securable to enable administrators to secure the codes within the validation table. Refer to the Vertical Security section of the GSM release 4.6, or later guide.
Codes: Click Codes to access the code editor for the validation table.

Properties tab

Table Type: The Table Type is system-generated and is used, as follows:

  • R: Regular
  • A: Accounts / Receivable
  • C: Property Control (for multimedia and zoning information)
  • B: Property Control (for the Property Area function)
  • M: Mass Appraisal
  • P: Permits and Inspections
  • S: Super User
  • T: Tax: Aircraft, Boat, Motor Vehicle, Personal Property and Real Property
  • U: Utility Billing

All tables created with the User Validation Table form are automatically assigned the Regular table type.

List of Validation Tables: This column contains the list of the existing system validation tables; newly added tables will appear in this list.
Table Name: This field displays the name of the table. Use a descriptive name such as acctNum for Account Number. Table names can be a maximum of eight characters.
English / French Description: Use these fields to enter a brief description or title for the table.

Creating a User Validation Table
To create a new user validation table…:

  1. Click New to clear the form fields.
  2. Enter a Table Name.
  3. Enter a description in the Description fields.
  4. Click Save to create a new User Validation Table.

Add a User Validation Table Code
To add codes to a new or existing validation table:

  1. Either follow the steps above to create a user validation table, or select an existing table from the List of Validation Table column on the left hand side.
  2. Click Codes to display the Code Editor form.
  3. Click New to clear the form fields.
  4. Enter a Code Name; enter Short and Long Descriptions, and any other second language descriptions in the required fields.
  5. Click Save.

A Note about Validation Table Codes

When the Verify the Existence, and Creation of Database Object process is run in GNA, the Govern user validation tables; i.e, the tables that are preceded by VT_USR_ in the Govern database are transferred to a single VT_USER table. During this process all codes are also transferred. Note that there is no process to copy the codes for User Validation tables that are created in GNA to Govern for Windows.

Permit Type Validation

In the Code Editor, it is possible to configure the system to apply a name type validation. This validation or filter is based upon the permit type that is being created. By default, when linking a name type, regardless of what permit type is being selected the system will display all name types. This applies to linking a name to a Complaint/Greivance/Request For Service/Workflow, Offence / Violation, or Permit/License/Certificate permit type in Govern.NET. When there are many name types in the list, the searching process for the name type can be tedious. When the validation filter is used, only the name types that apply to the permit type is displayed.
Permit Types that can be filtered are as follows:

  • Complaints/Workflows/Grievance/Request for Services
  • Offences/Violations
  • Permits/Licenses/Certificates

 

See Also

System Validation Table Editor

 

 

103-ed-010-v6-0

 

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...

GNA – User Validation Tables

User Validation Tables

Overview

User Validation Tables are used throughout Govern to provide input for a variety of drop-down lists on the forms. Information on specific tables is provided in the documentation on the specific modules. This page provides information on the general setup and features.

Accessing the User Validation Table Editor

To access the User Validation Table Editor:

  1. Launch GNA.
  2. Select Editors > User Validation Table Editor.
  3. Select one of the following:
  • Regular
  • Accounts Receivable
  • Mass Appraisal
  • Workflow Management
  • Property Control
  • Tax Billing
  • Utility Billing
NOTE: Some tables that are specific to a module, such as Accounts Receivable, are found under Regular.

Read More...

Documentation

To view this information in pdf format, click on the following link:
UserValidationTableEditor.pdf

User Validation Table Action Buttons

New
Click the New button to create a new User Validation Table. The table is created under the selected menu; i.e., if you selected Accounts Receivable from the User Validation Table Editor menu, the new table is created under Accounts Receivable.
When you click New, the Cancel button is available.
Save
Click Save to save modifications to a table.
Delete
When you click Delete, a confirmation message appears. If you click OK, you delete the table and the codes created for the table.
Codes
Click the Codes button to view or create

User Validation Table Parameters

Table Name
Enter a unique name for the table. Only alphabetical and underscore characters can be saved. Characters are automatically entered in uppercase.
English / French Description
Enter a English and French descriptions for identifying the table.

User Validation Table Options

The section describes the options that are applicable to some tables.

Securable

Select this option to enable security on the validation codes for the selected table. The security is applied in the Govern Security Manager.
The following scenario illustrates how to apply security on the Permit Activities validation codes table.

Scenario: Setting Security on the Permit Activities Codes

To enable security settings for the Permit Activities codes:

  1. Launch GNA.
  2. Select Editors > User Validation Table Editor > Workflow Management.
  3. Select DEPPMACT – Permit Activities in the list of tables on the left.
  4. Select the Securable option.
  5. Click Save.
  6. Follow the next procedure to set restriction on the Permit Activities Codes, as required.

Setting Security Permissions on the Validation Codes

To set security on the Permit Activities Codes:

  1. Launch the Govern Security Manager (GSM).
  2. Select Synchronize All.
  3. Select Applications > Validation Tables > User Validation Tables
  4. Double-click Permit Activities to expand the table and view the codes.
  5. Right click on the code on which you want to restrict permission.
  6. Select Exclusions.
  7. Select the users you want to exclude.
  8. Click Save.

For further details on the GSM, refer to the Govern Security Manager (GSM) documentation.

Generate Database View

Select this option to create a database view from the selected table. The view is saved under Views in the Govern database. The format is table name with the prefix V_. You must run the Database Verification to complete the procedure.
To generate a Database View:

  1. Launch GNA.
  2. Select Editors > User Validation Table Editor.
  3. Select the applicable category.
  4. Select the applicable table in the list on the left.
  5. Select the Generate DB View option.
  6. Click Save.
  7. Select Utilities > Database Verification in the GNA ribbon.
  8. Run the Database Verification procedure.

Maintained By System

The Maintained By System option is selected for the user validation tables that are created and maintained by Govern.
This option cannot be modified from the User Validation Table Editor form.

Use Rich Text

You can now add Rich Text Format (RTF) to the full description of all user validation tables. This is particularly useful for Global Messages. With RTF, you can change the font and font size; add numbers or bullets; add character formatting, such as, bold, italics, or underline; change the alignment to left, center, or right; and add highlights and color to your messages.
Global messages are predefined in the Message Type User Validation Table under the Editors menu in GNA These messages can be modified in Govern, as required for the situation.
For details on adding rich text format, click on the following link:
Global Messaging

By Year

This option is selected for the user validation tables that are maintained by year. For example, many Mass Appraisal user validation tables are defined by year. These tables are defined in Govern and cannot be modified on this GNA form. However, you can create new tables By Year.

When the By Year option is selected, the Year ID column is added to the Validation Codes form for the table.

The Year parameter displays the year for the selected validation code.

You can set a validation code in one year to Is History, while maintaining the code in other years.

By Jurisdiction

This option is selected for the user validation tables that are defined for a specific jurisdiction. This tables are defined in Govern and cannot be modified on this GNA form. However, you can create new tables By Jurisdiction.
The Jurisdiction column is added to the table.

The Jurisdiction is listed by code in the column. It is listed by Code and Short Description in the Jurisdiction parameter at the bottom of the form.

By Department

This option is selected for the user validation tables that are set up by department. For example, the Workflow Management user validation tables are defined by department. This tables are defined in Govern and cannot be modified on this GNA form. However, you can create new tables By Department.

If the By Department option is selected, the Department column is added to the validation codes for the table. This is shown in the following screen shot of the Permit Activities table:

Note that the departments are listed by code in the Department column. However, the code and short description are provided in the Department parameter under the table.

Added Fields

Added fields are used for some validation tables. In this procedure, you create a new database column for the selected table.
To set up added fields for a user validation table:

  1. Launch GNA.
  2. Select Editors > User Validation Tables.
  3. Select the category, such as Regular or Mass Appraisal.
  4. Select the table.
  5. Select Add Field in the Added Fields tab.The Database Field Creation form appears.The existing columns are listed on the right.
  6. Enter the name of the new column in the New Column Name field.
  7. The Description field is automatically populated with the new column name. Modify this if required.
  8. Select a data type, such as currency, date / time, numeric, or text in the Column Type field.
  9. Click Save.

Used In

The Used In section, at the bottom of the form, lists the entities that contain the selected table.

Creating Validation User Codes

Click the Codes button on the Validation Table Editor to create codes for the selected table.

Code

Enter a unique code for the validation user code. This is used for identification.

English and French Short and Long Descriptions

Enter a description to easily identify the validation code in lists and on reports.

English / French Full Description

Enter a longer description in this field. If the Use Rich Text option is selected, then character styles can be applied to the text.

Is History

Select this option if the selected validation code is no longer required. This option is useful if the validation code is used in records from previous years that you are maintaining, but is not applicable for any current or future records.

To apply the Is History option:

  1. Launch GNA.
  2. Select Editors > User Validation Tables.
  3. Select the category, such as Regular or Mass Appraisal.
  4. Select Editors > User Validation Tables.
  5. Select the table.
  6. Click the Codes button to open the Validation Codes Editor for the table.
  7. Select the code that is no longer required.
  8. Select Is History.
  9. Click Save.

If you decide that you would like to reinstate the code, you can deselect this option at any time.

Scenario: The Is History Option on Property Records

The following scenario illustrates how the Is History option can be applied to property records.
In this scenario, one of the validation codes in the Mass Appraisal Value Change table is no longer needed. The Is History option is applied.
In the first screen shot, the Environmental Disaster option is selected for the Change Reason on a Mass Appraisal Property Information record for the last time.

To apply the Is History option to this code.

  1. Launch GNA.
  2. Select Editors > User Validation Tables > Mass Appraisal.
  3. Select the MA_CHNG – Appraisal Change reason table.
  4. Note that the entity that uses the table is displayed under Used In.
  5. Click the Codes button to open the Validation Codes Editor.
  6. Select the Environmental Disaster code.
  7. Select Is History.
  8. Click Save.

To view the change in Govern:

  1. Launch Govern.
  2. Select a Profile that contains the Mass Appraisal Property Information.
  3. Select the Property Information form.
  4. Expand the Value Change drop-down list.
  5. Note that the Environmental Disaster option is not there.
  6. Select a record on which this code was previously selected.
  7. Note that the code is still selected for the record, but that a dot appears it.

See Also

System Validation Table Editor

 

 

103-ed-010

 

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...

GNA – Data Mapping Editor

Data Mapping Editor

Overview

When an external application, e.g. a GIS application, is required to communicate with the Govern system, it will need to understand how data is stored within the system. Govern’s Web service methods accept requests, to Retrieve, Update, or Delete data.
The Data Mapping Editor allows users to map specific tables and columns within the Govern database to unique Data Element Names. When the application makes a request from Govern, the data element names must be included in the methods that are sent to the Web services.
There are specific rules that are required when making a request to the Web Service, e.g. the Data Element Name of the data map must exist, or the parcel ID requested must exist in the database, etc. Refer to the MS Govern Property Control System Service API guide for the list of methods and file structure details.
There are three (3) tables in the Property Control section that can currently be updated, (Table: PC_AREA, PC_PARCEL, and PC_LEGAL_INFO).

To access the Data Mapping Editor…

  1. In GNA select Setups/Editors > Editors > Data Mapping Editor…

Read More...

Data Mapping Editor buttons

New – To create a new data mapping record click New.
Cancel – Use Cancel to cancel the creation of an new entry. The Cancel button replaces the New button a save of the entry is made.
Save – Click Save to save a new record or any changes to an existing record. New records will appear under the List of Data Mappings column on the left hand side of the editor.
Delete – After selecting an existing mapping record from the List of Data Mappings list on the left hand column, click Delete to delete the record.

Data Mapping Editor parameters

Choosing Data Element Names – The names that are used for Data Elements must ensure that no Special Characters or Reserved Keywords are used. Refer to Govern Keywords for a list of keywords that should not be used.

Oracle Users and Data Element Names

Due to the case sensitivity of table names, a convention of all Uppercase or all Lowercase names should be decided upon. Do not use any Oracle Keywords for Data Element Names.

Data Element Name

Specify a Data Element Name for the mapping record. This is a unique name that must be included in the request from the external application to the Web service.

NOTE: This field has a maximum of 15 characters; no special characters or spaces are allowed.

Enter a descriptive name for the mapping record that will be used in the following parameters:

English Short Description – Enter a short description for the mapping record. This is useful for fast data entry and look-ups if space is limited on the forms.
English Long Description – Enter a long description for the mapping record. This will be displayed for look-ups on forms and is normally used for reporting.

Second Language Fields

When there is a 2nd language, or multiple languages, ensure that these description fields are also completed; i.e. French Short Description, and French Long Description.
Table Name – From the drop down menu, select the name of the Govern table that the data will be mapped to. Available tables are:

  • PC_LEGAL_INFO
  • PC_AREA
  • PC_PARCEL

Column Name – The table columns that are listed are filtered according to the table that is selected in the Table Name parameter.

Creating a Data Map record

To create a data map record, use a Data Element Name that will be acceptable to the requesting external application. This name will be used in the method that will be sent to the Web service.

  1. On the GNA ribbon, select Editors (tab) > Data Mapping Editor…
  2. Click New in the Data Mapping Editor.
  3. Locate the parameter called Data Element Name; enter the Data Element Name.
  4. If not expanded click the expansion arrow (A) to display the additional parameters in the form; complete the parameters.
  5. Select a table from the Table Name drop down menu.
  6. Choose a column name within the table that was selected.
  7. Click Save to save the mapping record to database.

When the external application makes a request to the web service, if the Data Element Name is in the method, the data will be retrieved, updated or deleted from the Govern database.
Testing a Web Service Request

As an example, we want to make a request that will obtain the tax map and the zoning information of the following Parcel ID’s, 16800, 16804, and 16807. This can be done in three (3) steps.

STEP 1 – Create the data mapping records

It is necessary to create the data mapping records for the elements that will be called in the method structure. For our example we will be using the pcTaxMap and areaZoning elements.

  1. On the GNA ribbon, select Editors (tab) > Data Mapping Editor…
  2. Click New, to create a new Data Mapping Record.
  3. Enter a Data Element Name of pcTaxMap.
  4. Click to expand the fields and enter an English Short and Long Description; enter PC Tax Map as a description.
  5. The tax map information will be coming from is the PC_AREA table in the ZONING column; select PC_PARCEL for the Table Name, and TAX_MAP for the Column Name.
  6. Click Save to save your mapping record.

Repeat the above steps to create the areaZoning data element. Use PC Area Zone as the description. The Table Name and Column Name are PC_AREA and ZONING

STEP 2 – Create the XML request structure

Refer to the Service Contract section of the MS Govern Property Control System Service API guide; this will provide you with the expected structure of the MSGovern_GetElementValue function. From the guide we obtain the following information:

Function MSGovern_GetElementValue (
ByVal strXmlElement As String ) As String
The retrieve elements must in structure of xml:
<?xml version=”1.0″ encoding=”utf-8″?>
<getElementValue>
<ParcelIds>
<ParcelId value=”16800″/>
<ParcelId value=”16807″/>
<ParcelId value=”23452″/>
</ParcelIds>
<ElementItems>
<ElementItem name=”areaZoning”/>
<ElementItem name=” areaSchDist “/>
</ElementItems>
</getElementValue>

For our example we will use the following…

<?xml version=”1.0″ encoding=”utf-8″?>
<getElementValue>
<ParcelIds>
<ParcelId value=”16800″/>
<ParcelId value=”16804″/>
<ParcelId value=”16807″/>
</ParcelIds>
<ElementItems>
<ElementItem name=”pcTaxMap”/>
<ElementItem name=”areaZoning”/>
</ElementItems>
</getElementValue>

The Parcel ID’s that we are requesting are specified within the <ParcelIds> tags. our Element Items are specified within the <ElementItems> tags. Note that the names are identical to what was specified in GNA in STEP 1 above.

NOTE: Verify that the XML structure is identical to specifications in the MS Govern Property Control System Service API document.

Always ensure that the Element Item name is identical to the one created in GNA.

STEP 3 – Validate the XML request with the Test Client

Locate the WcfTestClient.exe application that is included with the WCF PC Web Services package. This program is usually located in a folder called Test Application. Refer to the MS Govern Property Control Service Setup and Configuration guide for details about using the test application.

  1. Start the test application; add the WCF Service.
  2. On the left hand side, under the list of available methods in the service, locate the MSGovern_GetElementValue() method.
  3. Double click on the method to load it in the Test Client.
NOTE: A limitation of the supplied test client is that Return characters and Line feeds are not recognized. These characters must be manually removed in the editor.

As an example, the following formatting will become a single line when the returns and line feeds are removed.

<?xml version=”1.0″ encoding=”utf-8″?>
<getElementValue>
<ParcelIds>
<ParcelId value=”16800″/>
<ParcelId value=”16804″/>
<ParcelId value=”16807″/>
</ParcelIds>
<ElementItems>
<ElementItem name=”pcTaxMap”/>
<ElementItem name=”areaZoning”/>
</ElementItems>
</getElementValue>

becomes…

<?xml version=”1.0″ encoding=”utf-8″?><getElementValue><ParcelIds><ParcelId value=”16800″/><ParcelId value=”16804″/><ParcelId value=”16807″/></ParcelIds><ElementItems><ElementItem name=”pcTaxMap”/><ElementItem name=”areaZoning”/></ElementItems></getElementValue>

The above is only a charateristic of this test client; other clients may differ in behavior.

4. Copy the single line version of your XML code and paste it into the Value field in the Test Client.
5. Click Invoke; any errors will be displayed in a dialog box.
6. When the action is successful, a response is displayed in the Response pane of the Test Client.

Viewing the Results

In the Test Client, the request and response parameters can be displayed in two (2) modes, Formatted, and XML. You can switch between the two views with a click on the corresponding tabs along the bottom of the Request pane. When you are in XML mode results from the successful requests to the Service can be observed.

 

 

103-ED-011

 

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...