WM – System & User Registry

Workflow Management – System & User Registry

Version 6.1

System Registry Parameters

Registry Filter: None
Year Filter: Not Applicable

Section Name Key Name Key Value Description
Workflow Management Inspection Form Select a Form The inspection form is called automatically from different areas of the system.
When this is the case, the form selected here will be displayed.
Workflow Management Template Form Select a Form Workflow models are created dynamically.
In addition, if a form template is entered here, a workflow form for the model will be created.

 

User Registry Parameters

Registry Filter: Workflow Management
Registry Key Type: User ID

Section Name Key Name Key Value Description
Workflow Management Autocollapse Completed Steps True/False When checked, the steps completed will auto collapse in order to facilitate scrolling and viewing large workflows.
Workflow Management Completed Activity Color Color Picker Used to select for the user the color to display completed activities
Workflow Management Initiated Activity Color Color Picker Used to select for the user the color to display activities that are initialized

 

All Module System Registry

For a complete list of System Registry Parameters
Click here

 

 

100-sy-registry-wm

 

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

Reporting in OpenForms

Reporting in OpenForms

Version 6.0 and Version 6.1 (In Development)

Overview

The following page reviews General OpenForms reporting features and options specifications.
For additional information, see Standard Feature Reports in Govern (std-fea-013) and Report Editor and Report Criteria setup in Govern Administrator.

Specifications

The following standard features are available for reporting

  • Standard and Custom Reports Definitions
  • SAP Crystal Reports and Crystal Reports server are supported
  • Microsoft SQL Server Reporting Services are supported
  • Reports are setup by Profiles
  • Security can be setup by Profile User and Role
  • Run-Time parameters (required and not required) and selection criteria can be setup by report definition
  • User persistent run-time parameters by user (parameters and criteria entered are saved by user)
  • User defined output report formats
  • Reports can be executed automatically upon a batch definition execution (after batch process completion)
  • Reports can be scheduled using Govern Scheduler
  • Reports output format can be configured

Read More...

System Registry Parameters

Default paths and server information are stored in the system registry.

To access, in the GNA ribbon…

  1. Select Parameters (tab) > System Parameters (group) > General Settings Editors.
  2. In the OpenForms General Settings form, select Report from the Registry Filter combo-box.
  3. Locate the Section Name column.

Configurable paths related to reports are presented in this section of the registry.

NOTE: Errors will be displayed in the Report Editor if paths are not correctly defined.
  • Crystal Report

    • Custom and Standard report paths
  • Log File
    • Standard Log Path – N.B. specified at the report level
  • Report Parameters
  • SSRS configuration parameters, service and connection information

Report Definition Editor

There is an underlying intelligence in the functioning of the Reports editor.
When setting up a report, both SQL Server Reporting Service (SSRS) and Crystal Reports reports are read, and the data sources are scanned.
On run-time, connection key(s), parameters and predefined criteria are used to execute the report.
Multiple report definitions can be configured for the same report. Currently there are two (2) editors:

  • Crystal Report
  • DocX Reports

Crystal Report Definition Editor

The report definition contains:

  • Report Name
    • Physical report name selected from the standard or the custom report path
  • Audit Trail
  • Report Group – now linked to profiles
    • Upper Level
    • Lower Level
  • Recordset Key – that is to be used.
    • List of Govern IDs
  • Report Criteria
  • Criteria Key
    • User Selection Report Criteria Prompts that can be configured using any of the fields of tables used in the report
  • Alternate Connections Key
    • The deployment connection key is used when executing a report. In some cases, a secondary connection key can be provided
  • For detail information, see Report Editor and Report Criteria

Report Parameters

The following are standard report parameters

Parameter Name Value returned
Govern ID code Govern IDs (p_id, na_id, wm_id, etc.)
dept Ids.Dept
dept_label Vt_user WHERE tableName=’depart’ AND code=Ids.Dept
language Cuurent set language
year Ids.Year
rpt_county Sy_registry WHERE sectionName=‘general’ AND keyName-‘county’
rpt_date ‘ShortDate LongDate’ (as string)
rpt_default_date ‘ShortDate’
rpt_login Ids.User
rpt_logo

