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.

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

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.

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

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

Govern Impact Assessment

Impact Assessment

Overview

This page is a summary list of changes that occurred in a given version of the product that have an impact on new deployment installation or upgrades.

NOTE: For System Options and/or 3rd Party integrations, it is important to contact R&D as it may not be released at the same time as the module it complements.

Govern OpenForms Version 6

Read More...Read Less...

Version	Detail…	System Requirements
6.1		Design for MS SQL Server 2014 (to be validated)
6.1		Detail VT_System and VT_User tables will be removed. All the tables are available in VT_SYSTEM and VT_USER. The VT_System table definition
6.0		Table Change Event: New record locking and notification feature. When upgrading, the first time a ‘Verify Database Process’ is run, a script is executed to create a job that requires SysAdmin rights (read-write) in SQL Server. It can be executed manually by the database SA. Script name: CreateCleanupJobForRecentTableChanges. Click here for the MS SQL SERVER SCRIPT commands to execute.
6.0?	setup	Batch Process Setup Attachment Folders Access: For each batch definition, you can now specify the path and folder where the attachments (logs & output files) are to be copied. IMPORTANT: These folders need to be shared with Read/Write access granted to the users that will run the batch process AND to the server that hosts the Batch Scheduler Service. (To grant access to a server, use the format SERVERNAME$)
6.0	sysreq	Twain for imaging is no longer supported supported by Windows. Replaced by WIA (Windows Image Acquisition).
6.0		Batch Processing Scheduler Windows Service (BSS) is now updated automatically. However, ONLY one (1) deployment connection key can be setup per machine. Appender Service is deprecated.

		Database Resources and Data Model
6.1		In prior Govern for Windows release, because of the use of MS Access there was a limitation on the number of attributes in a table. For this reason, multiple instances of the table were created (ex: LAND, LAND-2, LAND-3…) as well as an additional INFO table (Land_Info, Bldg_Info, etc.) The following INFO tables have been merged. We will continue to create additional instances, but only after 1000 fields versus 256 as it was before,
6.1		BOECK Appraisal Methodology no longer supported. Table MA_PARM_BOECK is dropped from the standards.
6.1		Simulation Code Removed
6.0		Batch_ID was added to CC_MASTER
6.1		PC_PARCEL NON_PARCEL_FLAG and VIRTUAL PARCEL changed to Non Nullable
6.0		USR KEY MASTER Changes (impact to be verified)
6.0.1703		CREATE_DATE and CREATE_UID was added to the USR_MESSAGE (Global Messages)
		Query Tool
6.1		Because of the changes in the VT system and user table, many if not all queries will need to be reviewed if not rewritten.

		Mass Appraisal
6.1		Formulas and Logical Expressions are no longer supported. Replaced by expressions.
6,1		Multiple Assessment Rate (unavailable in 6.1)
6.1		Property Distance Weight (unavailable in 6.1)
6.1		Simulation code is remove. With 6.1 simulation will be done via the EMT tool.
6.1		Site records are now mandatory for all appraisal components (land, building, misc. structures, income, personal property, MRA). The site description is setup in the query MASITELIST and will most likely be the concatenation of other fields. Split merge will group all the components by site description. For instance Site Description = Class + Liability + Exemption
6.1		Total Override feature and new field for override amount added to land, land adjustments, bldg, misc. structures, income, mra, and personal property. Note: The reports will need to be changed because the total value if overridden will be located in TOTAL_VALUE_OVERRIDE instead of TOTAL_VALUE
6.1		MA APPRAISERS not available in 6.1.1511 See roadmap
6.1		Miscellaneous Structure not available in 6.1.1511 See roadmap
6.1		CAMA Exemptions not available in 6.1.1511 See roadmap
6.1		Copy MA Tables to Next Year not available in 6.1.1511 See roadmap
6.1		The Is Required option in mass appraisal tables will now use an expression. A new field was created to facilitate the conversion. [MA_TABLES.IS_REQUIRED_EXPRESSION]
6.1		Rename Sequence (Land, Building, MRA ..) not available in 6.1. See Roadmap
		MA Income Simulation Table is no longer supported. Income method has changed.
