100-ChangesDBStructure

Changes in Database Structure

Version 6.0 and 6.1

Overview

Standard Functions and Features

System and User Validation Tables

Version 6.0 and 6.1

  • Changes to VT_USER and VT_SYSTEM tables. System and User Tables are now validated and compared against the standard structure XML file.

 

Read More...

Userfile

Version 6.0

  • New GLOBAL KEY to allow us to link Workflow and global messages to users.
    • U_ID field added to USR_USERFILE.

User Profiles

Version 6.0.1412

  • Fields removed from USR_PROFILE
    • ORG_NBR
    • GROUP_CODE
    • JURISDICTION_CODE
    • OWNER_MM
    • OWNER_YY
    • NB_REC_WARN
    • NB_MIN_ROLLBACK

Roll Forward Exclusion Tables

Version 6.0

  • New tables added to support the roll forward exclusion of fields.
    • SY_ROLLFORWARD_EXCLUSION
    • SY_ROLLFORWARD_EXCLUSION.TABLE_NAME [PK]
    • SY_ROLLFORWARD_EXCLUSION.COLUMN_NAME [PK]

User Audit Trail New Tables (3)

Version 6.0 – see User Audit for more info [std-fea-017]

  • USR_AUDIT_OPENFORMS
    • AUDIT_ID
    • AUDIT_ACTION
    • ENTITY_ID
    • FORM_CODE
    • USER_ID
    • AUDIT_DATE
    • IP_ADDRESS
    • SOURCE_COMPUTER_NAME
    • REMOTE_COMPUTER_NAME
  • USR_AUDIT_OPENFORMS_CHANGE
    • AUDIT_ID
    • ATTRIBUTE_ID
    • TABLE_NAME
    • COLUMN_NAME
    • OLD_VALUE
    • NEW_VALUE
  • USR_AUDIT_OPENFORMS_KEY
    • AUDIT_ID
    • ATTRIBUTE_ID
    • KEY_NAME
    • KEY_VALUE
    • IS_PRIMARY_KEY
NOTE: The legacy table USR_AUDIT_TRAIL will be kept for modules running in prior releases, but developers should note the new modifications and table structures impact for custom processes.

Property Control (PC)

PC Parcel

Version 6.1

  • NON_PARCEL_FLAG and VIRTUAL_PARCEL cannot be set to null.

PC Sales
Version 6.0

  • PC_SALES is no longer used, only MA SALES

Accounts Receivable & Cash Collection (CC)

Version 6.0

Payer Name

  • PAYER_NAME added to CC_MASTER (name was previously kept in CC_MASTER_NOTES) – 6.0 and 6.1

Mass Appraisal (MA)

For the specification document, click on Appraisal Detail Specification for listing.

Building Changes

Version 6.1

  • Current_P_ID was added to MA_BUILDINGS
  • VT_SY_DRAWCMD is no longer used

Site Changes

Version 6.1
Site changes to support new override methodology

  • These columns were added:
    • LAND_VALUE_OVERRIDE (money)
    • LAND_AG_VALUE_OVERRIDE (money)
    • BLDG_VALUE_OVERRIDE (money)
    • MISC_VALUE_OVERRIDE (money)
    • INCOME_GRM_VALUE_OVERRIDE (money)
    • INCOME_DIR_VALUE_OVERRIDE (money)
    • MRA_VALUE_OVERRIDE (money)
    • PP_VALUE_OVERRIDE (money)
  • These columns were dropped : (No longer used in v6.1)
    • TEMPLATE_CD
    • TEMPLATE_VA
  • A misc. correction script was added to move :
    • LAND_VALUE to LAND_VALUE_OVERRIDE when LAND_OVERRIDE = -1
    • LAND_AG_VALUE to LAND_AG_VALUE_OVERRIDE when LAND_AG_OVERRIDE = -1
    • BLDG_VALUE to BLDG_VALUE_OVERRIDE when BLDG_OVERRIDE = -1
    • MISC_VALUE to MISC_VALUE_OVERRIDE when MISC_OVERRIDE = -1
    • INCOME_GRM to INCOME_GRM_VALUE_OVERRIDE when INC_GRM_OVERRIDE = -1
    • INCOME_DIR_VALUE to INCOME_DIR_VALUE_OVERRIDE when INC_DIR_OVERRIDE
    • MRA_VALUE to MRA_VALUE_OVERRIDE when MRA_OVERRIDE = -1
    • PP_VALUE to PP_VALUE_OVERRIDE when PP_OVERRIDE = -1
  • A misc. correction script was added to move :
    • All XXX_VA values to XXX_OV_VALUE when XXX_OV = -1
    • – XXX_OV_VALUE should be created as well.

