Batch Process – Import Name to Email
Overview
In Development
101-std-bp-005
In Development
101-std-bp-005
Version 6.0 and 6.1
Version 6.0 and 6.1
Read More... Version 6.0 Version 6.0.1412 Version 6.0 Version 6.0 – see User Audit for more info [std-fea-017]
PC Parcel Version 6.1 PC Sales Version 6.0 For the specification document, click on Appraisal Detail Specification for listing. Version 6.1 Version 6.1 Version 6.1 Income changes to support new calculation method and configuration Available in GA Release 6.1.1606 In prior versions, only the AR Class Code was used for the invoice and invoice detail. To simplify data entry and offer more flexibility, the following tables were added. New Database Fields When the fields for ST forms are created, the following USR_FIELDS_XXXXX tables, are no longer used. New Field added in ST_MASTER New Tables added for Estimated Filings New Table added for Corporate Account For ACH processing and field encryption, the following changes have been made: Version 6.0 Tables Removed from versions: 6.0.1411.0106 and 6.1.1411.0106 Tables Removed from versions: 6.0.1411.0017 and 6.1.1411.0021 Release 5.x Version 5.x See Prior Database Changes (ref. v6.1.1508) Govern Database Diagrams – Refer to the List of Changed Tables section 100-ChangesDBStructure Userfile
User Profiles
Roll Forward Exclusion Tables
User Audit Trail New Tables (3)
NOTE: The legacy table USR_AUDIT_TRAIL will be kept for modules running in prior releases, but developers should note the new modifications and table structures impact for custom processes.
Property Control (PC)
Version 6.0
Accounts Receivable & Cash Collection (CC)
Payer Name
Mass Appraisal (MA)
Building Changes
Site Changes
Site changes to support new override methodology
Income Changes
Income changes to support new override methodology
Miscellaneous Billing
To offer more flexibility, the misc. billing parameters are now year base.
As such the YEAR_ID was added to the following tables:
Self Reported Business Tax (ST)
NOTE:The data in the above have been copied to (Table: ST_PARM_CATEG)
NOTE: This field is now a Standard System Field and may need to be converted if it was created as an Added Field.
Name and Address (NA)
OpenForms Tables
1. OF_SE_APP_TYPE replaced by an object in memory
2. OF_DE_MODELCONTENT was used only for MOD
3. OF_MD_UPDATER was used only for MOD
4. OF_LK_PROFILE_OF1 was used only for MOD to establish the link with a profile.
The tables defined in MSGDatanaseStructMods.xml (so also in OPENFORMS_REFERENCE_60):
Related Topics
Version 6.0 | Version 6.1 (In Development)
The KEY TYPE is used to identify USER and MACHINE registry parameters.
Key Type 1 = User ID registry, – IDENTIFICATION Code = User Id
Key Type 2= Machine registry – IDENTIFICATION Code = Machine Name
Payment Processors not updated
| Registry Type | Section Name | Key Name | Key Type | Identification CD | Key Value | Encrypted | Action | Notes |
| Cash Collection Cashier | Cash Collection Cashier | auto collapse MCR Group and AR Class Distribution | 1 | user id | 0 or 1 | 0 | ||
| Cash Collection Cashier | Cash Collection Cashier | search style | 1 | userid | Style lookup | 0 | Default lookup group in Cash Collection Form VERIFY conditions | |
| Cash Collection Cashier | Cash Collection Cashier | real estate up to installment | 1 | userid | 1,2,3,4,t | 0 | ||
| Cash Collection Cashier | Cash Collection Cashier | self reported tax breakdown by periods | 1 | userid | 0 or 1 | 0 | ||
| Cash Collection Cashier | Cash Collection Cashier | show only accounts by balance | 1 | userid | 0 or 1 | 0 | A/R with a zero balance will not be displayed in the grid | |
| Cash Collection Cashier | Cash Collection Cashier | year to collect | 1 | userid | YEAR, 0 or null | 0 | If a year is entered, only A/R for this year will be displayed | |
| default collection type | Missing (credit card, cash, etc.) | |||||||
| Cash Collection Parameters | Cash Collection | credit card type | 1 | userid | Table Lookup | will need to use the new table CC TYPE | ||
| Cash Collection Parameters | Govern | allow Misc. Cash Receipts | 1 | |||||
| Govern | allow xxx Data Entry (Fee, Demand, Discount…) | 1 | Deprecrated | |||||
| Govern | bill validation | verify | ||||||
| Govern | cashier Id | Text | verify | |||||
| Govern | check validation | |||||||
| Govern | credit card data entry | Automatic/Manual | Deprecated? | |||||
| Govern | default access type | Table Lookup | Property Control, Real Property, SRT, Name … Still in use? | |||||
| Govern | default cycle | |||||||
| Govern | default payment data entry year | |||||||
| Govern | display cycle code | Deprecrated | ||||||
| Govern | display fiscal year field | Deprecrated | ||||||
| Govern | display installment field | Deprecrated | ||||||
| Govern | print credit card receipt | to verify | ||||||
| Govern | print receipt log | see roadmap | ||||||
| Govern | receipt group | 3 letter | ||||||
| Govern | use cash drawer | |||||||
| Govern | slip driver, font, etc. | To be reviewed | ||||||
| Cash Collection Parameters | Payment Data Entry | deposit | to be reviewed |
| Registry Type | Section Name | Key Name | Key Type | Identification CD | Key Value | Encrypted | Action | Notes |
| Cash Collection Cashier | Cash Collection Cashier | cash drawer name | 2 | machine name | EPSON TM-H6000IV Receipt | 0 | As shown in Windows Printer names | |
| Cash Collection Cashier | open cash drawer sequence | 2 | machine name | 27;105 | 0 | |||
| Cash Collection Parameters | All the same section names and parameters as by User ID |
100-USR-Registry
Version 6.0 | Version 6.1
This is the standard receipt printed when using Cash Collection module.
Available in GA 1606.
– Undefined –
cc-rpt-058
A sample report will be provided when available.
101-cc-rpt-058-Receipt
Version 6.0 | Version 6.1
This is the standard report used to print the check endorsement when using Cash Collection.
Available in GA 1609.
cc-rpt-060
– To be provided when available –
101-cc-rpt-060-CheckValidation
Datasets that appear in the Dataset Treeview are populated with the results of searches made through the Search form. Records that are loaded into the Dataset Treeview may be appended to through the Saved Dataset pane, or deleted directly in the Treeview pane.
To populate the Dataset Treeview with search results…
The Treeview Explorer displays record information in a hierarchical arrangement. In the Treeview panel, you are able to expand or contract a record by clicking on the arrowhead icons.
For example, on a search that retrieves tax map records, when you double-click on the tax map, it lists name information at the next level. Each item can be expanded to show specific data on the property, such as owner and occupant names, parcel information and location, permits, utility billing and accounts receivable records.
As you select each level of information, the data is displayed in the appropriate OpenForm when it is displayed on the right hand side.
When a dataset has been loaded, it is easy to select and begin to edit a record. This ease of selection may at times be a detriment as at times the wrong record may be selected, and the user immediately begins to edit in error. It has been determined that if a secondary confirmation is introduced during the record selection process, there is less chance of erroneously editing the wrong record.
Through the Govern New Administration (GNA), the Record Edit Confirmation option can be enabled to add a secondary confirmation. When Record Edit Confirmation is enabled, after the user selects a record, they are obliged to click on a secondary icon (A), to fully unlock the record for editing.
To enable Record Edit Confirmation…
When this option is enabled, after loading a dataset, users may still select a record for editing, but the selected record will have an icon beside it. The user must click the icon in order to fully unlock the record for editing.
For all details regarding the Govern Treeview Architecture, refer to 101-std-fea-005-Treeview_Architecture.
NEW! Users of the Dataset Treeview will note that when it is populated with one or more records, there is a description for each record. This description can be a Parcel ID, an Account Number, and so on. A quick method of deleting individual records is to hover the mouse pointer over a record. When the width of the Dataset Treeview pane is wide enough, placing the mouse cursor over the description will display an “x” that can be used to remove the record. Unfortunately when there is insufficient space, i.e. the space is not wide enough to display the full description, the “x” is not visible. To address this situation a context based menu has been added to the interface.

