202-all-mgovern

 mGovern – Your Mobile Solution

Overview

The mGovern Mobile Solution provides a secure, user-friendly interface for transferring property records from the office server to a mobile device. It also allows for updating records in the field over a wireless connection or when disconnected from the office server. Records are kept up to date and synchronized on both the Mobile device and the Office server.
For more information, see technical info or education plan.

Configuration

The mGovern solution offers easy, secure configuration and installation in any Govern environment .
To configure the mGovern mobile solution:

  • Create a database on each mobile device. The Govern structure is copied to these databases when the application is installed.
  • Create a temporary database on a server. This is used for the deployment and initialization only.
  • Deploy the mGovern solution using Deploy EZ as you would any application in the Govern Product Suite, version 5.1.
  • The Govern database is copied to the mGovern database during deployment.
  • The user transfers records directly from the source database on the office server to the mGovern database when required.

 

NOTE: To improve the user experience, special forms can be designed to better fit the mobile device display characteristics.

 

Read More...

 

User Interface

The Govern Mobile UI provides user forms with the same look-and-feel and features as the Govern for .NET application.
The following are available in the mobile application:

  • All the user forms available in Govern.NET
  • All the functionality available in Govern.NET
  • Same user form layout and icons
  • Same Govern Ribbon and Status Bar
  • Dataset TreeView, Forms and Reports Explorer
  • Predefined Searches

Process Schema

Click below to view/download the mGovern process flowchart.
mGovern 6.0_01.pdf

Documentation

Click below to view/download the mGovern Release 6.0 User Guide
202-all-mgovern[guide]-(6.0).pdf

Schema – Govern 6.0 Mobile Solution
Schema – mGovern 6.0 Process Flow

Technical

See [6.0] Mobile Technical Page

Education

Also available, Mobile 6.0 Hands-on Installation Course Education Agenda and Plan page.
Class 2-201.202-Mobile

See Also

Initialize Mobile Database
Govern Mobile Technology

Govern Administrator (GNA) System Wiki Map

 

 

202-all-mgovern

 

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 Mobile Technology

Govern Mobile Technology

See General Process Schema, Govern Mobile Schema.

Specification & Features

  • Check-in / Check-out process to protect data integrity
  • Synchronizes data on demand
  • Mobile device works in connected and disconnected mode (visual identification of mode)
  • Same user *forms, profiles and functionality are available on mobile device
  • Search on line server, retrieve named datasets…
  • Mobile Option available for the following module applications:
    • Appraisal, Real Property Tax, Business Tax (Self Reported Tax & Licensing)
    • Land Management Permits & Inspections (OpenForms version 6.1 and greater)
  • System and module application parameters can be copied by year range
*NOTE: New profiles and lighter versions of forms may be created due to limited screen space and requirements to create a better user experience. Furthermore, search and embedded queries should be limited, unused data removed, and so on.

Unsupported Mobile Features

The following section will contain features that are not supported in the Govern Mobile Application.

Alternate Connection Keys

In environments where there are multiple databases, the Govern New Administration (GNA) can access alternate databases by creating secondary and tertiary connection keys. Users should note that Govern Mobile does NOT support the use of Alternate Connection Keys. Unlike the GNA, Govern mobile was designed to function with a single connection key.

Read More...

 

Requirements

Mobile Device Requirements

  • Windows operating system (Laptop, Tablet, Mobile device…)
  • MS SQL Server and/or MS SQL Server Express
  • Zip program
  • Govern license to operate
  • Govern deployment (binaries, system resources, custom controls, govern)
  • Govern installation pack (Crystal Report)

Installation Requirements

  • Admin rights to local machine (laptop, tablet)
  • Admin rights to the source database server
  • Ability to set user rights on the databases (set user Govern as Sys Admin)
  • Rights to modify database physical location if in Program Files (.mdf & log)
  • Rights to the shared folder used for the mobile initialization and transfer of info (detached db, OFresources, etc.)

Optional Mobile Device Features

Although the following device features are not essential for functioning of Govern Mobile Technology, they will enhance the user experience of the Mobile device.

  • Embedded GPS / 4G-LTE Mobile network connectivity

Mobile Initialization Process

  • Executed on the SOURCE Server to create a mobile mirror package of the deployment with the:
    • Detached database structure (empty) and selected dataset information (.mdf)
    • The system resources (reports, tables, etc.) copied
    • The general and selected module parameters and tables for the given years….
  • The package is zipped and copied to the SHARED FOLDER, used in turn as input by the mobile devices
  • Add Custom Tables to the new deployment. See What’s New section of Initialize Mobile Database.
  • As needed populate the Database Objects Exclusion table with db objects that are not required in the mobile (Remote) database.
