WM – General Parameters

Workflow Management – General Parameters

Version 6.1

Overview

System Registry Parameters

From Govern Administrator (GNA), select Parameters, General Settings Editor

  • Section Name = Workflow Management
  • Year Filter = Not applicable

The following system registry parameters are available for the module:
Inspection Form

  • The inspection form is called automatically from different areas of the system. When this is the case, the form selected here will be displayed.

Template Form

  • Workflow models are created dynamically. In addition, if a form template is entered here, a workflow form for the model will be created.

 

System User Registry

The following system registry parameters are available for the module users. Each user can have predefined values. An action button can be added to any of the workflow form for direct access.
From Govern Administrator (GNA), select Parameters, User Registry Editor

  • Section Name = Workflow Management
  • Registry Key Type = User

Autocollapse Completed Steps

  • When checked, the steps completed will auto collapse in order to facilitate scrolling and viewing the results of large workflows.

Completed Activity Color

  • Used to select for the user the color to display completed activities

Initiated Activity Color

  • Used to select for the user the color to display activities that are initialized

 

Reference

 

 

103-wm-parm-101

 

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-UT-006

Initialize Mobile Database

Version 6.0 / Version 6.1

Overview

The Initialize Mobile Database process is executed on the source server to create a copy, i.e. a Mobile mirror package of the deployment. The process creates an empty, detached database structure, and select dataset information. Copies of the system resources, i.e. reports, tables, and so on are also copied. In addition, general and selected module parameters and tables for given years are created. This process is executed at the initial setup of the Mobile device, or when changes occur in the source database. Changes include database structure, e.g. tables and fields, product resources, i.e. Views, Forms, tables, reports, and so on.

NOTE: Running this process on a database that is being used will result in the destination database being overwritten by the source. In addition, the size of some of the tables being processed can be a factor in the processing time.

What’s New!

Exclude Database Objects during Initialization (Manual process)

The Database Objects exclusion feature is an enhancement intended for the Govern Mobile application. This enhancement will allow users to manage the initialization of database objects, i.e. tables, functions, or views. In order to implement this enhancement, the (Table: SY_MOBILE_DB_OBJ_EXCLUSION) has been added to Govern Reference. This table will contain all object names that should be excluded during the GNA Initialize Mobile Database process. Refer to Mobile Configuration Editor for object exclusion through Govern UI.

GNA User Interface Changes

As a result of the added functionality and enhancements to the Govern Mobile application, changes have been made to the Govern New Administration (GNA) user interface. Changes are as follows; the Initialize Mobile Database process icon has been moved from the Database Utilities group. A new Mobile group is now present on the right hand side of the Import / Export Tools group. It is under this new Mobile group that mobile related functions will be found. Currently there are two mobile related options, the new Mobile Configuration, and the new location for the Initialize Mobile Database process.

NOTE: The functions within the Mobile group can be found using the expander arrowhead beside the Mobile Tools icon label.

Functionality

NEW! This new feature targets the Govern Mobile application in that it provides users with the ability to exclude database objects, i.e. a Table, a View, or a Function. It is not necessary to specify which of these three objects is contained in the table as the names of the content of the table are unique.
, and update user tables, during the Initialize Mobile Database, and the Get Latest process. For this implementation two (2) new tables have been added to the Govern reference; SY_MOBILE_TABLE and SY_MOBILE_COLUMN
This table has only one column called NAME. This column contains the name of the database object that is to be excluded.

WARNING: Administrators using this feature should take care when manually populating their source database.

Table Details
The (Table: SY_MOBILE_DB_OBJ_EXCLUSION) is a table with only one column. The column name is NAME. Refer to the Mobile – Database Objects Exclusion Technical Documentation for technical descriptions of this table.

Requirements

Prior to using this feature, run the verify database process Database Verification from the GNA ribbon to ensure that the source database has been updated with required tables.

The Process

