OpenForms V6 Sunsetting Notification

Formal Announcement: Sunset of OpenForms Version 6.1

Effective December 31, 2026

This notice is to inform you that Version 6.1 of our OpenForms software will reach its official end-of-support on December 31, 2026.

Click to Read More...

Communiqué

As part of our ongoing commitment to product quality, security, and long-term platform stability, we are consolidating our development and support efforts around fewer modern versions of the software. This focus enables us to more efficiently deliver enhancements and provide a stronger overall customer experience.

We encourage all customers currently operating on OpenForms Version 6.1 to begin planning their transition to OpenForms Version 7, which includes a wide range of technical and functional improvements:

  • 64-bit application architecture for improved performance and reliability
  • Generic Import Tool for enhanced data management
  • Enhanced export capabilities for self-service data extraction
  • Merge-to-PDF capabilities for modern reporting workflows
  • Enhanced Form Designer with expanded customization options
  • Upgraded Workflow Engine offering greater automation and flexibility
  • Improved Web Portal functionality for streamlined online services
  • Name merge utility for accurate record keeping
  • Parcel annexation and incorporation module for streamlined processing
  • Optimized compute functions allowing for faster calculations
  • Modernized GIS interface allowing integration with cloud hosted mapping providers
  • Modern Marshall & Swift interface leveraging cloud hosted valuation models
  • Condominium management module to build efficient workflows for Condominiums
  • Support for new modules Utility Billing and Special Assessments

 

The upgrade path from Version 6.1 to Version 7 is straightforward and can be self-performed. Upgrade guides are available on our knowledge base here. Additionally, our team is available to assist with upgrade planning, scheduling, and execution to ensure a smooth transition.

Over the coming weeks, we will also be reaching out to your designated technical contacts to discuss timelines, answer questions, and help coordinate your upgrade strategy.

If you require more immediate guidance or would like to begin planning now, please contact our support or product teams.

We appreciate your continued partnership and look forward to supporting you on Version 7 and future releases.

Related Topic(s)

OpenFormsTM Go Live! 6.1 to 7.0 Checklist

 

 

 

100-OF_Sunset_V6

 

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 – GoLive! 6.1.x to 7.0 Check List

OpenFormsTM Go Live! 6.1 to 7.0 Checklist

Go Live Checklist 6.1.x to 7.x with eGovern

Expand to view the detailed steps of the information below; review the detailed checklist if you are using eGovern.

Click to Read More...

Overview

This document provides a high-level overview of the upgrade process from OpenForms version 6.1.x to 7.x. It is intended for technical teams responsible for planning and executing the migration. The checklist ensures that all critical steps are completed in the correct order to minimize downtime and maintain system integrity. The process involves preparation, upgrade execution, and post-upgrade validation, covering application servers, web servers, and associated components such as eGovern and Keycloak.

Required Steps

OpenForms 6.1.x to 7.x Upgrade-Go-live Checklist

  • Items to be completed in specified order.
  • Please contact the Application Specialist assigned to your upgrade if you encounter any errors or issues with a step, before proceeding to the next step. Provide screenshots and error logs where applicable.

Pre-Upgrade Activities

Preparation in Advance

On Clients, Application Server and Web Server

Ensure everyone has 64-bit crystal runtime.

On Web Server

  • Confirm .Net 4.8 is installed
  • Confirm client has SSL certificate created
  • Install WebEz application, do not create website until cutover day

GNA

  • Edit Email templates that eGovern uses to contain desired verbiage and appropriate URL
    • ST Account Invitation
    • ST Acct Inv accepted

The Day Before Upgrade

  • Obtain password for download of Keycloak binaries during eGovern install process.
  • Ensure all users have saved their work and logged out.
  • Download the OpenForms version 7 binaries of tested version.

Upgrade Activities

On Web Server

  • Stop Production website in IIS

On App Server/SQL Server

  • Back up Production database

On App Server

  • Upgrade the deployment using OpenForms version 7 binaries of tested version.
  • Run database verification from the GNA application.

On Web Server

  • Upgrade eGovern with WebEz

 

Run initial install of eGovern

Enter production site parameters

  • Site name to be used in IIS
  • Enter path to deployment directory on app server where the GovernNet.config file is
  • Select or Create certificate
  • Enter URL to use if different than Certificate
  • Enter route path on local machine for files to be installed.
  • Enter port to be used for website
  • Enter the Keycloak port to be used – can increase the site port by 1.
  • Enter text to be displayed on web page to id the page for users.
  • Check use docker for Keycloak.
  • Configure the realm.

