Web Browser Integration

Web Browser Integration (WBI)

Overview

The OpenForms Application Browser form technology is a form that is based on the Web Browser OpenForms technology. This form can be used as a container for simple, e.g. Web Browser, to complex integrations such as MATIX, a GIS solution from Harris Govern.
An unlimited number of forms can be set up to meet the requirements for displaying spatial, and tabular content of profile users. In addition, an unlimited number of Application Browsers can be configured in a form. Forms can be set up with options that can include the following Key Types, e.g. Parcel ID, Name ID as well as Unformatted Tax Map). Other options include configuration by GIS Server URL, through Synchronization Options, and by Viewing Tabular Data.

Form basic integration, Web Browser Integration (WBI) can be used for adding an interactive website to Govern OpenForms. For example, you could use WBI to add a Geographic Information Services (GIS) web browser interface, such as the Govern GIS Explorer, to a Govern user form and Profile. You could then select records in Govern and view them on the GIS interface. You could also select records on the GIS interface and load them to the Govern Treeview, with the option to set up manual or automatic synchronization between Govern and the website.

The WBI control is added to a custom entity in the Govern OpenForms Designer (OFD). All the configuration is performed in the OFD including any related security settings.

WBI is supported by most websites. It is fully integrated with Govern. It implements predefined commands to add the following functionalities:

  • Loading all records from the Govern treeview to the website
  • Loading the active record in Govern to the website
  • Replacing all records in the Govern treeview with a list provided by the website
  • Replacing the active record in Govern with a list provided by the website

Configuration

Custom entities are used for adding specific predefined controls to a Govern form. In this case, a custom entity is used for adding Web Browser Integration (WBI) functionality. A custom entity cannot stand alone. It needs to be added to an existing form. The form must be added to Profile.
You can add the same custom entity to multiple forms, and add the forms to multiple Profiles, if required.

You need to select a Parent Entity for your new custom entity. Usually, this is the Root Entity.

The following rules apply:

  • The WBI control must be added to a custom entity.
  • The custom entity must be added to an existing form.
  • The form must be added to a Profile.
  • The Dataset Type Code for the Profile must be set to Parcel ID (P_ID) or the Name ID (NA_ID), and must correspond to the value set for the SelectedKeyType.
  • The Dataset Type Code is shown in the following screen shot:

Documentation

Click on the link below to view a .PDF containing details about Web Browser Integration and configuration procedures.
Adding and Configuring WBI

Video Demonstrating Test Tool

A video demonstrating how to test the  integration will be be posted below shortly.

Click here to view the How To demo video

What’s New!

Web Browser Integration (WBI) was introduced in Govern 6.0. As of Govern OpenForms version 6.0.1405, it is used for integrating the Govern GIS Explorer with Govern.

NOTE: The WBI control is used for integrating GIS functionality with Govern as of Govern OpenForms 6.01.1405

Troubleshooting

Any issues that may be related to the Web Browser Integration form will be listed below.

No Access to the Wiki (Log In Error)

Symptom

This error displays a Script Error screen which appears on top of a Wikispaces sign in screen.

Resolution

A solution to resolving this error is to log in to the Wiki prior to launching Govern. When you have successfully logged into the Wiki, start Govern and open the form with the Web Browser Integration form.

Related Topics

 

 

101-std-frm-003-WebBrowserIntegration

 

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 – Database Verification

Database Verification

Version 6.x

Overview

Database Objects are objects that make up a relational database. These are objects that are used to store or reference data. Examples of database objects are tables, columns, indexes, and stored procedures.

This process creates the following required database objects the first time it is run. When the process is repeated, it verifies that the following database objects are present:
The following is a list of some of the Database Objects that are updated:

  • System Stored Procedure
  • Miscellaneous Corrections
  • Tables
  • Deletion of Indexes
  • Columns
  • Indexes
  • USR_KEY_MASTER Stored Procedures
  • New VT_SYSTEM Table Records
  • New VT_USER Table Records
  • Rebuild the VT_USER Table from the VT_USR tables
  • Verifying VT_USR table indexes
  • Functions
  • Views
  • Post Miscellaneous Corrections
  • Post System Stored Procedures

Below are explanations of parts of the process.

 

Read More...

 

Pre Database Verification

Deleting Govern Stored Procedures

This is the step in the process where existing Stored Procedures (stored procs) are deleted

System Stored Procedures

This process creates system stored procedures. These stored procedures are required by the Data Access Block (DAB).
Stored procedures are saved to SY_STORED_PROC_LIST and the parameters used in the search or modification are saved to the SY_STORED_ PROC_PARAM table.
The procedures in SY_STORED_PROC_LIST can begin with the following:

  • s_: Select
  • i_: Insert
  • d_: Delete
  • u_: Update

Examples of parameters stored in SY_STORED_PROC_PRM are:

  • @na_id: This parameter is equal to the current NA_ID
  • @user_id: This parameter is equal to the current user ID
  • @internet_acct: This parameter is equal to the current Internet account

Miscellaneous Corrections

The Post Miscellaneous Corrections process performs the following actions:

  1. Removes the blank spaces from the CODE column, In the VT_USR_ STATE table. All values in this column are state and provincial codes and are two characters in length.
  2. Creates the records, in the VT_SY_ECOMP_FIELDS table, using a stored procedure.
  3. Creates records, under the Validation Table Brule heading, in the VT_SYSTEM table.
  4. Creates records, under the Validation Table LangIdent heading, in the VT_SYSTEM table.
  5. Creates records, under the Web_PayType heading, In the VT_SYSTEM table.
  6. Encrypts the nonencrypted number in the CC_CC_WEB table.
  7. Updates the codes, under the table <month>, in VT_SYSTEM.
  8. Transfers old column data to new ones.

