103-UI-001

GNA Standard User Interface (UI)

The following are the standard UI for the Govern New Administration (GNA). These interface features include Editors, Configuration screens, command buttons, parameters, drop down menus (combo boxes), and so on.

Introduction

The Govern New Administration (GNA) user interface was redesigned for Release 6.0 and upwards. The interface uses ribbons for quick access to the required areas of the application. Forms are now accessible through tabs on the ribbons. Presentation of forms can be changed from the standard Multi-window forms, overlapped and staggered, to a tabbed layout. GNA applications are arranged under the tabs that logically groups them by their function. With the exception of the File tab, GNA applications are found under one of the following tabs:

  • Options
  • System Parameters
  • Applications Configurations
  • Editors
  • Utilities
  • Windows
  • Help

Overview

The Editors tab contains the forms and editors required to create and edit components that are used within the Govern suite of application. These components can be OpenForm Profiles, Field Masks, Constant Values, SQL Queries, Formulas, Expressions, SQL Queries, and Validation Tables to name a few.

Standard Editors

The majority of editors within the Govern New Administration (GNA) are referred to as “standard” because of the common features in their interfaces.
GNA Standard editors can be found by selecting Editors (tab) > Editors (group) > “Name of the Editor”

Command Buttons (Common)

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.

Codes: Click Codes to access the code editor for the validation table.

NOTE: With Release 6.1 a Standard Template(s) has been introduced in GNA. This template will be applied for most of the Editors and Tables needed in the Mass Appraisal module.

Interface Exceptions

Below are featured interface exceptions.

Mass Appraisal – Multiple Years with Link MA Group Option

The following explains how to navigate multiple years with the new Link MA Group option.
– COMING – The number involves and rules.

Related Topics

Govern New Administration (GNA)

 

 

103-ui-001

 

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 – Report Editor

Report Editor

Overview

The Report Parameters Editor form is used to configure reports on an individual basis. These reports display query results found in the fields of tables within the data source.
Reports are given access through the default connection key. If required, they may also be configured using an alternate connection key. As long as the alternate connection key has been defined in the Connection Key Management form, it will be available in the Alternate Connection Key list. See Alternate Connection Key Properties group for details about alternate connection keys. In Release 6.0 of GNA, there is enhanced support for SQL Server Reporting Services (SSRS)™. SSRS reports and Crystal Reports™ are configured in the OpenForms General Settings form, see OpenForms™ General Settings for details.

Intelligent Scanning in Reports Editor

There is an underlying intelligence in the functioning of the Reports editor. Both SQL Server Reporting Service (SSRS) and Crystal Reports reports are read, and the data sources are scanned.
Connection options to the database are by default specified as the current connection. If required, secondary sources can be selected from a list of alternate Connection Keys. During the initial scanning phase, if a report is determined to be invalid, i.e. incompatible, a warning is displayed in the form of a window with a list of the offending reports.

NOTE: When there is no backwards compatibility with a report, the default connection setting will be used.

Details of the Report Scanning Process
When the Report Editor is launched, each report that is selected from the List of Reports list is scanned. The report connection key is tested. When the system encounters either a Crystal Report or an SSRS report that is not associated with a Govern connection key, the system will ask to associate the report with…:

  • The current Connection Key (Default) OR
  • The user can see the path to the data source, and may select a connection key from the list of available Alternate Connection Keys.

During the “Database Verification” process…

After performing an update / general maintenance, or defining database connections, running the Database Verification process is recommended as it will update the database for access by Govern applications.When this process is run in GNA, during the Misc. Corrections phase a script performs the following:

  • Conversion of Alternate Connection Key information (i.e. server, database names, etc.) into the Connection Key in the new table.

The following four (4) fields will be set to NULL:

  • [DTSRC_SERVER]
  • [DTSRC_DBNAME]
  • [DTSRC_UID]
  • [DTSRC_PASSW]

Note: In the SY_REGISTRY screen, four key names were removed,

  • [DTSRC_SERVER]
  • [DTSRC_DBNAME]
  • [DTSRC_UID]

Record Set Key: This option provides the ability to run the report by dataset, e.g. current P_ID, current dataset, or database. In the drop down menu list, select the primary key that will be used by this report, otherwise the user will not be prompted to select a dataset for the report.

NOTE: A Record Set Key should be specified.

The report dataset will be filtered with a list of values for the selected key.
Example: SELECT * FROM pc_parcel WHERE p_id = ‘123’ OR p_id = ‘456’ etc.

Report Criteria: Click Report Criteria (A) to display the editor. The Report Criteria Editor is used to configure prompts for reports that require user input. See Report Criteria Editor on page 85 for details on configuring prompts.

The report dataset will be filtered with a unique value for the selected keys.

For Example…
SELECT * FROM pc_parcel WHERE p_id = ‘123’

Criteria Key group

Add Criteria Key: Click Add Criteria Key to display the criteria key list; select one or more criteria to be added, click OK or Cancel.
Remove Criteria Key: Select a criteria key from the Criteria Key list and click Remove Criteria Key to remove it from the list.

Alternate Connection Key Properties group

Although database connection parameters are set in the Govern DeployEZ™, they can be overridden on a report by report basis. If required, each report can be configured with an alternate connection key.

NOTE: All settings made in this section override the current, default, connection key. Users should ensure that the alternate connection
key required has been entered in the Connection Key Management form. See The Connection Key Management form.

Data Source: This is the path to the server that the report will be accessing.
Alternate Connection Key: Select an alternate Connection Key from the list.

Report Group