6.1		Neighborhood Table can be set to work with jurisdictions. In lookups, the system will only show the neighborhoods for the property jurisdiction. See What’s New
		Computation Sequences were changed from a small integer to a long integer. Will be formatted with 6 digits on the forms 999999.
6.1		Copy Land Record to Parcel or Dataset. It now copies the Lot Size, Lot Units Type, Units, and Unit Type where before it did not.
6.1		Formatting of MA PARM Table Values was added for the land, site, mra (adjustments) and building (elements). See What’s New and GNA Value Formatting Editor
6.1		PID (Current_PID) was added to the MA_BUILDING table. This impacts splits and merge as well as parcel duplication. A corrective script will be available the first time the Verify Database is run.

		Tax Billing and Assessment
6.1.1611		TIF implementation (New Tables and Columns)
6.1.1611		Levies and Exemptions now use Expressions. [6.1] The TIF levy parameter will always be auto-created in code. The user will not be able to see the TIF levy parameter on GNA. The only way to view a TIF levy parameter is to go in the database with the following query: selectfrom TX_PARM_LEVY where IS_TIF_LEVY =-1selectfrom TX_PARM_EXEMPT where IS_TIF_EXEMPTION =-1

		Name and Address (ACH Processing)
6.0.1609	ar-wnew	ACH processing available in this version. A new field was added for the Transit and Bank Sequence Description, Field sizes have changed for encryption NA_ACH_INFO.ACH_SEQ (new field) NA_ACH_INFO.BANK_ACCOUNT_NO (new field lenght = 44) NA_ACH_INFO.BANK_TRANSIT_NO (new field length = 32)
6.0.1609		New Standard System Code in MAILING INDEX TYPE
		Cash Collection
6.0.1603		Cash Collection module is available on OpenForms.
6.0		PAYOR_NAME added to CC_MASTER (was stored previously in CC_MASTER_NOTES)
6.0		Proportional Distribution is no longer available (Deprecated)
6.0		USR Table CC_TYPE transferred to SY TABLE CC_TYPE
6.0		CC_ID is now a Govern ID
6.0		Batch_ID was added to AR BATCH INFO
6.0		New Log files for Payment Processors WEB and Point of Sale See 317-CSI Pay

		Standards Forms and Features
6.1.1503		New Roll Forward Exclusions Function
6.1		Name Belongs To Group Security does is not functional in 6.1 (see TFS 15286-15473)
5.1		My workload deprecated until the new Land Management Module is released (see 101-std-fea-019)

		GNA Editors
6.1		External Command Editor no longer supports Formulas and Logical Expressions. The commands will need to be recreated using the Expression Editor.
6.1		Formulas and Logical Expressions are no longer supported. Replaced by Expressions.

		GIS Integration
6.0.1511		The GIS integration now uses the Standard Application Integration Browser (frm-005). GNA GIS Parameters, no longer needed, was removed. GNA GIS Synchronizing Tool was modified to use a GUID format for MATIX Integration.
6.0.1511		Tool Tips are not available in version 1511. GNA Tool Tips, no longer needed, was removed.
6.0		PC Lien Certificate default version The lien certificate function is not part of tax title but an extract function used for reporting all balances due for a given property. This function is not on the roadmap because it is customized for each customers or State, and the default version in VB6 was not used.

6.1		Miscellaneous Billing
6.1.1606		General Availability of OpenForms Module
		Changes were made to the Database Structure to support year base parameters and new parameter tables were added (MB_PARM_CATEGORY and MB_PARM_ITEM)
		Mailing Index is now used and created automatically

		Workflow Management (Previously Permits & Inspections)
6.1.1609	wm-wnew	Many changes were made to the Data model. Please review the Workflow Management Install page for a checklist to review.
6.1.1609		USR_KEY_MASTER is replaced by USR_KEY_DYNAMICS (to support the Mobile option)

Version 6.0

Considered an hybrid version, it uses Govern release 10.8 Daemon for Mass Appraisal Computation.

Version	Detail	System Requirements
	—	See 6.1/6.0 above
		Database Resources and Data Model
