BP – Quick Search Index Build

Batch Process – Quick Search Index Build

GA 6.1.1803

Overview

This process will allow users to rebuild the Quick Search Index. Additional details will be posted.

 

 

101-std-bp-010

 

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

 

BP – Email Registration Link to ST Accounts

Batch Process – Email Registration Link to ST Accounts

Overview

Standard Batch Process and Definition to send a link by email messaging to the members of a list of ST accounts that do not have web access to eGovern portal.

 

 

101-std-bp-011

 

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

Govern Standard Module Configuration

Govern Standard Module Configuration

Overview

 

 

101-std-config

 

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]

Govern Help Documentation

Govern Help

Overview

Installation of the Govern Help system is managed by the Deploy EZ application during the installation or update process. It is during this process that required directories are created and help content is updated. For the Govern application, unlike the Help system of the other applications in the suite, Govern help content is not invoked with the F1 key. Help content is displayed with a click on one of the help icons (A) displayed under the Help tab (B) in the Govern application interface. The user selects the icon that corresponds to the profile, form, or entity of interest.

NOTE: Users can still invoke Help content with the F1 key in all other applications within the Govern suite. All help content that is presented to the user is contextual, i.e. relevant to the active user screen.

 

Read More...

User Interface

Govern

For a user to open the Help file within the Govern application, they will need to select the Help tab in the ribbon of the Govern application (A). Under the ribbon, the help content which corresponds to the Application, the Profile, the displayed Open Form, and the Entity is displayed (B).

  • Applications – Content corresponding to the suite Application; the General group
  • Profile – Help content for the Profile
  • Form – The help content for the displayed Open Form
  • Entity – Help content related to the Entity
  • Report – This is the Report associated with the form or entity.

The Help button displays information for the main application, and the OpenForm Help will display Help content that is related to the active OpenForm.

Missing / Unavailable Help Content

When content is not present the broken help link icon is displayed. This icon is an indication that there is an issue with accessing the Help file(s). Issues can be anything from the files not being present or incorrect directory structure due to a change in the Open Forms General Settings form in GNA; the Help Folder Structure Type parameter may have been changed.To correct this situation, users will need to either:

  • Place the required content in the appropriate directory

OR

  • Verify that the Help Folder Structure Type parameter setting in the Open Forms General Settings form in GNA is set to the correct Help folder structure.

 

Help Content Directory Structure

Open Form Hierarchy

The Open Forms hierarchy is as follows with order of precedence decreasing from left to right.
The above hierarchy is reflected in the structure of the Help directories and subdirectories.

Order of Precedence for Help files Directories

When a user calls the help file, the Govern system first checks in the Custom folder. If the requested file is not found, it will default to the Standard folder to display the file. The Custom folder is reserved for users that want to generate their own custom PDF help files.

Directory Structure

As illustrated in the grid illustration, the structure of the Help directory is multi-leveled. The <HELP ROOT> refers to the root level of the help directory, and not the actual deployment installation of the Deploy EZ application.

Grid illustration examples:

  • Standard (same level option)
    • The versionNum directory will be a version number, i.e. 5.1, 5.2, 6.0,…
  • Custom (same level option)
    • The structure for the Custom directory is nearly identical to that of the Standard directory.
    • The exception is that the Version directory is not present at Level 1. All sub-directories are shifted up by one level.
  • Custom (profile option)
    • Different profiles will require the same report. When the Profile option is selected in the System Registry, the different profiles will be using the same report.Copies of the same report are placed in the different Profile directory.
101-std-fea-002-GOV60-(UI HelpStruct-StdDir-SameLvl)-[v6.0].png
STANDARD – SAME LEVEL option

 

101-std-fea-002-GOV60-(UI HelpStruct-CustDir-SameLvl)-[v6.0].png
CUSTOM – SAME LEVEL option

 

101-std-fea-002-GOV60-(UI HelpStruct-CustDir-ProflOptn)-[v6.0].png
CUSTOM – PROFILE option

Click the diagram to enlarge and open in a new window

Setup

GNA – System Registry (xxx)

Default folders & options

The directory structure, as in previous releases, has two (2) principal subdirectories, Standard, and Custom. Both the Standard and Custom directory structures are set by the system and should not be modified by the user. The structure, and how the system will access the Custom directory can be determined by the user through settings in the Govern New Administration (GNA). There are two (2) options to choose from in the form. [to be verified]