Keycloak config

  • Remove links to Google & Microsoft

From the application server in the Govern install directory copy the following:

  • ResourceFiles
  • governdabconfig
    • Paste the Resourcefiles directory and GovernDABConfig.xml file into the eGovern install directory on the webserver.

From the Deployment you are pointing eGovern to function with directory, copy the following folders from the application server (i.e. C:\Govern\Deployments\[DeploymentName]) to the webserver C:\GovernApp\Govern_Test

  • CustomControl
  • SystemFiles
  • eGovern
  • WebApi
  • WebFrontend
  • And file: GovernNetConfig.xml
    • Edit the paths in GovernNetConfig.xml to point to the local directories
  • Run the migration of existing eGovern profiles to Keycloak.

Post Upgrade Activities

  • Test logins to eGovern.
  • Test eRemittance thru payment.

Summary

  • Complete all tasks in the specified order and contact the assigned Application Specialist for any issues.
  • Preparation steps include ensuring 64-bit Crystal runtime on all servers, .NET 4.8 installation, SSL certificate setup, and WebEz application installation.
  • Update GNA email templates for eGovern prior to upgrade.
  • Before upgrade day: obtain Keycloak binaries password, ensure all users log out, and download tested OpenForms 7 binaries.
  • Upgrade steps: stop production IIS site, back up production database, deploy OpenForms 7 binaries, verify database, and upgrade eGovern with WebEz.
  • Configure eGovern site parameters, SSL certificate, ports, Keycloak settings, and realm configuration.
  • Copy necessary resource files and configuration files from application server to web server and adjust paths in GovernNetConfig.xml.
  • Migrate existing eGovern profiles to Keycloak.
  • Post-upgrade validation includes testing eGovern logins and eRemittance payment functionality.

 

Go Live Checklist 6.1.x to 7.x without eGovern

Expand to view the detailed steps of the information below; review the detailed checklist if you are not using eGovern.

Click to Read More...

Overview

This document provides a high-level overview of the upgrade process from OpenForms version 6.1.x to 7.x. It is intended for technical teams responsible for planning and executing the migration. The checklist ensures that all critical steps are completed in the correct order to minimize downtime and maintain system integrity. The process involves preparation, upgrade execution, and post-upgrade validation, covering application servers

Required Steps

OpenForms 6.1.x to 7.x Upgrade-Go-live Checklist

  • Items to be completed in specified order.
  • Please contact the Application Specialist assigned to your upgrade if you encounter any errors or issues with a step, before proceeding to the next step. Provide screenshots and error logs where applicable.

Pre-Upgrade Activities

Preparation in Advance

On Clients, Application Server

Ensure everyone has 64-bit crystal runtime.

The Day Before Upgrade

  • Ensure all users have saved their work and logged out.
  • Download the OpenForms version 7 binaries of tested version.

Upgrade Activities

On App Server/SQL Server

  • Back up Production database

On App Server

  • Upgrade the deployment using OpenForms version 7 binaries of tested version.
  • Run database verification from the GNA application.

Summary

  • Complete all tasks in the specified order and contact the assigned Application Specialist for any issues.
  • Preparation steps include ensuring 64-bit Crystal runtime on all servers, .NET 4.8 installation.
  • Before upgrade day:
    • Ensure all users log out, and download tested OpenForms 7 binaries.
  • Upgrade steps:
    • Back up production database
    • Deploy OpenForms 7 binaries
    • Verify database.

 

 

 

100-UpgdChklst_61to70

 

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 – System Requirements (100-systemreq)

OpenFormsTM System Requirements

System Requirements

The listed documents contain the minimum hardware and software requirements for Govern’s eGovernment solutions and Microsoft .NET applications. When referring to these documents, ensure that you are viewing the one that corresponds to your required release.

Version 6.1

Version 6.1.2212

Starting with version 6.1.2212 the minimum required version for SQL Server Reporting Services (SSRS) is 2017 on the server side.

NOTE: This system requirement update notice only applies to SSRS and not to SQL Server.

 

Version 6.1.1611

The Minimum System Requirement is .NET Framework 4.7.2 or higher. Users of the following versions of the Govern suite of applications are required to upgrade to the Microsoft Framework V4.6 or higher:

Affected release versions are as follows:

  • GA Release 1611 +
NOTE: Windows XP users should note that after an upgrade to Microsoft Framework 4.x, Govern will no longer function on platforms that are running the Windows XP operating system.

Crystal Report Run-Time

  • The framework used was upgraded to 4.6 as a result of a new Crystal Report run-time. It is mandatory to re-install the Crystal Report Run time pack for versions GA Release 1611 for version 6.0 and 6.1. For releases prior to GA 1611, the installation pack to install is 13.0.12 otherwise, 13.0.20.
IMPORTANT: Reports will not function without installing the new pack. The installation package must be run locally.

 

 UPDATE  Version 6.1 Support for MS SQL Server 2019

Below is the link to the current Govern Release 6.1 System Requirements.

101-all-govern-SysReq61

 

Read More...

Version 6.0

NOTE: Upgrading to MS SQL Server 2016 is not recommended for Govern Release 6.0 users that are still running Govern for VB6. Issues may arise from possible incompatibilities between data types that are used in VB6 and Govern for .NET Release 6.0. The currently identified data types are:

  • TEXT
  • NTEXT
  • IMAGE

It should be noted that Govern Release 6.1 users are NOT affected by this issue.

The Minimum System Requirement is .NET Framework 4.6 or higher

Users of the following versions of the Govern suite of applications are required to upgrade to the Microsoft Framework V4.6 or higher:
Affected release versions are as follows:

  • 6.0.1702.0486 (6.0.DEV)
  • 6.0.1702.0486, 6.1.1611.0281
NOTE: Windows XP users should note that after an upgrade to Microsoft Framework 4.x, Govern will no longer function on platforms that are running the Windows XP operating system.

6.0 Govern OpenForms Hybrid Version (10.8)

  • 6.0.1410 Twain for imaging is no longer supported by Windows. Replaced by WIA (Windows Image Acquisition).
  • 6.0.1502 Record locking management implemented. MS SQL Server System Table is used. Govern user needs Read-Write access the first time Verify Database will be used. A SQL script needs to be executed to create the table.
SUGGESTION: Provide the script to the DB Manager to execute the script.

101-all-govern-SystemRequirements[user]-(6.0)

3rd Party Requirements

Other 3rd party or system options requirements not included in main document.
Apex
– To Be Confirmed –

Requirements Overview

Systems

  • Windows OS and Frameworks
  • General System Requirements

OpenForms Servers

  • DeployEZ
  • Deployment Resources
  • Harris Govern FTP Access
  • Govern Resource Folders

Enterprise Server(s)

Credentials & Logins

  • Authentification method
  • LDAP integration

Govern Scheduler Server(s)

  • Windows Services – only 1 deployment
  • Govern Batch Daemon (version 6. only)

Databases

  • MS SQL Server and Oracle
  • Clients & drivers
  • Indexes & tablespaces

Third Parties

  • Crystal Report
  • SSRS
  • APEX
  • Silverlight (GIS option)

Administrator Tools

  • About
  • Diagnostics & Logs
  • Govern Validator
  • Error Reporting
  • Help & Support Resources

 

 

100-SystemReq

 

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 – Module Map

Accounts Receivable (A/R) Module Product Map

Overview

General Forms & Features

General Business Rules, Processes, Forms and Features

 