Path : ‘{RegistryVaue}ReportCompagnyLogo.bmp’

Registry Value is found in the User/System Regostry using those rules:

  • Try to get value from usr_registry WHERE sectionName=’govern’ AND keyName=’bitmap’
  • If no value found, fall back on sy_registry WHERE sectionName=’path’ AND keyName=’bitmap’
rpt_name Report Path
rpt_range Return, as string, all the filter dynamically applied on the Report
rpt_state Sy_registry WHERE sectionName=’general´AND keyName=’state’
rpt_title Report description (as set in GNA)
rpt_ub_max_variation Sy_Registry WHERE sectionName=ub parameters’ AND keyName=’Max Variation’
rpt_uid Ids.User
rpt_username OrganizationName set in GovernNetConfig.xml
uniform Sy_registry WHERE sectionName-‘work_text’ AND key_name=’Assessment Equalisation Rate’

 

Formulas for Crystal Reports

This section lists the recommended, general, read-only and conditional formulas to include when creating reports through Crystal Reports.

Recommended Formulas

Include the following formulas when you create Crystal Reports:

Formula Definition
@rpt_date (totext (currentdate)) Date & Time
@rpt_name Report Name
@rpt_Username Town or Company Name

General Formulas

Govern populates the following Crystal Reports formulas automatically, if they are included in your reports:

Formula Definition
@dept Department (code)
@dept_label Department label
@language Language
@rpt_county County
@rpt_default_date Default Date
@rpt_login User name
@rpt_range Range Text
@rpt_state State
@rpt_title Report Title
@rpt_uid User identification code (UserID)
@uniform Assessment Equalization Rate
@year Fiscal year in use by current user in Govern

 

Read-Only Formulas

The following Crystal Reports formulas are read-only; i.e., they must contain a non-blank value in the report. These formulas trigger specific actions or populate specific formulas:

Formula Action
@acbill Refreshes the AC_POST_MASTER table with the current Aircraft ID or the current Name ID (in duplicate bill printing).
@all_ar_needed_ac Populates the value of several formulas for the current NA_ID and for the all Tax sub-systems. See the Conditional Formulas section on this page.
@all_int
(under revision)		 Updates the following fields in the AR_ SUMMARY table for all installments with positive balance, for all Taxation and Assessment sub-systems and for the current NA_ID. (All updated installment records within a sub-system will contain the same information).
LATE_CHARGES (Accrued Penalty or Interest)
CHARGE_DATE (Current date as defined in Govern)
BALANCE_AS_OF_DATE (Total balance due, exclusive of late charges)
@btbill Refreshes the BT_POST_MASTER table with the current Boat ID or the current Name ID (in duplicate bill printing).
@drilldown Enables Crystal Reports Drill Down feature
@govern_tx_interest
*This formula is used when calling a Web Crystal Report		 Updates the LATE_CHARGES column in the AR_SUMMARY table.
Use when calling a Web Crystal Report in the Real Property Tax Subsystem.
@govern_ub_interest
*This formula is used when calling a Web Crystal Report		 Updates the LATE_CHARGES column in the AR_SUMMARY table.
Use when calling a Web Crystal Report in the Utility Billing Subsystem.
@mv_ar_needed_ac Populates the value of several formulas for the current NA_ID and for the Motor Vehicle Excise Tax sub-system. See the Conditional Formulas section on this page.
@mvbill Refreshes the MV_POST_MASTER table with current Motor Vehicle ID or the current Name ID (in duplicate bill printing).
@mv_int Updates the following fields in the AR_ SUMMARY table with motor vehicle excise tax information, for all installments having a positive balance for the current MV_ID. (All updated installment records will contain the same information).
LATE_CHARGES (Accrued Penalty or Interest)
CHARGE_DATE (Current date as defined in Govern)
BALANCE_AS_OF_DATE (Total Balance Due, excluding late charges.)
@pp_ar_needed Populates the value of several formulas for the current PP_ID and for the Personal Property Tax sub-system. See the Conditional Formulas section on this page.
@pp_ar_needed_ac Populates the value of several formulas for the current NA_ID and for the Personal Property Tax sub-system. See the Conditional Formulas section on this page.
@ppbill Refreshes the PP_POST_MASTER table with the current Personal Property ID or the current Name ID (in duplicate bill printing).
@pp_int Updates the following fields in the AR_ SUMMARY table, for the current PP_ID, with Personal Property Tax information, for all installments having a positive balance. (All updated installment records will contain the same information).
LATE_CHARGES (Accrued Penalty or Interest)
CHARGE_DATE (Current date as defined in Govern)
BALANCE_AS_OF_DATE (Total Balance Due, excluding late charges)
@re_ar_needed Populates the value of several formulas for the current P_ID and for the Real Estate Tax sub-system. See the Conditional Formulas section on this page.
@re_ar_needed_ac Populates the value of several formulas for the current NA_ID and for the Real Estate Tax sub-system. See the Conditional Formulas section on this page.
@re_int Updates the following columns in the AR_SUMMARY table, for the current P_ID, with Real Estate Tax information, for all installments having a positive balance. (All updated installment records will contain the same information).
LATE_CHARGES (Accrued Penalty or Interest)
CHARGE_DATE (Current date as defined in Govern)
BALANCE_AS_OF_DATE (Total Balance Due, excluding late charges)
@td_ar_needed Populates the value of several formulas for the current P_ID and for the Tax Deferral sub-system. See the Conditional Formulas section on this page.
@td_int Updates the following fields in the AR_SUMMARY table for all installments having a positive balance, with Tax Deferral information for the current P_ID. (All updated installment records will contain the same information).
LATE_CHARGES (Accrued Penalty or Interest)
CHARGE_DATE (Current date as defined in Govern)
BALANCE_AS_OF_DATE (Total Balance Due, excluding late charges)
@tt_ar_needed Populates the value of several formulas for the current P_ID and for the Real Property Tax Title sub-system. See the Conditional Formulas section on this page.
@tt_int Updates the following fields in the AR_SUMMARY table, for the current P_ID, with Tax Title/Lien information, for all installments having a positive balance. (All updated installment records will contain the same information).
LATE_CHARGES (Accrued Penalty or Interest)
CHARGE_DATE (Current date as defined in Govern)
BALANCE_AS_OF_DATE (Total Balance Due, excluding late charges)
@txbill Refreshes the TX_POST_MASTER table with the current Property ID or the current Name ID (in duplicate bill printing).

 

Conditional Formulas

The Crystal Reports formulas listed in this table are populated by Govern conditionally, on the presence of the following read-only formulas:

  • @all_ar_needed_ac
  • @mv_ar_needed_ac
  • @pp_ar_needed
  • @pp_ar_needed_ac
  • @re_ar_needed
  • @re_ar_needed_ac
  • @td_ar_needed
  • @tt_ar_needed

 

Formula Action
@ar_interest_1
@ar_interest_2
@ar_interest_3
@ar_interest_4		 Calculates the interest and penalties committed for the current fiscal year and the specified installment.
@current_due Calculates the total balance due for the current fiscal year, including late charges.
@daily_interest Calculates the daily interest and penalties.
@prior_ar_fee_1
@prior_ar_fee_2
@prior_ar_fee_3
@prior_ar_fee_4		 Calculates the demands, charges and fees committed for prior fiscal years and the specified installment.
@prior_ar_interest_1
@prior_ar_interest_2
@prior_ar_interest_3
@prior_ar_interest_4		 Calculates the interest and penalties committed for the prior fiscal years and for the specified installment.
@prior_due Calculates the total balance due for the prior fiscal years, including late charges.

 

Tables/Fields and Naming Standards