NOTE: Process needs to be executed on the initial setup of the device or when the following changes occur in the SOURCE environment:

Changes to the Database Structure (tables and fields), Product Resources (views, forms, tables, reports…)

Installation

Step by Step – See Mobile Setup Steps in Govern Deployment
On the server ….

  1. Update the SOURCE DEPLOYMENT (i.e download binaries and deploy new version on server, run database verification, etc.) ……. [PROD]
  2. Create a SHARED FOLDER on a location accessible from both the database server and each of the mobile devices
  3. Verify/Set the SOURCE SERVER DATABASE [db_PROD] — check path for database and log
  4. Create a MIRROR DATABASE on the SOURCE DB SERVER (can be on a different server if proper security access) ….. [db_PROD_MOBILE]
    • Setup USER Govern with system admin rights
    • Setup Physical Location paths for exports and logs
  5. Create a Mobile DEPLOYMENT [PROD_MOBILE]
  6. Create a Mobile CONNECTION KEY with LOCALHOST specified as the SERVER [Localhost]
  7. Run Initialize Database process in GNA

On the mobile…

  1. On the MOBILE device DATABASE SERVER, create a new DATABASE with the same name as the MIRROR [db_PROD_MOBILE]
    • Setup USER Govern with system admin rights
    • Setup Physical Location paths for exports and logs
  2. Deploy GOVERN MOBILE
    • Resources, System, Custom Control and Govern V6
  3. Synchronize Mobile data

Troubleshooting

The following tips and troubleshooting information can be helpful to users that are configuring an mGovern – Mobile deployment.

Quick Tips

  • Lots of database and file manipulations across servers over the network…. The first time …. Small is beautiful!
  • 95% of problems are related to security!!!
  • The Microsoft Event Viewer should be used to monitor and help detect security or configuration problems
  • Connection keys are loaded at start up so ensure that you exit GNA after having created a key!
  • Allow the deployment of Govern v6 to a Mobile deployment; found under the Applications tab in DeployEZ
  • Problems with checked out parcels can be resolved with the By-Pass Checkout option in the Govern Security Manager (GSM)
    NOTE: This option is only available to users with Super User administration rights.
  • Might have error the first time deployment is executed on mobile device (because of synchronization).
    Close and restart Govern
  • External systems look up should be removed
  • Synchronization is set to every 5-10 seconds
  • Program files should not be used for any installation in general because of special security and folder management
  • Ensure that Mobile Devices do not share the same name as a network server (i.e. server names are unique).

Issues with Empty Search Combo Boxes…

When a Mobile deployment is remote in the field, i.e. away from local the home database that it synchronizes with, combo boxes that are populated by (Table: NA_NAMES) or (Table: PC_ADDRESS) search queries could result in empty combo boxes. This behavior has been observed with queries that may use the SQL SELECT DISTINCT statement:
Ex.: SELECT DISTINCT <columnName> FROM NA_NAMES; or SELECT DISTINCT <columnName> FROM PC_ADDRESS;
These types of queries are valid, the queries are by design intended to search on the Parent or Local Database. The understanding is that the Local but should be executed when the mobile deployment is connected to the home/main database.
Explanation: The combos should be populated by selecting the Search on Server option to search the Parent/Home database while the Mobile deployment is docked at the office, and the Search on Server option is available. When the deployment is on the road, the child/remote database becomes the Local database. The search combo boxes will now be populated with the required data records.

TIP: As a Best Practice for successful use of mGovern while in Remote Mode, i.e. away from the office, users should include as a part of their planning schedule, a process to pre-load searches with the names and addresses of locations that will be visited. This should be done while at the office. When a search is performed with the Search on Server option is selected, the combo’s will be populated by pre-fetching the parcels from the LOCAL/Home DB.

What’s New

NEW! Check Out parcels are flagged as ReadOnly for all users

The Check In and Check Out features are options that are available for the Govern Mobile application. When a user checks out parcels, they are flagged as ReadOnly for all users except Admin/SuperUsers users, and the user that checked out the parcels. This ReadOnly status can be set as a default to extend to the user that checks out the parcels as well. Click to read the documentation (202-mobile-fea-005-Mobile-ReadOnly-Checked-Out-parcels-DOC.pdf).

 

 

202-tech-mobile

 

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