Verifying Database Objects

For tables structure, refer to the ‘MSGDatabaseStructureMods.xml’ file.

Tables

This process will:

  • Create missing tables with action=ADD.
  • Delete existing tables with action=DROP.

Delete Indexes of type

This option allows the deletion of Govern indexes, or All indexes.
Select the Govern option (default) to delete only Govern indexes (Prefix: ‘PK_’ or ‘GV_’).
These indexes are automatically rebuilt. Selecting the All option will delete all indexes including those of user created tables.

Columns

This process will verify the columns.
It will:

  • Create missing columns with action=ADD.
  • Delete existing columns with action=DROP.
  • Ensure that existing columns types are correct

Create missing BE Attributes

In the Columns verification process, it will check for Entities map to the table that the column is been added to.
If those Entities don’t already have an Attribute map to the newly added column, it will create it.

Indexes

This process will verify the indexes.
It will:

  • Create missing indexes with action=ADD.
  • Delete existing indexes with action=DROP.
  • Recreate existing indexes if columns don’t match
  • NEW! Recreate existing indexes if change to clustered; i.e. any existing non-clustered indexes will be recreated if they are changed to clustered in the system files during deployment.

USR_KEY_MASTER Stored Procedures

This process will create the Stored Procedure: ‘sy_Gov_GetAKey’.

New VT_System Table Records

This process will verify VT_System records. Refer to ‘MSGDatabaseStructure_SystemTables.xml‘ for structure.
It will:

  • Create missing VT_System Tables with action=ADD.
  • Create missing VT_System records action=ADD.
  • Delete existing VT_System Tables with action=DROP.
  • Create existing VT_System records action=DROP.
  • Verify existing VT_System for properties changes.
    • If the record needs an update, an error will occurs with the required informations to execute an SQL update manually.

New VT_User Table Records

This process will verify VT_User records. Refer to ‘MSGDatabaseStructure_UserTables.xml‘ for structure.
It will:

  • Create missing VT_User Tables with action=ADD.
  • Create missing VT_User records action=ADD.
  • Delete existing VT_User Tables with action=DROP.
  • Delete existing VT_User records action=DROP.
  • Verify existing VT_User for properties changes.
    • If the record need an update, an error will occurs with the required informations to execute an SQL update manually.

Functions

This process will verify Govern Functions. Refer to sections ‘functions_SQL‘ and ‘functions_Oracle‘ of the ‘MSGDatabaseStructureMods.xml’ file.
It will drop (if already existing) and create the function base on server type.
Views
This process will verify Views. Refer to the ‘ViewsScripts.xml‘ files.
It will:

  • Create missing Views with action=ADD.
  • Delete existing Views with action=DROP.
  • Delete and recreate existing with.

Add validation Tables Poco Mapping View

During the Views verification process it will also add (recreate if existing) views used for mapping to validation table which are NOT included in the viewscripts.

USR_KEY_MASTER IDs Update

This process will verify IDs in table USR_KEY_MASTER. Refer to the ‘UsrKeyMasterIDsReferences.xml‘ files for IDs mapping.
For each IDs, it will:

  • Check the highest number from all References.
  • Update the Database field if the number obtain is higher than the Database one.

If ‘hascheckdigit=”True”‘ the last digit in the number obtain from the reference is remove before the compare is made.

System Data

This process will verify System Data. Refer to the ‘MSGDatabaseStructure_SystemData.xml‘ file.
It will add data (records) into given tables. If there’s a ‘vtuser‘ node it will add an new VT_USER as well.

Post Database Verification

Post Miscellaneous Corrections

This script is a final clean up process for the Miscellaneous Corrections.

Post System Stored Procedures

This is a correction script containing clean up procedures, for Govern Stored Procedures.

Govern Health Check

This process will execute multiple Health Check.

  • Check Countries Correction
  • Bankruptcy Health Check
  • Building Parcel Link Health Check
  • Attribute Encryption Health Check

Related Topics

User Key Dynamics
System Data Dictionary
View Query

 

What’s New!

NOTE: Changes are presented in reverse chronological order; i.e. newer to older.

NEW! Implementation of Clustered Indexes (Release 6.1.1811)

As of Release 6.1.1811, clustered indexes have been implemented on some system tables. These indexes will be recreated during the next Database Verification Process. Due to the nature of the procedure, a significant amount of time will be required to perform the process. The recommendation is that this procedure should be performed over a week-end, or a period of low activity. Although all applications are able to perform without the use of clustered indexes, the implementation of this new methodology can improve overall system performance.

 

Addition of VB6 Fail safe Notification for Verify Database Process

Users that are prompted with a notification when they are upgrading from Govern for Windows to OpenForms need to be made aware that upon running the Verify Database Process, their database will be irreversibly changed. This means that they will not be able to perform a rollback that will allow them to once again run Govern for Windows on their database. As a result of the impact of this action, they must be prompted with a dual confirmation message. The message will remind them of the importance of performing a full backup of their database prior to running the process. They must also confirm that they are about to proceed with an irreversible process. Suitable notification to this effect have been added. Now when the user clicks START [>], and the system performs a compatibility check, they will first be prompted with the following message:

Versions of the application and the database are not compatible.
You must run a Database Verification before continuing. This will update your database to <updateVersionNumber>.

