AR – Search to Load Data (101-ar-fea-026)

Accounts Receivable (A/R) Search to Load Feature

Available in Govern Rel. 6.0/6.1

Overview

Selecting a Record Key from the DataSet TreeView will load AR Data, the form also has a feature that allows you to search for keys to load the data. The key is then sent to the TreeView as a Temporary Key to allow the application to recalculate information based on that key.

Demonstration of the Temporary Key

To demonstrate the functioning of a Temporary key in Govern, follow these steps:
Preparatory steps:
  1. Search for a few records to add to the Treeview from the eSearch then open the AR Inquiry form.
  2. Search for a key that contains a field that is of the same type as the profile and is already in the Treeview. It gets selected.
  3. Perform Step 1) but for a key that isn’t in the Treeview already. It gets added, selected, 1st and orange background.
  4. Perform Step 2). the key added by 2) gets replaced by this new one.
  5. Repeat Step 1). notice that the same result and the one added in Step 3) remains.
  6. Perform a search for a key that doesn’t contain a field that matches the Treeview key. The description is based on the Main ID of the key.
  7. Manually remove the temporary key from the Treeview and search for it again. It gets added as Temporary again.

Related Topics

 

 

101-ar-fea-026

 

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

Dataset Treeview Temporary Records

Dataset Treeview Feature – Temporary Records

Overview

The Dataset Treeview Panel contains a list of record keys that, when selected, will send the information to OpenForms which, in turn, will load records accordingly.

Temporary Records

Normally, a user simply searches for record keys and navigates through them to work but some features can load their keys internally without being linked to the Record Keys from the Tree View, for example AR Inquiry and Cash Collection forms. The side effect is that any information normally available outside the form are not refreshed because they are triggered only by a selection in the Tree View, this is the case with Tiles. In order to resolve this issue, these keys are sent to the Tree View but are flagged as “Temporary”. Only one of these keys can appear in the Tree View. The keys are replaced when a new one is introduced; this approach is used so as not to clutter the Tree View with keys that are not part of the user’s workload. In addition these keys can also quickly increase disproportionately. These keys are also not retained when the application is closed.

Business Rules

In order to trigger as many features as possible, the key will be filled with as many ID’s obtained from the database, based on available and missing ID’s from the Temporary Key.

  • First we check to see if we can find IDs from AR_MASTER based on an ordered list of specific ID Types that we get from the Temporary Key. These keys are the same that are needed to add to the Temporary Key afterwards from AR_MASTER.

    From AR_MASTER
    • The ordered ID types are: AR_ID, PP_ID, ST_ACCT_ID, UB_ID, MB_ID,  BR_ID, DC_ID, BT_ID, MV_ID, AC_ID, P_ID, NA_ID 
      • This means that as soon as one key returns records, we stop and take the most recent one.
  • If no AR_MASTER records are found directly, we try to find an AR_MASTER record linked to AR_DETAIL based on specific ordered field types from AR_DETAIL, noting that the IDs taken from AR_MASTER will still be the same as before.

    From AR_DETAIL Expand source
    • the ordered AR_DETAIL Field Types are: ST_ID, INVOICE_NO, PRJ_ID, PM_ID
      • This means that as soon as one key returns records, we stop and take the most recent one.
      • In version 6.1, the content of PM_ID will be a Workflow ID
  • If no NA_ID is found after that for the Real Estate Sub-System, we’ll try to get it from the primary NA_MAILING_INDEX if a P_ID was previously found.

    From NA_MAILING_INDEX

The Temporary Key will be inserted at the top of the Tree View with an Orange background. For example:

  • It is possible that the Temporary Key contains an ID that matches the Profile’s Key Type at this point, but its current Main ID Type is not the same. In that case, we will make this ID Type the main one so as to see the correct description in the Tree View.

Duplicate of an Existing Key

It is possible that after the work is done, the Temporary Key’s main ID exists in the Tree View. If that’s the case, it won’t be added to the Tree View like a Temporary Key, although the ID’s of both will be merged together, it will only be selected.

Context Menu

In the Dataset Treeview, a right click on an item will display and a menu with 3 options:

  1. Remove the current selected item
  2. Remove All items from the Dataset Treeview
  3. Remove All the items except the item where we did a right click on it

