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

 

Central Notes Feature

Central (Centralized) Notes

Overview

Central Notes are designed to allow users to enter and store notes in a centralized storage location. When used, Central Notes enables users to maintain, and review, any notes that are entered when an action is performed, or when a modification is made.

User prompts for a central note entry can be made to occur at the entity level, or at the field level of a profile. This means that a user can be prompted to make an entry when they either access and make a change anywhere in the profile, or in a specific parameter in the profile. These settings are made by an administrator in the Business Entity Designer (BED) release 5.1 or greater. in addition Central Notes can be applied on a dataset basis, i.e. all records of a search result could have a note applied to them collectively.

NOTE: Central Notes that are applied as a dataset are permanent, Notes applied to a dataset cannot be removed.

 

101-std-fea-009-(uiTN)-[v6.0].png
Centralized Notes Pane & Viewer

As an example, in the Parcel Linking profile if a new parcel link is created, or a modification is made to an existing Start Date or End Date, justification may be required for the action. This layer of security can be provided with the Central Notes System. When enabled, the user will not be able to complete the action unless an entry has been made in the Central Notes form. When entered and saved, the record of the username, change, and details is saved.
When a centralized note is entered, an optional flag can be assigned to it. A note can be entered with three (3) statuses. These statuses can be used as part of a search criteria. (Table: PC_CENTRAL_NOTES).

Locating the Central Notes pane

The Central Notes can be found by default as an Auto-Hide tab located on the left hand side of the Govern user interface. To display the note field, hover your pointer over the tab to display it. Refer to Auto-Hide Panes (std-fea-001).

Read More...

Enabling Central Notes

Creating an Entity Level Centralized Note requirement

At the entity level, when an entity is made or modified, the user will be required to enter a centralized note entry.

To set up an Entity level Central Notes entry request, you will need to make changes using the Business Entity Designer (BED) release 5.1 or greater. Refer to the BED release 5.1 guide for details about modifying Business Entities (BE’s)

  1. In the BED, under the Model Explorer pane, click on the Business Entity that will require a Centralized Note entry; for our example we will use Parcel Linking.
  2. Under the Properties pane on the right hand side under 1 – Basic Data Settings, set the Note is required on creation flag to True.
  3. Set the Note is required on modification flag to True.
  4. Click Save.

When the flags are set at this level, i.e. the Entity level, a Centralized Note entry will be required to create a new parcel link entry.
Creating an Attribute Level Centralized Note requirement
At the Attribute level, in order to enter a note, or when a modification is made to an attribute, i.e. field, a note entry will also be required to be made.
To set an attribute level Centralized Note entry request…

  1. In the BED release 5.1, under the Model Explorer pane, click on the Business Entity that will require a Centralized Note entry; for our example we will use Parcel Linking.
  2. In the central area under the List of Attributes pane, select an attribute that you want the user to be prompted with a Centralized Note entry request; for our example select the END_DATE attribute.
  3. On the right hand side, locate the Central Notes property, set both the Allow Notes, and the Note is required on modification flags to True.
  4. Repeat the above steps 2 and 3 for the FROM_DATE attribute.

About Entity / Attribute Level Centralized Note requests

Users that are enabling Central Notes for Entities and Attributes should note that the request for a Centralized Note entry by the system are separate. This means that if the flags are set at both the Entity and Attribute level, a separate prompt for a Centralized Note entry will be issued by the system.

Central Notes pane

The Central Notes pane is used to enter and display the notes that are related to the selected parcel. These tabs are used to enter and view the Central Notes, as well as controlling what notes are displayed after a search, through a series of user selectable filter fields.

Notes Viewer form

With a click on the Notes Viewer button in the Central Notes pane, the Notes Viewer form is displayed. This form contains two (2) tabs, one for defining your search parameters, and the other for displaying the search results.

NOTE: by default when the Notes Viewer button is clicked, the Notes Viewer form is displayed with the Notes Viewer Search Results tab.

Notes Viewer Search Criteria tab

In the Notes Viewer Search Criteria tab, you are able to search the Govern system for existing notes. The results of the query are filtered based upon your search parameters.

Central Notes Management tab

Notes Viewer Search Criteria tab – Command Button
Retrieve Notes:
Click Retrieve Notes to perform a search of the Centralized Note based upon the Filter options selected.

Notes Viewer Search Criteria tab – Parameters

The following is a description of the parameters that are found under the Notes Viewer Search Criteria tab.

Filters group

Dataset Filter group

Selections in the Dataset Filter group will restrict the display of notes to those within the current dataset.
All: Click All to display all notes in the current dataset.

Current Parcel: Select this option to display notes that are restricted to the current parcel.

Current Name: When Current Name is selected, only the Central Notes that were created on records that are linked to the current name account.

Author Filter group

All Authors: Select this filter option to display notes from all authors under the Author list. (TABLE: USR_USERFILE)

My Notes Only: When selected, this option will display only notes made by the current logged in user.