6.0	gna	Initial DB creation and tables, attributes and index updates performed by GNA Verify Database function
6.0	dbchg	See Obsolete Fields (database changes)
6.0	fea-017	Std-Fea What’s new User Audit Trail Tables (3 new tables)
6.0	dbchg	User Added Field Definition table change. See module SRT, PP, …to be validated
6.0	dbstd	New Standard type of View
6.0		MA_BLDG_AREA removed and a new table added

		Core Standards and Business Rules
6.0.1503		Roll Forward Exclusion – Configuration Screen is now available. Roll Forward will be modified at a later time. See Govern Admin Application Parameters.
		Formulas and Logical Expressions in 6.0 (only) – Need to add the NO LOCK statement
		Datasets, PC EXTERNAL, new Synchronize function

		Property Control
6.0		Table PC_SALES is no longer used. MA_SALES will be used

		Accounts Receivable Security
6.0.1503		Security for AR transaction was setup in GSM in prior releases. In version 6.0, the security setup is made in OFD.
6.0.1503	na-wnew	ACH information centralized in NA NAMES and removed from the tax module assessment tables
		A/R Cycles are now Mandatory for Real Estate, Personal Property, Boat, Aircraft and Motor Vehicle (need to validate – see roadmap)

		Real Property

		Personal Property
6.0.1503	pp-wnew	New Version 6 Module
		A/R Cycle is now mandatory

		Self Reported Business Tax
6.0.1609	tech doc setup	Changes to support Estimated Filings (Garnishments) New column NAICS created in ST_MASTER New table ST_ESTIMATE New form ST008
6.0.1606		Corporate Account Table created ST_CORP_ACCOUNT
6.0.1503	st-wnew	New Version 6 Module (see Upgrade technical Information)
6.0.1502	st-wnew	Exemptions linked to levies are no longer available


		Mass Appraisal
6.0.1503		MA_BLDG_AREA was transferred to MA_BLDG_AREA_YEAR. Year of the area was added. The data will be converted in the verify database, but not the reports. The Daemon was changed for Clay County and SAMA. More information will be provided on how to implement the new feature.
6.0.1503	gna	Verify Database Process NOTE: One of the recently updated scripts in the Verify Database Process will require SysAdmin rights in SQL Server. Script Name: CreateCleanupJobForRecentTableChanges:

System Options and 3rd Party

System Options and 3rd Party Integration may or may not be released at the same time as the module. Please check with R&D.

Version ………	Detail …….	System Option
6.0.1503		e-Government General Availability release
6.0.1503		Mobile Option General Availability release for MA, SRT and RE (to validate)
		3rd Party Integration
6.0.	301-apex	APEX available. See Building Drawing
6.0.1503		Melissa Integration (to be verified)
6.0.1503

NOTE: 3rd Party upgrades to new versions is not part of the default roadmap. These upgrades are normally driven by customer project or general functionality needs.
Please contact R&D and make sure to review system (new 3rd party version to be installed or …) and functionality requirements with customer as this may change.

Govern for Windows to OpenForms

Major technology changes from Govern for Windows to OpenForms. Some features no longer applies, some were changed, some will be available in a future release, etc.
For the complete report prepared by R&D, please click Feature Compare VB6 to V6 (Last Updated April 7th). As the software evolves, the additional changes will be added here:

100-ImpactAssmt

(0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.

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

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

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

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

Best Practices for SQL Queries

Specify Table and Field Names

EXAMPLE 1

EXAMPLE 2

Results in the Treeview

Controlling the appearance of Results in the Treeview

FOR EXAMPLE:

SAMPLE LISTING:

Related Topics

Standard Batch Process – Report Scheduler

General

Specification

Configuration

Tools and Tips

Troubleshooting

Standard Batch Process – Test Batch

General

Specification

Prerequisites

Features

Tools and Tips

Troubleshooting

Impact Assessment

Overview

Govern OpenForms Version 6

System Options and 3rd Party

Govern for Windows to OpenForms

Encryption Methodology

Overview

Encryption Mode

Configuration

ACH Information by Name Entity

Troubleshooting