WARNING: Ensure that you have made a backup of this database. This action is irreversible. Do you want to proceed?
Their selection options are YES or NOUpon clicking on YES, they are presented with a confirmation message that reads as follows:WARNING: You have clicked on YES. After running this Verify Database process, you will not be able to perform a rollback, and you will no longer be able to run Govern for VB6 with this database. Click ‘YES’ to proceed.
A click on YES will initiate the process.

RE / PP Tax Conversion Scripts to add required “RE” Cycle Codes

In Govern for Windows a Cycle Code was not mandatory. As a result of the architectural change in Govern for .NET, a Cycle code in Real Property (RE) and Personal Property (PP) is mandatory. The default Cycle Code is “RE”. A script will need to be provided in order to create a Cycle code and change all existing Data to this cycle code. See document below for details on the scripts.
103-ut-005_DB_Verification-RE_PP_Tax_Conversion_Script.pdf

New Process for Addition of System Columns
[Pending validation of release versions] When system columns have been added to the database, during the GNA Verify Database process, after the columns have been added, the process must scan all entities, and add a new attribute in all entities that use tables with added columns.
These changes are available in the following releases:

  • 6.0.1608.x (6.0 Dev.)
  • 6.0.1606.x (6.0 Rel.)
  • 6.1.1608.x (6.1 Dev.)
  • 6.1.1606.x (6.1 Rel.)

Standardized Storage of Boolean Data Types in Govern

In all releases of Govern, Boolean datatypes were stored in the database with three possible values:
FALSE = 0
TRUE = 1 or -1 (dependent on the version of Govern)
Newer tables predominantly used 1, whereas older tables used -1. In accordance with Governs’ ongoing standardisation process henceforth Boolean datatypes will be stored, WITHOUT EXCEPTION, as follows:
FALSE = 0
TRUE = -1
This standard will be carried out for all tables. This standard will be effective as of the following versions:

  • 6.0.1608.0019 (6.0 Dev.)
  • 6.0.1606.0023 (6.0 Rel.)
  • 6.1.1608.0043 (6.1 Dev.)
  • 6.1.1606.0042 (6.1 Rel.)

BA’s and Developers please refer to Confluence for additional details.

New Process in Database Verification Process

[6.0 / 6.1 Multiple Versions]

During the Database Verification process, at the ‘Check Column’ subprocess the application will now manage the description of fields in (Table:SY_DICT_DESC). The process is as follows, the Database Verification process reads the MSGDatabaseStructMods.xml file and reviews the SY_DICT_DESC. Each column is checked in the table to see whether the (ENG / FRA) descriptions exist, and if it needs to create (add) or remove (drop) them. In situations when a complete removal of a table is required, the process will remove any descriptions that are not connected.
Only the following fields are updated

  • LANGUAGE
  • TABLE_NAME
  • FIELD_NAME
  • DESCRIPTION
    • Uses the property ‘description’ limited to 50 characters; all additional characters are truncated
  • DETAIL
    • Uses the property ‘description’

These changes are available in the following releases:

  • 6.0.1603.0410
  • 6.0.1606.0010
  • 6.0.1608.0006
  • 6.1.1603.0481
  • 6.1.1606.0021
  • 6.1.1608.0016

[Release 6.1.1509.117]

Need to perform a verify database process. This is to apply a correction made to change the NULL 0 in (Table: VT_SYSTEM) INVISIBLE.

[Release 6.0.1412]

The following will occur when a new database is created:
.Make sure “Govern Users” role exists, if not create it
.Make sure “govern” User exists, if not create it with the password govern
.Make sure “govern” is in the “Govern Users” role
.Make sure “Govern Users” role has full access to GSM AND GNA

Property to Re-create Indexes for Extended Tables

A new property called hasextendedtables has been added in the Tables section of the MSGDatabaseStructureMods.xml. This property is used to recreate indexes for extended tables like (Table: MA_BUILDINGS) that can support additional tables like MA_BUILDINGS_2 to MA_BUILDINGS_9.

Below is an example of the property in the MA_BUILDINGS table definition in the MSGDatabaseStructureMods.xml file.
<table name=”MA_BUILDINGS” description=”Mass Appraisal Building.” action=”add” gnaaversion=”4.7.3.0″ dbversion=”10.7″ hasextendedtables=“True“>

Currently this property has been added for the following tables:
· MA_BUILDINGS
· MA_LAND
· MA_MRA
· MA_INCOME PP_ASSESSMENT”

6.0 R and 6.1 R and in their development branches( 6.0 dev and 6.1 dev).
This new attribute is available in the following releases:

  • 6.0.1606.x
  • 6.0.1608.x
  • 6.1.1606.x
  • 6.1.1608.x

 

 

 

103-ut-005

 

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

General Connection Parameters

Overview

Connection Pool

A Connection Pool is a collection of database connection objects. In order for a Govern application to communicate with a database, a connection must be established with a connection object from the Connection Pool.

Connection States

Connections can have two (2) states, Active, or Inactive. In the system, connections can exist in two (2) ways Physical and Logical. When created in the pool by a system request, the connection is Physically and Logically active. When a request for the connection to be closed is made by the system, the connection becomes Logically inactive, but Physically it is still active in the Connection Pool. Creation of a new connection is time intensive, therefore a happy medium must be maintained when configuring the parameters for the Connection Pool.

Connection Pool Polling Intervals

The Connection Pool is periodically checked, or Polled for inactive connections. This process is based upon a user defined interval or a built in system rule; inactive physical connections are removed from the connection pool during this set time interval or based upon this system rule.

Oracle Systems

