SSRS – Changes to Handling of SSRS Reports (301-ssrs-util)

Changes to Behavior of SQL Server Reporting Services (SSRS)

Version 6.1.2206.0142 / 6.1.1811.2019

Overview

The following contains a description of the changes to the behavior of the SSRS feature in Govern

New Features and Changes in Behavior

Parameter Setup Changes

Users should note that parameters are no longer setup in the Reports Parameters screen. This screen will display only the run options that have been configured in GNA.

Possible “Run on” options that can be displayed are as follows:

On Database – Is configured to do not pass any record that is listed in the Govern Dataset Treeview.

On Recordset – Select this option when the SSRS report is to process a set of records. *

On Current Record – Select this option when the SSRS report is to process the current record.*

Changes related to Recordsets

The Recordsets created by the On RecordSet and On Current Record options come from the DataSet Treeview and are saved into the database (Table: USR_SAVED_DATASETS).
These records are grouped by the field SAVED_SET_NAME with a name like: SSRS_REPORT_GUID, where the GUID is a random GUI text generated at runtime.

Since these new recordsets are temporary, they are automatically removed each time a new SSRS report is executed. The criteria for removal is determined by confirming that SAVED_SET_NAME is like SSRS_REPORT_GUID and the field LAST_MODIF_DATE is older than the day before the current execution. For example, if a report execution is done on 08/10/2022, then all reports created before 08/09/2022 will be removed.

Note the following:

  • The Output tab with the report result is no longer displayed for SSRS reports.
  • The report result will be displayed directly on the default browser pointing to the SSRS server that has been configured for Govern.

New Online SSRS Viewer

In the new online SSRS viewer, the end user must perform the following actions to get the Report.

  1. Select/full fill the Report Parameter fields with the desired values for the report.
  2. Click the View Report button.
  3. A preview for the report will be displayed in the bottom.

To download the report, the user must select any of the output formats for the report with a click on the Save button.

To print the report

  1. Click the Print icon.
  2. The report will not be modified and will be copied into the TEMP folder, but in order to execute the report, it will keep looking in the Custom and Standard folders configured in the GNA settings.

 

NOTE: The appearance of the online SSRS screen can vary depending on the SSRS report version installed on the end users server.

This screen will display only the parameters configured as Visible on the report. Hidden parameters are not displayed here and must be configured in GNA under the parameters section in order to map a Govern Id value to them.

Considerations when running an SSRS report

  • At least one Run on option must be selected to run the report.
  • Reports created or edited in Report Builder 3.0 (2014), and the New SSRS Report Builder (2016), are supported and will be executed in Govern.
  • The report must have the SERVER and DATABASE parameters, where the parameters must be configured as:
    • The very first parameters in the report parameters; this because they will be used to configure the datasource.
    • The parameter visibility can be configured as Visible, or Hidden (this is the preferred value).
    • These parameters will be mapped by Govern with the name and database that are to be used to process the report.
    • The DataType must be ‘Text‘.
  • For the options On Recordset and On Current Record,  the report must have a parameter like RECORDSET_{GOVERN_ID} where:
    • {GOVERN_ID} is the Govern ID that will be used to filter the records.
      For example: if the Govern profile that will use the report is configured to use Parcel Ids, then the name for the parameter will be RECORDSET_P_ID.
    • The DataType must be ‘Text‘.
    • The parameter visibility could be configured as Visible, or Hidden (this is the preferred value).
    • A new recordset entry will be created with a dataset name like SSRS_REPORT_{GUID} to store the GovernId, or set of GovernIds that will be used for the operation.
    • These datasets will not be visible to the user in Govern in the Saved Dataset(s) screen.
    • These datasets will be automatically removed from the database after 2 days, upon the next SSRS report execution.
  • The new SSRS report functionality is no longer creating copies in the TEMP folder that is configured in GNA. As a result of this change, it means that the new version is no longer supporting:
    • Add filters on execution time.
    • Display the report output or parameters at govern.

In order to create/add these parameters the SSRS Converter Tool can be used to convert the rdl reports.

See Also

301-ssrs

301-ssrs-util

 

 

301-ssrs-util

 

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 Database Diagrams and Tables

Govern Database Diagrams and Tables

Govern for OpenForms Release 6.x

The following are the current database diagrams for Govern OpenForms modules. These files are presented in .PDF format for easy viewing.