103-sy-008

Govern Standard Feature – User System Settings Action Button

Overview

The following USER or CASHIER registry parameters are accessible on the active OpenForms by Registry SECTION. The following sections are available to use.

103-cc-parm-User-ui-button.png

103-cc-parm-User-ui-form.png
Click to enlarge

Cash Collection Cashier

The following parameters are available by User ID for the Cash Collection
Section name: [Cash Collection Cashier]
  • Auto-Collapse MCR and Payment Distribution by A/R Detail (Class Code)
  • Show only Accounts with Balance
  • Year to Collect

To be added (see roadmap)

  • Default Real Estate Up to Installment
  • Default Self Reported Tax Period
  • Default Search Style
  • Default Payment Collection Type (cctype) – check, credit …) – CURRENTLY setup in General User Parameters.

Matix Integration

The following parameters are available by User ID to change Application Browser Defaults.

 

 

103-sy-008

 

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

 

GNA – Queries

SQL Syntax Rules for GNA

Release 6.0 | Release 6.1

Govern Data Access Block (DAB)

The Data Access Block or DAB has several functions in the Govern system. One of these functions is to act as the intermediary between the .NET applications and the database. SQL queries that are used by Govern must go through the DAB. While SQL can be flexible with its syntax, due to its many functions, the DAB must be stricter with syntax. In short what may work in SQL, may have to be modified for the DAB. In fact some of the rules that the DAB requires you to follow are good practises for SQL as well.

The following guidelines and examples have been collected to increase your level of success with Govern SQL queries.

Basic SQL Query Guidelines

A. Field in Table is Always on the Left Hand Side

When creating your query statement, the field that you are referencing in the table should always be on the left hand side (LHS), and the Dynamic Search object should always be on the right hand side (RHS).

Read More...

For Example:

In the following SQL statement …

NOT VALID: WHERE @pmnumber_1=PM_MASTER.PM_NUMBER

NOTE: The above statement is valid in SQL, but it will fail in Govern. The Data Access Block (DAB) will not interpret it correctly.

Should be written as…

VALID: WHERE PM_MASTER.PM_NUMBER=@pmnumber_1

B. No Spaces Allowed after Logical Operators

OPERATORS
Symbol Description
= Equal To
<> Not Equal To
> Greater Than
< Less Than
>= Greater Than or Equal To
<= Less Than or Equal To

 

For Example:

NOT VALID: WHERE PC_PARCEL.PID1 > PC_PARCEL.ID2

should be written as…

VALID: WHERE PC_PARCEL.PID1>PC_PARCEL.ID2

C. Space Before and After LIKE Operator

The LIKE pattern matching operator is used to select only rows that are “like” what you specify. When using it ensure that there is a space before and a space after the operator.

For Example:

NOT VALID: WHERE PC_PARCEL.PID1LIKEPC_PARCEL.P_ID

should be written as…

VALID: WHERE PC_PARCEL.PID1 LIKE PC_PARCEL.P_ID

D. Always Specify Tables and Fields in Statements

When writing statements, always specify Tables then Fields (TABLE.FIELD). This applies even in cases where you are referring to a single table and there would be no ambiguity.

For Example:

The following statement…

SELECT NA_ID, INDEX, DESC FROM NA_NAMES WHERE NA_ID=@nanameid_0

is the same as ….

SELECT NA_NAMES.NA_ID, NA_NAMES.INDEX, NA_NAMES.DESC FROM NA_NAMES WHERE NA_NAMES.NA_ID=@nanameid_0

In the first statement we are only specifying the columns in the NA_NAMES table. This would not pose as a problem if we are only dealing with one table. Realistically, we will often have to interact with multiple tables, and many tables have the same column names; this would create an ambiguity. The system would not know which table is being referred to.

Release 6.0

What’s New

Related current changes to the working of Queries in Release 6.0 will be indicated below.

Release 6.1

What’s New

The following are current changes to the working of Queries in Release 6.1.

Nomenclature

As of Release 6.1, it is mandatory that query names must begin with a letter. [Release 6.1.1506.82]

Related Topics

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