Section Product Code/ Wiki Page Description Supporting Information Developer
General 101-ar Accounts Receivable Module Overview
101-ar-brules System Integrity and Business Rules System Registry
100-ach Centralized page for Automated Clearing House (ACH) 100-ach (dev)
100-pos Centralized page for Point-of-Sale Processing (POS) 100-pos (dev)
A/R Forms 101-ar-frm-001 AR Inquiry 101-ar-frm-001
101-ar-frm-003 AR Inquiry Notes with ACH Information
101-ar-frm-004 AR Inquiry ACH Information General ACH Processing
101-ar-frm-008
101-ar-fea-038
AR Inquiry Payment Plan
AR Allow Payment Less Than Payment Plan Feature
101-ar-frm-006 AR Deposit Management
101-ar-frm-020 AR Payment Data Entry
101-ar-frm-021 AR Data Entry – AR Transactions
101-ar-frm-022 AR Data Entry – Abatements and Exemptions
101-ar-frm-023 AR Data Entry – Adjustments
101-ar-frm-024 AR Data Entry – Interest, Penalties, Fees and Charges
101-ar-frm-025 AR Data Entry – Refunds
101-ar-frm-026 AR Data Entry – Payment Reversals
101-ar-frm-027 AR Data Entry – Payment Transfer
101-ar-frm-028 AR Data Entry – Refund Reversals
A/R Features 101-ar-fea-002 Using Protest Flags
101-ar-fea-003 Receipting
101-ar-fea-004
101-std-fea-004
Dynamic e-search – Standards A/R
Dynamic e-search – Standards
101-ar-fea-010 Accounts Receivable Interest & Penalty Methods A/R Parameters
101-ar-fea-005 Overpayments (OCR & OCH processing)
101-ar-fea-006 ACH Processing General ACH Processing
101-ar-fea-010 A/R Credited Interest on Refund
101-ar-fea-011 A/R Class Code Included in Balance Forward 101-ar-fea-011
101-ar-fea-020 Group Adjustments
101-ar-fea-025 BT – Period Validation for AR Deposit in CC Payment Data Entry
101-ar-fea-026 A/R Search to Load Feature
101-ar-fea-027 Change Payer Name in A/R Inquiry
101-ar-fea-028 AR Inquiry – Payment Transfer
ACH 201-ar-fea-006 ACH Processing eGovern
101-ar-fea-016 ACH Processing Govern Payment Plan (option) Roadmap 101-ar-fea-016
101-ar-fea-017 ACH Processing Credit Filing
ACH egov 201-ar-fea-017 ACH Processing eGovern Credit Filing (ST Remittance)
101-ar-fea-007 Allow Interest and Fees as of date
101-ar-fea-008 Allow Payment Plan Processing
101-ar-fea-009 Security by Property Area Fields Roadmap (DEV) 101-ar-fea-009
Custom Control Payer name 101-ar-fea-021 Payer name Custom Control (New) 101-ar-fea-021-ofr (DEV) 101-ar-fea-021
(QC) 101-ar-fea-021
Action Button Control 101-ar-fea-022 Create A/R for MB, ST, RE, PP, etc. 101-ar-fea-022-ofr
101-ar-fea-023 A/R Method Waiver for Min/Max SRT Filings
101-ar-fea-024 AR Payment Action Button 101-ar-fea-024-ofr
Cash Collection 101-cc-frm-001 Cash Collection Data Entry CC wiki Map (DEV) 101-cc-frm-001

 

Batch Process (bp)

Accounts Receivable Batch Processing