Available Modules:

Read More...

Land Management 6.1

LandManagement61.pdf

 

UPDATED! Land Management 6.0

101-lm-LandManagement60.pdf

 

UPDATED! Workflow Management 6.1

101-wm-Workflow61.pdf

 

Mass Appraisal (MA)

101-ma-Mass Appraisal 61.pdf

 

Miscellaneous Billing (MB) 6.1

Miscellaneous Billing 61.pdf

 

Name & Address (NA) 6.1

Name and Address 61.pdf

 

Personal Property (PP) 6.1

Personal Property 61.pdf

 

Personal Property / Motor Vehicle / Business Tax

(Updated 2017.06.12)

101-tx-PP MV BT and AR 61.pdf

 

Accounts Receivable (PP / MV / BT / AR) 6.1

PP MV BT and AR 61.pdf

 

Property Control (PP) 6.1

(Updated 2016.12.06)

101-pc-Property Control 61.pdf

 

Security 6.1

Security61.pdf

 

Self Reported Tax and Accounts Receivable (ST & AR) 6.1

(Updated 2017.06.12)

101-st-Self Reported Tax 61.pdf

 

Tax and Accounts Receivable (Tax & AR) 6.1

(Updated 2017.06.12)

101-tx-Tax and AR 61.pdf

 

Utility Billing and Accounts Receivable (UB & AR) 6.1

(Updated 2017.06.12)

101-ub-UtilityBilling and AR 61.pdf

 

Workflow 6.1

(Updated 2017.08.01)

101-wm-Workflow Management 61.pdf

 

Audit

Audit.pdf

 

Delinquency (DC) 6.1

(Updated 2017.06.12)

101-DC-Delinquency and AR 61.pdf

 

NEW! OpenForms Designer (OFD) and Business Entity Designer (BED)

101-std-OFD and BED61.pdf

 

Govern for Windows (VB6)

The following are the current database diagrams for Govern for Windows (VB6) modules. These files are presented in .PDF format for easy viewing.

NOTE: For information only. Source 10.5 Govern for Windows.

Available Modules

Read More...

Land Management (LM)

101-wm-LandManagementVB6.pdf

 

Mass Appraisal (MA)

101-ma-MassAppraisal VB6.pdf

 

Property Control (PC)

101-pc-Property Control VB6.pdf

 

Self Reported Tax / Accounts Receivable (SRT & AR)

101-st-SRT and AR VB6.pdf

 

Personal Property / Motor Vehicle / Business Tax /
Accounts Receivable (PP / MV / BT / AR)

101-tx-PP MV BT and AR VB6.pdf

 

Tax and Accounts Receivable (Tax & AR)

101-tx-Tax and AR VB6.pdf

 

Utility Billing and Accounts Receivable (UB & AR)

101-UtilityBilling and AR VB6.pdf

 

Security

101-std-Security VB6.pdf

 

List of Changed Tables

UPDATED! The following is a list of tables that are present in each of the major releases of Govern, i.e. Govern for Windows (VB6), Govern for OpenForms Release 6.0 and 6.1. This .PDF file lists which tables have changed between the three (3) aforementioned releases.

Click to view the “GovernTableChanges_2020.08.27.pdf” document or download the document

NOTE: The above list is not exhaustive; it does not provide a complete breakdown of changed columns or their functionalities. Table details may be found through the GovernDB page in Confluence.

 

Videos

Webinar – Govern for Windows Dataflow (Internal Access)

Govern for Windows Dataflow Webinar Click to view the recording

(Recorded – Dec. 16, 2016)

Red_Play_Button

Related Topics

 

 

100-Database_Diagrams

 

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

 

GNA Conversion MA Tables

(GNA) Conversion – Mass Appraisal Tables

Overview

A conversion is required for clients upgrading to Govern OpenForms, version 6.1 from an earlier release version of Govern for OpenForms, or from Govern for Windows. This upgrade is due to changes that have been made to the structure of the Govern Database. See Govern Database Diagrams – Refer to the List of Changed Tables section

 

 

103-ma-cvt-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...

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

100-ChangesDBStructure

Changes in Database Structure

Version 6.0 and 6.1

Overview

Standard Functions and Features

System and User Validation Tables

Version 6.0 and 6.1

  • Changes to VT_USER and VT_SYSTEM tables. System and User Tables are now validated and compared against the standard structure XML file.

 

