GNA – Queries – Special Cases

Special Cases

Obtaining a Value when No Govern ID is Present

SQL Queries are used for Calculated Fields, Formulas, and Logical Expressions. In the SQL Query Editor, users are provided with a list of Govern ID’s that are used as keywords in queries. A Keyword type was introduced in Release 4.7, 5.1, and Release 6.0. When building a query, instead of using Govern ID’s, the attribute name in a Business Entity (BE) can be used to read its value.
An advantage of the attribute keyword search syntax is that it can be used to obtain attribute values from Business Entities (BE’s) that do not use any Govern ID’s. As long as the attribute is specified explicitly, its value can be obtained from the associated BE.

Read More...

EXAMPLE
In the following example, we want to compare an NA_ID value in the NA_NAMES table with the values FREE_LINES_X, where X is a value of 1 to 6; these values are stored in the NA_LK_TO_NAME Business Entity.
In the query sample, using the SELECT and CASE statement, the values contained in FREE_LINE_1, FREE_LINE_2, FREE_LINE_3, FREE_LINE_4, FREE_LINE_5, and FREE_LINE_6 can be retrieved.
LTRIM – Removes any leading spaces; CAST – Casts the value as a variable character type

Query Fragment

SELECT (LTRIM(CAST((CASE WHEN NA_NAMES.FREE_LINE_1 IS NOT NULL
THEN NA_NAMES.FREE_LINE_1
ELSE ” END)
AS VARCHAR(80)) ||
CAST((CASE WHEN NA_NAMES.FREE_LINE_2 IS NOT NULL
THEN CHAR(13) || CHAR(10) || NA_NAMES.FREE_LINE_2
ELSE ” END)
AS VARCHAR(80)) ||
CAST((CASE WHEN NA_NAMES.FREE_LINE_3 IS NOT NULL
THEN CHAR(13) ||CHAR(10) || NA_NAMES.FREE_LINE_3
ELSE ” END)
AS VARCHAR(80)) ||
CAST((CASE WHEN NA_NAMES.FREE_LINE_4 IS NOT NULL
THEN CHAR(13) ||CHAR(10) ||
NA_NAMES.FREE_LINE_4 ELSE ” END)
AS VARCHAR(80)) ||
CAST((CASE WHEN NA_NAMES.FREE_LINE_5 IS NOT NULL
THEN CHAR(13) ||CHAR(10) || NA_NAMES.FREE_LINE_5
ELSE ” END)
AS VARCHAR(80)) ||
CAST((CASE WHEN NA_NAMES.FREE_LINE_6 IS NOT NULL
THEN CHAR(13) ||CHAR(10) || NA_NAMES.FREE_LINE_6
ELSE ” END)
AS VARCHAR(80)))) NAME_DESC
FROM NA_NAMES
WHERE NA_NAMES.NA_ID=attr@NA_LK_TO_NAME.LINK_NA_ID

Prior to the Entity/Attribute keyword, the FREE_LINES_X values could not be obtained in the traditional manner because it is not a Govern ID. With the keyword we are able to compare the value of FREE_LINE_X with our NA_ID.
To do a comparison with a SQL query, the syntax for our keyword (attr@EntityName.AttributeName) will specify the code from the entity and
the name of the required attribute.
In the last line of the query sample, the value in the NA_ID is compared to the value in the LINK_NA_ID in the NA_LK_TO_NAME Business Entity.
NA_NAMES.NA_ID=attr@NA_LK_TO_NAME.LINK_NA_ID
…where…
EntityName = NA_LK_TO_NAME and AttributeName = LINK_NA_ID

NOTE: Currently the entity and attribute names are entered manually, therefore caution should used when typing.

Related Topics

 

 

100-Queries-(Special Cases)

 

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 – Queries

SQL Syntax Rules for GNA

Release 6.0 | Release 6.1

Govern Data Access Block (DAB)

The Data Access Block or DAB has several functions in the Govern system. One of these functions is to act as the intermediary between the .NET applications and the database. SQL queries that are used by Govern must go through the DAB. While SQL can be flexible with its syntax, due to its many functions, the DAB must be stricter with syntax. In short what may work in SQL, may have to be modified for the DAB. In fact some of the rules that the DAB requires you to follow are good practises for SQL as well.

The following guidelines and examples have been collected to increase your level of success with Govern SQL queries.

Basic SQL Query Guidelines

A. Field in Table is Always on the Left Hand Side

When creating your query statement, the field that you are referencing in the table should always be on the left hand side (LHS), and the Dynamic Search object should always be on the right hand side (RHS).

Read More...

For Example:

In the following SQL statement …

NOT VALID: WHERE @pmnumber_1=PM_MASTER.PM_NUMBER

NOTE: The above statement is valid in SQL, but it will fail in Govern. The Data Access Block (DAB) will not interpret it correctly.

Should be written as…

VALID: WHERE PM_MASTER.PM_NUMBER=@pmnumber_1

B. No Spaces Allowed after Logical Operators

OPERATORS
Symbol Description
= Equal To
<> Not Equal To
> Greater Than
< Less Than
>= Greater Than or Equal To
<= Less Than or Equal To

 

