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

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

PC – Building Information

Miscellaneous Billing (MB) Module

Version 6.x

Overview

Govern’s Miscellaneous Billing module is a flexible invoicing and collection system. It can be used for special or occasional invoicing functions such as transportation costs or courier fees that do not fit easily into any other category. The system facilitates the entire billing process for uncommon charges, by updating the Accounts Receivable records and calculating financial and past due account charges, for all bills. The system can be integrated with the G/L for automatic updates.

The user forms for Miscellaneous Billing include the following:

  • Miscellaneous Billing Account Miscellaneous Billing accounts are set up for individuals or companies. Multiple accounts can be set up for each individual or company. Each account can be exempt from one or both sales taxes.
  • Invoice Data Entry The data entry for the miscellaneous billing invoices is performed on the Miscellaneous Billing Invoice. Invoices can be posted manually from this form or automatically in a batch process.
  • Recurring Invoice Data Entry Recurring invoices can be created for miscellaneous billing items that occur on a regular basis.

The administrative menus for Miscellaneous Billing are as follows:

  • Miscellaneous Billing General Parameters: This form is used for defining the sales tax parameters for the items that are invoiced under Miscellaneous Billing. One or two sales taxes can be defined, depending on the requirements of the organization. The Sales Tax is associated with each item. An account can an account can be exempt from one or both taxes.
  • Miscellaneous Billing Items The Items are defined for the invoices. A default amount is added. An A/R Class is associated.
  • Miscellaneous Billing Categories: The Miscellaneous Billing categories are used for creating groups of items. This facilitates data entry.
  • Recurring Batch Codes: The Miscellaneous Billing Recurring Batch Codes are used for defining schedules for the miscellaneous billing invoices that occur on a regular basis.
  • Copy to Year: The Miscellaneous Billing Copy to Year is used for copying the Miscellaneous Billing parameters: Sales Tax definitions, Items, Categories, and Recurring Batch Codes from one year to the next.
  • Initialize Next Year: The Miscellaneous Billing Initialize Next year is used for copying the recurring invoices from one year to the next.

 

Read More...

 

Specification

Miscellaneous Billing

  • Standard Search
  • Flexible Account Setup and Maintenance
  • Regular & Recurring Invoices
  • Invoice & Recurring Invoices posting
  • Detail Invoicing Itemized by User Defined Miscellaneous Billing Items setup with an A/R Class Code
  • Up to 2 Sales Tax Applicable

Accounts Receivable

  • Interest calculation on past due amounts
  • Re-Apply Funds (A/R OCH and OCT processing)
  • ACH Processing by Name

Tax Lien

  • Link to Property
  • Transfer unpaid invoice due to real property tax (tax lien)

Standard Reports

  • Recurring Entry List (by status)
  • Aged List of Accounts by A/R class code (A/R Standard Reports)

Automated Workflow (Activity Base) Miscellaneous Billing

  • Activity can trigger generation of Misc. Billing Invoices

 

See Also

  • Accounts Receivable
  • Cash Collection
  • Real Property Taxes

What’s New

New developments related to the Miscellaneous Billing module will be listed here.

 

 

 

101-mb

 

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

BP – NY State – Generate Real Property Tax – ARLM 1 & 2 Batch Process

New York State – Generate Real Property Tax – ARLM 1 & 2 Batch Process

Release v6.x

Specification Overview

Purpose

The purpose of this batch program:

Identification

  • Process Name: NY_ARLM1_2
  • Requirement Number: 15890

Records to be processed:

  • Year selected: or all if none selected
  • Records (parcels) selected: all, saved named dataset (includes autosave dataset), jurisdiction, neighborhood
  • Record Frozen-id = zero (current)

 

Read More...

 

Records to be calculated:

  • T/C

Batch Processing:

  • The batch program can be scheduled to run periodically.
  • The transaction Mode “Roll Back If One Transaction Failed” is not supported. It will be “Continue If One Transaction Failed” by default
  • Refer to the Standard Batch Process details Batch Program Setup or Govern Scheduler for more details

 

Batch Compute User Interface

The following parameters and options are available:

Year :

  • All if no year is selected. The year field is user persistent and displays the year selected when the batch process was last run – to verify

Parcels to compute option:

  • All, or by Jurisdiction, Neighborhood or Saved Name Datasets – to verify

TIP: If you turn on the TREEVIEW Synchronization option (Govern’s Option menu), and select the AUTOSAVE from the Saved Datasets drop down table, the compute will processed all records in the user’s Dataset Treeview.

Batch Execution

The batch program can be executed on demand or scheduled with Govern Scheduler.

During the execution, warning and error messages will be presented in the batch result grid. – to verify

  • On error, the parcel id will be displayed in the message
  • Double-click on the message to access the full text

Once completed, information will be displayed, that includes:

  • Parameters and Options used
  • Total number of records read
  • Total number of records processed

 

Batch Processing (technical)

Before Executing Subprocesses:

  • Select all parcel ID and frozen ID related to the year (or all year if none selected) the jurisdiction, or the neighborhood or the saved dataset if chosen.

Execute Subprocess

  • For each batch process

Error Reporting
In addition to the standard Batch Processing standard error reporting, the following will be validated:

 

What’s New

[6.0] Batch program created for OpenForms

Troubleshooting

The following is to help troubleshoot the batch process.

  • After changes, it is always best to compute for a single year and small dataset
  • The parcel id is listed in the error message
  • Turning on the Govern Diagnostic Tool
  • Turning on the SQL Profiler Tool (system administrator)

See Also

The following information might be of interest

 

 

 

998-re-bp-113

 

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 – Tax Lien to Real Property

Miscellaneous Billing (MB) – Tax Lien to Real Property

Overview

Feature is currently not available and under review. Contact R&D for roadmap information.
For unpaid miscellaneous billing items, it is possible to transfer the unpaid miscellaneous billing invoices amount due to a tax levy.
In order to do so, you the following is needed:

  • Setup of Real Property Levies to use
  • Accounts need to be linked to a property
  • The Tax Lien Batch Process that will transfer the amounts to a tax levy need to be executed.

Linking a Property

Use the following procedure to link a property to a Miscellaneous Billing Account record.

 

Read More...

 

Adding a Property

To link a property, click on the Link Property Tab
Search and select a property
Save the Miscellaneous Billing Account.

Once the parcel is linked, the MB_MASTER record is populated with the P_ID. If there is an AR_MASTER, the P_ID is also populated

Removing a Property

Once a property is linked, you can remove this link by clicking on the remove button.
This will prompt for “Remove Parcel Code #9999999999? with Yes or No as options.
If answered Yes, the display of the parcel link is removed. The MB Account record still needs to saved. This will then populate the P_ID with null, and also update the AR_MASTER.P_ID to null.

 

 

 

101-mb-fea-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...