Read More...

Userfile

Version 6.0

  • New GLOBAL KEY to allow us to link Workflow and global messages to users.
    • U_ID field added to USR_USERFILE.

User Profiles

Version 6.0.1412

  • Fields removed from USR_PROFILE
    • ORG_NBR
    • GROUP_CODE
    • JURISDICTION_CODE
    • OWNER_MM
    • OWNER_YY
    • NB_REC_WARN
    • NB_MIN_ROLLBACK

Roll Forward Exclusion Tables

Version 6.0

  • New tables added to support the roll forward exclusion of fields.
    • SY_ROLLFORWARD_EXCLUSION
    • SY_ROLLFORWARD_EXCLUSION.TABLE_NAME [PK]
    • SY_ROLLFORWARD_EXCLUSION.COLUMN_NAME [PK]

User Audit Trail New Tables (3)

Version 6.0 – see User Audit for more info [std-fea-017]

  • USR_AUDIT_OPENFORMS
    • AUDIT_ID
    • AUDIT_ACTION
    • ENTITY_ID
    • FORM_CODE
    • USER_ID
    • AUDIT_DATE
    • IP_ADDRESS
    • SOURCE_COMPUTER_NAME
    • REMOTE_COMPUTER_NAME
  • USR_AUDIT_OPENFORMS_CHANGE
    • AUDIT_ID
    • ATTRIBUTE_ID
    • TABLE_NAME
    • COLUMN_NAME
    • OLD_VALUE
    • NEW_VALUE
  • USR_AUDIT_OPENFORMS_KEY
    • AUDIT_ID
    • ATTRIBUTE_ID
    • KEY_NAME
    • KEY_VALUE
    • IS_PRIMARY_KEY
NOTE: The legacy table USR_AUDIT_TRAIL will be kept for modules running in prior releases, but developers should note the new modifications and table structures impact for custom processes.

Property Control (PC)

PC Parcel

Version 6.1

  • NON_PARCEL_FLAG and VIRTUAL_PARCEL cannot be set to null.

PC Sales
Version 6.0

  • PC_SALES is no longer used, only MA SALES

Accounts Receivable & Cash Collection (CC)

Version 6.0

Payer Name

  • PAYER_NAME added to CC_MASTER (name was previously kept in CC_MASTER_NOTES) – 6.0 and 6.1

Mass Appraisal (MA)

For the specification document, click on Appraisal Detail Specification for listing.

Building Changes

Version 6.1

  • Current_P_ID was added to MA_BUILDINGS
  • VT_SY_DRAWCMD is no longer used

Site Changes

Version 6.1
Site changes to support new override methodology

  • These columns were added:
    • LAND_VALUE_OVERRIDE (money)
    • LAND_AG_VALUE_OVERRIDE (money)
    • BLDG_VALUE_OVERRIDE (money)
    • MISC_VALUE_OVERRIDE (money)
    • INCOME_GRM_VALUE_OVERRIDE (money)
    • INCOME_DIR_VALUE_OVERRIDE (money)
    • MRA_VALUE_OVERRIDE (money)
    • PP_VALUE_OVERRIDE (money)
  • These columns were dropped : (No longer used in v6.1)
    • TEMPLATE_CD
    • TEMPLATE_VA
  • A misc. correction script was added to move :
    • LAND_VALUE to LAND_VALUE_OVERRIDE when LAND_OVERRIDE = -1
    • LAND_AG_VALUE to LAND_AG_VALUE_OVERRIDE when LAND_AG_OVERRIDE = -1
    • BLDG_VALUE to BLDG_VALUE_OVERRIDE when BLDG_OVERRIDE = -1
    • MISC_VALUE to MISC_VALUE_OVERRIDE when MISC_OVERRIDE = -1
    • INCOME_GRM to INCOME_GRM_VALUE_OVERRIDE when INC_GRM_OVERRIDE = -1
    • INCOME_DIR_VALUE to INCOME_DIR_VALUE_OVERRIDE when INC_DIR_OVERRIDE
    • MRA_VALUE to MRA_VALUE_OVERRIDE when MRA_OVERRIDE = -1
    • PP_VALUE to PP_VALUE_OVERRIDE when PP_OVERRIDE = -1
  • A misc. correction script was added to move :
    • All XXX_VA values to XXX_OV_VALUE when XXX_OV = -1
    • – XXX_OV_VALUE should be created as well.