To open the form, in the GNA, select System Parameters > General Settings Editor…
In the Open Forms General Settings editor, select the following:

  1. Under the Registry Filter, select General.
  2. Locate the General Section Name, available options are Profile or Same Level.
  3. The selection of Profile or Same Level, are dependent upon user requirements.

 

Same Level option

Users that are content with the Property Control (PC) profile that is the system default should use the Same Level option. The same profile will be used by all departments, i.e. the same Open Forms will be accessible to all users. All users will be viewing the same help content for the active forms.

NOTE: The Same Level option is the system default.

Profile option

In situations when different profiles are required for the same, or different departments customized profiles will need to be designed. For example, a PC profile that is created for the Assessors department may not necessarily be the same one used by the Public Works department. As the Profiles and Forms are different, the Help content may not be the same. Some confusion regarding functionality may arise unless specific instructions are provided. In this situation, the option for Profile should be selected. With the Profile option, content is placed in a separate directory that corresponds to each customized profile.

NOTE: Changing the parameter after the directory structure has been established is not destructive to the custom help content, but it will no longer be available until the settings are restored.
101-std-fea-002-GOV60-(UI HelpStruct-Schema)-[v6.0].png
Help Content Directory Structure – Click image to open in new window.

GSM – Security & Custom Folders

There is no security imposed on the Custom Help directories. This is the default setting for the installation. Administrators that wish to limit user access to these directories will have to do so using Windows security. Security settings will also need to be done on a user by user basis.

Custom HELP Directories

Security

There is no security imposed on the Custom Help directories. This is the default setting for the installation. Administrators that wish to limit user access to these directories will have to do so using Windows security. Security settings will also need to be done on a user by user basis.

Security Best Practices

BEST PRACTICES – SECURITY
The recommended security setting for administrators that require user restriction to directories, is as follows:

  • All top level Help directories should be set to READ ONLY. for the Custom folder.
  • In order for users to be able to add or update custom content, sub-directories of the top level Custom folder should be made accessible, i.e. READ / WRITE for users. This will allow them to place help in the directories when required.*

 

NOTE: The structure of default Standard, and Custom folders should not be modified.

Users are not required to create directories for the Custom Help folder; the structure established during installation must be kept in order for the content to be available.

NOTE: Unless additional files are required, the help content are in PDF format. Any additional formats that are mentioned above are files that are supplemental to the PDF with the main help content.

 

NOTE: When including any supplemental content, users must ensure that the file format is supported by the end-users system; e.g. if a MicroSoft Office PowerPoint document is to be one of the supplemental files, a PowerPoint viewer or a fully licensed version must be installed on the installation computer.

Note: Network traffic …

Custom HELP Content Nomenclature

CUSTOM HELP CONTENT NOMENCLATURE

  • Lower case names should be used.
  • Users should try to limit filenames of help content to no more than 12 characters because the group will expand to accommodate the name. See image below
  • Limit the length of directory names directories; try not to exceed 12 characters
  • Use the underscore character “_” in place of spaces. Ex. parcel_asmnt
  • Ensure that the extension of the file is supported by the end-user’s system that the content will be viewed on.
  • As a result of the brevity required for the filename, a detailed description of the Help Content can be entered using the Resource File editor in GNA. The node that contains this information is located in the WD module, CustomHelp function. The Keys for tool tips will be appended with an _TT in the names.

Refer to the Govern New Administration (GNA) Resource File editor. <LINK>

Help files Administration

Downloading

Deploy EZ option

Creating

The Govern application is designed to be flexible, with the understanding that users are able to design forms and reports. It is therefore expected that they may have a requirement to customize their Help files contents. When users customize Govern, supplementary help content can be created in one of two (2) ways.

  • Annotate existing system Help files
  • Generate new content with new PDF files

Annotating System Help Files

Users may annotate, i.e. add Notes, to existing system PDF files that correspond to the modules. Although system files should not be modified, there are steps that can be taken to ensure that system integrity is maintained.

Annotation Best Practices

BEST PRACTICES – ANNOTATING SYSTEM FILES
When annotating system PDF files, users should make a complete back up of the installed files. Only the copied files should be annotated and placed in the Custom folder. Original system files will remain in the Standard folder.

Generating PDF Help Files