Oracle systems have a polling interval of approximately 3 minutes. Every 3 minutes, the system will review the number of inactive connections in the pool. Based upon the Decrement Pool Size setting, the system will reduce the number of connection by the value, up to the minimum number that is specified in the Minimum Connection Pool Size parameter.

SQL Systems

The polling intervals for connections to SQL databases, is not user configurable. Maintenance of the number of Open connections are handled internally by the system, there are no user configurable parameters.
The parameters that are located in the Connection Key General Parameters Management form are set by default. Unless instructed by MS Govern Technical Support, do not modify these settings as they can impact the overall performance of the application.
To access the Connection Key General Parameters Management form…

  1. In the Govern New Administration (GNA) ribbon, select Utilities (tab) > General Connection Parameters
WARNING: The parameters in this form should only be modified by Administrators, and with the understanding that changes made will be system wide and will affect all users.

Parameters

General group

Connection Key General Management – General group Connection Pool (Minimum Size / Maximum Size)

From the Web, the .NET components access the database through a Connection Pool. Users are able to define the minimum and maximum number of connections for the pool.
• Minimum Connection Pool Size – Enter the minimum number of data connection objects to be established in the pool. (Default = 1)
• Maximum Connection Pool Size – Enter the maximum number of data connection objects that can be allocated in the pool in the Maximum Connection Pool Size field. (Default = 50)

NOTE: Users refer to the About Connection Pool Settings for additional details about Connection Pool Size settings.

Database Cache

The database cache uses system memory to store information that is read from the hard disk. The next time the same information is requested, it is read directly from memory. Increasing cache size can increase system performance, but always ensure that you have sufficient system memory to accommodate your settings. Cache sizes are specified in megabytes (MB)

Cache Size (Minimum Size / Maximum Size / Refresh Rate)

Minimum Cache Size: This is the minimum memory size that the system will allocate to the cache.
Maximum Cache Size: As the cache size is dynamic, this is the maximum memory space that the system will allow the cache to grow to.
Cache Refresh Rate: This is the frequency that the cache is refreshed. The unit is in seconds, therefore to set the rate to 5 minutes, you would enter a value of 300:

300 sec. / 60 sec. = 5 min.

NOTE: The above parameters are automatically set by the system and do not require user modification.

 

Oracle group

The parameters that are found in the Oracle group of the Connection Key General Parameters Management form are used to set the Pool Size increment and Pool Size decrement values. See Oracle Systems for details.
Increment Pool Size : The Pool Size Increment value determines the number of connections that will be automatically created when a request is made to access the database. For example, if a value of three (3) is entered in this parameter, even if a single connection is requested, three connections will be created in the pool.
Decrement Pool Size : The Pool Size Increment value will determine the number of connections that will be closed when a request is made. For example, a value of 5 is entered in this parameter. In a pool of 6 idle connections, when a request to close a single connection is sent, 5 of the 6 idle connections will be closed.

About Connection Pool Settings

The Minimum Connection Pool Size: and Maximum Connection Pool Size: fields are used to determine the number of connections that will be established with the server.
As an example, a user has a minimum setting of five (5) connections, and a maximum setting of ten (10) connections. In the instance of a single query request, all 5 requested connections will be created even if only one connection is required. When the query transaction has been completed, the created connections will be removed during the Connection Pool polling interval. Likewise, if 11 connections are required for a process, since the maximum specified was 10, the system will hold the last process and continuously check until a free connection is available in its assigned pool.

Performance Issues and Connection Pool Settings

In a multiuser environment, performance issues may be observed as a result of connection pool settings. For example, in a 10 user environment, each user has a minimum setting of 5 connections and a maximum setting of 100 connections. Should each user run a single query, there would potentially be 50 connections running simultaneously, i.e. (5 queries x 10 users = 50 connection). Should each user reach the maximum number of connections, 1000 connections would be created.

Connection Pool Settings for Web Sites

Determining the number of potential simultaneous connections is a part of the planning procedure for a Web site. Once the anticipated load on the site has been determined, the minimum size can be set accordingly. Administrators should keep in mind that each site will use one Data Access Block (DAB); therefore the parameter setting should be in reference to the number of connections. In addition the session Timeout settings for the Web server could also be adjusted to ensure that connections are periodically refreshed.
As individual Web site requirements will vary There is no minimum recommended setting for the Minimum Connection Pool Size: parameter for a Web site.

 

Recommended Single User Settings

The following are the recommended settings for the Oracle group for a single user access to the database:

General group

  • Minimum Connection Pool Size: 1
  • Maximum Connection Pool Size: 25
  • Minimum Cache Size: 50
  • Maximum Cache Size: 5000
  • Cache Refresh Rate: 300

Oracle group

  • Pool Size Increment: 1
  • Pool Size Decrement: 3

 

 

103-ut-003

 

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

WM General Link Type Editor

Workflow Management – General Link Type Editor

Version 6.1

Overview

Adding Links to a Workflow

This page describes how to add links using the Workflow Links Controller. This controller adds a central location for all links associated with a workflow. There are two categories for these links:

  • Links to Names
  • Links to Everything Else: This category includes other properties, departments, buildings, workflows, inspections, hearings, miscellaneous billing, self reported tax, and personal property.

This document describes the following topics:
Configuring Links

  • Configuring links in the OpenForms Designer
    Creating Link Types in GNA
  • Using Links in Govern

Documentation

To view this information as a pdf, click on the following link:
Links.pdf
Confluence Technical Document: Workflow Link Type Editor

Configuring Entities for the Links in the OpenForms Designer (OFD)