Income Changes

Version 6.1
Income changes to support new override methodology

  • These columns were added in MA_Income.
    • Building_Value_Override
    • DIR_Rate_Amount_Override
    • GRM_Rate_Amount_Override
    • Gross_Effective_Override
    • Gross_Rent_PCT_Override
    • Gross_Rent_Value_Override
    • Land_Value_Override
    • Misc_Value_Override
    • Net_Dir_Override
    • Net_GRM_Override
    • Net_Value_Override
    • Rent_Units_Override
    • Vacancy_PCT_Override
    • Overall_ADJ_VAL_Override
  • These columns were added in MA_Income.
    • Ma_Income_Group

Income changes to support new calculation method and configuration

  • Income Fields added
    • Ma_Income_Record_Type
  • Income Table added
    • For Added Fields – to be validated

 

Miscellaneous Billing

Available in GA Release 6.1.1606
To offer more flexibility, the misc. billing parameters are now year base.
As such the YEAR_ID was added to the following tables:

  • MB_INVOICE and MB_INVOICE_DET
  • MB_RECURRING and MB_RECURRING_DET

In prior versions, only the AR Class Code was used for the invoice and invoice detail. To simplify data entry and offer more flexibility, the following tables were added.

  • MB_PARM_CATEGORY (contains a category that will be used to link the detail invoice items)
  • MB_PARM_ITEM

New Database Fields

  • LAST_RECUR_DATE was added to the MB_INVOICE_REC table
  • BATCH_ID was added to the MB_INVOICE table

Self Reported Business Tax (ST)

When the fields for ST forms are created, the following USR_FIELDS_XXXXX tables, are no longer used.

  • USR_FIELDS_DEF
  • USR_FIELDS_LABEL
  • USR_FIELDS_MASK
  • USR_FIELDS_NUMERIC_FORMAT (Added for 6.0 and 6.1)
NOTE:The data in the above have been copied to (Table: ST_PARM_CATEG)

New Field added in ST_MASTER

  • NAICS (Varchar 15) MANDATORY when using Estimated Filings.
NOTE: This field is now a Standard System Field and may need to be converted if it was created as an Added Field.

New Tables added for Estimated Filings

  • ST_ESTIMATE_ID

New Table added for Corporate Account

  • ST_CORP_ACCOUNT

Name and Address (NA)

For ACH processing and field encryption, the following changes have been made:

  • NA_ACH_INFO.ACH_DESC (new field)
  • NA_ACH_INFO.BANK_ACCOUNT_NO (new field length = 44)
  • NA_ACH_INFO.TRANSIT_NO (new field length = 32)

OpenForms Tables

Version 6.0

Tables Removed from versions: 6.0.1411.0106 and 6.1.1411.0106
1. OF_SE_APP_TYPE replaced by an object in memory
2. OF_DE_MODELCONTENT was used only for MOD
3. OF_MD_UPDATER was used only for MOD
4. OF_LK_PROFILE_OF1 was used only for MOD to establish the link with a profile.

