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 …

Restore Database to MS SQL Server
Create Deployment/Connection Key
Download & Install Binaries
Install GNA
GNA Utilities – Verify Database
Correct Errors — see MS SQL SERVER Option to allow
GNA Utilities – Verify Database
Review Users
Review Departments
GNA Import/Export – Import ….
GNA Import/Export – Import Forms
GNA Verify database (Always after an import)
GNA System Registry for Reports
GNA Create Profile (Forms, Reports, Batch Process (testbatch) ….
GSM Synchronize
GSM Import Departments (If desired)
GSM Review Roles
GSM Review Security (Applications, Forms, etc.)
Open Govern and review the options
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 5)
You need to be a registered member to rate this.

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

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 5)
You need to be a registered member to rate this.

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 5)
You need to be a registered member to rate this.

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

Open the Govern New Administration (GNA) Release 5.1.
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.
Perform a complete backup of your current Release 5.1 database with your Database Management application.
Update your current deployment with Deploy EZ; update the applications to the latest Release 6.0 versions.
Run the Govern New Administration (GNA) Release 6.0.
At the prompt, click Yes to perform the database update.
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

Perform a complete backup of your current Release 5.1 database with your Database Management application.
With you DB Management application, create a duplicate of the Release 5.1 database; rename with a 6.0 designation, e.g. mydbase_60
Open the Govern New Administration (GNA) Release 5.1.
Use the Connection Key Management form to create a connection key to the newly designated Release 6.0 database.
Set the new connection key as the Default connection; close the GNA application when done.
Launch Deploy EZ.
Create a new deployment with a Release 6.0 designation.
Create your deployment with the latest required Release 6.0 applications.
Run the Govern New Administration (GNA) Release 6.0.
At the prompt, click Yes to perform the database update.
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 5)
You need to be a registered member to rate this.

100-Installation-Hybrid108

Govern 6.0 HYBRID Installation (Govern for Windows)

[The content on this page is under review]

Overview
Quick Reference guide for the installation of Govern for Windows 10.8 Components.
Download requirements and installation steps are covered here.

Requirements

When installing from scratch, the 10.8 REFERENCE DATABASE & BINARIES must be used as a starting point.
Download FULL SERVICE PACK 10.8 and password file.

MS ACCESS is REQUIRED suggested as Govern for Windows uses Microsoft Attach Tables Methodology for improved client/server performance.

Installation

Read More...Read Less...

100-(ui)-updata-[v10.8].png

STEP 1 – System Installation packs

Unzip pack and perform SETUP – to be verified with Richard Support

STEP 2 – Create ODBC Drivers Client connections

For each OpenForms Govern Environment (Production, Staging, Training, etc.)

STEP 3 – Setup Organization Licenses INI files

Create a .INI file that will be configured with an Organization Name and Serial Number.
Below is a sample .ini entry…

‘—————————– START —————————–
[General]
organization name=MyCompany
serial number=123456-78910111213-141516
primary activation key=
secondary activation key=

SQL=sqlserver
GLOBAL_USR_ADM=
GLOBAL_PASSWORD_ADM=XXXXXXX
USE_ACTIVE_DIRECTORY=no

PASSWORD_DOUBLE_CHECK=no
password=XXXXXXXXX
password suffix=
userid prefix=
User=CITY
Login Web Service URL=

[Database]
DSN=GOV_PSTRAIN
DB=GOV_PSTRAIN
Local Name=
DatabaseName=MYSERVERGovernDatabaseGOV_PSTRAIN_MYSERVER_SQL.mdb

[Upgrade]
Grant Name List=upgduser
‘—————————– STOP —————————–

STEP 4 – Run UPDATA – Database UPGRADE

Run the Govern for Windows Updata.exe application.

STEP 5 – Run UPDATA – Create … ATTACH TABLES

If you need more info on installing Govern for Windows, click here for the Getting Started in 10.8 manual.

STEP 6 – OpenForms Installation

OpenForms Initial Setup needs to be performed after installing Govern for Windows. After the Govern for Windows installation, OpenForms Database Verification needs to be performed.

STEP 7- OpenForms Update

Database Verification in GNA
Synchronize in GSM

Advanced SQL Queries

The prior sections contained general rules that are to be followed when creating SQL queries. The following are specific examples of issues with advanced queries, and how they may be resolved.

A. Double Brackets Workaround

Database entries in Govern can have three (3) states, TRUE, FALSE, and NULL. The NULL is placed in a field as a placeholder when no data is entered. TRUE is equal to a value of -1, FALSE is equal to zero (0), and the NULL should equate with zero (0).

A NULL value is treated differently from other values due to its special nature. NULL and 0 cannot be compared because they are not equivalent.
The following example demonstrates how the NULL can be handled when it is encountered in the database.

In the following query…

Read More...Read Less...

Query Fragment

SELECT PC_PARCEL.P_ID, PC_PARCEL.TAX_MAP, PC_ADDRESS.FORMATED_ADDRESS, PC_PARCEL.EFFECTIVE_YEAR, PC_PARCEL.INACTIVE_YEAR

FROM PC_PARCEL left outer join PC_ADDRESS on PC_PARCEL.P_ID=PC_ADDRESS.P_ID AND PC_ADDRESS.LOC_SEQ=0