1 – Populate the Table Manually

In order for the synchronization process to occur, users must populate the SY_MOBILE_DB_OBJ_EXCLUSION table manually. A recommended method is through Microsoft SQL Server Management Studio (MSQL MS). To populate the table through SQL Management Studio, use a Copy and Paste process to manually copy the information to the table.
(Table: SY_MOBILE_DB_OBJ_EXCLUSION).

2 – Verify the Content of the Database

After the table has been populated, finalize the changes. Verify that the copied tables are the ones that are to be excluded. All records that now appear in the table will be excluded, i.e. not copied to during the Initialize Mobile Database process.
SELECT*
FROM SY_MOBILE_DB_OBJ_EXCLUSION;

3 – Run the Initialize Mobile Database Process

Once the Source database table has been populated with the database objects that are required for exclusion, run the Initialize Mobile Database process in GNA.

NOTE: Read the confirmation that appears prior to the process being run.

 

TIP: Upon completion, as this is a manual process, always perform a random verification to ensure that the objects in the list of excluded objects table (Table: SY_MOBILE_DB_OBJ_EXCLUSION), do not appear in the destination table.

Tables

The following is the table, or list of tables, that were modified or created to implement this feature.

  • SY_MOBILE_DB_OBJ_EXCLUSION

Add and Update User tables during Initialization and Get Latest

NEW! The new feature in the Govern Mobile application is the ability to add, and update user tables, during the Initialize Mobile Database, and the Get Latest process. For this implementation two (2) new tables have been added to the Govern reference; SY_MOBILE_TABLE and SY_MOBILE_COLUMN
NOTE: The system still maintains a fixed list of system tables through the MobileTables.xml XML file, only user defined custom tables are added to the new SY_MOBILE_TABLE, and SY_MOBILE_COLUMN tables.

WARNING: Administrators using this feature should take care when manually populating their Source database

Table Details

Below are the columns within the data tables. Refer to the Technical Documentation for further descriptions of the tables.
SY_MOBILE_TABLE – Contains custom tables that can be used in data extraction

COLUMN_NAME DATA_TYPE TYPE_NAME PRECISION LENGTH NULLABLE COLUMN_DEF SQL_DATA_TYPE
NAME 12 varchar 30 30 0 NULL 12
READ_ONLY 5 smallint 5 2 0 (‘0’) 5
DOWNLOAD_ALL 5 smallint 5 2 0 (‘0’) 5
KEY_MASTER 12 varchar 30 30 1 NULL 12
IS_KEY_DYNAMIC 5 smallint 5 2 0 (‘0’) 5
KEY_COLUMN 12 varchar 30 30 1 NULL 12
OPTIONAL 5 smallint 5 2 0 (‘0’) 5
UPLOAD_ONLY 5 smallint 5 2 0 (‘0’) 5

SY_MOBILE_COLUMN – Contains custom columns that can be used in data extraction

COLUMN_NAME DATA_TYPE TYPE_NAME PRECISION LENGTH NULLABLE COLUMN_DEF SQL_DATA_TYPE
TABLE_NAME 12 varchar 30 30 0 NULL 12
NAME 12 varchar 30 30 0 NULL 12
REFERENCES 12 varchar 61 61 0 NULL 12
CONDITION -1 text 2147483647 2147483647 1 NULL -1
ONE_TO_MANY 5 smallint 5 2 0 (‘0’) 5
IGNORE 5 smallint 5 2 0 (‘0’) 5
READ_ONLY 5 smallint 5 2 0 (‘0’) 5

Requirements

Prior to using this feature, run the database verification process to ensure that the source database has been updated with the latest tables.

NOTE: In the current implementation of this feature, any required user tables must be specified manually.

Populating the Tables Manually

As indicated, in order for the synchronization process to occur with user defined tables, users must populate the SY_MOBILE_TABLE manually. A recommended method is through Microsoft SQL Server Management Studio (MS SQL MS). To populate the table through SQL Management Studio, use an INSERT statement to copy the required tables into (Table: SY_MOBILE_TABLE).

