SSRS – SQL Server Reporting Services

SQL Server Reporting Services (SSRS)

Version 6.0 & 6.1

Overview

SQL Server Reporting Services (SSRS), is a server-based report generation software system from Microsoft™. SSRS is administered via a web interface, and is used to prepare and deliver interactive and printed reports. SSRS is viewed as an alternative to Crystal Reports or any other tools that are used in gathering business intelligence.

 

NOTE: Govern supports SQL Server 2010 to 2014 for SSRS. SSRS 2016/2017 will not work. Database instances can exist in SQL Server 2016 or greater, but SSRS will need to be on a 2012 or 2014 instance. Users should NOT open SSRS 2014 reports with SSRS 2016 and save them. This will result in an error in GNA and Govern. Additional details can be found at the following link on the Microsoft Developers Network (MSDN)

What’s new

SSRS Report Conversion Tool (301-ssrs-util)

How to Install SSRS

Click here to follow the current instructions on how to install SSRS.

Documentation

Refer to the following user guide(s) for setup and configuration information.
301-(man)-SSRS-v5.1.pdf

Configuration

Refer to the “Configuration in the Govern New Administration (GNA)” section in the “Documentation & Standards SSRS” user guide.
This guide explains the configuration of SSRS in Govern.
Click here to see the General Settings Parameters (SY REGISTRY).

Report Parameters

dept Govern IDs: dept
dept_label Govern IDs: dept long description
language Current application culture
year Govern IDs: Year
rpt_county SY_Registry – SectionName: “General”; KeyName: “county”.
rpt_date String.Format(“{0} {1}”, Date.Now.ToShortDateString(), Date.Now.ToLongTimeString())
rpt_default_date Date.Now.ToShortDateString()
rpt_login Govern IDs: User
rpt_logo USR_Registry – SectionName: “govern”; KeyName: “bitmap”. OR SY_Registry – SectionName: “path”; KeyName: “bitmap”.
rpt_name Report Path
rpt_range Report Range Value (Filter on xyz)
rpt_state SY_Registry – SectionName: “General”; KeyName: “state”.
rpt_title Report Display Name
rpt_ub_max_variation SY_Registry – SectionName: “ub parameters”; KeyName: “Max Variation”.
rpt_uid Govern IDs: User
rpt_username GoverNetConfig.OrganizationName
uniform SY_Registry – SectionName: “work_text”; KeyName: “Assessment Equalisation Rate”.
all_int Call ‘ComputeLateChargesAmountsForArSummary(“na_id”)’ method

 

See Also

301-ssrs-util

 

 

301-ssrs

 

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

MA – M&S Valuation Setting Editor (103-ed-025)

Valuation Setting Editor (Marshall & Swift MVP Interface)

Available in release 6.1.2211 – (In Development)

Overview

Marshall & Swift (M&S) is a cost-based appraisal methodology intended to value buildings and non-buildings improvements using the reconstruction cost method. It comes with two different valuation approaches, one for residential properties and one for commercial ones. This appraisal method is rarely used to produce final values but often used to provide a comparison point with other value types such as comparable sales or market values (MRA). The Marshall & Swift Valuation Platform Online (MSVPO) integrates with Computer Assisted Mass Appraisal (CAMA) systems via web services hosted by CoreLogic®.

Purpose

In Govern for Windows, M&S was offered as a special set of configurations within the Building Structural Element (BSE) function. An interface was developed to periodically load M&S valuation tables within the Govern BSE tables from the M&S database tables.

A different approach has been taken with OpenForms v6.1. In OpenForms, a new M&S API was developed to support the MSVPO interface for both residential and commercial valuations.

M&S In Govern

New admin parameters have been created as well as new database table structures that are specific to M&S. An internal API or data exchange tool will be needed for each Harris Govern product line to read/write the data from/to our product specific format (either in the legacy improvement tables or in new ones).

With the implementation of the new MSVPO API, a conversion tool has been created to convert the legacy M&S data into the new format.

The CoreLogic MSVPO API has been developed by CoreLogic as a public facing Web Service. This MSVPO service has been leveraged for Govern development.

The system defaults are by year and valuation types. As the M&S tables determine the type of computation, residential or commercial, the interface offers two entries, one for the Residential valuation method and one for the Commercial valuation method.

Valuation Settings Editor User Interface (UI)

The Valuation Setting Editor interface is located in the Govern New Administration (GNA)

To access the UI in GNA…

  1. On the GNA ribbon click Editors (tab) > Valuation Settings Editor
  2. The Valuation Settings editor will be displayed.

<–>

Valuation Settings Editor Setup Parameters

Valuation Settings Form – tab buttons

New – Click New to create a new Valuation Setting record.

Save – After completing the required parameters, click Save to save your Valuation Settings.