Report File Name

  • Physical report name available in the standard or custom report path
  • Report File Name Maximum Length is 15
  • Recorded in VT_SYSTEM where table_name = REPORTS

Report Options

  • Standard report parameters that can be used in the report (ex: Department, City/Town Name, Report Title, etc.)
  • Recorded in VT_SYSTEM where table_name = RPT_OPT

Report Record Set Keys

  • Standard Govern IDs located in table VT_SYSTEM where table_name = BRULE

Report Definition

  • Report definitions are stored in table USR_REPORT_DEF
  • Table contains:
    • File Name (available in Standard or Custom report paths)
    • Audit Trail – deprecated
    • Record Key
    • LK_Brule

Batch Processing and Reports

Parameters defined for a batch process can be used by reports.

100-bp-reporting.png

Batch Process On Completion Report

It is possible to setup a report to be executed upon a batch process definition completion.

Batch Process to Schedule Reports

It is possible to setup a batch process definition to schedule reports.

Report Formats

You can specify the output format of a report that will be generated by a batch process. Verify with IT for the list of file formats allowed for the organization.

Batch Process Parameters

The parameters defined for the batch process can be accessed by the report.

 

Troubleshooting

  • A new installation pack for Crystal ReportTM is required to be installed on each client when upgrading to Release 1706.

 

What’s New

Related Topics

Additional Information related to Reporting

 

 

100-Reporting

 

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

Govern 10.8 to OpenForms 6.0 Upgrade

Upgrade from Govern 10.8 to OpenForms 6.0

Upgrading to OpenForms version 6.0 or greater

Overview

As Govern has undergone a major revamp it is a good time for business re-engineering. Prior to upgrading to 6.1, a review of customer processes and requirements is recommended.
More than likely needs have changed, not to mention technology, hardware and software that evolved.

  • NOT A REGULAR UPDATE *** Structure changes and new features that can bring significant benefits to users if reviewed and analysed beforehand.

See also Database Standards (100-Standards) | System Requirements (100-SysReq)

Configuration Changes

DATABASE Cleanup

To improve management, the reference database information is now recorded in a XML file and created automatically when GNA is first run. Indexes have been standardized (see standards).

  • Database column types, lengths and/or nullable properties, etc. when not in compliance with the ReferenceXML need to be cleaned-up.
  • Database Indexes should be deleted and recreated at each version upgrade. Please note that CUSTOM indexes will need to be recreated manually after a delete ALL!

NOTES:

  • Before starting the process, we highly recommend to review the CUSTOMIZED indexes to make sure they are still needed and that they do not create performance issues.
  • To make it possible to change field types in design mode when there is data in the column, you need to turn OFF the PREVENT DESIGN CHANGE option in MS SQL SERVER and make sure to turn it back ON afterwards!!!

CLEAN UP TIPS:

  • Delete the indexes first (ALL if you have reviewed custom indexes and can recreate them) than rerun the verify database. Invalid indexes can cause multiple errors.
  • Unused tables (ex: Boat, Aircraft, MV…) or empty tables (no records) should be deleted (quicker) as they will be created correctly at the next initialize.
  • Before making changes to the column types via the design mode, you need to turn off the option that ‘Prevents design changes in MSSQL SERVER‘. Remember to turn in back ON afterwards.

DOCUMENTATION

  • Detailed information on creating the windows environment, the upgrade process and examples of data corrections made to to an upgraded database.

700-upgrade108_to_60.pdf.
[700-upgrade108_to_60 documentation]

GOVERN STRUCTURE

The basic structure of Govern has changed. The profile is now the cornerstone of the setup and the security is setup directly in the OpenForms Designer.
The same table is used for USERS and Groups can be imported into ROLES in GNA. Note: Create the desired Structure on paper first to see if doing so will be effective.

FORMS
All forms need to be created using the new OpenForms DESIGNER.

PROFILES

Profile links need to be created for Batch Programs, Reports, Forms, Accounts Receivable, etc.