1 – Determine the Structure of the Tables

exec sp_columns SY_MOBILE_TABLE;
exec sp_columns SY_MOBILE_COLUMN;

The results will display the table columns that help when designing the action query to populate the tables. For example, an INSERT statement can be as follows…

2 – Design and run the INSERT Query

INSERTINTO SY_MOBILE_TABLE
VALUES (‘USR_MYTABLENAME01′,”,”,’USR_MYTABLENAME_COL1’,”,”,”,”);

Where USR_MYTABLENAME01 is the value entered in the NAME column, and so on. Insert all user tables that are required in both SY_MOBILE tables.

3 – Verify the INSERT Query

The INSERT action can be verified with a SELECT statement. As an example, the result of the following SELECT query will help to confirm that data has been inserted into the table.
SELECT*
FROM SY_MOBILE_TABLE;

…repeat for the SY_MOBILE_COLUMN table.

3 – Run Initialize Mobile Database Process

Once the Source database tables have been populated with required user tables, run the Initialize Mobile Database process in GNA when creating a new mobile deployment.

OR

3 – Synchronize on the Mobile Application

When the mobile application is running, and the Status indicates Connected, it will verify that a change has been made to the source database; the Get Latest icon will be active. Click Get Latest on the Mobile ribbon. During the Get Latest process, the Source and Mobile database will synchronize with any values found in the tables that are listed (Table: SY_MOBILE_TABLE).
For additional information on the process, refer to the Mobile Initialization section of the 202-[tech]-Mobile page on the Govern Wiki.

TIP: Upon completion, as this is a manual process, always perform a random verification to ensure that the requested user tables appearing in (Table: SY_MOBILE_TABLE, SY_MOBILE_COLUMN), appear in the destination table.

Tables

The following is the table, or list of tables, that were modified or created to implement this feature.

  • SY_MOBILE_COLUMN
  • SY_MOBILE_TABLE

See Also

Govern Mobile Technology

*

 

 

103-ut-006

 

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

User Interface

User Interface

Overview

The Govern New Administration (GNA) user interface was redesigned for Release 6.0 and upwards. The interface uses ribbons for quick access to the required areas of the application. Forms are accessible through tabs on the ribbons. Presentation of forms can be changed from the standard multi-window forms that can be overlapped and staggered, to a tabbed layout.

GNA Tools and Utilities are arranged under the tabs that logically groups them by their function. With the exception of the File tab GNA tools are found under one of the following:

  • Options
  • System Parameters
  • Application Configurations
  • Editors
  • Utilities
  • Windows

Change Interface Language

Language

The Govern New Administration (GNA) interface language can be changed as needed; currently the two languages supported are English and French.
To change the interface language:
Select Options > Language > (Select the language of choice)
Additional languages will be supported in future releases.

NOTE: The default language of Govern is determined by the administrator when the deployment is set up in the Deploy EZ™ Publisher.
Text that appears in the GNA interface can be modified with the Govern Resource Editor. Refer to the Resource File Editor

Modify User Interface Language

Under the Options tab are the interface language choices. Selection options are Mutually Exclusive, i.e. when an option has been selected, that option will no longer be displayed as a selection option.

Tile Horizontally / Vertically

Tiling open windows for You can keep all three tools open on your desktop and arrange them to optimize your available space. Windows can be tiled horizontally or vertically by selecting any of the options under the Windows menu in the Govern System Config & Admin application.

Layout (Standard or Tabbed)

The Layout option will control the presentation of any open windows. As with other option selections, they are mutually exclusive. When an option is selected it will not be available in the menu list. For example, when the Standard option is selected, only the Tabbed option will be available in the menu.

 

 

103-UI-All

 

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-UI-001

GNA Standard User Interface (UI)