When generating a PDF file with custom content, in order for the system to recognize the custom PDF file, it must have the same name as the one that is used in the Govern application or module.

For example, the Hazards (PC24) OpenForm in the Property Control module has been customized. A new PDF file is made containing custom instructions. In order for it to be accessible, the new PDF file should have the same name as the system default Help file. For Hazards the file is PC24.pdf; when this file is created, it should then be placed in the appropriate subdirectory in the Custom folder.

NOTE: When a custom PDF is placed in the Custom folder, it is not necessary to remove the system default help file in the Standard folder. System files should never be modified.

Adding or Replacing Help Content
There are two zones to the Help content ribbon in Govern. Zone 1 which contains the icon for the help content file is the area to click when you need to access the content. Zone 2, when selected, will give access to the directory that the content is located in.

NOTE: In instances where there is no help content and the broken help link icon is displayed, a click on the link will also display the directory.

The directories at the custom content is to be placed in is easily accessible with a click on the icon under the Help tab in the Govern ribbon.

Upgrades

The subject of upgrades is undergoing validation. News will be forthcoming.

Documentation

How to configure System Help

Click to view the Configure System Help document.

 

What’s New

Read More...

Web Help

[v6.0 1509.x] A Web based Help system is in place for the following Govern applications:
DeployEZ, Govern, Govern New Administration (GNA), OpenForms Designer (OFD), Business Entity Designer (BED), Govern Scheduler (GS), Govern Security Manager (GSM), and the Query Tool (QT).

On-line Help

[v6.x] On-Line Web Help
Product on-line Help&Doc Web

[v6.x Beta] Product Knowledge Base access
Access to Product Knowledge Base

Changes to the Help Directory

[Release 6.0.1407] Help is available for the batch processes
To setup:

  1. Standard or Custom Folders
  2. Then a folder “Batch Processes”
  3. Then a folder whose name is the bp name code
[Release v5.1] From Govern Release 5.1 and greater, changes were made to the structure of the Help file directories. The new structure was created to be able to present users with help content in different file formats. Content can include video clips, user system supported file types, custom images, and so on. As with prior versions of the help, the Adobe Acrobat PDF file format is used to distribute the content.
Help content is stored in multiple level directories. All standard content will be deployed as a ZIP archive file. Upon installation, the.ZIP package is then extracted to the Standard directory.

Subject Author Replies Views Last Message
No Comments

 

 

101-std-fea-002

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

ST Late Filing Penalty Method

Business Tax (ST) Late Filing Penalty Method

Overview

This is a new computation method for the Late Filing Levies and the Late Payment feature of Self-Reported Business Tax (ST). This new method was introduced for the current 6.0.1706 and 6.1.1706, 6.1.1707 and greater releases. See below for details about this new method.

Functionalities

The following system and UI changes can be associated with this feature implementation.

System Registry – OpenForms General Settings

There is a new entry under the Self-Reported Tax Registry Filter in the OpenForms General Settings (System registry Registry) form. There is a Force Late Filing Levies Method Date. While the default date of 1/1/0001 is present in the parameter, the Late Filing Levy Method will not be enforced. When any another date is entered, the late filing method will be enforced.

NOTE: Within Govern some settings that appear in the OpenForms General Settings form (SY_REGISTRY), may have other locations that can override the system registry settings form. This location is the only point in which the Force Late Filing Levies Method Date parameter can be overridden.

User Interface (UI)

Category tab – General sub tab

Previously, the Late Filing Penalty and Late Payment Penalty group boxes were hidden conditionally. Entries were required in the A/R Class and Late Payment parameters in order to display the Late Filing group and Late Payment Penalty group boxes respectively. Both groups are now visible.

System Registry – OpenForms General Settings

There is a new entry under the Self-Reported Tax Registry Filter in the OpenForms General Settings (System registry Registry) form. There is a Force Late Filing Levies Method Date. While the default date of 1/1/0001 is present in parameter, the Late Filing Levy Method will not be enforced. When another date is entered, the late filing method will be enforced.

NOTE: Within Govern some settings that appear in the OpenForms General Settings form (SY_REGISTRY), may have other locations that can override the system registry settings form. This location is the only point in which the Force Late Filing Levies Method Date parameter can be overridden.

Late Payment Penalty group