Status Wiki Page / Code Batch Process Name Batch Process Supporting
Information
GFW Batch Process
Batch Processes 101-ar-bp-001 AR Apply Pending Credits ar_applypencr mnu_apply_cr
101-ar-bp-002 AR Set Warning Flag on Delinquent ar_setwarning mnu_set_w_flag
101-ar-bp-003 AR Apply Penalty on Delinquent ar_apppendelinq mnu_ar_interest
101-ar-bp-004 AR Generate Delinquent Charges ar_gendelinqchg mnu_ar_charge
101-ar-bp-005 AR Apply Deposits ar_appdeposits
101-ar-bp-006 AR Compute Balance As Of a Date ar_compbaldue mnu_late_charge
101-ar-bp-007 AR Extract As Of Date A/R Detail Table ar_extrasofdate mnu_extract_ar
101-ar-bp-008 AR Generate Refunds ar_genrefunds Missing batch process mnu_gen_rf
101-ar-bp-009 AR Generate Over and Short ar_genovershort mnu_bal_adj
101-ar-bp-010 AR Transfer to History ar_tranartohist mnu_ar_hist
101-ar-bp-011 AR Re-Initialize A/R Tables ar_reinittables mnu_ar_init_tab
101-ar-bp-012 AR Period Closing ar_perclosing mnu_ar_p_close
101-ar-bp-013 AR Transfer Credits from One Year to Another ar_transcrd mnu_ar_credit
101-ar-bp-100 AR Posting – Combined Posting of all type Roadmap (14487)
101-ar-bp-020 AR Posting – Payments
AR Posting – Cash Collection (CC or)
ar_postcashcol mnu_ar_cc
101-ar-bp-021 AR Posting – AR Transaction Not available
101-ar-bp-022 AR Posting – Abatements and Exemptions Not available
101-ar-bp-023 AR Posting – Adjustments ar_postadjust mnu_ar_adj
101-ar-bp-024 AR Posting – Interest, Penalties, Fees and Charges Not available
101-ar-bp-025 AR Posting – Refunds ar_postrefunds mnu_ar_refund
101-ar-bp-026 AR Posting – Payment Reversals ar_postpayrev mnu_ar_rev
101-ar-bp-027 AR Posting – Payment Transfers ar_postpaytrf
101-ar-bp-030 AR Posting – Postdated Payments ar_postdatedpmt mnu_ar_pdt
101-ar-bp-031 AR Posting – Deposits ar_postdeposit mnu_ar_deposit
eGov 201-ar-bp-033 AR eReipting (e-Gov System) ar_ereceipting
eGov 201-ar-bp-034 AR eBilling (eGov System) ar_ebilling
101-ar-bp-035 AR Create AR Levy Close File? ar_levyclose
101-ar-bp-036
101-ar-frm-036
AR Lock Box Batch Process Posting
AR Lock Box Maintenance Form
ar_lockbox 101-frm-036-config
Lockbox Layout to distribute 6.0/61
Change Assessment
101-ar-bp-038 AR Generate Check Refund Numbers ar_gencheck
DC 101-ar-bp-039 AR Transfer Delinquency GA 1609 Batch process to transfer delinquant accounts to Delinquency
Other 101-ar-bp-040 AR Generate GL Account gl_tranacc_updt General Ledger Account Update
101-ar-bp-041 AR Generate Payment Reversals for a Batch ar_gen_reversal GA 1609 Batch process to create payment reversals for a posted batch of payments
ACH 101-ar-bp-060 AR ACH Pre-notification File ar_ach_prenote GA1609
101-ar-bp-061 AR ACH Prepare Data for ACH File Balance Due ar_ach_bal GA1609
101-ar-bp-062 AR ACH Generate ACH File ar_ach_file GA1609 Changed from 037 to 060 AR ACH File Process
101-ar-bp-063 AR ACH Post Dated Payment Plan Roadmap Changed from 039 to 063
101-ar-bp-064 AR ACH Update Payment Plan Status version 6.0 only
eGov 201-ar-bp-065 AR ACH Process for Web Payments Validate if any changes
Tax billing 101-tx-bp-040 Tax TSO Registration tx_tso_registr
101-tx-bp-041 Tax TSO Bill Request tx_tso_billreq
101-tx-bp-042 Tax TSO Generate Tax Amount tx_tso_amount
101-tx-bp-043 Tax TSO Batch Payment Generation tx_tso_pmtgen
101-ar-bp-080 AR Batch Deletion of Payments ar_delpayments mnu_ar_pmt_del
101-ar-bp-081 AR Batch Deletion of Refunds ar_delrefunds mnu_ar_rf_del
101-ar-bp-082 AR Batch Deletion of A/R Transactions ar_deltrans mnu_ar_tran_del
Bankruptcy Bankruptcy
101-br-bp-050 AR Bankruptcy Posting bk_postbkruptcy
101-br-bp-051 AR Bankruptcy Delinquent Posting bk_postdelinq
General Ledger 101-ar-bp-040 AR GL Account gl_tranacc_updt
Parameters 103-ar-bp-105 Copy AR CLass Code Batch Process ar_copy_to_year

Reports (rpt)

Accounts Receivable Standard Reports

Status Wiki Page Batch Process Name Report Process Name Supporting Information Description
Edits & Balancing 101-ar-rpt-001 A/R report
101-ar-rpt-002
101-ar-rpt-003
101-ar-rpt-004 Cash Balancing Report cashbal.rpt under construction Version 6.0 and 6.1
ACH Processing 101-ar-rpt-060 ACH Edit List (Encryption Method Backward Compatible) ach_list Roadmap This reports displays ACH information.
101-ar-rpt-061
101-gl-rpt-001 AR Distribution General Ledger auxialgl.rpt

 

Business Rules

Status Wiki Page Name Document Type Notes
101-ar-ref-TransactionRules AR Transaction Rules (table) The Golden rules of AR Transactions
101-ar-ref-TransactionType AR Transaction Type System Table (table)
101-ar-ref-GLAccountingRules AR to GL Account Business Rules (rules)(schema)
101-ar-brules-validation AR Object Error Reporting
101-ar-brules-payment Payment Application Priorities
101-ar-ref-ErrorCodes AR Posting Error Table

Application Parameters

See GNA map for more information