Link Types are created in GNA. They are made available in Govern through the Workflow Links Controller. You must add and configure this controller to the following entities:

Adding the Workflow Controller for Names

To add the Workflow Links Controller for Names:

  1. Launch the OpenForms Designer (OFD).
  2. Open the required workflow form.
  3. Open the Name Links entity.
  4. Select Custom Control in the Controls explorer.
  5. Drag it to the required position on the entity.
  6. Select the new custom control.
  7. Complete the parameters as describe in the next section:
  8. Click Save.

Configuring the Layout Properties

To configure the Layout properties:

  1. Expand Layout and modify the margins, and the horizontal and vertical alignment if required.
  2. Click the ellipsis button beside the Text style parameter to modify the foreground style of the name control.
    Note: The background color cannot be changed for the custom control.
    The foreground color is applied to the heading, but not the options Only the font size and bold and italic character styles are applied.
    This opens the Expression Selector.
  3. Open the name of the text style between single quotation marks and click OK on the Expression Selector.
    A text style is applied to the Workflow Control for Names in the following screen shot:

Configuring the Controller Properties

To configure the Controller properties:

  1. Expand Misc > Action.
  2. Click the ellipsis button.
    This opens the Extension Selector.
  3. Select MsGovernOpenForms.CustomControls.dll under Assembly.
  4. Select WM_Link_Control under Class.
  5. Click OK on the Extension Selector.

Configuring Additional Properties

You can add expressions to enable the controller and / or to make it visible only under certain conditions. Refer to the Expressions section of the OpenForms Designer documentation for details.

Configuring the Name Links Entity

To configure the Name Links entity, you need to set up the Browse window and add the configuration for the filters.

Setting Up the Browse

To set up the Browse window:

  1. Open the form in the OFD.
  2. Select the tab for Name Links entity.
  3. Click the ellipsis button in the Columns parameter.
    This opens the Select Columns window.
    All attributes are listed under Available.
  4. Select the Description attribute and move it to the Selected column.
  5. Click OK.

Adding Filters to the Name Links Entity

You need to add the following configuration for the filters. The Name Links entity is defined to filter on the Name ID (NA_ID) reference type.
To add the configuration for the filters:

  1. Open the form in the OFD.
  2. Select the tab for Name Links entity.
  3. Expand Misc in the Properties explorer.
  4. Click the ellipsis button in the Configuration parameter.
  5. This opens the Entity Configuration window.
  6. Add the ID Type under Filter by Constants.
  7. Select equal to under Operator.
  8. Select NA_ID under Constant.
  9. Click OK.

Adding the Workflow Controller for Other Links

Other Links refers to all links other than names.
These include

  • Parcels
  • Buildings.

To add the Workflow Links Controller for Other Links:

  1. Launch the OpenForms Designer (OFD).
  2. Open the required workflow form.
  3. Open the Other Links entity.
  4. Follow the remaining steps under Configuring the Name Links Entity

Configuring the Other Links Entity

To configure the Name Links entity, you need to set up the Browse window and add the configuration for the filters.

Setting Up the Browse for Other Links

To set up the Browse, follow the procedure Setting Up the Browse on page 179.

Adding Filters to the Other Links Entity

The procedure is almost the same as Adding Filters to the Name Links Entity on page 180. The difference is in the operator that you select for the Reference ID under constants. For the Other Links select Not equal to.
To add the configuration for the filters:

  1. Open the form in the OFD.
  2. Select the tab for Other Links entity.
  3. Expand Misc in the Properties explorer.
  4. Click the ellipsis button in the Configuration parameter.
  5. This opens the Entity Configuration window.
  6. Add the ID Type under Filter by Constants.
  7. Select equal to under Operator.
  8. Select NA_ID under Constant.
  9. Click OK.

 

Managing Link Types in GNA

Link Types facilitate the management of all the links added to a workflow. This section describes how to view the existing link types and how to create new ones.

Viewing Link Types

By default, Link Types are provided for the following:

  • Names:
  • Applicant
  • Primary Contact
  • Contractor
  • Owner
  • Primary Inspector
  • Other:
  • Building
  • Miscellaneous Billing
  • Parcel Information
  • Self Reported Tax
  • Utility Billing
  • Workflow

You can create all the additional Workflow Link Types that you require.
To view the predefined Link Types:

  1. Launch GNA.
  2. Select Applications Configurations > Workflow Management > Link Types.
  3. By default, link types are listed by code and short description.
  4. Select the link type that you want to view in the tree view.
  5. Click the arrow beside Code to view the Short and Long Descriptions.
  6. Parameters are defined as follows:

Reference Type

The Reference Type drop-down list contains the Govern System IDs (System Validation Table: BRULE – Business Rules). They are selected as follows:

  • Applicant: NA_ID – Name ID
  • Building: BLDG ID – Building ID
  • Primary Contact: NA_ID – Name ID
  • Primary Inspector: NA_ID – Name ID
  • Miscellaneous Billing: MB_ID – Misc. Billing ID
  • Owner: NA_ID – Name ID
  • Parcel Information: P_ID – Parcel ID
  • Personal Property: PP_ID – Personal Property ID
  • Self Reported Tax: ST_ACCT_ID – Self Reported Tax ID
  • Utility Billing: UB_ID – Utility Billing ID
  • Workflow: WM_ID – Workflow ID

Form Name