For the Late Payment Penalty group, when there is no A/R Class selected in the combo, the penalty is broken down by A/R Class, i.e. associated with each levy’s A/R class, and the Minimum/Maximum Amount does not apply to the total return, rather, it is per A/R record. The amounts are applied to each penalty record created.

Category tab – Levies sub tab

At the bottom of the Levies sub tab form is the Late Filing Levy combo-box. This parameter is used to link a levy to a Late Filing Levy.

Levies sub tab

In the Computation Method group, the Late Filing Levy combo box is available for all radio button options, i.e. Base X Rate, Fixed Amount, etc. The Late Filing Levy can be linked with the currently selected levy code.

Category tab – Levies sub tab – Computation Method group

In the Computation Method group of the Levies sub tab form is a new Late Filing Levy radio button option. The new Computation Method, when selected, noticeably absent are the Rate Type, Computation Information groups, and the Late Filing Levy combo box.

New Computation Method

When the new computation method, Late Filing Levy is selected, A/R Class must be selected. For this option the only two (2) A/R Classes that can be selected in Invoice (INV) or the parameter field is blank; a blank will also default to invoice.

The new Computation Method called Late Filing Levy when selected, noticeably absent are the Rate Type, Computation Information groups, and the Late Filing Levy combo box.

Business Rules

When a Late Filing levy is being used within the system, should a modification be made to one of the parameters, e.g. Computation Method, and a save is attempted, a warning will be triggered. The warning message will read as, “The following Late Filing Levy cannot change its Computation Method: <methodName>”.

Setup

The setup of a Late Filing Levy follows the same methodology of other standard levies. To associate late filing charges with an existing levy…

  1. Select or create the levy that will be configured.
  2. In the Computation Method group, click to select Late Filing Levy
  3. You will note that the Rate Type and the Computation Information groups will be immediately hidden on the form.
  4. Select an A/R Class; click the ellipsis […] button beside the parameter to open the A/R Class form.
  5. In the A/R Class form, create or select an existing class code.
NOTE: There are only two (2) transaction types that can be selected in the Transaction Type parameter; invoice, i.e. Billed, or leave the parameter blank.

Verify Database Process

As is often the case with a new feature, it is always recommended that administrators run the Verify Database process in the Govern New Administration (GNA). During the process the Verify Database health check will check to see if the SY_REGISTRY default date is being used. When this check has confirmed that the old Late Filing Levies Method is still in use, you will be presented with a warning screen. The screen will link you to the OpenForms General Settings form to change the date in the Force Late Filings Levies Method Date parameter and enable the Late Filing Levy Method.

 

 

101-st-fea-010

 

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

 

Self Reported Business Tax Audit Trail

Self Reported Business Tax Audit Trail

Overview

The purpose of the Self Reported Business Tax Audit Trail feature is to view access and modification information related to the ST account.
information for this feature is obtained from (Table: USR_AUDIT_OPENFORMS)
When the Audit Trail is enabled by an administrator through the GSM, the information that is presented in the columns includes the following:

  • Date – The date of the modification. (Table: USR_AUDIT_OPENFORMS.AUDIT_DATE)
  • User – Name of the user that accessed the account. (Table: USR_AUDIT_OPENFORMS.USER_ID)
  • Action – What action was performed on the account, i.e. Viewed, Created, Deleted, and so on. (Table: USR_AUDIT_OPENFORMS.AUDIT_ACTION)
  • Form – The name of the form that was accessed. (Table: USR_AUDIT_OPENFORMS.FORM_CODE)
  • IP Address – The IP address of the computer that accessed the form. (Table: USR_AUDIT_OPENFORMS.IP_ADDRESS)
  • Computer – The Name, Asset or Service tag of the computer that accessed the form. (Table: USR_AUDIT_OPENFORMS.SOURCE_COMPUTER_NAME)
  • Remote Computer – If the access was remote, the name of the Remote Computer. (Table: USR_AUDIT_OPENFORMS.REMOTE_COMPUTER_NAME)

When viewing a form, the Entity Audit feature can be accessed from the Govern ribbon, View (tab) > Entity Audit
Alternatively the keyboard short-cut (Ctrl + H) may also be used.

NOTE: The audit feature is available for the Tax Account, Tax Filing Master, and the Mailing Index OpenForms in the Business Tax module. In addition the feature should only be accessed by users with Administrator level access as sensitive information is readily visible.

 

See Also

101-std-fea-017

 

 

101-st-fea-017

 

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