Code Keyword Description
ar_id Account Receivable ID Unique identification number of the current Account Receivable record
key_counter Activity ID Identification number of the current Activity record
ac_id Aircraft ID Unique identification number of the current Aircraft Excise Tax record
br_id Bankruptcy ID Identification number of the current Bankruptcy record
bt_id Boat ID Unique identification number of the current Boat Excise Tax record
bldg_id Building ID Identification number of the current Building
bldg_seq Building Sequence Sequence number of the current Building
cc_id Cash Collection ID Identification number of the current Cash Collection record
co_id Complaint ID Identification number of the current Complaint record
*date Current Date The Current Date
dept Department The Department code
frozen_id Frozen ID Identification number of the current Frozen record
haz_id Hazard ID Identification number of the current Hazard record
h_id Hearing ID Identification number of the current Hearing record
in_id Inspection ID Identification number of the current Inspection record
land_id Land ID Unique identification number of the current Land
mb_id Misc. Billing ID Identification number of the current Miscellaneous Billing account
misc_id Miscelleaneous ID Identification number of the current Miscellaneous Billing account
mv_id Motor Vehicule ID Identification number of the current Motor Vehicle Account
na_id Name ID Unique identification number of the current Name
of_id Offence ID Unique identification number of the current Offense record
p_id Parcel ID Unique identification number of the current parcel
pm_id Permit ID Unique identification number of the current Building Permit, Electrical Permit, General Permit, Plumbing Permit, Permit to Name, Animal License, Business License, License to Name, Approval, Bond, Decision, Prosecution or Appeal record
pp_id Personal Property ID Identification number of the current Personal Property account
pp_det_id PP Detail ID Unique identification number of the current Personal Property Item
folio_id Project Folio ID Identification number of the current Project Folio
prj_id Project ID Identification number of the current Project record
tax_id Real Estate ID Identification number of the current Real Estate Tax record
sale_id Sale ID Identification number of the current Sale record
st_acct_id Self Reported Tax Acct ID Identification number of the current Self Reported Tax Account record
st_id Self Reported Tax ID Identification number of the current Self Reported Tax record
si_id Site ID Identification number of the current Site
sa_id Special Assessment ID Identification number of the current Special Assessment record
tax_map Tax Map Number Tax Map Number of the current record
usr_id User ID Unique identification number of the current user
ub_id Utility Billing ID Unique identification number of the current Utility Billing account
year_id Year ID Year identification of the current record

 

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

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

Std. Integrity Business Rules

Govern Standard Integrity Business Rules (To be or not to be!)

Overview

The following integrity rules ensure that record dependencies are maintained when inactivating or deleting a record to ensure no orphan records are created.
These rules are referred to as Govern’s “To be, or not to be” business rules.

  • Inactive parcels are grayed out in the tree view and the records are read-only.
  • A effective and Inactive year is used in Govern to determine if a property or building is active.
  • In some modules (Self Reported business tax and Personal Property tax…) it is possible to temporarily deactivate an account

Property Control

Parcels (Property Info)

The property master information record PC_PARCEL is not year based.

  • It is considered ACTIVE when the EFFECTIVE YEAR is equal to or less than the current year.
  • It is considered INACTIVE when the INACTIVE YEAR is equal to or less than the current year.

If a parcel was created or inactivated in the middle of a role year (splits merges, new subdivision), then the dates are used and verified.

  • It is considered ACTIVE when the EFFECTIVE YEAR = or < than the current year AND the current date is equal or greater than the EFFECTIVE DATE.
  • It is considered INACTIVE when the INACTIVE YEAR = or < than the current year AND the current date is equal or greater than the INACTIVE DATE. (validate if inactive year must be year + 1 of the inactive date)
  • When a parcel is inactive all the records in the different tables must be inactivated for the current AND the future years.
  • All tables with frozen_id and year_id are set to inactive by setting their frozen id to -32766.
  • All link tables with EFFECTIVE_YEAR, INACTIVE_YEAR, FROM_YEAR, END_YEAR, EFFECTIVE_DATE, INACTIVE_DATE, FROM_DATE or END_DATE must also be inactivated

Parcel Linking

Parcels can be linked together using the parcel linking function PC_PARCEL_LINKS, generally used for condos.

  • A property is considered part of the link if its parcel linking effective date is less than or equal to the current date and the effective date is greater than the current date
  • If a property that is the MASTER record of a link is inactivated, than all the records in the link are inactivated

Buildings

The physical buildings are linked to the property using PC_LK_PARCEL_BLDG records that are not year based.

  • It is considered ACTIVE if the property is ACTIVE
  • It is considered ACTIVE when the EFFECTIVE YEAR is equal to or less than the current year.
  • It is considered INACTIVE if the property is INACTIVE
  • It is considered INACTIVE when when the INACTIVE YEAR = or < than the current year AND the current date is equal or greater than the INACTIVE DATE (same validation)