Income Changes

Version 6.1
Income changes to support new override methodology

  • These columns were added in MA_Income.
    • Building_Value_Override
    • DIR_Rate_Amount_Override
    • GRM_Rate_Amount_Override
    • Gross_Effective_Override
    • Gross_Rent_PCT_Override
    • Gross_Rent_Value_Override
    • Land_Value_Override
    • Misc_Value_Override
    • Net_Dir_Override
    • Net_GRM_Override
    • Net_Value_Override
    • Rent_Units_Override
    • Vacancy_PCT_Override
    • Overall_ADJ_VAL_Override
  • These columns were added in MA_Income.
    • Ma_Income_Group

Income changes to support new calculation method and configuration

  • Income Fields added
    • Ma_Income_Record_Type
  • Income Table added
    • For Added Fields – to be validated

 

Miscellaneous Billing

Available in GA Release 6.1.1606
To offer more flexibility, the misc. billing parameters are now year base.
As such the YEAR_ID was added to the following tables:

  • MB_INVOICE and MB_INVOICE_DET
  • MB_RECURRING and MB_RECURRING_DET

In prior versions, only the AR Class Code was used for the invoice and invoice detail. To simplify data entry and offer more flexibility, the following tables were added.

  • MB_PARM_CATEGORY (contains a category that will be used to link the detail invoice items)
  • MB_PARM_ITEM

New Database Fields

  • LAST_RECUR_DATE was added to the MB_INVOICE_REC table
  • BATCH_ID was added to the MB_INVOICE table

Self Reported Business Tax (ST)

When the fields for ST forms are created, the following USR_FIELDS_XXXXX tables, are no longer used.

  • USR_FIELDS_DEF
  • USR_FIELDS_LABEL
  • USR_FIELDS_MASK
  • USR_FIELDS_NUMERIC_FORMAT (Added for 6.0 and 6.1)
NOTE:The data in the above have been copied to (Table: ST_PARM_CATEG)

New Field added in ST_MASTER

  • NAICS (Varchar 15) MANDATORY when using Estimated Filings.
NOTE: This field is now a Standard System Field and may need to be converted if it was created as an Added Field.

New Tables added for Estimated Filings

  • ST_ESTIMATE_ID

New Table added for Corporate Account

  • ST_CORP_ACCOUNT

Name and Address (NA)

For ACH processing and field encryption, the following changes have been made:

  • NA_ACH_INFO.ACH_DESC (new field)
  • NA_ACH_INFO.BANK_ACCOUNT_NO (new field length = 44)
  • NA_ACH_INFO.TRANSIT_NO (new field length = 32)

OpenForms Tables

Version 6.0

Tables Removed from versions: 6.0.1411.0106 and 6.1.1411.0106
1. OF_SE_APP_TYPE replaced by an object in memory
2. OF_DE_MODELCONTENT was used only for MOD
3. OF_MD_UPDATER was used only for MOD
4. OF_LK_PROFILE_OF1 was used only for MOD to establish the link with a profile.

Tables Removed from versions: 6.0.1411.0017 and 6.1.1411.0021
The tables defined in MSGDatanaseStructMods.xml (so also in OPENFORMS_REFERENCE_60):

  • 1. OF_BE_MAPEXPR
  • 2. OF_BE_MAPTYPE
  • 3. OF_BE_NAVIGATION
  • 4. OF_BE_SERIALIZATION
  • 5. OF_BE_VALRULE_ATTB
  • 6. OF_BE_VALRULE_PARM
  • 7. OF_CTRL_TO_COLUMN
  • 8. OF_LK_ATT_VALRULE
  • 9. OF_MODEL_PERSONALIZATION
  • 10. OF_SE_ACCESSRIGHTS (notion still useful but the table has been replaced by an enumeration in the code)
  • 11. OF_SE_AUDIT
  • 12. OF_SE_LK_ROLE_USER
  • 13. OF_SE_USER_EXCL
  • 14. OF_UI_MAPTABLE (notion still useful but the table has been replaced by CLR objects in the code)

Release 5.x

Version 5.x

  • PC_LK_PARCEL has been replaced with PM_LK_MASTER

See Prior Database Changes (ref. v6.1.1508)

Related Topics

Govern Database DiagramsRefer to the List of Changed Tables section

 

 

100-ChangesDBStructure

 

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