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

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

SSRS – Changes to Handling of SSRS Reports (301-ssrs-util)

Changes to Behavior of SQL Server Reporting Services (SSRS)

Version 6.1.2206.0142 / 6.1.1811.2019

Overview

The following contains a description of the changes to the behavior of the SSRS feature in Govern

New Features and Changes in Behavior

Parameter Setup Changes

Users should note that parameters are no longer setup in the Reports Parameters screen. This screen will display only the run options that have been configured in GNA.

Possible “Run on” options that can be displayed are as follows:

On Database – Is configured to do not pass any record that is listed in the Govern Dataset Treeview.

On Recordset – Select this option when the SSRS report is to process a set of records. *

On Current Record – Select this option when the SSRS report is to process the current record.*

Changes related to Recordsets

The Recordsets created by the On RecordSet and On Current Record options come from the DataSet Treeview and are saved into the database (Table: USR_SAVED_DATASETS).
These records are grouped by the field SAVED_SET_NAME with a name like: SSRS_REPORT_GUID, where the GUID is a random GUI text generated at runtime.

Since these new recordsets are temporary, they are automatically removed each time a new SSRS report is executed. The criteria for removal is determined by confirming that SAVED_SET_NAME is like SSRS_REPORT_GUID and the field LAST_MODIF_DATE is older than the day before the current execution. For example, if a report execution is done on 08/10/2022, then all reports created before 08/09/2022 will be removed.

Note the following:

  • The Output tab with the report result is no longer displayed for SSRS reports.
  • The report result will be displayed directly on the default browser pointing to the SSRS server that has been configured for Govern.

New Online SSRS Viewer

In the new online SSRS viewer, the end user must perform the following actions to get the Report.

  1. Select/full fill the Report Parameter fields with the desired values for the report.
  2. Click the View Report button.
  3. A preview for the report will be displayed in the bottom.

To download the report, the user must select any of the output formats for the report with a click on the Save button.

To print the report

  1. Click the Print icon.
  2. The report will not be modified and will be copied into the TEMP folder, but in order to execute the report, it will keep looking in the Custom and Standard folders configured in the GNA settings.

 

NOTE: The appearance of the online SSRS screen can vary depending on the SSRS report version installed on the end users server.

This screen will display only the parameters configured as Visible on the report. Hidden parameters are not displayed here and must be configured in GNA under the parameters section in order to map a Govern Id value to them.

Considerations when running an SSRS report

  • At least one Run on option must be selected to run the report.
  • Reports created or edited in Report Builder 3.0 (2014), and the New SSRS Report Builder (2016), are supported and will be executed in Govern.
  • The report must have the SERVER and DATABASE parameters, where the parameters must be configured as:
    • The very first parameters in the report parameters; this because they will be used to configure the datasource.
    • The parameter visibility can be configured as Visible, or Hidden (this is the preferred value).
    • These parameters will be mapped by Govern with the name and database that are to be used to process the report.
    • The DataType must be ‘Text‘.
  • For the options On Recordset and On Current Record,  the report must have a parameter like RECORDSET_{GOVERN_ID} where:
    • {GOVERN_ID} is the Govern ID that will be used to filter the records.
      For example: if the Govern profile that will use the report is configured to use Parcel Ids, then the name for the parameter will be RECORDSET_P_ID.
    • The DataType must be ‘Text‘.
    • The parameter visibility could be configured as Visible, or Hidden (this is the preferred value).
    • A new recordset entry will be created with a dataset name like SSRS_REPORT_{GUID} to store the GovernId, or set of GovernIds that will be used for the operation.
    • These datasets will not be visible to the user in Govern in the Saved Dataset(s) screen.
    • These datasets will be automatically removed from the database after 2 days, upon the next SSRS report execution.
  • The new SSRS report functionality is no longer creating copies in the TEMP folder that is configured in GNA. As a result of this change, it means that the new version is no longer supporting:
    • Add filters on execution time.
    • Display the report output or parameters at govern.

In order to create/add these parameters the SSRS Converter Tool can be used to convert the rdl reports.

See Also

301-ssrs

301-ssrs-util

 

 

301-ssrs-util

 

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 Report Conversion Tool

SQL Server Reporting Services Report Conversion Tool

Version 6.1

Overview

The SSRS Report Conversion tool is a Windows application developed to assist, with some minor manipulations, the conversion of a .rdl report for use in the latest versions of Govern and GNA.

User Interface

When initialized, the SSRS Report Conversion Tool displays as a utility window with input and output parameters.

 

SSRS Report Conversion Tool Parameters