REPORTS
Report defined in the database (configured) are verified to make sure the SSRS or Crystal report exists in the standard or the custom folders defined.
Note: The user will be asked to delete invalid definitions the first time. Make sure report folders are setup correctly.

Step by Step

Update 10.8 to v6.0+ and create a deployment …

  1. Restore Database to MS SQL Server
  2. Create Deployment/Connection Key
  3. Download & Install Binaries
  4. Install GNA
  5. GNA Utilities – Verify Database
  6. Correct Errors — see MS SQL SERVER Option to allow
  7. GNA Utilities – Verify Database
  8. Review Users
  9. Review Departments
  10. GNA Import/Export – Import ….
  11. GNA Import/Export – Import Forms
  12. GNA Verify database (Always after an import)
  13. GNA System Registry for Reports
  14. GNA Create Profile (Forms, Reports, Batch Process (testbatch) ….
  15. GSM Synchronize
  16. GSM Import Departments (If desired)
  17. GSM Review Roles
  18. GSM Review Security (Applications, Forms, etc.)
  19. Open Govern and review the options
  20. Search, send to the treeview and open a form

 

Model Updater

IMPORTANT NOTE:
Model Updater has not been re-engineered for version 6.0. It is on the roadmap.

Troubleshooting

At any point, if there are problems, Govern VALIDATOR should be executed,

 

 

100-upgrade-GFWtoOF

 

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

Product Resources page

Product Resources

System

100-Expressions
100-Queries
100-Constants
100-Formulas & Logical Expression
100-SY Registry

Database Diagrams

Visio Database Diagrams

Data Configuration

Resource File
System Validation Tables
User Tables

Technical Information

System Dictionary (SY DICT DESC)
Data Mapping

TECH NOTE: The main difference between a QUERY and an EXPRESSION is that the expression has access to the FORM’S Attributes. Furthermore, these expressions are bound to the entity. Change EVENTS will recalculate any expression that depends on, or uses a, newly changed attribute.

– # –

 

100-upgrade-OFto61

Upgrade to Govern 6.1

Overview

This page is intended for customers, business analysts and technical services to provide tools and tips when upgrading to OpenForms 6.1 from a prior OpenForms version or from Govern for Windows. Version 6.1 is the first OpenForms version that is no longer backward compatible with Govern for Windows 10.8. It is an important upgrade as there are structure changes and core functionality changes so it is important to be well prepared.

NOTE: Everyone’s COLLABORATION is needed to improve, optimize the process of Upgrading to 6.1 (major milestone release). HOW? By sharing knowledge, experience or tips and tricks that can be of interest to the next person that will perform an upgrade. This can be sent via email (object: UPGRADE …), or by sending a note to Harris Govern R&D…
IF or WHEN?
– R&D … You think that a software change may impact the upgrade process
– PS … You experienced problems or singularities during an upgrade that could be of interest to others …
Thank you in advance for your cooperation.

Before Getting Started

Read More...

It is highly recommended that a complete backup of the database prior to copying or upgrading be performed.
Because of the structure changes and core functionality changes, it will be important to review and assess the work that will be needed.

Things to consider

  • Formulas and Logical Expressions …. are replaced with Expressions. Formulas will be converted, but not all of them may work. Logical Expressions will need to be rewritten.
  • Queries will need to be reviewed to make sure they still work or to implement the new features (setup by jurisdiction, year, etc.)
  • Conversions will need to be performed that will impact reporting and queries
  • Reports will need to be reviewed
  • Vt and System tables used in reports will need to be flagged so that a view will be created for reports
  • New Table structure BUSINESS RULES

Database Changes needed prior to upgrade
A new Business Rule for Table Naming is enforced and Invalid table names should be fixed prior to the upgrade.

  • Table name must start with a LETTER
  • Table name cannot contain non ALPHA-NUMERIC characters except for the underscore ‘_’ character
    • See a Script Example that checks User Validation Tables (where the problem is most likely to appear) for INVALID characters.
    • Tip: With the select tool set to on, you can copy text from PDF documents that can be pasted in a SQL Query Window

Tables and Data Manipulation

  • A copy of all MA PARM tables will be created automatically when executing the Database Verification. Ex ma_parm_income copied to ma_parm_income_backup

 

Upgrading

Deployment

Download and deploy 6.1 Binaries
Note: Client installation of Crystal Report for .Net is not mandatory if already installed

Database Verification

The first time you open Govern Administrator (GNA), a message will prompt the user that the version of the database is not the same and that a database verification is needed.
Please note that it will need to be run twice because of changes that cannot be processed in one step only. This error message will be displayed the first time: The VT_USER records cannot be verified because the SIMULATION column is still in the VT_USER table. Click START to rerun the process and remove the error.

System and User Tables

Before release 6.1, system and user validation tables were each a distinct table in the database, recorded under VT_USER_xxxx or VT_SY….
These tables have been merged into a single table for USER and SYSTEM.

User Added Fields
Upgrading from Govern for Windows … need to validate if any tools
Upgrading from Govern OF 4.7.5, 5.1, 5.2 …. ‘need to be handled manually‘

Conversion (GNA)
A new menu item was added in GNA to convert or merge tables

Batch Programs need to be recreated
Batch Programs standard (verify if it can be added) and custom need to be recreated.

Troubleshooting

PC PARCEL

  • 2 fields have been changed to nullable in this table in 6.1. If you get errors during the Verify Database on VIRTUAL_PARCEL_FLAG or NON_PARCEL_FLAG, it might be that a non-supported customer index exists on this table. If this is the case, than you need to manually drop this index prior to running the Verify Database

 

Unverified Notes

When you come upon information that might be of interest, create a note here. It does not have to be pretty or formatted …

 

100-upgrade-OFto61

 

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

Govern Technical Standards

Govern Technical Standards

Overview

Govern has established standards and best practices at both the database and application level.
Unless specified otherwise, customized tables, attributes, etc. should be prefixed by the customer 3 digit code.

What’s New

[6.1] Database Table Names are limited to 30 characters to support Oracle Database Business Rules.

[6.0.1409] All Govern Database indexes that are managed by the application now have the prefix of GV_.
You can now delete indexes (Govern or ALL) in GNA, when you run a Database Verification.
IMPORTANT: Govern indexes are automatically recreated. Custom indexes are not.

[6.1] New Table Name Business Rule

  • must start with a LETTER
  • must not contain special characters except the underscore ‘_’
  • must be less than 8 characters

Database Objects Standards

These standards are mandatory as the naming convention is used in the application and can cause problems in certain situations if not followed or if reserved words or prefixes are used.

Table Name

IMPORTANT: The table name maximum length is 30.
The name is broken down in 3 sections: Prefix + Type (optional) + Descriptive Name

  • Prefix:
    • SY System Config
    • USR User Config
    • OF OpenForms Config
    • MODULE (see Module Codes)
    • CUSTOMER CODE (if custom tables)
  • Type (optional):
    • parm (parameter)
    • lk (link to)
    • table (master table used often used for calculation)
    • tmp (temporary)
    • web (e-government)

Attribute Name (Fields)

    • CUSTOMER CODE prefix if customized fields (best practice)

Indexes & Primary Keys

  • Prefix:
    • PK = Primary Keys
    • GV = Govern Indexes – They are managed by the Verify Database and may be deleted.
    • Customer Code prefix is custom = We recommend to use a standard code for all custom indexes.

Views

  • Prefix:
    • V = Govern Standard Views
    • V_VT= User tables represented in a seperate view to be backward compatible with 6.0 reports, etc. Manage in GNA, Editors, User Validate Tables.,
    • VW = Customized Views
  • Prefix_TREEVIEW_ used for the different Treeview
  • Prefix_MATIX used for MATIX integration and setup by form

 

Stored Procedures

  • Prefix (to be verified):
    • As a general rule of thumb, custom stored procedures or packages should be prefixed with the customer code.

 

System Resources Standards

System Flags

Validation tables used by Govern are flagged as system and will be replaced when upgrading.

Connection Keys

Database name + Server + Server & Server Version

Batch Programs

  • Prefix with Customer Code for customized batch programs
  • Batch Codification and Classification for new programs

Reports

  • Prefix with Customer Code for customized batch programs

Govern Queries

  • AT= Audit / Summary
  • CN = Central Notes
  • DH = Dashboards
  • SM = Summary
  • PRF = Profile Queries

Module Codes

  • PC = Property Control
  • NA = Name & Address (na)
  • TX = Tax Real Property
  • PP = Personal Property
  • BT = Boat
  • AC = Aircraft
  • MV = Motor Vehicles Excise
  • BU = Business Tax
    • ST = Self Reported Tax
    • PM = Licenses
  • MA = Mass Appraisal
  • PM = Land Management (Before 6.1)
  • UB = Utility Billing
  • MB = Miscellaneous Billing
  • AR = Accounts Receivable
  • CC = Cash Collection
  • DC = Delinquency
  • TT = Tax Title
  • BR = Bankruptcy
  • WM = Workflow Management (6.1+)

 

 

100-Standards

 

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

100-upgrade-OFtoOF

Upgrade from Govern 5.x to Govern 6.0

Overview

This page is intended for customers, business analysts and technical services to provide tools and tips when upgrading to Openforms 6.0 from a prior Openforms version or from Govern for Windows. Govern users that are upgrading from Release 5.1 to Release 6.0 will need to note the changes in the behavior of the Release 6.0 suite of applications. Click here for Upgrade Configuration Details.

Tips before upgrade

  • Prior to any upgrade, it is recommended that a complete backup of the database prior to copying or upgrading be performed.

Design Workflow Changes

The Model Designer (MoD) application is no longer a part of the suite. Forms are now designed with the OpenForms™ Designer (OFD). The Business Entity Designer (BED) is still used for designing Business Entities.

Database Changes

For Release 6.0, changes have been made to the structure of models used in the Model Designer (MoD) Release 5.1 and the new OpenForms™ Designer (OFD) Release 6.0. As a result of these changes, the databases that are used by Release 6.0 applications are not compatible. Govern applications that are prior to Release 6.0 will be referred to as legacy applications. Govern Databases created for use with releases prior to 6.0 will be referred to as legacy databases.
In order to assure the integrity of the 6.0 database, the Govern system will prevent the use of any legacy databases unless they have been created for, or upgraded to Release 6.0.

Legacy Applications

Release 5.1 Applications

The following Release 5.1 applications WILL NOT work with a Release 6.0 database.

  • Business Entity Designer (BED)
  • Query Tool (QT)
  • Security Manager (SM)
  • Model Designer (MoD)
  • Govern
  • Govern New Administration (GNA)

 

Release 5.1 Exceptions

Users attempting to set a Release 6.0 database as a Default Connection Key in the Connection Key Management form in the Release 5.1 Govern New Administration (GNA), will be presented with a warning indicating that they cannot select a database version that is greater than Release 5.1. No change will be made to the default connection key.
When a user tries to access any of the above applications, a warning message is displayed.

Release 6.0 Applications

Govern Release 6.0 applications will not run with a Release 5.1 or lower database. The following is a list of the Release 6.0 applications that will not work with a legacy database, i.e. a version that is less than Release 6.0.

  • Business Entity Designer (BED)
  • Security Manager (SM)
  • Query Tool (QT)
  • Open Form Designer (OFD)
  • Govern (Release 6.0)

Attempting to run any of the above Release 6.0 applications will result in a warning being displayed.

Release 6.0 Exceptions

Users attempting to set a Release 5.1 database as a Default Connection Key in the Connection Key Management form in the Release 6.0 Govern New Administration (GNA), they will be presented with a warning indicating that they cannot select a database version that is less than Release 6.0. If the user selects Yes, the system will run the Database Verification process and will update the selected database to a Release 6.0 version.

WARNING: When users select the Yes option, GNA will display the Database Verification form to perform a non-reversible upgrade to their database. After the process is complete, the NET_DB_VERSION column in (Table: USR_KEY_MASTER) is updated.

 

NOTE: If errors are encountered during the Database Verification process, the conversion to a Release 6.0 database will not be complete. Any errors will have to be addressed and the process repeated.

Upgrade Paths to Release 6.0

WARNING: Prior to any upgrade, it is recommended that a complete backup of the database prior to copying or upgrading should be performed.

Users that will be using Release 6.0 have two (2) paths to upgrade to Govern Release 6.0 applications:

OPTION 1 – Direct Upgrade

This path is one that will immediately upgrade your current installation database from Release 5.1 to Release 6.0. The database upgrade is irreversible and as such, a complete database backup should be made prior to the upgrade. Should it be necessary to roll back to your Release 5.1 database, the backup can be restored. The Deploy EZ application will be used to update the currently existing deployment. The deployment will consist of the Release 6.0 replacement applications.

NOTE: This Option 1 upgrade path will replace the Release 5.1 applications with their Release 6.0 versions.

 

Upgrade Steps for OPTION 1

  1. Open the Govern New Administration (GNA) Release 5.1.
  2. Use the Connection Key Management form to ensure that the default connection key is set to your Release 5.1 database; close the GNA application when done.
  3. Perform a complete backup of your current Release 5.1 database with your Database Management application.
  4. Update your current deployment with Deploy EZ; update the applications to the latest Release 6.0 versions.
  5. Run the Govern New Administration (GNA) Release 6.0.
  6. At the prompt, click Yes to perform the database update.
  7. When the process is complete, restart the application.

Upon completion of the process, the NET_DB_VERSION column in (Table: USR_KEY_MASTER) is updated. The database conversion is complete. Close GNA and restart the application.

OPTION 2 – Parallel Install

This Option 2 upgrade path is non destructive in that a new Release 6.0 Deployment is created; a name that reflects that it is a Release 6.0 is recommended. As with Option 1 above, a full backup of the Release 5.1 database is mandatory. In addition a new Connection Key (CK) must be created to reflect the existence of a Release 6.0 database. Installing the applications in the Release 6.0 deployment will not overwrite any existing Release 5.1 applications. The newly installed application will run independently of the legacy applications on a separate database.

NOTE: The Option 2 upgrade path will leave the existing Release 5.1 applications and database intact; as no upgrade is actually performed on existing Release 5.1 applications. The database upgrade that is performed is on a duplicate database that is created from a backup of the Release 5.1 version.
There is no synchronization of data between the old and new database; the 5.1 and 6.0 environments are independent of each other. If synchronization of data is required it will have to be performed by a qualified database administrator that is knowledgeable on the functioning of the Govern application and the database structure.

Upgrade Steps for OPTION 2

  1. Perform a complete backup of your current Release 5.1 database with your Database Management application.
  2. With you DB Management application, create a duplicate of the Release 5.1 database; rename with a 6.0 designation, e.g. mydbase_60
  3. Open the Govern New Administration (GNA) Release 5.1.
  4. Use the Connection Key Management form to create a connection key to the newly designated Release 6.0 database.
  5. Set the new connection key as the Default connection; close the GNA application when done.
  6. Launch Deploy EZ.
  7. Create a new deployment with a Release 6.0 designation.
  8. Create your deployment with the latest required Release 6.0 applications.
  9. Run the Govern New Administration (GNA) Release 6.0.
  10. At the prompt, click Yes to perform the database update.
  11. When the process is complete, restart the application.

Upon completion of the process, the NET_DB_VERSION column in (Table: USR_KEY_MASTER) is updated. The database conversion is complete. Restart your applications.

Batch Programs

Batch programs are now linked to profiles and as such will need to be recreated.
The USR_BP_MENU will no longer be used.

Configuration Re-engineering

Click here for more information.

 

 

100-upgrade-OFtoOF

 

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