To display this menu…
By default, there will be an option to “[x] Remove”. When there are other options, e.g. Edit, they will also be presented in the menu.
This feature is available in the following releases: 6.0.1611.0067 / 6.0.1702.0080 / 6.1.1611.0060 / 6.1.1702.0121
Previously, when performing a search of records with the same NA_ID but multiple ST Account numbers, when you copy the record to the Treeview, the system would only select the first account. Now the selected record will be sent to the Treeview. (Available in release 6.0.1503)
This behavior of selecting only the first account also applies to the Hibernate process. As Govern is restored from a hibernation if a second or third account is selected before hibernation, when the application is restored, although the NA_ID is correct, only the first account will be displayed.
As data is loaded or appended to the Treeview from the Search, or the Saved Datasets form, the following rules apply:
Previously the Hibernate would store the NA_ID of the records displayed in the various panes that are opened in the interface. Now to maintain the fidelity of the hibernated user environment, all Govern ID’s are used; i.e. NA_ID, P_ID, ST_ID, and so on.
| NOTE: User Hibernate information is stored by user in (Table: USR_HIBERNATE). The following query will display the hibernation information for “userName” |
SELECT *
FROM USR_HIBERNATE
WHERE USR_ID = ‘userName’;
Treeview Synch
In Govern for VB6, external tables (PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL), were used by external applications and reports to automatically know the current recordset and currently viewed parcel. In Govern release 6.0 and upwards, these external tables are being phased out and the functionality provided by them will need to be reproduced.
NEW! The Treeview sync. feature saves the contents of the current profile in (Table: USR_SAVED_DATASETS) with a “Saved Dataset” name of “AUTOSAVE” under (Column: USR_SAVED_DATASETS.SAVED_SET_NAME). Should a profile be changed, the dataset loaded in the Treeview will be automatically synchronized to (Table: USR_SAVED_DATASETS).
This feature recreates the functionality provided by the three (3) external tables that were used in Govern for Windows, (Tables: PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL). For example users could run a batch process on a saved external dataset as opposed to a set range.
| NOTE: In release 6.0 a simultaneous save will be made to (Table: PC_EXTERNAL) and (Table: USR_SAVED_DATASETS), Tables NA_EXTERNAL and PM_EXTERNAL are no longer supported. In release 6.1, all three (3) tables PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL will not be supported.
|
This feature is enabled in the User Registry through the User Registry Manager. The Options button is located below the Govern suite button in the Govern User Interface.
When you return to the Govern interface, the Treeview Sync. icon will be enabled. This is a toggle, i.e. ON/OFF button that will enable or disable the feature.
As indicated above, all data will saved in (Table: USR_SAVED_DATASET). Associated columns are as follows:
| COLUMN | DESCRIPTION |
| USR_ID | User ID |
| SAVED_SET_NAME | By default will be AUTOSAVE |
| REF_TYPE | “P_ID”, “NA_ID”, etc. Based on the profile Key Type |
| SORT_SEQ | Order in the Treeview |
| IS_CURRENT | TRUE if the current item in the Treeview |
NOTE: All data will be saved based on the Key Type of the profile. This is done so as to support multiple Key Types at the same time.
The desired behavior when there is more than one Treeview dataset for the same ID Type is to perform a reload when the user switches from one instance to another.
Programmers should note the following Business Rules.
| NOTE: This is done by setting the current id to -1 and setting the prior id to 0 |
NOTE: Always hide AutoSave SAVED_SET_NAME from saved dataset functions
|
101-std-fea-005
Version 6.1 (In Development)
The Multimedia OpenForm is used for linking multimedia files to property, name, permit and sales records; for example, building drawings can be linked to a property record, photographs or video files to a complaint, building plans can be scanned and linked to a permit or the property deed to a sales record. PDF documents and unlimited text lines can used as annotations to the file. Each property control OpenForm can create and maintain customized multimedia links. The Multimedia tab can be configured with any number of different OpenForms in order to create a link to the following:
Multimedia can be recorded by property, name or by a multitude of reference ID’s (Account Number, Sale, Building, Inspection, Split Merge Transaction, Permit, Complaint, and so on.)
For setup information, see Standard Feature Installation of the Multimedia control.
| NOTE: The Multimedia tab can be found in numerous profiles as it is a general usage form that allows users to attach multimedia files to records as needed. |
Govern can support a variety of Multimedia documents. These documents can range from image formats such as .BMP, .TIF, .JPG, to Adobe Acrobat .PDF, or Microsoft Word .DOC files, etc.
When a multimedia image document has been linked to the current record, the document will be displayed in the right hand pane when you open the form. Otherwise, click Open Document or doubleclick on the image the Preview pane to display the document. The document will be displayed with the application that is set as the default for viewing the file type that is selected. For example if you have
Microsoft Word installed and you preview a .doc file, Microsoft Word will be launched. Use the controls of the previewing application to close the window and return to the Multimedia tab.
Setup Options
Depending upon the business requirements, through the parameters, the same form controller can be configured with different keys and for different multimedia types.
Below is the technical setup and configuration document for the Govern Multimedia Documents custom entity.
See – 101-std-frm-001 Govern 6.0 Multimedia Documents
101-std-frm-001