Delete – Click Delete to delete the currently selected valuation settings record

Refresh – To update the settings in the form with those of the M&S Valuation tables, click Refresh.

Valuation Settings Form – parameters

Description – Enter a descriptive name for the new valuation settings record.

Commercial / Residential – These options refer to the valuation method; select which type of table will be obtained from the M&S tables, e.g., Commercial or Residential.

Years – This column lists the valuation type and corresponding year that are available.

Year – This field that will indicate the year of the currently selected record.

Residence Type – This optional parameter is a drop-down menu that displays the residence types available in the Marshall & Swift (M&S) tables.

NOTE: This parameter is disabled when the valuation method selected is Commercial.

Default Style – When a Residence Type is selected, all possible styles will be displayed.

NOTE: This parameter is disabled when the valuation method selected is Commercial.

Valuation Date – All valid valuation dates will be displayed in this drop-down menu

Base Date – Select a Base Date from the date picker; this is a value that is less than or equal to the Valuation Date. The default is the Valuation Date.

Multipliers (group)

The local multiplier adjusts the calculated costs to the location of the building. Commercial Estimator automatically uses a local multiplier based on the ZIP or Postal Code entered on the General Information screen.

Local Multiplier – Enter a value to set the Local Multiplier; this parameter accepts values between 0.10 and 3.00.

Local Multiplier Adjustment Percentage – The Local Multiplier Adjustment is used to increase or decrease costs for unusual situations, such as remote locations, resort locations, shortages, surpluses, and so on. Enter a positive or negative percentage to increase or decrease the local multiplier. Accepted values are -50.00 to 200.00

Regional Multiplier – Accepted values for this parameter are 0.10 to 3.00.

NOTE: This parameter is disabled when the valuation method selected is Commercial or when the Regional Multiplier parameter is not set.

Manufactured Home Mult. Type (group)

Manufactured homes are residential structures built on steel undercarriages with necessary wheel assemblies to transport them to permanent or semi-permanent sites.

Use Regional Multiplier / Use Local Multiplier – Select either Use Regional Multiplier or Use Local Multiplier.

NOTE: This parameter is disabled when the valuation method selected is Commercial.

Effective Age Adjustment Value – When entering an Effective Age Adjustment Value, accepted values are 0 – 20.

Rounding Value – Accepted Rounding Values are 0 – 1000000.

Architect Fee Percent – Valid values for the Architect Fee Percentage is 0.00 – 100.00.

Depreciation Percent Adjustment Value – Refer to MPV Commercial 2.1.3 & 8.6.3 and MPV Residential 2.1.4 & 7.8.3 for more information.

US Localization Type (group)

Select one of the available three (3) options, 3-digit only, 5-digit only, or 5-digit or 3-digit.

Depreciation Percent Apply Flag – Select True or False ; See MPV Commercial 8.6.2 and MPV Residential 7.8.2 for details

Depreciation Maximum Percent – Refer to MPV Commercial 2.1.3, 8.6.3 & 8.6.4 and MPV Residential 2.1.4 & 7.8.4 for details.

Section Depreciation Maximum Percent – See MPV Commercial 2.1.3, 8.6.3 & 8.6.4 and MPV Residential 2.1.4 & 7.8.4 for details.

Zone Information Adjustment Override (group)

NOTE: The Zone Information Adjustment Override frame is only available when the valuation method selected is Residential.

Target Zip Code – Enter the zip code of the required area on the M&S table.

Energy Zone – Select an Energy Zone, e.g., Moderate.

NOTE: This parameter is enabled only if a Target Zip or Postal Code has been entered.

Foundation Zone – Select a Foundation Zone.

NOTE: This parameter is enabled only if a Target Zip or Postal Code has been entered.

Hillside Construction – Choose a value from the drop-down menu; e.g., Flat.

NOTE: This parameter is enabled only if a Target Zip or Postal Code has been entered.

Seismic Zone – Choose a value from the drop-down menu.

NOTE: This parameter is enabled only if a Target Zip or Postal Code has been entered.

Wall/Energy Zone – Select a Wall Energy Zone code; e.g., 2×4 Base Cost.

NOTE: This parameter is enabled only if a Target Zip or Postal Code has been entered.

Wind Zone – Select a Wind Zone code.

NOTE: This parameter is enabled only if a Target Zip or Postal Code has been entered.

Documentation

When documentation is available click here to view it.

GNA Product Map

 

 

103-ED-025

 

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

Generic Import Editor (103-ed-024)

Generic Import Editor

Available in release 6.1.xxxx – (In Development)

Overview

The Generic Import Editor is a GNA Editor that will allow users to import

The function of the Generic Import Editor is as follows:

  • Allow import definitions to be stored in a configuration
  • Allow imports to be tracked and monitored from a single location.
  • Allow imports to be created faster with minimal coding required.