Tables Removed from versions: 6.0.1411.0017 and 6.1.1411.0021
The tables defined in MSGDatanaseStructMods.xml (so also in OPENFORMS_REFERENCE_60):

  • 1. OF_BE_MAPEXPR
  • 2. OF_BE_MAPTYPE
  • 3. OF_BE_NAVIGATION
  • 4. OF_BE_SERIALIZATION
  • 5. OF_BE_VALRULE_ATTB
  • 6. OF_BE_VALRULE_PARM
  • 7. OF_CTRL_TO_COLUMN
  • 8. OF_LK_ATT_VALRULE
  • 9. OF_MODEL_PERSONALIZATION
  • 10. OF_SE_ACCESSRIGHTS (notion still useful but the table has been replaced by an enumeration in the code)
  • 11. OF_SE_AUDIT
  • 12. OF_SE_LK_ROLE_USER
  • 13. OF_SE_USER_EXCL
  • 14. OF_UI_MAPTABLE (notion still useful but the table has been replaced by CLR objects in the code)

Release 5.x

Version 5.x

  • PC_LK_PARCEL has been replaced with PM_LK_MASTER

See Prior Database Changes (ref. v6.1.1508)

Related Topics

Govern Database DiagramsRefer to the List of Changed Tables section

 

 

100-ChangesDBStructure

 

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

 

Dataset Treeview

Dataset Treeview

Overview

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

Populating the Dataset Treeview

To populate the Dataset Treeview with search results…

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

 

The Treeview Explorer

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

Record Edit Confirmation

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

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

To enable Record Edit Confirmation…

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

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

System Architecture

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

What’s New

Context Menu in Dataset Treeview

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

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

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

Reposition

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

Hibernate Mode

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

Load to Treeview and Add (Append)

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

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

Hibernate

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

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

SELECT *
FROM USR_HIBERNATE
WHERE USR_ID = ‘userName’;

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

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

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

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

Enabling “Synchronize Dataset Treeview”

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

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

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

Location of Data

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

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

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

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

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

Business Rules

Programmers should note the following Business Rules.

When Parameters Change:

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

When Opening Govern (Before opening Profiles):

  • Starts monitoring Dataset tree view changes if Flag is on

When monitoring Dataset tree view changes:

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

 

NOTE: Always hide AutoSave SAVED_SET_NAME from saved dataset functions

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

Related Topics

Dataset Treeview Temporary Records

Forms Explorer
Reports Explorer

 

 

101-std-fea-005

 

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

 

Workflow Setup

Workflow Setup

NOTE: This page contains information that is intended for advanced Govern users that are familiar with the steps that are required to configure a form.

Overview

The following are the sections that require configuration by an Administrator prior to setting up a Workflow.

Admin Setup

Read More...

(GNA) System Registry

In the Govern New Administrator (GNA)…

  1. From the GNA ribbon, select Parameters tab > System Parameters group > General Settings Editor.
  2. Set the Registry Filter parameter to General.
  3. Configure the following parameters:
  • Section Name: SMTP (If email option is used)
  • Section Name: Imaging > Imaging Path

 

(OFD) Configuration

Workflow (Root Entity)

Controller

Workflow_Controller

Misc

Allow delete save insert expressions can be entered

Configuration

Filters by System ID

  • Reference ID = parcel id
  • Primary Department = department

Filters by Constants (Attribute, Operator, Constant)

  • Reference Type (equal to) = P_ID
  • Key Type co (equal to) = co

Name

Business Entity Model

Text

OFD name for Business Entity Model

Tab Sequence

Divider Tab sequence ?

Record Description

(would be nice to have workflow type)

 

Workflow – General

Controller

WorkflowType_Control (For Combo box)

+ Attributes

 

Workflow – Form

Controller

WorkflowAddedFields_Control

 

Activities

Controller

Activity_Control

 

Multimedia

Controller

MultimediaDocuments_Control

Parent Entity

Workflow

 

Steps to Set Up a Workflow

NOTE: The following steps must be completed by users with Administration access to Govern.