If we decide to right click on the panel, only 1 option will show up, allowing the removal of all items from the Dataset Treeview:

Remove

  • The item which we made a right click on will be removed from the Dataset Treeview.
  • If “Dirty”, a confirmation will show up asking you to save the data first.
    • Yes: Save the data and remove the item
      • If there is a validation error on saving, the item will not be removed and the item will remain “dirty”
    • No: Cancels the change and remove the item
    • Cancel: Not remove the item and the item is still “dirty”

Remove All

  • All the items will be removed from the Dataset Treeview.
  • If “Dirty”, a confirmation is displayed asking you to save the data first.
    • Yes: Save the data and remove all the items
      • If validation error on saving, the items will not be removed and the changed item remains “dirty”
    • No: Cancel the change and remove all the items
    • Cancel: Will not remove the items; the item is still “dirty”

DEV NOTE: Currently there is a bug in the techno and the message is displayed twice (2 times).

Remove All But This

  • All items will be removed except the item which we did a right click on in the Dataset Treeview.
  • If “Dirty”, a confirmation will show up asking you to save the data first.
    • Yes: Save the data and remove all the items except the item which we did a right click on it
      • If validation error on saving, the items will not be remove and the changed item is still dirty
    • No: Cancel the change and remove all the items except the item which we did a right click on it
    • Cancel: Will not remove the items and the item remains “dirty”

DEV NOTE: Currently there is a bug in the techno and the message is displayed twice (2 times).

 

Related Topics

Dataset Treeview

Forms Explorer
Reports Explorer

 

 

101-std-fea-049

 

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

 

System Architecture (Dataset Treeview)

System Architecture (Dataset Treeview)

[In Development]

Overview

The following table describes the rules that the Dataset Treeview is adheres to. For flexibility, Views (queries) are used to define the content to be displayed. To improve the user experience, a Standard Iconology provides visual information to identify the type and status of records listed in the treeview.

Database Views

Naming Standard
V_TREEVIEW_(name) Standard system Govern views that are distributed.
VW_TREEVIEW_(name) Custom views to include in the list of Treeview that can be selected for a profile
Database
Security Access No special security required for the view
SQL View Syntax
Primary Govern ID LINE 1
The first field matching a Governs ID name must match the Profile Dataset Type (brule)
Secondary Govern ID LINE 1
Sequential, i.e. Line 1, Line 2, and so on…
Information Displayed LINE 1
The attributes and their order to be displayed are defined in. Formatting is made in the SQL query view…
Mouse-Over (Tool Tip) LINE 1 to Line X (Need to verify)
Each line will be displayed on the mouse-over
Sort Order Primary Sort
Not relevant…
Security
Database Access Set up in Profile Editor
Setup
Profile Editor For each profile, a treeview is selected that matches the correct dataset type access

Supported Views

Standard Views
For name dataset profiles (NA_ID) The following views are supported:

  • V_TREEVIEW_ADDRESS (Name and Address)
  • V_TREEVIEW_BTAX (Name and Business Tax Info)
  • V_TREEVIEW_PP (Name and Personal Property Tax Info)
  • V_TREEVIEW_MB (Name and Misc. Billing Info)
For parcel dataset profiles
(P_ID)
The following views are supported:

  • V_TREEVIEW_LOCATION (Property Location)
  • V_TREEVIEW_PARCEL_INFO (Property General Info)
For A/R dataset profiles
(NA_ID)
For Accounts Receivable Profiles (NA_ID)

Distribution Methods (Govern Techno)

Views are created, updated, included in …

SYSTEM AREA ITEM DESCRIPTION
Database Verification
Create The standard views are created automatically on a Database Verification execution when the view does not exists
Update The standard views are replaced when there is a deletion. They are recreated;
Verify The standard views are executed for errors … errors are thrown
EMT (Import / Export)
Exported When a profile is exported Views are also transferred
Imported No Views are imported
Database Extraction
Extracted with The standard/custom views in use for all Views and Functions and are extracted and copied. >00b050
Mobile
Copied Standard and Custom views are copied.

Standard Iconography