Status Wiki Page Name Notes
103-ar-parm-General General AR Parameters
103-ar-parm-Deposit Deposit Management Parameters
103-ar-parm-Priorities Sub-System Payment Application Priorities
103-ar-parm-ARClasscode A/R Class Codes
103-ar-parm-GLAccounts A/R GL Account
103-ar-parm-CC Cash Collection Parameters
103-ar-parm-ACH ACH Parameters
103-ar-parm-Tables System and Validation Tables
103-ar-parm-Escrow Escrow Paramters
103-ar-parm-CopyYear Copy AR Class Code to Year
103-ar-parm-Calendar A/R Parameters Calendar

 

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

SSRS – SQL Server Reporting Services

SQL Server Reporting Services (SSRS)

Version 6.0 & 6.1

Overview

SQL Server Reporting Services (SSRS), is a server-based report generation software system from Microsoft™. SSRS is administered via a web interface, and is used to prepare and deliver interactive and printed reports. SSRS is viewed as an alternative to Crystal Reports or any other tools that are used in gathering business intelligence.

 

NOTE: Govern supports SQL Server 2010 to 2014 for SSRS. SSRS 2016/2017 will not work. Database instances can exist in SQL Server 2016 or greater, but SSRS will need to be on a 2012 or 2014 instance. Users should NOT open SSRS 2014 reports with SSRS 2016 and save them. This will result in an error in GNA and Govern. Additional details can be found at the following link on the Microsoft Developers Network (MSDN)

What’s new

SSRS Report Conversion Tool (301-ssrs-util)

How to Install SSRS

Click here to follow the current instructions on how to install SSRS.

Documentation

Refer to the following user guide(s) for setup and configuration information.
301-(man)-SSRS-v5.1.pdf

Configuration

Refer to the “Configuration in the Govern New Administration (GNA)” section in the “Documentation & Standards SSRS” user guide.
This guide explains the configuration of SSRS in Govern.
Click here to see the General Settings Parameters (SY REGISTRY).

Report Parameters

dept Govern IDs: dept
dept_label Govern IDs: dept long description
language Current application culture
year Govern IDs: Year
rpt_county SY_Registry – SectionName: “General”; KeyName: “county”.
rpt_date String.Format(“{0} {1}”, Date.Now.ToShortDateString(), Date.Now.ToLongTimeString())
rpt_default_date Date.Now.ToShortDateString()
rpt_login Govern IDs: User
rpt_logo USR_Registry – SectionName: “govern”; KeyName: “bitmap”. OR SY_Registry – SectionName: “path”; KeyName: “bitmap”.
rpt_name Report Path
rpt_range Report Range Value (Filter on xyz)
rpt_state SY_Registry – SectionName: “General”; KeyName: “state”.
rpt_title Report Display Name
rpt_ub_max_variation SY_Registry – SectionName: “ub parameters”; KeyName: “Max Variation”.
rpt_uid Govern IDs: User
rpt_username GoverNetConfig.OrganizationName
uniform SY_Registry – SectionName: “work_text”; KeyName: “Assessment Equalisation Rate”.
all_int Call ‘ComputeLateChargesAmountsForArSummary(“na_id”)’ method

 

See Also

301-ssrs-util

 

 

301-ssrs

 

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

MB – Category Parameters (103-mb-parm-Category)

Miscellaneous Billing (MB) – Category Parameters

Setting Up Miscellaneous Billing Categories

The Miscellaneous Billing Categories are used for classifying the Miscellaneous Billing Items. This facilitates data entry.
To define the Miscellaneous Billing Categories:

  1. Launch GNA.
  2. Select Application Configurations > Miscellaneous Billing.> Categories.
    The existing Miscellaneous Billing Categories are listed in a treeview on the left.
    The Miscellaneous Billing Items are listed in a grid at the bottom of the form.
  3. Click New to create a new category.
  4. Expand the description fields.
  5. Enter a code in the Code field.
  6. Enter descriptions in the English and French Short and Long Description fields.
  7. Select the Available column for each item that you want to classify under the selected category.
  8. Select the Default column for the item that you want to display as a default when the category is selected in Govern.
  9. Click Save.

 

Read More...

 

Miscellaneous Billing Categories Validation Codes