From Author: Click to select the From Author option; this will display the notes entered by the author that is selected from the drop down menu.

NOTE: The drop down menu list will not be active unless the option is selected. When this option is selected, but no author is selected, a warning will be displayed requesting that an author be selected from the list.

Subject Filter group

Entity Name: Click to select an Entity Name from the drop down list; the notes that are displayed are the ones that are related to the Entity.

Control / Attribute: Select the Control / Attribute option to filter for the Control or Attribute that is associated with the selected control or attribute

Table Name: Click to activate and filter Central Notes that are associated with the selected table name.

Column Name: After selecting a Table Name, you can further filter down and display Central Notes associated to a selected column name.
Date Filter group

Fiscal Year From / Fiscal Year To: Enter the Fiscal Year range of interest in the From and To fields.

Entry Date From / Entry Date To: Enter the date range of the Central Notes that you would like to view.

General Filter group

Note Priority: When a priority has been assigned to a Centralized Note, use this option to filter the search results for a specific priority. If no priority is selected, the all notes will be specified.

Exclude Private Notes: Select this option to exclude all notes that have been assigned with the Private Notes option.

Searching for Central Notes

Users with access to Central Notes can perform a search on all notes entered in the system. The search can be by parcel, name, or by author, for a given entity or attribute.
To perform a search for Central Notes that have been entered in the system:

  1. Click to display the Central Notes auto-hide pane.
  2. Select the Notes Viewer Search Criteria tab.
  3. In the Filters group, select each criteria required from each of the filter groups.
  4. If required select a priority note from the General Filter group.
  5. Click Retrieve Notes.

Notes Viewer Search Results

The search results will be displayed under the Notes Viewer Search Results tab.

Notes Viewer Search Results

As indicated earlier, the Notes Viewer Search Results tab displays the results of search queries based upon selected filters. The columns displayed can be re-arranged with a drag and drop action.

Grouping by Columns

The Central Notes drag and drop feature also allows for grouping by column heading. The space above the columns titled Drag a column header here to group by that column is referred to as the Grouping Area (A). This space expands to accommodate column names as they are added.

For example, if we have the following columns headings…:

  • Priority
  • Private
  • Entry Date
  • Relates To
  • Note
  • Author Name

We may want to view the entered notes grouped according to the Priority (A).

To group according to the Priority:

  1. Click and drag the Priority column into the Grouping Area above the columns; when empty this area is marked”Drag a column header here to group by that column”. Drop the column heading on the Grouping Area.
  2. You will note that the data has now been grouped according to the Priority column. You will see a heading that indicates the column grouping, the item that it is being displayed under, and the total number of items under that grouping. Click on the “^” beside the column grouping (A) to expand or contract the content listed.

Multiple columns or attributes can be grouped by dragging and dropping them into the Grouping Area above the column headings. Additional columns will appear as subgroups within the original group.

The order of the groups and subgroups can be changed with a drag and drop procedure.

To re-arrange subgroups:

  1. Click and hold the pointer on the subgroup title.
  2. Drag the title to its new location, noting the insertion point between the subgroups. The insertion is indicated by a bright vertical bar.
  3. Release the mouse button to complete the insertion.

Removing Column Groupings

To remove column groupings from the Grouping Area:

  1. Click and drag the grouped or sub-grouped title to an area outside of the Grouping Area.
  2. When an ‘X’ appears, release the mouse button to drop the object. The grouping or sub-grouping will be removed.

Viewing Central Notes Search Results

After result have been generated, there are two (2) options available to view the results; export results to an Microsoft Excel spreadsheet, Print with a preview.

Notes Viewer Search Criteria tab – Command Button

Export to Excel: When Export to Excel is selected, the current search result grid will be exported as an Microsoft Excel spreadsheet.

NOTE: The Excel export will not be affected by the sort order or grouping; the columns are output in the default order of the system.

Print Preview: Click Print Preview to display a preview of the current search result grid.

Behavior of Central Notes when enabled in Govern

When Central Notes are enabled, fields that have the Central Notes enabled through the Business Entity Designer (BED) will have icons that flag the state of the field.

Central Notes Status Icons

Central Notes fields are indicated with Notepad icons that lets the user know their status. Red icons indicate that note entries are required, i.e. mandatory; Gold icons are an indication that note entries are optional:

Allowed: The yellow icon indicates that entry of notes is optional for the user.

Required: This indicates that any changes to the field involves a mandatory note entry

Exists and Allowed: The yellow icon and magnifying glass indicates that notes exist in the system, but they are optional for the user.

Required and Exists: The red icon and magnifying glass indicates that a notes exist, but mandatory entry is required for changes by the user.

How to make a Centralized Note entry

Users that are attempting to save a record when the field is set as Required will be presented with the following error window: To resolve this situation…
1.Click OK to acknowledge the notification.
2.Locate the Central Notes auto-hide tab; place your pointer over the tab to display it.
3.Click Add a New Note.

