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

100-Queries-(Best Practices for SQL Queries)

Best Practices for SQL Queries

Specify Table and Field Names

When creating SQL queries, it is good practice to specify both the table and the field names in your WHERE query statement.

EXAMPLE 1

The Original query below would function in Govern for Windows, but would result in an error in Govern.NET. In order for it to function
in Govern.NET it is necessary to include the table name in the WHERE statement. This was done in the Corrected example by using a “.” as a
separator.

Read More...

Original

select count(*)
from pm_lk_permit_name,na_company_info
where key_id = permit id
and pm_lk_permit_name.na_id = na_company_info.na_id
and link_type = ‘contr’
and cont_type = ‘SI’
and (in_exp_date < current date or in_exp_date is null)

Corrected

select count(*)
from pm_lk_permit_name,na_company_info
where pm_lk_permit_name.key_id = permit id
and pm_lk_permit_name.na_id = na_company_info.na_id
and pm_lk_permit_name.link_type = ‘contr’
and na_company_info .cont_type = ‘SI’
and (na_company_info.in_exp_date < current date or
na_company_info.in_exp_date is null)

Specifying the table name in the WHERE statement is a good practice to follow when building SQL queries.

EXAMPLE 2

Another example of a query is the following. This is a SELECT query for PRIMARY_LAND

Original
SELECT DISTINCT
I.PRIMARY_LAND
FROM
PC_LEGAL_INFO I LEFT JOIN
PC_AREA A ON A.P_ID = I.P_ID
WHERE
I.P_ID = Parcel ID AND
I.YEAR_ID = Year ID AND
A.FROZEN_ID = Frozen IDCorrected
SELECT PC_LEGAL_INFO.PRIMARY_LAND FROM PC_LEGAL_INFO WHERE
PC_LEGAL_INFO.P_ID = Parcel ID AND PC_LEGAL_INFO.YEAR_ID =
Year ID AND PC_LEGAL_INFO.FROZEN_ID = Frozen ID

Results in the Treeview

Controlling the appearance of Results in the Treeview

One feature of the Govern.NET application is the users ability to control the appearance of results in the Treeview. This feature will appeal to users that perform queries that require that they display a Tax Map as opposed to a Parcel.

FOR EXAMPLE:

In the following query, the Tax Map Number (‘TAX_MAP’) is being replaced with the Roll Number (‘ROLL NO’).

SAMPLE LISTING:

Name: ParcelDesc001
SELECT
CASE
WHEN A.NON_PARCEL_FLAG = -1 AND NON_PARCEL_ID > 0 THEN ‘PREMISE ID: ‘ ||
CAST(A.NON_PARCEL_ID AS VARCHAR(30)) || ‘ ‘ || B.CURRENT_TENANT
WHEN A.NON_PARCEL_FLAG = -1 AND NON_PARCEL_ID IS NULL THEN ‘P ID: ‘ || CAST(A.P_ID
AS VARCHAR(30))
ELSE ‘ROLL NO: ‘ || A.TAX_MAP
END
FROM PC_PARCEL A LEFT JOIN V_PC_OCCUPANT_CURRENT_TENANT B ON A.P_ID = B.P_ID
WHERE A.P_ID = 261362 AND ROWNUM = 1

When the above sample code is incorporated in the query, results with Tax Map numbers will be displayed with the Roll Number.

Related Topics

Query Types
Advanced SQL Queries
Keywords
Best Practices for SQL Queries
Special Cases

100-Queries

 

 

 

100-Queries-(Best Practices for SQL Queries)

 

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-bp-ScheduleReport

Standard Batch Process – Report Scheduler

General

The Report Scheduler is used to schedule a report that is not associated with a batch process but needs to be run on a regular basis. You may, for example, want to run a report every night that does not require any data from a batch process.

  • Process description: Report Scheduler
  • Process name: co_NoProcess

Specification

Prerequisites

  • Batch Process Definition is created and linked to profile
  • SSRS or Crystal Report is configured
  • The same report can be used in multiple batch process definitions

Configuration

Create a batch definition process and select report to be executed

    • When you add the report to the batch process definition, you need to define or update the Export Format Type
    • PDF, CSV, RPT, etc.
  • Add newly created batch process definition to profile

Tools and Tips

Before getting started

  • Take down the report code as it will need to be specified (report selection window does not show description)

 

Troubleshooting

Execute the report stand-alone before setting it up with a batch process definition

 

 

100-bp-ScheduleReport

 

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-bp-TestBatch

Standard Batch Process – Test Batch

General