The following are the steps required to create a Violation Workflow.

    Create A/R Class – Same Year Profile, Same Sub System Linked Profile, Allow Sub System Dept.

  1. Configure SMTP
  2. Create Kind: Complaint
  3. Create Category: Violation
  4. Apply Template Form: Workflow Name Template – This will create a basic complaint form in OFD
  5. Create Fees: e.g. Liquor Fee 1, Liquor Fee 2+, Cannabis Fee
  6. Create Activities with actions
  7. Create Types: e.g. Liquor Violation, Marijuana Violation
  8. Create Steps with actions
  9. Add the form to a profile
  10. Review the form in the OFD
  11. View the result in Govern

Videos

Workshop – R&D Workflow Workshop (Internal Access)

Video only available for internal use.

Presentation

Click to view the presentation as a .PDF file.

 

 

101-std-frm-002-setup

 

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

 

Dynamic Searches Standard OF Reference

Dynamic Searches – Standard OpenForms Reference (OFR)

Version 6.0 | Version 6.1

Overview

(In Development)
The following dynamic searches are distributed.

  • Module Specific
  • Bar Code
  • Synchronized Treeview

Module Specific Dynamic Search Details

The following search fields are available – See what is available and what is roadmap

General A/R

  • Bar code or A/R ID
  • Bill Number
  • Invoice Number
  • Mortgage Company or Tax Service Orgaization (TSO)
  • Receipt No. (payment)

Aircraft

  • Aircraft Serial Number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Boat

  • Plate Number
  • Boat Serial Number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Motor Vehicle

  • Plate Number
  • Motor Vehicle Serial Number
  • Motor Vehicle ID (MV_ID)
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Real Property

  • Tax Map Number
  • Tax Bill

Personal Property

  • Tax Map Number
  • Account Number
  • Personal Property ID (PP_ID)
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Miscellaneous Billing

  • Account Number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Utility Billing

  • Tax Map Number
  • Account Number
  • Utility Billing ID (UB_ID)
  • Meter Serial Number
  • Route Number and Sequence
  • Name Status (Owner…)
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Special Assessment

  • Project Name
  • Project Code

Complaints, Grievances, Request for Services …

  • Enter the reference number
  • Search in application number, permit number, certificate number, alternate permit id and any of the above

Permit

  • Reference number
  • Department
  • Permit Kind
  • Permit Type
  • From and to Date
  • Tax Map number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)
  • Include Void Permit
  • Include Historical Permit
  • Include License to Name
  • Search in application number, permit number, certificate number, alternate permit id and any of the above

Note: Backward searches are deprecated

AutoSave Treeview

Synchronized Treeview search

  • Select NAME SEARCH Autosave to access by the content of the Treeview
  • Note: Synchronize must be set to On
  • See the Govern Roadmap

 

 

101-std-fea-004-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...

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

AR – Payment Reversal Data Entry

Accounts Receivable (A/R) Payment Reversal Data Entry

Overview

Payment reversal transactions (rev) are adjustments that are used as corrections. They are run typically when NSF checks have been processed or records posted incorrectly
Run the Payment Reversal batch process in order to void a group of payment transactions. This is useful if there are payments that were made in error or that were paid from accounts with insufficient funds (NSF).

Documentation

For the complete reference guide, see Govern Accounts Receivable.
For the A/R Transaction Rules, see A/R Transaction Rules.

Payment Reversal Transactions and Processes

Read More...

Payment Reversal Transaction Type

Payment reversal transactions (rev) are used as corrections. They are run typically when NSF checks have been processed or records posted incorrectly.

Creating Payment Reversal Transactions

Payment Reversal transactions can be created individually or in a batch. Both methods create Payment Reversal Transactions, which can be viewed or deleted from the A/R Inquiry form.
It is faster to generate these transactions in a batch, especially if you have a large volume to process. However, if it is important to note the warnings that are described under the section. Running the Generate Payment Reversal Batch Process.
See Creating a Single Payment Reversal Transaction following this section.
See Generate Payment Reversal Batch Process: 101-ar-bp-041

Posting Payment Reversals