The Form Name drop-down list contains the Govern user form created in the OpenForms Designer (OFD). They are selected as follows:

  • Applicant: NA 01 – Name & Address
  • Building: MA026 – CAMA Buildings
  • Primary Contact: NA 01 – Name & Address
  • Primary Inspector: NA 01 – Name & Address
  • Miscellaneous Billing: MB01 – Miscellaneous Billing
  • Owner: NA 01 – Name & Address
  • Parcel Information: PC01 – Property Information
  • Personal Property: PP01- Personal Property Information
  • Self Reported Tax: ST007 – Self Reported Tax
  • Utility Billing:
  • Workflow:

Expression for Reference Type Description Header

Click the ellipsis button in this parameter to open the Expression Selector. The header is entered between single quotation marks. This appears above the Search parameter on the Govern user form.
The following screen shot show the parameter for the applicant.

  • Applicant: Name – Applicant
  • Building: Building
  • Primary Contact: Name – Contact
  • Primary Inspector: Name – Inspector
  • Miscellaneous Billing: Misc Billing
  • Owner: Name – Owner
  • Parcel Information: Property Information
  • Personal Property: Personal Property
  • Self Reported Tax: Self Reported Tax
  • Utility Billing: Utility Billing
  • Workflow: Workflow

Name for Reference Type Description Query

The queries must have a column named ID and a column named Description. For the Building, there must be a query name Sequence, as well. The entry point is either the Parcel ID for the workflow record or a linked ID.
All IDs already linked to the workflow are excluded.

Applicant: WMDESCNA – Name Description

For the Name query, the same Name ID (NA_ID) can be displayed multiple times in the same list. For example, the same name could be displayed for the Owner and Applicant. This is not true for any other system IDs.
For the names, the query returns all names

Building: WMDESCBLDG – Building Description

For the building, the query returns all buildings (PC_LK_PARCEL_BLDG. BLDG_ID) linked to the record.

Primary Contact: WMDESCNA – Name Description

For the contact, the name query is used.

Primary Inspector: WMDESCNA – Name Description

For the inspector, the name query is used.

Miscellaneous Billing: WMDESCMB – Misc. Billing Description

For Miscellaneous Billing, the query returns all Miscellaneous Billing records (MB_MASTER.MB_ID) linked to the parcel.

Owner: WMDESCNA – Name Description

For the owner, the name query is used.

Parcel Information: WMDESCPA – Property Description

For the parcel, the query returns all other active (Parcels PC_PARCEL.P_ID) linked to the parcel on which the workflow is based.

Personal Property: WMDESCPP – Personal Property Desc.

For Personal Property, the query returns all Personal Property records (PP_ASSESSMENT.PP_ID) for the Year ID and Frozen ID linked to the parcel.

Self Reported Tax: WMDESCST – SRT Description

For Self Reported Tax, the query returns all Self Reported Tax accounts (ST_MASTER.ST_ACCT_ID) linked to the parcel.

Utility Billing: WMDESCUB – Utility Billing Desc.

For Utility Billing, the query returns all Utility Billing records (UB_MASTER. U_ID) linked to the parcel.

Workflow: WMDESCWM – Workflow Description

For the workflow, the query returns all workflows with the same P_ID linked to the parcel.

Search Group Code

For the defaults, no search group is selected.

Search Style Code

Applicant: WMSEARCHNA – By Name ID
For the Names, the user can search for a name in the database (Search for existing) or create a new name.
If the user selects Search for existing, the Name Search is displayed. A Name ID can be entered.

Building: WMSEARCHBLDG – By Building ID

For the building, the user can search for any building by Building ID.

Primary Contact: WMSEARCHNA – By Name ID

For the contact, the name search is used. The user can search by Name ID.

Primary Inspector: WMSEARCHNA – By Name ID

For the inspector, the name search is used. The user can search by Name ID.

Miscellaneous Billing: WMDESCMB – Misc. Billing Description

For Miscellaneous Billing,.

Owner: WMSEARCHNA – By Name ID

For the owner, the name search is used. The user can search by Name ID.

Parcel Information: WMDESCPA – Property Description

For the parcel, the query returns all other active (Parcels PC_PARCEL.P_ID) linked to the parcel on which the workflow is based.

Personal Property: WMDESCPP – Personal Property Desc.

For Personal Property, the query returns all Personal Property records (PP_ASSESSMENT.PP_ID) for the Year ID and Frozen ID linked to the parcel.

Self Reported Tax: WMDESCST – SRT Description

For Self Reported Tax, the query returns all Self Reported Tax accounts (ST_MASTER.ST_ACCT_ID) linked to the parcel.

Utility Billing: WMDESCUB – Utility Billing Desc.

For Utility Billing, the query returns all Utility Billing records (UB_MASTER. U_ID) linked to the parcel.

Workflow: WMDESCWM – Workflow Description

For the workflow, the query returns all workflows with the same P_ID linked to the parcel.

Used In

The Used In list box of the bottom of the form displays the Workflow Categories that use the current Link Type.

Creating New Link Types

To create a Workflow Link Type:

  1. Launch GNA.
  2. Select Application Configurations > Workflow Management > Link Types.
  3. Do one of the following:
  4. Click Copy to create a new link type from an existing one. You must change the Code and make any modification on the form.
  5. Click New to create a new link type.
  6. Modify the parameters as required.
  7. Click Save.

Adding Link Types to Workflow Kinds and Categories

To add a Link Type to a Workflow Kind and Category:

  1. Launch Govern.
  2. Select Workflow Management > Kinds and Categories.
  3. Select the required Workflow Kind, such as Permits, in the tree view.
  4. Select the Categories tab.
  5. Select the General tab under Categories.
  6. Select the required category in the tree view.
  8. The Link Types that you created are displayed under Supported Link.
  9. Select the link types that are applicable to the category.
  10. Deselect the link types that are not applicable.
  11. Click Save.