The Miscellaneous Billing Category codes are contained in the Miscellaneous Billing validation table. This table is populated from the Miscellaneous Billing Categories form.
To access the Miscellaneous Billing Category Validation Table:

  1. Launch GNA.
  2. Select Editors > User Validation Table Editor > Miscellaneous Billing.
  3. Select MB_CATEGORY – Misc. Billing Categories on the left.

The entities where the miscellaneous billing category codes are used are displayed under the heading Used In.

NOTE: A category cannot be deleted if it is used in MB Accounts

 

 

 

103-mb-parm-Category

 

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

Transfer Credit from One Year to Another Batch Process (101-ar-bp-013)

Transfer Credit from One Year to Another Batch Process

Overview

The Transfer Credit from One Year to another batch process is run to adjust accounts by removing credits from one year and applying them to another. This is useful if you prefer to credit accounts at year end, rather than providing refunds for overpayments.

Transfer Credits from One Year to Another new parameters

 Availability: Release6.1.1707.1303 | 6.1.1811 | 6.1.1911 | 6.1.1912

NEW! The following new option parameters are an enhancement to the existing batch process for A/R – Transfer Credits from One Year to Another.

The new modifications will allow users to…:

  • Enable a minimum/maximum value to transfer
  • Introduce the ability to select from a saved dataset

In addition to the above modifications, users can exclude any properties which have a credit over a specific amount, and have had an owner transfer as of Department As of Date of the current year.

The transferring of Open Credits (OCR) is now optional; a flag in the system registry will display or hide the Open Credit section of the Batch Process.

Users no longer have to select a Batch Number for the payments and reversals transactions, they will be auto-created as needed.

If the batch Process needs to auto-generate a RECEIPT_NO, it no longer uses (Table: usr_key_receipt), it now uses (Table: usr_key_dynamic) where the key_name is RECEIPT_NO[<alias_id>] where <alias_id> comes from (Table:usr_key_receipt.alias_id) and the key format (key_format) is “{0:D8}“, the same as it was formatted before. A verify database process will transfer necessary keys and drop (Table: usr_key_receipt) afterwards.

 

Read More...

 

Govern New Administration (GNA)

There are changes in the GNA General Settings Editor to accommodate the above described options.

To locate these parameters in GNA…

  1. On the GNA ribbon select Parameters (tab) > System Parameters (group) > General Settings Editor
  2. In the OpenForms General Setting form, in the Registry Filter parameter, select Batch Process.
  3. Under the A/R Transfer Credits section you will note two (2) parameters: Allow transfer of Open Credits from one year to another, and Real Property – Maximum Credit Owner Transfer.

OpenForms General Settings – A/R Transfer Credits (section)

Allow transfer of Open Credits from one year to another – Select this option to allow the transfer of Open Credits from one year to another.

Real Property – Maximum Credit Owner Transfer – This parameter is used only for the Real Property Tax subsystem. This enhancement will look at the property owner to determine if the effective date of ownership is as of Department As of Date of the current calendar year that the batch process is being run in.

DEV NOTE: The query used to check the owner transfer is:

SELECT * FROM pc_owner 
   WITH (NOLOCK) 
   WHERE p_id=@p_id 
      AND status = 'O' 
      AND seq_priority = 1 
      AND as_of_date>=@department_as_of_date;

If the balance of the credit is above the amount set, then the transfer is not completed. Any amount equal to or below the amount set will be transferred. The transfer will proceed even if it is outside of the Minimum / Maximum threshold.

Batch Process parameters

In the Govern batch process, there are parameters in the Criteria Selection (group). They are as follows:

Transfer Credits from One Year to Another batch process parameter

  • Saved Dataset: This dropdown selection will enable you to select from a predefined dataset built in Govern.
    • It is enabled for all subsystems
    • The dataset is a selection of P_ID-s, except for the subsystems which work by name (AC, BR, BT, MB, MV, ST). In instances where the subsystem is AC/BR/BT/MB/MV/ST, the dataset will be a selection of NA_ID’s.
  • Minimum / Maximum Amount: new options to select a range of amounts to include in the process.
    • This parameter is enabled for all subsystems. When an Minimum Amount entered, values less than the entered amount will not be processed. (i.e., Input as a Positive Value).
    • If an amount is entered into the Maximum Amount parameter, anything greater than the entered amount will not be processed. (i.e., Input as a Positive Value)
    • If the parameters are empty, all amounts will be processed.

 

Related Topics

Accounts Receivable (A/R Module)

 

 

101-ar-bp-013

 

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