This parameter contains the Report Grouping for the Report Explorer in Govern.
Upper/Lower Level: Select configure these parameters to indicate the location of the report in the Treeview pane in Govern.
For Example…
When the following report, Mass App.- Inventory Report is configured to appear in the following Report Group; Upper Level: List & Reports, and Lower Level: CAMA. In Govern, the report will appear in the List & Report upper folder (A) and CAMA lower folder (B):

See Also

Report Criteria Editor

 

 

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

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

GNA – Number Format Editor

Number Format Editor

Overview

The Number Format Editor is new in Govern OpenForms, version 6. It is used for creating formats, such as currency symbols, one thousand separators, and negative symbols, for the values that are displayed on Govern user forms.

The formats are created in the Number Format Editor in GNA. As described in the documentation, they can be selected in the Business Entity Designer (BED) and applied to any numeric attribute of the data type integer or real. Once they are applied, they are displayed on the user form in Govern.

The formats can also be used in the definition of Mass Appraisal Tables (Land, Building, MRA, Site, Income).

Features & Benefits

With the Govern OpenForms Number Format Editor, you can:

  • Create formatting for numeric attributes
  • Create multiple formatting types
  • Preview formats as you are create them
  • Keep track of the attributes that use each format type

 

Number Format Editor UI

The Number Format Editor is available under the GNA > Editors menu. It has three panels. On the left, all the number formats in your deployment are listed. The list includes the default formats and the formats that you created.When you select a format, you can see the details in the center panel, and a list of the entities and attributes that use the format on the right.

Documentation

For details about setting up and using a number format, see the Number Format Editor 6.0

 

 

103-ed-008

 

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

eGov – Parameters

eGovern – Public Self Service Portal (Admin Parameters)

Overview

Configuration of the eGovern – Public Self Service Portal is carried out with the Govern New Administration (GNA) Release 6.0 or greater, and the Govern Admin release 10.8 in Govern for Windows.

eGovern Editors

The editors for configuration of the eGovern – Public Self Service Portal are listed below.

Manage Web Site

To access the configuration parameters:

In the GNA ribbon …
1. Select Application Configurations (tab) > Web Configuration (group) > Manage Web Site.
2. In the Manage Web Site form, click the General tab.
3. Locate the Mail group.
4. Complete the required fields.

NOTE: The following parameters are to be used for configuring release 4.0 and greater of the eGovern – Public Self Service Portal. Components that are prior to release 4.0 can be configured, with appropriate licensing, by the Govern for Windows Govern Admin release 10.6/10.7 application.

The main Web Configuration tab of the Web Site editor in GNA is used to access configuration parameters. Under the Web site tab are the sub-tabs used to configure the various eComponents. The grouping of the tabs are as follows:

Configuration tabs

General

Select the General tab to configure the Simple Mail Transport Protocol (SMTP) email parameters (Mail group), the default department that the Web site will be linked to.

eProfile
Select the eProfile tab to define default user permissions for the eProfile and the eComponents. The default permissions can be modified on a user-by-user basis through the Administration pages of the eProfile. In addition, Subscription and Password settings are maintained here. See eProfile tab (See Parameters)

ePayment

Under the ePayment tab are the configuration parameters for configuring online payment options, Credit/Debit cards and Automated Clearing House (ACH).

ePermit

The ePermit tab is used to manage the display characteristics of permits that are displayed through the eGovern.

eInspection

The eInspection tab is used to configure options for the online inspection module.

eRemittance (Self Reported Tax)

The Self Reported Tax tab contains the parameters and options for configuring the Self Reported Tax module.

Others

This tab is used to accommodate ad-hoc parameters. These parameters would be related to the eGovern. Currently there is a Misc. Billing Payment button which links to the Misc. Billing Receipt form.

Manage Web Skin

The Web Skins forms is used to define the look and feel of your Web site. To create your web skin, refer to the Create a WebSkin section in the guide.
To access the configuration parameters in the GNA ribbon, click Application Configurations (tab) > Web Configuration (group) > Manage Web Skin

Configuration tabs

Layout Type

Select the type of layout that is required.
Web Page Section
Click the Web Page Section tab to define general properties for the WebSkin.
Head Section
Click Head Section to define the information for the Head section of the Web page. The Head Section of a Web page contains keywords, meta tags, javascripts and references to CSS files. Meta Tags may be used by search engines, such as Google, Bing, and Yahoo, to categorize and rank your Web site in a search result.

Header / Footer / Left / Right Section(s)

Select these sections to define the properties for the borders of your Web pages.

Govern Section

Select the Govern Section tab to define the properties for the Govern section of your Web pages.

Open Web Config Editor…

The Govern Net Admin’s (GNA) Web Config File Editor is designed to manage Govern’s eComponents. With the Web Configuration File Editor, you are able to define configuration parameters, determine how errors and exceptions are managed by the system, and set auto login parameters. See Web Configuration File Editor for details.
To access the configuration parameters in the GNA ribbon, click Application Configurations (tab) > Web Configuration (group) > Open Web Config Editor.

Configuration tabs

Page 1 tab

In the Web Config File Editor form, select the Page 1 tab to define the configuration parameters.

eProfile

Select the eProfile tab to define default user permissions for the eProfile and the eComponents. The default permissions can be modified on user-by-user basis through the Administration pages of the eProfile. In addition, Subscription and Password settings are maintained here. See eProfile Tab Parameters

ePayment

Under the ePayment tab are the configuration parameters for configuring online payment options, Credit/Debit cards and Automated Clearing House (ACH). See ePayment – Setting the Web Parameters.

Documentation

For documentation explaining details of each parameter, refer to the Documentation section of of the eGovern – Public Self Service Portal user guides.

Related Topics

eGovernment (Public Web Portal)

 

 

201-egov-parms

 

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