For Example:

NOT VALID: WHERE PC_PARCEL.PID1 > PC_PARCEL.ID2

should be written as…

VALID: WHERE PC_PARCEL.PID1>PC_PARCEL.ID2

C. Space Before and After LIKE Operator

The LIKE pattern matching operator is used to select only rows that are “like” what you specify. When using it ensure that there is a space before and a space after the operator.

For Example:

NOT VALID: WHERE PC_PARCEL.PID1LIKEPC_PARCEL.P_ID

should be written as…

VALID: WHERE PC_PARCEL.PID1 LIKE PC_PARCEL.P_ID

D. Always Specify Tables and Fields in Statements

When writing statements, always specify Tables then Fields (TABLE.FIELD). This applies even in cases where you are referring to a single table and there would be no ambiguity.

For Example:

The following statement…

SELECT NA_ID, INDEX, DESC FROM NA_NAMES WHERE NA_ID=@nanameid_0

is the same as ….

SELECT NA_NAMES.NA_ID, NA_NAMES.INDEX, NA_NAMES.DESC FROM NA_NAMES WHERE NA_NAMES.NA_ID=@nanameid_0

In the first statement we are only specifying the columns in the NA_NAMES table. This would not pose as a problem if we are only dealing with one table. Realistically, we will often have to interact with multiple tables, and many tables have the same column names; this would create an ambiguity. The system would not know which table is being referred to.

Release 6.0

What’s New

Related current changes to the working of Queries in Release 6.0 will be indicated below.

Release 6.1

What’s New

The following are current changes to the working of Queries in Release 6.1.

Nomenclature

As of Release 6.1, it is mandatory that query names must begin with a letter. [Release 6.1.1506.82]

Related Topics

Query Types
Advanced SQL Queries
Keywords
Best Practices for SQL Queries
Special Cases

Code Keyword Description
ar_id Account Receivable ID Unique identification number of the current Account Receivable record
key_counter Activity ID Identification number of the current Activity record
ac_id Aircraft ID Unique identification number of the current Aircraft Excise Tax record
br_id Bankruptcy ID Identification number of the current Bankruptcy record
bt_id Boat ID Unique identification number of the current Boat Excise Tax record
bldg_id Building ID Identification number of the current Building
bldg_seq Building Sequence Sequence number of the current Building
cc_id Cash Collection ID Identification number of the current Cash Collection record
co_id Complaint ID Identification number of the current Complaint record
*date Current Date The Current Date
dept Department The Department code
frozen_id Frozen ID Identification number of the current Frozen record
haz_id Hazard ID Identification number of the current Hazard record
h_id Hearing ID Identification number of the current Hearing record
in_id Inspection ID Identification number of the current Inspection record
land_id Land ID Unique identification number of the current Land
mb_id Misc. Billing ID Identification number of the current Miscellaneous Billing account
misc_id Miscelleaneous ID Identification number of the current Miscellaneous Billing account
mv_id Motor Vehicule ID Identification number of the current Motor Vehicle Account
na_id Name ID Unique identification number of the current Name
of_id Offence ID Unique identification number of the current Offense record
p_id Parcel ID Unique identification number of the current parcel
pm_id Permit ID Unique identification number of the current Building Permit, Electrical Permit, General Permit, Plumbing Permit, Permit to Name, Animal License, Business License, License to Name, Approval, Bond, Decision, Prosecution or Appeal record
pp_id Personal Property ID Identification number of the current Personal Property account
pp_det_id PP Detail ID Unique identification number of the current Personal Property Item
folio_id Project Folio ID Identification number of the current Project Folio
prj_id Project ID Identification number of the current Project record
tax_id Real Estate ID Identification number of the current Real Estate Tax record
sale_id Sale ID Identification number of the current Sale record
st_acct_id Self Reported Tax Acct ID Identification number of the current Self Reported Tax Account record
st_id Self Reported Tax ID Identification number of the current Self Reported Tax record
si_id Site ID Identification number of the current Site
sa_id Special Assessment ID Identification number of the current Special Assessment record
tax_map Tax Map Number Tax Map Number of the current record
usr_id User ID Unique identification number of the current user
ub_id Utility Billing ID Unique identification number of the current Utility Billing account
year_id Year ID Year identification of the current record

 

100-Queries

 

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

Reporting Govern Actions

Reporting Govern Actions

Version 6.0 and Version 6.1

Overview

A GovernAction is a link between a method (InsertData) and a report. GovernActions take the form of a report object with a name that has a ‘GovernAction’ prefix, and value format. The process is similar to an Insert or Update action in the database. GovernActions are executed just prior to Displaying, Exporting, or Printing a report. Users should note that there is no Log, or indication of the running of the GovernAction. If the Govern Action triggers an exception, execution of the report stops, and the error is displayed but it is not handled. The GovernAction is designed to be triggered from any Govern report, but currently the action is only configured through Crystal Reports.
Govern Actions are an efficient way to…

  1. Perform an audit on parcels that have been accessed using Crystal Report.
  2. Provides a secure, and controlled method of inserting data in tables.