NOTE: This editor maintains records found in (Table: VT_USR_IMPORT_DEF).

Generic Import Editor Setup Parameters

T/C

 

GNA Product Map

 

 

103-ED-024

 

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

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

SSRS – SQL Server Reporting Services Report Conversion Tool

SQL Server Reporting Services Report Conversion Tool

Version 6.1

Overview

The SSRS Report Conversion tool is a Windows application developed to assist, with some minor manipulations, the conversion of a .rdl report for use in the latest versions of Govern and GNA.

User Interface

When initialized, the SSRS Report Conversion Tool displays as a utility window with input and output parameters.

 

SSRS Report Conversion Tool Parameters

Input Folder – Click to manually type in the path to the Input folder. This is the path to a physical folder that must contain at least one .rpt file that is to be converted.

[…] Select Folder – Click the ellipsis button […] to navigate to the required folder.

Output Folder – This non-editable parameter contains the path to the folder that the converted reports will be placed. This is always a folder named Converted that will be located under the Input Folder path.

Recordset – This combo-box is a GovernId that will be used to group records in Govern. This should be the same GovernId that is configured for the Profile that will be using the SSRS report.

Convert – Click Convert to run the conversion process.

Files to process: – The Files to process area will display all reports within the Input Folder. After a click on Convert, the report names with their status will be listed along with an indication as whether files were converted successfully, or if any issues were encountered during the process.

About the Conversion Process

Users should note the following about the conversion process:

  • The original .rdl file will not be modified.
  • The output file will always add the Parameters SERVER, DATABASE.
  • The parameters RECORDSET_{GOVERNID} will be added if the value for RecordSet is not empty.
    • For example, if the selected value is p_id, the parameter to add will be RECORDSET_P_ID.
  • The datasource connection string will be overridden with the following:
    =”Server=”+ Parameters!SERVER.Value +“;Database=” + Parameters!DATABASE.Value
  • The reports generated in the Output folder are the ones that should be submitted/replaced in the SSRS Server Folders.

 

See Also

301-ssrs

301-ssrs-changes

 

 

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

WM – System Architecture

Workflow Management – System Architecture

Version 6.1 Module (In Development)

Overview

The following provides architectural information on the new Workflow module.
Intended for a technical audience: developers, testers, technical services, customer support and system administrators.

System Database Tables

The main tables used in workflow management are prefixed with WM.

Parameter Tables

  • Prefixed with WM_PARM and include KIND, CATEGORY, DEPARTMENT, TYPE, ACTIVITIES …

Data tables

  • Master Tables are WM_LINKED_IDS and WM_MASTER for all workflow
  • WM_KIND_(kind code) for information related to this kind of workflow
  • WM_CATEGORY_(cat code) for information related to this kind and category workflows

System Dictionary

The added field description for each kind and category combinations are recorded in the system dictionary table (sy_dict_desc).

Developmental Changes

WM_PARM_TYPE.ALLOW_MULTIPLE_TYPE has been renamed to WM_PARM_TYPE.ALLOW_REUSE (Default Value = -1)
Implication: Type name can be reused in a different location, all other functionalities remain the same. N.B. Change 2016.09.22

Database Diagrams

For more information, see WM System Tables and Visio Database Diagrams.

Workflow Linked to…

Workflow items can be linked to:

  • Other Workflow types (was —> pm_lk_permit_type, pm_lk_pm_type_A-AL-B-BL-BN-CO-D-E-G-L-LP-OF-P-PA-PN)
  • Buildings (pm_lk_permit_bldg)
  • Miscellaneous Billing Account (PM_LK_MISC_PERMIT)
  • Self-Reported Tax Account (pm_lk_st_keys)
  • Utility Billing Account (pm_lk_ub_permit)
  • Personal Property (to verify)
  • Submissions (pm_lk_subm)
  • Project / Folio (to verify)
  • Conditions (pm_lk_conditions)
  • Events (pm_lk_events) – assigned to usr_id

Workflow is linked to names:

  • Names (pm_lk_permit_name) by Link Type
  • Different Names can be linked to workflow:
    • Applicant
    • Inspector
    • Owner
    • Other
    • Name Group (Contractors….)
  • AR Link Name is specified by Kind & Category
    • Owner
    • Contractor ACH & Bonds …
  • Default Applicant Name Type for Applicant
    • Owner….

Inspections can be linked from:

  • Complaints (pm_lk_insp_co)
  • to be developed – Phase 2

Visio Diagrams

See Generic page for Govern Database Diagrams (100-database_diagrams)

Version 6.1 (Release 1706)
For Version 6.0 and Govern for Windows 10.8, the only differences are 2 fields added in PM_TYPE

101-wm-system

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