Using Link Types in Govern

Overview

By default, Link Types are added to two separate entities on the Workflow form in Govern.
To add a Name Link Type:

  1. Launch Govern.
  2. Open a Profile that contains the Workflow form.
  3. Open the Workflow form.
  4. Select the Name Links entity.
  5. Click New to add a new linked name.
  6. Select the type from the Link Type drop-down list.
  7. All the link types, set up by NA_ID, that you have selected for the Workflow Kind and Category are displayed.
  8. Select a link type from the drop-down list.
    The Create New and Search for existing parameters are displayed.
  9. In addition, the Suggested Links parameter is displayed if a name was already added to the form. The same NA_ID can be added multiple times to a form.
  10. Follow one of the procedures in the following section:
  11. The name and address are added to the Description list.
  12. Click Save.

Adding a New Name and Address Account

You can create a new name and address account for the record. In order to update the record from a direct link, the Name and Address form must be added to the same Profile as the Workflow form.
To create a new Name and Address record:

  1. Follow the procedure for adding a new Name Link up to step 8.
  2. Click Create New.
  3. A new NA_ID is added to the form.
  4. Click Save.
  5. Click the new name link to open the Name and Address form.
  6. Enter the information for the new name account on the Name and Address form.
  7. Click Save on the Name and Address form.

Adding an Existing Name and Address Account

You can link a name from a name and address that is in the Govern database.
To add an existing name and address record:

  1. Follow the procedure for adding a new Name Link up to step 8.
  2. Click Search for existing to add an existing name to the form.
  3. The Name and Address search screen opens.
  4. Enter your search criteria.
  5. Select a name and address account from the list.

The name and address are displayed on the form.

Adding a Name From the Suggested Links

If name accounts are already linked to the Workflow record, they are displayed under Suggested Links. This is shown in the following screen shot:

To add a name from the Suggested Links list:

  1. Follow the procedure for adding a new Name Link up to step 8.
  2. Select a name from the Suggested Links list to add the name and address to the form.
  3. The name and address are added to the Description tree view on the left. They are displayed by link type.
  4. Click Save.

103-wm-parm-401

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

WM Organization Calendar

Workflow Management – Organization Calendar

Version 6.1 – In Development

Overview

Governs’ Organization & Department Calendar provides a way for users to define default scheduling parameters, at the following levels:

  • Organizational, on the Organization level.
  • Departmental, on the Departmental level.
  • Individual, on the Inspector’s Schedule form.
  • Territory, based upon a specific territory.

Calendars may also be specified for a combination of levels, e.g. Department and Inspector, Territory and Inspector, Department and Territory, or all three levels, i.e. Department, Territory and Inspector.
The Organizational Calendars are used to define the general availability, i.e. the days and times that inspectors are available, and the default length of time that the inspections take to perform.
With the understanding that the Inspector’s Schedule is a required form, before you can assign an inspector to an inspection, you will need to create an Inspector’s schedule, i.e. detailing the inspector’s availability, and territory. All inspection calendars and schedules define the:

  • Days that inspections can be performed; such as, Monday to Friday
  • Starting and ending times for performing inspections
  • Number of inspections to be performed each day
  • Minimum duration of an inspection

The Organization Calendar is secured through the Govern Security Manager (SM). See Securing the Organization Calendar in the Security section below.

Read More...

Functionality

User Interface (UI)

The Organization Calendar interface is divided into sections. The parameters in these sections help to define the calendar settings.

Territory

This combo box displays available territories. When a territory is selected and the Inspector parameter is blank, the days off entries will apply to the selected territory. Selecting the all option will apply the dates to all territories. When no value is set in this field, and the Inspector field is blank, all entries will be in reference to the Organization level.

NOTE: When both the Territory and the Inspector parameters are both blank, selected days off will apply to the Organization.

Inspector
This displays the list of inspectors that can be scheduled on the calendar. When a value is selected in this parameter and the Territory parameter is blank all entries will be in reference to the selected Inspector.

NOTE: When both the Inspector and the Territory parameters are both blank, any selected days off will apply to the Organization.

Work Days (group)

This will group will collectively display the selected and configured days of week for the Organization. Click to select each day of the week to perform the required configuration.

NOTE: The check boxes cannot be selected from this view. After a configuration has been made in the Regular Hours and, or, Days Off, the days of the week that have been configured will be checked.

Regular Hours for … (group)
When a day of the week is selected in the Work Days group the day will be appended to the group name. This group allows you to specify the working hour ranges.

Enter a Regular Hour

Click [+] to add a new range; the default range is 8:30 AM to 4:30 PM. The system allows for multiple ranges as long as the times for each day do not overlap.
Removing a Regular Hour
To remove an entered range, click the [x] that appears to the right of the time range.

Adding a Range of Regular Hours

Typically this is where overlapping errors occur. To enter a range of consecutive hours, i.e. a range of 8:00 AM to 10:00 AM, and 10:00 AM to 12:00 PM, this may be entered, but the second range will need to be changed to 10:01 AM to 12:00 PM, a difference of 1 minute. In addition, when specifying hours, the Start time must be earlier than then End time.

Saving Entries

When adding or modifying regular hours, it is not saved on the database directly; you must click Save to commit the entries. After a click on Save, a confirmation window is displayed with a summary of the changes or entries. You will need to click OK to confirm, or Cancel to return to the Calendar. The summary will display all added and removed entries.