SYSTEM AREA ITEM DESCRIPTION
Standard Icons
Govern IDs Profile Dataset Govern ID Icons that are displayed in front of each record when by:
Parcels = HOUSE icon (p_id)
Names = PERSON icon (na_id)ALL OTHER ITEMS
Accounts = FOLDER icon (ST_ID, PP_ID, MB_ID, UB_ID, RE_ID…)
None or Undefined = Govern ID only
Edit mode turned on = Padlock icon
Record Selected Regular – These use the same icons as the selected identifier
When Edit Mode
The Lock icon is displayed when Edit Mode is Activated. On selecting a record, the EDIT icon is displayed and must be pressed to access record in modification mode
Inactive Records Same Govern ID icon but greyed out

Dynamic Search (eSearch), Saved Datasets and Treeview

The Dynamic Search (AKA e-search) and saved dataset search is highly integrated with the treeview. Users can use the results of searches to append to, or remove records from the treeview.

Dynamic Queries

ACTION CONDITION EXPECTED RESULTS
Send to the Treeview From Dynamic Queries The result of a search 101-std-fea-004
On Append Records are added to the treeview
On Deselect and Load Not Applicable (N/A)
On Add and reposition Custom Control action – Determine Custom Control

Saved Datasets

ACTION CONDITION EXPECTED RESULTS
Get Records
From Saved Dataset The content of a saved dataset101-std-fea-006
From Action Button Send to Treeview If the action button sent to the treeview is used (available in the following standard forms: Split Merge, Parcel Linking, Name Linking

Other Treeview Integration

The treeview can be populated from the Dynamic Search Queries (e-search), from the Query Tool, from a Saved Dataset or from special Action Button Controllers (Send to Treeview). Optionally, if they are setup to this effect, the treeview can be populated by the results of the Matix GIS search, the Web Browser and the Application Browser forms.

ACTION CONDITION EXPECTED RESULTS
Get Records
From Action Button Send to Treeview If the action button send to treeview is used (available in the following standard forms: Split Merge, Parcel Linking, Name Linking
From GIS Matix Search 101-std-frm-008
Manual Mode
Automatic Mode
From Web Browser Form 101-std-frm-003
Manual Mode
Automatic Mode
From Application Browser From 101-std-frm-005
Manual Mode
Automatic Mode
From Query Tool Manual refresh to be performed by user. ()
Selected Record
Default First record is selected
User clicks on a record Record is selected
On Select
Refresh Govern IDs Main Govern IDs
Secondary Govern IDS
First Record is Selected
Refresh Forms

Treeview User Interaction

The users can perform the following Treeview Actions

ACTION CONDITION EXPECTED RESULTS
On Mouse Over
Tool Tip Line 2 to x is displayed as a Tool Tip
On Select
User clicks on a record The Govern IDs are refreshed
The icon changes
The forms are refreshed with the selected record Govern ID
On Remove
X The user can remove records from the Treeview
On Move
Previous F6 Go Up
Next F7 Go Down
On Expand
Form Expand Icon The Forms are displayed below the treeview entry.
The same forms as the Forms Explorer are displayed. Displays the forms that the user/role has access to in GSM
Double Click
On Collapse
Form Expand Icon The Forms are no longer displayed
Double Click

Inactive Business Rules

The users can perform the following Treeview Actions

ACTION CONDITION EXPECTED RESULTS
Parcel
Inactive and Effective year
Effective date
Name
Buildings
Effective and Inactive date
Links
Effective and Inactive date
Accounts
Jurisdictions
TFS13225
Mobile
Checkout Bypass Checkout

Special Features

The users can perform the following actions:

NOTE: The following actions are the same as on load.

 

ACTION CONDITION EXPECTED RESULTS
Auto Synch
Form Refresh
Govern F5 Used to update the treeview
If profile view is changed
If form is added
If date is changed
Hibernate

 

 

101-std-fea-005-Treeview_Architecture

 

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 – Self Reported Business Tax Treeview

Self Reported Business Tax Treeview

Overview

The datasets that appear in the Dataset Treeview are populated with the results of searches made through the Search form.
The Treeview Explorer displays record information in a hierarchical arrangement. In the treeview panel, you are able to expand or contract a record with a click on the arrow beside the record icon.
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.
The Self Reported Business Tax Treeview will display the ST requisite OpenForms, i.e. Self Reported Tax, Self Reported Tax Occasional, and the Self Reported Tax Zero Filer.

NOTE: The forms that are displayed in the treeview are dependent upon admin setup in the GNA Profile Editor and/or assigned access provided through the Govern Security Manager (GSM)

See also

 

 

 

101-st-fea-005

 

[rating]

Dataset Treeview

Dataset Treeview

Overview

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.

Populating the Dataset Treeview

To populate the Dataset Treeview with search results…

  1. When the Predefined Searches pane is in its default position, place your mouse pointer over the tab to display the search form (A).
  2. In the form perform a search type; for this example we will perform a property search by P_ID.
  3. Click Search for Result.
  4. Search results will be displayed in the lower portion of the search form.
  5. Click Load to the search result to transfer the search result records to the Dataset Treeview pane.
  6. If the Dataset Treeview pane is not displayed, click its tab at the bottom of the pane.

 

The Treeview Explorer

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.

Record Edit Confirmation

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…

  1. In GNA, select System Parameters (tab) > General Connection Parameters.
  2. In the General Connection Parameters form, locate the Organization Parameters group and select The user must explicitly enable editing for each parcel option.
  3. Click Save to save the option.
  4. To close the form, click Exit.

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.

System Architecture

For all details regarding the Govern Treeview Architecture, refer to 101-std-fea-005-Treeview_Architecture.

What’s New

Context Menu in Dataset Treeview

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.
TreeviewContextMenu00.png
To display this menu…

  1. Right click on the record of interest in the Dataset Treeview.
  2. In the floating menu, you now have option for additional functions that appear beside the record when the entire line is visible.

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

Reposition

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)

Hibernate Mode

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.

Load to Treeview and Add (Append)

As data is loaded or appended to the Treeview from the Search, or the Saved Datasets form, the following rules apply:

  • When a record is selected for append, only new files will be loaded. If previously loaded, the file will not be reloaded into the Treeview.
  • If no search result is selected, the Add to Search Results button will be disabled.

Hibernate

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.

  • PC_EXTERNAL (Supported in release 6.0; not supported in release 6.1)
  • NA_EXTERNAL (Not not supported in release 6.0 and 6.1)
  • PM_EXTERNAL (Not not supported in release 6.0 and 6.1)

Enabling “Synchronize Dataset Treeview”

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.

  1. Click the Options button; click Options.
  2. In the Registry Manager form, verify that the Registry Filter is set to User ID.
  3. Under the Section Name column, locate Synchronize Dataset Treeview; click to select the option under the Key Value column.
  4. Click Save to save your changes.

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.

Location of Data

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 data is not saved by profile, so the synchronization for a Key Type will be done on the last active profile using that key type.

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.

Business Rules

Programmers should note the following Business Rules.

When Parameters Change:

  • From TRUE to FALSE – Delete all SAVED_SET_NAME that have a status of “AUTOSAVE” and replace the value with the current USR_ID
  • From FALSE to TRUE – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with the current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
    – Starts monitoring Dataset tree view changes

When Opening Govern (Before opening Profiles):

  • Starts monitoring Dataset tree view changes if Flag is on

When monitoring Dataset tree view changes:

  • If Active profile changes – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
  • If Treeview is replaced (By eSearch / QueryTool / Matix/…); i.e. a Load
    – Delete All SAVED_SET_NAME equal to “AUTOSAVE” for current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the Treeview datazzz
  • If an item is added into the Treeview (By eSearch / QueryTool / Matix /…); i.e. Add Or AddAndReposition
    – Insert the new item into USR_SAVED_DATASET
  • If an item is removed from the Treeview (using the X button); i.e. Remove
    – Delete the new item into USR_SAVED_DATASET
  • If the active item changes in the Treeview; i.e. Reposition()
    – Update IS_CURRENT in USR_SAVED_DATASET
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

  • V6.0 (only) – PC_EXTERNAL will need to be maintained at the same time
  • V6.1 – All three (3) tables, PC_EXTERNAL, PM_EXTERNAL, and NA_EXTERNAL are to be removed.

Related Topics

Dataset Treeview Temporary Records

Forms Explorer
Reports Explorer

 

 

101-std-fea-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...