The following are the standard UI for the Govern New Administration (GNA). These interface features include Editors, Configuration screens, command buttons, parameters, drop down menus (combo boxes), and so on.

Introduction

The Govern New Administration (GNA) user interface was redesigned for Release 6.0 and upwards. The interface uses ribbons for quick access to the required areas of the application. Forms are now accessible through tabs on the ribbons. Presentation of forms can be changed from the standard Multi-window forms, overlapped and staggered, to a tabbed layout. GNA applications are arranged under the tabs that logically groups them by their function. With the exception of the File tab, GNA applications are found under one of the following tabs:

  • Options
  • System Parameters
  • Applications Configurations
  • Editors
  • Utilities
  • Windows
  • Help

Overview

The Editors tab contains the forms and editors required to create and edit components that are used within the Govern suite of application. These components can be OpenForm Profiles, Field Masks, Constant Values, SQL Queries, Formulas, Expressions, SQL Queries, and Validation Tables to name a few.

Standard Editors

The majority of editors within the Govern New Administration (GNA) are referred to as “standard” because of the common features in their interfaces.
GNA Standard editors can be found by selecting Editors (tab) > Editors (group) > “Name of the Editor”

Command Buttons (Common)

New: Click New to create a new System Validation Table. NOTE: When you click on New, the button changes to Cancel ; this will allow you to cancel the creation of the current record. The Cancel button is present until the new record is saved.
Save: Click Save to save any changes to an existing validation table or to save a new table.
Delete: Click to select an existing Validation table from the List of Validation Table list on the left hand column; click Delete to delete the table.

Codes: Click Codes to access the code editor for the validation table.

NOTE: With Release 6.1 a Standard Template(s) has been introduced in GNA. This template will be applied for most of the Editors and Tables needed in the Mass Appraisal module.

Interface Exceptions

Below are featured interface exceptions.

Mass Appraisal – Multiple Years with Link MA Group Option

The following explains how to navigate multiple years with the new Link MA Group option.
– COMING – The number involves and rules.

Related Topics

Govern New Administration (GNA)

 

 

103-ui-001

 

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 – Report Editor

GNA Report Editor

Overview

The Report Parameters Editor form is used to configure reports on an individual basis. These reports display query results found in the fields of tables within the data source.
Reports are given access through the default connection key. If required, they may also be configured using an alternate connection key. As long as the alternate connection key has been defined in the Connection Key Management form, it will be available in the Alternate Connection Key list. See Alternate Connection Key Properties group for details about alternate connection keys. In Release 6.0 of GNA, there is enhanced support for SQL Server Reporting Services (SSRS)™. SSRS reports and Crystal Reports™ are configured in the OpenForms General Settings form, see OpenForms™ General Settings for details.

Intelligent Scanning in Reports Editor

There is an underlying intelligence in the functioning of the Reports editor. Both SQL Server Reporting Service (SSRS) and Crystal Reports reports are read, and the data sources are scanned.
Connection options to the database are by default specified as the current connection. If required, secondary sources can be selected from a list of alternate Connection Keys. During the initial scanning phase, if a report is determined to be invalid, i.e. incompatible, a warning is displayed in the form of a window with a list of the offending reports.

NOTE: When there is no backwards compatibility with a report, the default connection setting will be used.

Details of the Report Scanning Process
When the Report Editor is launched, each report that is selected from the List of Reports list is scanned. The report connection key is tested. When the system encounters either a Crystal Report or an SSRS report that is not associated with a Govern connection key, the system will ask to associate the report with…:

  • The current Connection Key (Default) OR
  • The user can see the path to the data source, and may select a connection key from the list of available Alternate Connection Keys.

During the “Database Verification” process…

After performing an update / general maintenance, or defining database connections, running the Database Verification process is recommended as it will update the database for access by Govern applications.When this process is run in GNA, during the Misc. Corrections phase a script performs the following:

  • Conversion of Alternate Connection Key information (i.e. server, database names, etc.) into the Connection Key in the new table.