After generating Payment Reversal transactions, whether individually or in a batch, you need to post them. To post a payment reversal, run the Payment Reversal Posting batch process. See Posting Payment Reversal Transactions. See
Payment Reversal Posting: 101-ar-bp-026

Business Rules for Payment Reversals

All posted payment transactions can be reversed, with the following exceptions. The following payment transactions cannot be reversed:

  • Not posted Payment: If a payment is not posted, you can edit or delete it on the Payment Data Entry form. However, a payment must be posted before you can create a Payment Reversal transaction or include it in the Generate Payment Reversal batch process.
  • Payment Reversal (rev): If a Payment Reversal exists, the original payment is already reversed and a new payment reversal cannot be created.
  • Payment Refunded (rf): If a Payment Refund exists, the original payment is already refunded and a new payment reversal cannot be created.
  • Payment Transferred (tri or trp): If a Payment Transfer exists, the original payment is already transferred and a new payment reversal cannot be created.

For details on transaction types, see Transaction Types

Creating a Single Payment Reversal Transaction

Accessing the Payment Reversal Form

To access the Payment Reversal form:

  1. Open a Profile that includes A/R Inquiry.
  2. Open the A/R Inquiry form.
  3. Perform a search and load the required record to the tree view and form.
  4. Right-click on a record in the Summary section of the A/R Inquiry form.
  5. Select Payment Reversal from the drop-down list
  6. If multiple records are available the following screen appears:

The Payment Reversal form is divided into the following sections:

  • General Information
  • Detail
  • Comment
  • Payer Information

General Information

Subsystem: The subsystem for the record or entry selected on the A/R Inquiry form is displayed.
Year: This field displays the fiscal year of the record.
Bill Number: This field displays the bill number for the selected record.
Cycle Code: This field displays the Cycle Code associated with the record (Table: VT_USR_ ARCYCLE).
The Cycle Code is mandatory for the Real Property and Person Property Tax modules. It is used for tax billing cycles and is linked to the A/R Class Code in GNA.

Detail

Date: This field displays the entry date for the payment reversal. By default, this is the current date. To change the date, click the calendar beside this field and select a new date.
Effective On: By default this field is blank. If an effective date is applicable, click the calendar beside the field and select a new date. For example, you may want to enter the posting date.
Amount: This field displays the amount of the reversal.
Full Payment Reversal: A full payment reversal can be used when there are multiple records associated with a single name. For example, Bob’s Building Supplies owns three properties. Bob has made an overpayment of $10,000.00 on each property for a total of $30,000.00. You can create a full payment reversal to include all properties in the same payment reversal.
Select the Full Payment Reversal option. This displays the total for all property records.

Comment

Justification Code: Select a Justification Code to explain the reason for the payment reversal (Table: VT_USR_ARREASON).
Deposit Number: Depending on the options selected in GNA, deposit numbers can be automatically generated or user-defined.
Automatically generated deposit numbers are composed of one or two of the following fields: date, last deposit, and user ID. This number can be modified if security permissions allow.
If Deposit Management is activated, a drop-down list is added to the Deposit Information parameter. This is populated by the deposit numbers created in the Deposit Management form. See Deposit Management.
Do one of the following:

  • Enter a new deposit number if required.
  • Select a deposit number from the drop-down list.
NOTES: Enter any notes or comments applicable to the payment reversal.

 

Payer Information

Letter Code: Select a Letter Code that identifies the type of letter sent to the payer; for example, D: Duplicate Payment, O: Over Payment, RV: Payment Reversal (Table: VT_USR_LETER_C).
Payer’s Name and Address: This field is displays the payer’s name and address.
Click R to remove the displayed name and address record.
Click C to add a different name and address record. This opens the Name Search screen.

 

 

101-ar-frm-026

 

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

AR – Installation

Accounts Receivable Installation

Overview

The Govern OpenForms applications required for Accounts Receivable are installed through Govern Deploy EZ, See Deploy EZ.

 

 

101-ar-install

 

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