If a building is inactivated, then

  • Mass Appraisal Building Information MA_BUILDINGS is inactivated (-32766)
  • Mass Appraisal Miscellaneous Structures linked to a MA_BUILDINGS (to be verified)

Building Linking

Buildings can be linked together PC_LK_BLDG_TO_BLDG using the Building Linking function

  • The same rules apply as Parcel Linking

Names

Name records NA_NAMES cannot be deleted if in used:

  • Owner
  • Occupant
  • Releated Name
  • Grantor and Grantee

Property Locations

  • Property Location records PC_LOCATION cannot be deleted if a building is linked to it.

Mass Appraisal

Appraisal records are year and frozen id based.

MA Property Information

The Mass Appraisal Property Information MA_MASTER must exist for any computation to take place.

  • The record cannot be deleted if any appraisal components are linked to it
  • If an appraisal record is created in land, building, site, MRA, income, personal property, miscellaneous structure, the MA MASTER will be created for the specific year and frozen id if it does not exists. Note: The Valuation Method will be set to Cost (1).

MA Sites

All Mass Appraisal components are linked to a site record MA_SITE

  • Still Active Site Record Cannot be Deleted! if a site record is used by another mass appraisal component, it cannot be deleted.

 

Linked to INCOME or MRA

  • Land records linked to an active Income or MRA record cannot be deleted
  • Building records linked to an active Income or MRA record cannot be deleted

Tables Considered

The following tables are considered when applying these rules: (to be reviewed)
Refer to each module section for the list of tables applicable.

Property Control (PC)

  • PC_PARCEL
  • PC_LEGAL_INFO
  • PC_AREA
  • PC_PARCEL_LINKS
  • PC_LK_PARCEL_BLDG
  • PC_LK_BLDG_TO_BLDG

 

Real Property Tax (TX)

  • TX_EXEMPTIONS
  • TX_LEVY_MASTER
  • TX_LK_LEVY_EXEMPT
  • TX_QC_REP_FISCALE
  • TX_RE_ASSESSMENT

 

Mass Appraisal (MA)

  • MA_CA_VAL_TRACKING
  • MA_INCOME
  • MA_INC_INFO
  • MA_INC_SIMULATION
  • MA_LAND
  • MA_LD_INFO
  • MA_LK_EXEMPTIONS
  • MA_LK_INC_FIELD
  • MA_MASTER
  • MA_MISC_STRUCTURES
  • MA_MRA
  • MA_OVERRIDE
  • MA_SALE_SAVED_P
  • MA_SITE
  • MA_VALUES_TABLE

 

Personal Property (PP)

An account can be temporarily inactivated (to be validated)

  • PP_ASSESSMENT
  • PP_ASSESSMENT_DET
  • PP_AUDIT_INFO
  • PP_EXEMPTIONS
  • PP_LEVY_MASTER
  • PP_LK_LEVY_EXEMPT
  • PP_TEMPLATE_AS

 

100-std-brules

 

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-Installation-FromScratch

Govern Installation from Scratch

Version 6.0 | Version 6.1

Overview

This section covers the steps and the best practices when installing 6.0 from scratch.
For upgrades or updates see 100-Upgrade where you will find tools, tips and training material to help with the upgrade.
Return to the Main Installation page 100-Install

Before Getting Started
Database Server (optional)

  • Install and/or start MS SQL SERVER 2014
  • Create Database / Restore Databases for upgrades
  • Roles and Security

Step by Step

OpenForms Initial Installation from a blank database.

  1. Create Govern Database(s) – make sure to add Govern as the owner of the database
  2. Install DeployEZ
  3. Create Deployment and Connexion key (note you will need to supply a Serial Number License Key)
  4. Install GNA
  5. GNA Run Database Verification (twice – first time prepares what it needs)
  6. GNA Set Organization parameters & SY REGISTRY, Create department, Create new sysadmin user
  7. GNA Import (EMT) System Queries & Tables (DynamicSearch.xml) and basic forms (FormReference.xml)
  8. GNA Create a report
  9. GNA Create a batch process
  10. GNA Create a profile
    • Set Forms, Batch programs, A/R allowed, Reports…
  11. GSM Create Roles
  12. GSM Synchronize
  13. GSM Setup Access rights (Apps, menu, profile)
  14. In SQL, make sure to enter 0 or 1 in USR_KEY_MASTER (until 1504)

See Also
100-Standards
100-Technical Requirements

 

100-Installation-FromScratch

 

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