The following four (4) fields will be set to NULL:

  • [DTSRC_SERVER]
  • [DTSRC_DBNAME]
  • [DTSRC_UID]
  • [DTSRC_PASSW]

Note: In the SY_REGISTRY screen, four key names were removed,

  • [DTSRC_SERVER]
  • [DTSRC_DBNAME]
  • [DTSRC_UID]

Record Set Key: This option provides the ability to run the report by dataset, e.g. current P_ID, current dataset, or database. In the drop down menu list, select the primary key that will be used by this report, otherwise the user will not be prompted to select a dataset for the report.

NOTE: A Record Set Key should be specified.

The report dataset will be filtered with a list of values for the selected key.
Example: SELECT * FROM pc_parcel WHERE p_id = ‘123’ OR p_id = ‘456’ etc.

Report Criteria: Click Report Criteria (A) to display the editor. The Report Criteria Editor is used to configure prompts for reports that require user input. See Report Criteria Editor on page 85 for details on configuring prompts.

The report dataset will be filtered with a unique value for the selected keys.

For Example…
SELECT * FROM pc_parcel WHERE p_id = ‘123’

Criteria Key group

Add Criteria Key: Click Add Criteria Key to display the criteria key list; select one or more criteria to be added, click OK or Cancel.
Remove Criteria Key: Select a criteria key from the Criteria Key list and click Remove Criteria Key to remove it from the list.

Alternate Connection Key Properties group

Although database connection parameters are set in the Govern DeployEZ™, they can be overridden on a report by report basis. If required, each report can be configured with an alternate connection key.

NOTE: All settings made in this section override the current, default, connection key. Users should ensure that the alternate connection
key required has been entered in the Connection Key Management form. See The Connection Key Management form.

Data Source: This is the path to the server that the report will be accessing.
Alternate Connection Key: Select an alternate Connection Key from the list.

Report Group

This parameter contains the Report Grouping for the Report Explorer in Govern.
Upper/Lower Level: Select configure these parameters to indicate the location of the report in the Treeview pane in Govern.
For Example…
When the following report, Mass App.- Inventory Report is configured to appear in the following Report Group; Upper Level: List & Reports, and Lower Level: CAMA. In Govern, the report will appear in the List & Report upper folder (A) and CAMA lower folder (B):

See Also

Report Criteria Editor

 

 

103-sy-006

 

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 – General Connection Parameters

GNA General Connection Parameters

Overview

In the General System Parameters form, you are presented with database details about the currently selected connection key, configuration parameters for controlling how users access the application, and synchronization and refresh parameters for mobile installations.

General Connection Parameters

Database Default Server Type group

In the Database Default Server Type group (A) you will see the database server type of the currently selected connection key.

NOTE: This area is informational and cannot be modified.

Specifying Connection Key Source Folder at Startup

As a time saver users starting up GNA can specify a connection key source folder; i.e. a location for the list of Connection Keys. This feature is useful in multiple database environments where users need to frequently switch between databases. By default GNA will maintain a lock on the location of the last selected Connection Key. The file that the GNA will obtain its list of connection keys from is (File: GovernDABConfig.xml)

Read More...

Database Connection Key parameters

The list of Connection Keys are obtained from the GovernDABConfig.xml file. If an administrator would like to provide an alternate GovernDABConfig.xml file containing Connection Keys, this information can be specified.

Definition File Folder: Type in a new path to the connection keys definition folder, i.e. location of the GovernDABConfig.xml file, or click “…” to browse for a folder.

Organization Parameters

In the Govern New Administration (GNA), it is possible to modify the parameters that were entered at installation. In the Organization Parameters group, you can modify the Organization name.

Organization Name: Enter your organization name. This is the name that appears in the GovernNetConfig.xml document.