The Test Batch is used to test the batch execution and configuration, the batch scheduler service, etc.
It creates an Audit Batch ID, generate errors every 1000 records, etc. and records the information in the Audit Batch Table.

  • Process Description: Test Batch Process
  • Process Name: co_TestProcess

Specification

Prerequisites

  • Batch Process Definition is created with the process name
  • Batch Process Definition is linked to a profile

Features

  • Creates error messages for email notification
  • Creates attachment

Tools and Tips

Try first in Govern

  • First use the Test Batch Process in Govern as additional information for errors is provided in the process window (stack trace)

Schedule periodically

  • To validate the service is running

Schedule at specific times

  • After system maintenance, to validate service is up and running
  • After system upgrades, installation, change in reporting or notifications, etc.

Troubleshooting

Any information related to troubleshooting will be presented in this area. Currently there are no troubleshooting entries.

 

 

100-bp-TestBatch

 

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

Encryption Methodology

Version 6.0/ Version 6.1

Overview

A new standard encryption method was implemented in OpenForms 6.1.
For compatibility purposes, changes were made in the Business Entity Designer in order to select which encryption mode to use.
A Correction Script is provided to convert the data.

Encryption Mode

100-Encryption-ui-mode.png

Business Entity Designer Attribute Properties

 

The options include:

Legacy3

  • Compatible with Govern for Windows

Legacy5

  • Compatible with Govern for Windows

TripleDES

  • New Encryption mode available for OpenForms GA 1609 in version 6.0+

None

  • No Encryption – System Default

Configuration

The setup is made by attribute in the Business Entity Designer (BED).
The following are the standard OpenForms business entity attributes encrypted:

ACH Information by Name Entity

NA_ACHINFO

  • BANK_ACCOUNT_NO
  • BANK_TRANSIT_NO

 

Miscellaneous Correction Script
A Miscellaneous Correction Script is provided when executing the GNA – Utility Verify Database.
Upon execution, a warning message will be displayed.
When double-clicking the message, the warning along with an hyperlink to execute the Miscellaneous Script will be presented.
Should be run with care!
See also:

Troubleshooting

The User Password located in the USER MANAGEMENT users is encrypted.
Table USR_USERFILE

  • PWD

Please note that the User Password is not used in Govern OpenForms 6.1 except in certain circumstances:

  • Administrator Login Action Button (To Be Validated)
  • Deployment of Type GOVERN instead of MSAD (Validate: do we encrypt in 6.1 – was encrypted in Security Manager 6.0 and less?)

If the new encryption mode is used, and the circumstances can be met, it is recommended to open and make a modification to the users in order to RE-SAVE the records with the new encryption mode.

 

 

100-encryption

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-install-SMTP4Dev

Test SMTP Server Installation

Overview

For testing purposes, you can install SMTP4Dev, a dummy Simple Mail Transport Protocol (SMTP) server that sits in the system tray and does not deliver the received messages. This Open Source Software is distributed by Code Plex.
To download and get more information, access the Code Plex website smtp4dev.codeplex.com

Downloading

You can download the SMTP4Dev server from Code Plex (Open Source Distributor)
www.smtp4dev.codeplex.com

Harris Govern Employees, can copy from the Shared Program Folder
FSERVERsharedPGSMTP4Dev

Alternatively, when testing on the Harris Govern server, you can use the Harris e-mail Server.
Contact Govern Support for the SMTP server information account information.

Installation and Setup

Read More...

Once downloaded and installed (double click on the documented downloaded), you will see an email icon in the system tray or on your desktop.
RIGHT-CLICK on the icon, and select OPTION in the menu
On the Server Tab, you need to setup:

Port Number

  • Default is 25 but it can be changed if already used.

Listen Interface

  • Select 0.0.0.0 for all or 127.0.0.1 for local

The same information needs to be setup in Govern Administrator, Parameters, General Settings Editor, Filter = General, Section Name = SMTP

FOR DETAIL INFORMATION and print screens, see SMTP4Dev Setup Presentation

See Also

106-(tech)-SMTP Server for Testing Purpose (smtp4).docx

 

 

100-install-SMTP4Dev

 

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-ofr-new

OpenForms Reference – What’s New!

Version 6.0

Overview

This table contains changes made to supported OpenForms Reference items between major releases. Table is entered by date, newest items first.
Click here to return to the OpenForms Reference main page.

 

Date
yyyy/mm/dd…..
Version
. .[6.0.0000]. .
Element
…. (Form, Business Entity, Query, etc.) ………….
……Description…….. …..See Also
2014-08-25 6.0.1408 Business Entity Expression X Expression was changed to

Return to OpenForms Reference

 

 

100-ofr-new

 

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