WHERE (PC_ADDRESS.CIVIC IS NULL OR (PC_ADDRESS.CIVIC>=@pcfhouseno_0 AND PC_ADDRESS.CIVIC<=@pcthouseno_1))
AND (ISNULL(PC_ADDRESS.STREET,”) = ISNULL(@pcstreetname_2PC_ADDRESS.STREET,”))
AND (ISNULL(PC_ADDRESS.SUFFIX,”) = ISNULL(@pcstreettype_0PC_ADDRESS.SUFFIX,”))

In the above query, the SQL ISNULL() function is used, so that when searching specified columns in the table, should a NULL character be encountered, the ISNULL() function will equate it with zero (0). In the above example a modification in the form of double square brackets “[[ ]]”, have been added to the query. This modification has been made for the DAB. When When the DAB encounters double-brackets it will immediately use the data type of the TABLE.COLUMN combination that are within the brackets to declare the leftmost variable that is outside of the brackets, in our case the ISNULL.

B. NULL Characters Alternate Method

As stated in the previous example, the database entry can have three (3) states, TRUE, FALSE, or NULL. A check box in a user interface can have two (2) states, TRUE (-1), or FALSE (0). We would need to code our query to equate a NULL with a zero (0). The following example demonstrates an alternate method of handling the NULL character.

Query Fragment

AND(PC_PARCEL.NON_PARCEL_FLAG=@pcnonparcel_0 OR ( 0=@pcnonparcel_0 AND PC_PARCEL.NON_PARCEL_FLAG IS NULL))

The above statement is written to handle the NULL by equating NON_PARCEL_FLAG with NULL.

The above example statement can also be recreated with the double brackets method. The statement would be as follows:

AND (PC_PARCEL.NON_PARCEL_FLAG=@pcnonparcel_0PC_PARCEL.NON_PARCEL_FLAG,”)

C. Linking Interface Selections

We would like to present the user with a search option that will include inactive parcels. Unfortunately in the database there is no field in the database that will tell you that a parcel is inactive. To be able to link something that does not exist in the database to something that does, and get a TRUE or FALSE value that we can then manipulate.

The PC Inactive Parcel field does not exist in the database but we want the user to use the check box, it will have to be linked to one that is of the same type. i.e. integer, float, text, small int, etc.

Create a dummy condition

This is a condition that will always return a value of TRUE, this also declares a variable based upon a column.

AND (PC_PARCEL.NON_PARCEL_FLAG=@pcinactiveparce_0 OR 1=1)

To declare the pcInactiveParcel object, we will link it to a field that is of the same type as that required by the checkbox, i.e PC_NON_PARCEL_FLAG. The DAB will now be able declare pcInactiveParcel as valid.

The conditions are now set for the two states of the checkbox option…

AND (( 0=@pcinactiveparce_0 AND PC_PARCEL.EFFECTIVE_YEAR<= year id AND

PC_PARCEL.INACTIVE_YEAR > year id )

OR (-1 = @pcinactiveparce_0 ))

If the Include Inactive Parcel option is not checked, i.e. FALSE (0), or Include Inactive Parcel is checked, TRUE(-1).

Following the above steps, we are able to declare a variable based upon a column. Based upon the fact that the variable does not exist, the Data Access Block (DAB) is being directed not to look directly at the column, but rather it is being told what to expect.

Upgrade from Govern 10.8 to OpenForms 6.0

Overview

Configuration Changes

DATABASE Cleanup

GOVERN STRUCTURE

PROFILES

Step by Step

Model Updater

Troubleshooting

Product Resources

System

Database Diagrams

Data Configuration

Technical Information

Upgrade to Govern 6.1

Overview

Before Getting Started

Upgrading

Deployment

Database Verification

System and User Tables

Troubleshooting

PC PARCEL

Unverified Notes

Govern Technical Standards

Overview

What’s New

Database Objects Standards

Table Name

Attribute Name (Fields)

Indexes & Primary Keys

Views

Stored Procedures

System Resources Standards

System Flags

Connection Keys

Batch Programs

Reports

Govern Queries

Module Codes

Upgrade from Govern 5.x to Govern 6.0

Overview

Tips before upgrade

Design Workflow Changes

Database Changes

Legacy Applications

Release 5.1 Applications

Release 5.1 Exceptions

Release 6.0 Applications

Release 6.0 Exceptions

Upgrade Paths to Release 6.0

OPTION 1 – Direct Upgrade

Upgrade Steps for OPTION 1

OPTION 2 – Parallel Install

Upgrade Steps for OPTION 2

Batch Programs

Configuration Re-engineering

Govern 6.0 HYBRID Installation (Govern for Windows)

Requirements

Installation

STEP 1 – System Installation packs

STEP 2 – Create ODBC Drivers Client connections

STEP 3 – Setup Organization Licenses INI files

STEP 4 – Run UPDATA – Database UPGRADE

STEP 5 – Run UPDATA – Create … ATTACH TABLES

STEP 6 – OpenForms Installation

STEP 7- OpenForms Update

Related Links

Advanced SQL Queries

A. Double Brackets Workaround

Query Fragment

B. NULL Characters Alternate Method

Query Fragment

C. Linking Interface Selections

Create a dummy condition

Related Topics