User Name Prefix: The User Name Prefix field is used to enter a text string that is added to the beginning of the User ID. This feature allows for backwards compatibility with Govern for Windows. The specified prefix is concatenated with the user name, encrypted, and stored. Since it is appended to the password after a user enters their assigned password, they are not aware of it. The use of this method means that users will never see their real database UserID.

User Name Prefix: If required, enter a prefix into this optional field.

To specify an Organization Name and a User Name prefix…

  1. Select System Parameters > General Installation Parameters…
  2. In the Organization Parameters group, enter an Organization name, and a user name prefix.
  3. Click Save to confirm your changes.

The user must explicitly enable editing for each parcel: When selected the user must click on the Edit icon in the Govern.NET Dataset Treeview before editing a record. By default this option is disabled.

NOTE: This option is designed to minimize errors when selecting a record to edit in Govern. When a record is selected in the Dataset Treeview, a conscious effort must be made to click the Click to Edit icon a second time, and unlock the record for editing.

Mobile Device Parameters

Mobile Device Connection Check Trigger (in ms): After installing a mobile deployment, one of its functions is to continually check the connection to the master database, and compare and update changes to the data.

Connection Check Trigger (in ms): The Connection Check Trigger value determines the length of the interval, in milliseconds, between each check to verify the availability of the connection to the main database. The default value is 1000 milliseconds.

Synchronization Interval (in ms): The value in this field is the interval that will be used to force a synchronization of data between the mobile database and the main system database when Govern.NET’s automatic synchronization option is selected. This option is set on the mobile devices Govern.NET install.

NOTE: For details about Mobile Device configuration, refer to the Govern Mobile user guide.

 

 

103-sy-002

 

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

ST – Category Form Setup

Category Form Setup

Overview

Use the Self Reported Business Tax Categories form to create categories for self reported tax. You can add penalties and discounts to the categories. Then, set up Fields and Levies for each category.
The field setup function for the filings is very similar to prior OpenForms versions (backward compatible to Govern for Windows) with the exception of the method to add the fields to the WEB when using the e-Government System option.

NOTE: eGovernment version 6.0.1503 is required

What’s New

Available in Release 6.0.1511 and later

“Is Read Only” flag for Self Reported Business Tax Form Parameters

(Perform the “Verify Database Process” in the Govern New Administration (GNA) prior to use.)
In the form for “Categories Form Setup” in the GNA, options are available to restrict user access to the parameters that are presented on the OpenForm in the application. Administrators that need to present parameters with read only information can use the Is read Only flag. This flag allows administrators to let users view a parameter but not change it on the eGov.

Preview

This option is available for use in the OpenForm Settings and the Web Site Settings form. When set, “real time” preview can be observed under the Preview and Preview Web tabs. Previously, by default a parameter was always editable.

Technical Information

Changes to the Database Structure

The following modifications were made to the Reference file MSGDatabaseStructureMods.xml for (Table: ST_PARM_FIELDS):

  • IS_READONLY
  • IS_READONLY_WB

For example:
<column name=”IS_READONLY” type=”smallint” length=”0″ nonull=”False” action=”add” gnaaversion=”6.0.0.0″ description=”Hide Field” />
<column name=”IS_READONLY_WB” type=”smallint” length=”0″ nonull=”False” action=”add” gnaaversion=”6.0.0.0″ description=”Hide Field for Web” />

Conversion

When performing an ST conversion, prior to setting up users to begin, you must also set up a Department in the ST_MASTER form. Unless a Department has been set up data will not appear in the ST Master form.

NOTE: Users of the eGovern that are configuring eRemittance (i.e. Online Self Reported Business Tax submissions), will need to create a duplicate of any forms that will be accessed. Creating this form will allow them to specify which fields are to be made available online.

See Also

What’s New in the eGovern Public Self Service Portal
Form Setup Section Manual 5.1

 

 

103-st-parm-FormSetup

 

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