Input Folder – Click to manually type in the path to the Input folder. This is the path to a physical folder that must contain at least one .rpt file that is to be converted.

[…] Select Folder – Click the ellipsis button […] to navigate to the required folder.

Output Folder – This non-editable parameter contains the path to the folder that the converted reports will be placed. This is always a folder named Converted that will be located under the Input Folder path.

Recordset – This combo-box is a GovernId that will be used to group records in Govern. This should be the same GovernId that is configured for the Profile that will be using the SSRS report.

Convert – Click Convert to run the conversion process.

Files to process: – The Files to process area will display all reports within the Input Folder. After a click on Convert, the report names with their status will be listed along with an indication as whether files were converted successfully, or if any issues were encountered during the process.

About the Conversion Process

Users should note the following about the conversion process:

  • The original .rdl file will not be modified.
  • The output file will always add the Parameters SERVER, DATABASE.
  • The parameters RECORDSET_{GOVERNID} will be added if the value for RecordSet is not empty.
    • For example, if the selected value is p_id, the parameter to add will be RECORDSET_P_ID.
  • The datasource connection string will be overridden with the following:
    =”Server=”+ Parameters!SERVER.Value +“;Database=” + Parameters!DATABASE.Value
  • The reports generated in the Output folder are the ones that should be submitted/replaced in the SSRS Server Folders.

 

See Also

301-ssrs

301-ssrs-changes

 

 

301-ssrs-util

 

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 – How to Install

How to Install SSRS

Version 6.0 & 6.1

Overview

The following are the steps required to install Microsoft SQL Server Reporting Services. After successful installation you will be able to use SSRS reports in Govern.

Installation Steps

To proceed you will first need to obtain SQL Server Reporting Services from the Microsoft website.

NOTE: Before any installation, ensure that you have Administrator access to the target computer.
  1. Download Microsoft SQL Server Reporting Services from the following URL: https://www.microsoft.com/en-us/download/details.aspx?id=55252
  2. To install SSRS, click on SQLServerReportingServices.exe.
    • At the first screen click Install Reporting Services.
    • Click to select an edition – select Free: Developer or Free: Express).

      OR

    • Accept the License Terms and click Next.
    • At the Install Database Engine option select Install Reporting Services only. Click Next.
    • At the Specify an install location screen, use the default, or select a path. Click Install.
    • SSRS will be installed.

    • When the installation has completed, restart your computer and prepare to install the Report Server Configuration Manager.
  3. After the system restart, open the Report Server Configuration Manager from the Windows menu.

    1. In the Report Server Configuration Manager screen, at the Report Server Connection prompt, select a server name. This should be the server that contains the SSRS installation.
    2. After the server name has been specified, start the server. Click to select the server on the left hand pane of the Report Server Configuration Manager, and on the right-hand side (RHS), click Start.
    3. At the Report Server Database screen, specify the Report Server Database server.
    4. Next select the option to Create a new report server database.

      At the Change Database prompt, click Database Server on the left hand side. Enter the Server Name, Authentication Type, Username, and Password to test your connection.

      In the Change Database screen, click Database then either use the default or select a name.

      Click Credentials to get the prompt, select an Authentication Type, enter a Username, and a Password.

      Summary of the database, click on next if everything is correct

      On Progress and Finish, click Finish to finish the process.

    5. Select Web Service URL and click on the button Apply

    6. Click on the URL link

    7. Select Database and click on the button Apply
    8. Select Web Portal URL and click on the button Apply
    9. Click on the URL link
    10. Create 3 folders (Standard, Custom and Temp)
    11. Manage folder by adding security to everyone
    12. Refresh the Report Server site, you will see 3 folders
    13. Open the port
    14. Setup SSRS in GNA, go to Parameter\General Settings Editor, choose Report as Registry Filter.
  • Authentication Type – Use the windows integrated security
  • Custom Report Path – Set with the folder named “Custom” created in SSRS previously
  • Standard Report Path – Set with the folder named “Standard ” created in SSRS previously
  • Temporary Report Path – Set with the folder named “Temp” created in SSRS previously
  • URL – The Report Server Web service URL from SSRS
  • Use SSRS – Must be checked to be able to see the menu SSRS in GNA
  • User Domain / User ID / User Password – Will be empty (no need to be set)
You will need to install the Report Builder to be able to change/edit SSRS reports. At the moment you will need to install the version 2014 otherwise you may not be able to edit a Report: https://www.microsoft.com/en-us/download/details.aspx?id=42301

 

 

301-ssrs_how-to-install

 

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this.Loading...