NOTE: When a new note is created, the date, time, and user log-in name is displayed for reference.

4.Click in the note field and enter your note

5.When complete, click Save.

As long as the Centralized Note is created and the reason for the creation or change, i.e. “justification” is entered, the system will them allow a save.

Creating a Centralized Note for a Dataset

WARNING: A Centralized Note that is applied to a dataset cannot be modified or deleted. Take care when making your entry

Creating a Centralized Note for a Dataset, i.e. a group of records that are the result of a query, hand picked records, or appended list, is a similar procedure to applying one to an individual record.

NOTE: In order to be able to click on the Central Notes button, you will need to open a Profile, then perform a search.

To create a Centralized Note that will apply to a dataset…

  1. Perform a search; the resulting records will be the dataset.
  2. Load the dataset into the Dataset Treeview.
  3. If not selected, click the Home tab in the Govern Ribbon.
  4. In the Flags group, click to select Central Notes.
  5. In the Central Notes form, enter your notes that will apply to the dataset (1).
  6. Select a Priority status, and select the Private option if the note is to be set as private (2).
  7. Click Save (3) to create the note or Cancel (4) to stop the creation process.

Central Notes for Datasets are saved in the same table as the individual record notes, (Table: PC_CENTRALIZED_NOTES), the exception here is that these notes are permanent, i.e. they cannot be deleted.

Modifying a Centralized Note

Once a Centralized Note has been created, the author or creator of the note can modify their entry. In addition, with the correct security flags set in the Govern Security Manager (GSM), an author can modify all Centralized Note entries.

To modify a Centralized Note…

1.Display the Centralized Note pane.

2.Select the note and effect any required change.

To enable a Centralized Note author to be able to edit all notes…

1.In the GSM, ensure that the permissions flag for Update (U) has been set; refer to the Working with Central Notes section of the GSM 5.1 user guide.

NOTE: If the update flag has not been set, the author will only be able to change the notes that they created, and no others. Refer to the GSM release 5.1 for details on Working with Central Notes.

 

What’s New

[v6.0.1404]
  • The search panel is now dockable. Users can keep this window open while performing other tasks. Very handy for users with dual screens.
  • Collective notes can be recorded by dataset (permanent)
[v5.1]
  • Note Priorities
  • Private notes are used to flag notes that should not appear on the web

Specification

Product feature specification [v6.0] for centralized notes:
General

  • Recorded at the business entity level or at the field/attribute level
  • Recorded for the active parcel, name, building… or for the entire dataset or recordset results (permanent)
  • Metadata recorded along with the note (i.e. the author, date, dept. fiscal year, entity name, attribute/field name… is saved along with the note)
  • Additional security level based on authorship (my notes, other people notes)
  • Allowed or Required (on creation or on modification) Business Entity notes
  • Allowed or Required notes on Attributes
  • Priority status (3)
  • Private notes

User Interface

  • Auto-hide and dockable Note Pane synchronized with active form and ids
  • Notes are saved with the form
  • Centralized Notes Viewer with Search & Results (sort, group, print and export to xls)
  • Search Criteria:
    • Dataset: All, Current Dataset, Current Parcel
    • Author: All, Mine, Specific Author
    • Subject: Entity name, Attribute name, Table name, Column name
    • Date: Fiscal Year From and To, Entry Date From and To
    • General: Priority, Exclude or Include Private Notes
  • Visual representation (cues) of the note state on the form (required & missing, required and available … )
  • Notes can be deleted

Business Rules

  • Required Note Option to enable an additional layer of security to prevent a user from completing an action unless a note is created
  • Is dirty property is set to true on the form when a note is created or modified

Examples

  1. in a profile with Parcel Linking, if a new parcel link is created, or a modification is made to an existing Start Date or End Date, justification (note entry) may be required to complete the action (save or modify).

Setup (BED)

Setup in the Business Entities Designer as true or false properties for the Business Entity or for an Attribute (field).

Business Entity

  • A note is required on creation
  • A note is required on modification

Attribute

  • Allow notes
  • A note is required on modification

Security

In Govern Security Manager (GSM), there are 2 items that can be secured for notes; Entry & Viewer.
In addition, a distinction is made for Centralized Notes Entry between My Notes (notes entered by the user) and Other people’s Notes.

Expand ApplicationsGovernMenuViewViewCentral Notes to get the following:
Central Notes (change to Centralized Notes)

  • Central Notes Entry
    • My notes
    • Other notes
  • Central Notes viewer

For more information, see 102-Govern Security Manager (GSM) OpenForms System Suite

Technical Info

Tables

PC_CENTRAL_NOTES
PC_LK_CENTRAL_NOTES

[v6.0] New Govern Standard Attribute PC_CENTRAL_NOTES REQUIRED

Best Practices

  • Do not overuse (it is human nature to overdo it); this can be overwhelming when reviewing the information.
  • If Required Notes are not set properly, they can be a burden for users with data entry functions.

 

 

101-std-fea-009

 

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