Have a report display information on multiple accounts, the report can then generate history information in the table and show new data that has been inserted; this new data is inserted in the (Table: ST_EVENT_HIST)

Read More...

Documentation

User

Click below to display or download the user documentation
100-reporting-GovernActions.pdf

Technical

Click below to display or download the technical documentation.
100-reporting-GovernActions-TECH.pdf

Related Topics

OpenForms Reporting Features

What’s New!

Changes Due to Refactoring

NEW! As a result of recent refactoring, the following two (2) changes have been made to the Govern Actions.

Placement of Govern Actions in Crystal Reports

Govern Actions no longer need to be placed exclusively in the Details section in a Crystal Report; Actions may now be placed in any of the main sections available to Crystal, i.e. Report Header, Page Header, Details, Report Footer, and Page Footer.

Grouping Allowed

A Crystal Report report can now have grouping and Govern Actions at the same time. For example there could grouping under an ST_ID. The methodology employed involves parsing the exported XML file and identifying required keywords.

NOTE: There is a limitation to the size of the XML file that is parsed; file size should not exceed 2 GB.

 

 

100-reporting-GovernActions

 

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

OpenForms Reference

OpenForms Reference

Overview

The following is listed for information only. When there is a discrepancy, refer to the List of Changes Tables section of the Govern Database Diagrams page for the latest information and changes in the database structure or forms.

EMT Tool (Import Export)

XML files are located in the system library under:

  • FormReference.xml
  • DynamicSearch.xml

List of OpenForms Standard Forms

The following are links to the list of OpenForms standard forms that are found in the OpenForms release reference database.

Changes

Read More...

Changes made to the OpenForms supported items (forms, models, system tables, etc.) will be listed by date and version on this page (100-ofr-new). We suggest you setup a notification if you are in an implementation project or just to be informed.

Tables deleted or obsolete

OFR Product Catalog Codes

System Module Type Version Name OFR
101 ma ofr 1 [v6.0] CAMA Building Drawing ma001
101 ma ofr 14 [v6.0] CAMA Property Info ma014
101 ma ofr 15 [v6.0] CAMA Sale info ma015
101 ma ofr 17 [v6.0] CAMA Land ma017
101 ma ofr 21 [v6.0] CAMA Value Override ma026
101 ma ofr 26 [v6.0] CAMA Buildings (contains BSE) ma026
101 ma ofr 71 [v6.0] Combined CAMA Prop Info (014) + PC Area (017) + PC Legal (018)
101 na ofr 1 [v6.0] Name & Adress na001
101 na ofr 2 dash [v6.0] Name Summary na_sum
101 na ofr 35 [v6.0] Name Linking na035
101 pc ofr 1 [v6.0] Property Parcel Information pc001
101 pc ofr 2 dash [v6.0] Property Summary pc_sum
101 pc ofr 17 [v6.0] Property Area pc017
101 pc ofr 18 [v6.0] Legal pc018
101 pc ofr 38 [v6.0] Deed pc038
101 pc ofr 39 [v6.0] Combined PC Parcel (012) + PC Property Location (004)

 

 

100-ofr

 

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

100-bp-Execution

Standard Batch Process – Execution & Connection

Version 6.0 and Version 6.1 (In Development)

Overview

The following explains the type and mode of batch executions.

Transaction Type

A Govern batch process can run synchronously or asynchronously.

Synch

In synchronous batch processing, transactions are processed one after another in a sequence.
If there are multiple steps in the process, one step is completed before the next begins.

Asynch

In asynchronous processing, multiple operations are started and run at the same time. As soon as one finishes, the next begins.
Multiple steps can run at the same time; for example, steps one, two, three, and four can all begin at the same time.
For long batch processes, using asynchronous batch processing can speed up the transaction time, because multiple computer operations or threads are processed at the same time compared to synchronous batch processing, where one operation has to finish before the next can begin.

IMPORTANT: If a batch process has multiple steps that need to be performed in order; for example, if the results of the first step are required for a calculation in the second step, use synchronous batch processing.

 

Connection Pool

You can define a Maximum Connection Pool Size for asynchronous batch processing in the addition to the general Connection Pool Size. You can also set a Connection time out for batch processes.
These parameters are defined on the Connection Key General Parameters Management form in GNA.

The Connection Pool is the number of connections that can be open on the server at the same time. Connections are required for the asynchronous batch processes. They are used by the threads to perform operations for batch processing. They are also required for all other Govern operations from all deployments in your organization.

The Connection Time Out refers to the length of time that a batch process executes a query before a time out occurs. The default is zero (0). This means that there is no time out.

Transaction Mode

Select one of the following transaction modes for the process.
Break If One Transaction Failed
The process terminates when the transaction fails.

Roll Back If One Transaction Failed
The process terminates when a transaction fails. All the transactions that were completed are cancelled. All the computations are returned to the starting point.

IMPORTANT: The roll back can take a long time to execute if the error occurred at the end of the process.

Continue If One Transaction Failed
The process continues to run even if a transaction fails.

 

 

100-bp-Execution

 

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

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