Inspection (group)

Duration – Specifies the duration of the inspection; enter the minimum amount of time (in minutes) that an inspection is expected to be performed in. See also Scheduling an Inspection in the Functionality section.
There is an order of precedence for Inspection duration times. The hierarchy is as follows:
Inspectors > Organization > Territory > Department
Duration default levels begin with the Organization and ends with the Inspectors. Any duration set for an inspector will override any durations entered for any of the other levels. This means that if a duration time is entered for an Organization, that time can be overridden by the time entered for the Territory. Likewise the Territory duration time is overridden by the Department, and so on.

NOTE: Inspection time cannot exceed the maximum value of 999.

Days Off (group)
Calendar – This calendar will allow the selection of specific dates and date ranges that are marked as “days off”. These can be holidays or time off. Single days can be selected with a click. The calendar is supported by a Selected Days Off pane on the right hand side of the calendar.

Selected Days Off (pane) – This pane serves to display the details of days off and any accompanying comments; only the first 25 characters of a comment are displayed. A tool tip will also display the full comment. When days are overlapping, the pane will be presented as “dirty” with a red line around the pane. This error will need to be resolved before the save action can be performed. This can be done by
From – This field contains the From date of the day off, or date range. The default start time is 12:00 AM.

To – This field contains the To date of the day off, or date range. The default time is 12:00 AM. The default end time is 11:59 PM.

Partial Days

Partial days can also be specified by modifying the time parameter beside the date or in its own parameter that is displayed with a click on the expander [v] beside the date and time field. Partial day entries that appear in the Selected Days Off pane are presented with a date and time.

NOTE: Half days can also be specified by modifying the time.

Comment – Comments can be added to the Comments field as a means of elaborating on the reason for the day off. These comments will also be displayed in the Selected Days Off pane on the right of the calendar.

NOTE: Only the first 25 characters of the comment are displayed in the Selected Days Off pane. The full comment is displayed in the tool tip.

Determine if an Inspector is Off in a Territory

  1. Select a date on the calendar.
  2. Click to select a territory.
  3. Choose the inspector required from the list.
  4. Look in the Selected Days Off pane.

The days off for the selected inspector will be displayed in the Selected Days Off pane. If there is a day off, it will be displayed in the color that corresponds to the Inspector and Territory. The assigned colors in the legend that the days off appear, will help to interpret availability and in what area.

Specify a Day Off

Mark as Off – Click to mark the selected date or date range as a day, or days off
To set a day as a Day Off…

  1. Click to select the date, or a date range can be selected with a click and drag action.
  2. Click Mark as Off to mark the selected date or date range.

When a day off is marked, it will be added to the Selected Days Off pane, along with any comments.

NOTE: Once created, users cannot modify the time or the associated comment. If a change is required, the time and comment must be reentered.

Canceling a Day Off

To remove a day off entry, locate the line with the entry in the Selected Days Off pane, and click the [x] beside the entry.

Modifying a Day Off

Once a Day Off has been created it cannot be modified. In order to change the entry, the old one must be deleted and replaced with a new entry.

Legend (group)

The legend that is displayed below the Selected Days Off pane displays the color code that is applied to Days Off entries. The colors correspond to the various levels and combinations that the entries for the Organization Calendar can be made at. The levels are as follows:

  • Organization Level
  • Department Level
  • Inspector Level
  • Territory Level
  • Department and Inspector Organization Level
  • Territory and Inspector Level
  • Department and Territory Level
  • Department, Territory and Inspector Level

Selecting a Territory or an Inspector, or a combination of both, will display the text and labels for the days off in the colors represented on the legend.

NOTE: Descriptions that appear in Grey refer to closed Territories.

Viewing Information

When selecting a Territory or Inspector, the days off or regular hours that were set at the Organization level will be visible in the calendar. Likewise when selecting a Territory or Inspector, the days off and regular hours that were set at the Department level will be visible in the calendar.

Opening the Calendar for a Department

To open the Calendar for a specific Workflow Department…
Open the Govern New Administration (GNA)…

  1. On the GNA ribbon select Application Configuration (tab) > Workflow (group) Workflow Management > Departments
  2. In the Departments form, select a Department.
  3. On the Workflow – Department tab, click the View Calendar button.
NOTE: The difference between the Organization Calendar and the Department Calendar is that you are presented with a Calendar that is set to your selected department. The modal window is a constant.

Scheduling an Inspector
When scheduling a selected inspector, if no duration is specified, i.e. value = 0, the Organization default specified in the Duration field will be used for the inspection time. When an entry is made at the Inspector level it will act as an override to the organization level.

Security

Access to the Organization Calendar interface is controlled through the Govern Security Manager (SM). As is standard with the SM access can be granted via Role or User. Refer to the Govern Security Manager user guide for details about securing Govern suite applications with the SM.

NOTE: When secured, the menu option for the Organization Calendar will not be visible on the GNA ribbon in the Workflow group menu.

Securing the Organization Calendar
Access the required node by expanding the following nodes:
Applications > GNA > Application Configurations > Workflow > Workflow Management > Organization Calendar
…drill down into the Workload Manager node and right click on the Organization Calendar node:

NOTE: The Refresh or Synchronize All processes are not required in GSM, they will be performed by the Govern New Administration (GNA).

The Refresh or the Synchronize All processes are not required in the GSM, these will be performed by the GNA.

See Also

Department Calendar

Workflow Management

Click here to return to the main workflow form

 

 

103-wm-parm-504

 

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

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