RE – Capping Rates

Capping Rates

Overview

Some municipalities will limit annual increases in assessed value of property with Homestead Exemption to a set percentage or the change in the Consumer Price Index, depending on whichever is lower. This will ensure that no assessment, will exceed the current fair market value. In some instances, this limitation will only apply to property value, not property taxes. As a result, Cap and Exemption are removed at the end of the calendar year if the property has been sold. Taxes are then calculated on the full Just/Market Value. As a result, the property will benefit from the limitations of the Cap in the second year of the new owner’s Homestead Exemption.

For example, if a property owner applies for and receives Homestead Exemption for 2022, the Assessed Value will be capped in 2023. In this instance, when determining Taxable Value, exemptions are subtracted from the Assessed Value to reach a Taxable Value. The Taxable Value is then multiplied by the annual Millage Rate to determine the amount of tax due.

In some instances, a change in property ownership will reset the Capped Value to full market value. As a result, it is important to know that property taxes will increase the following year as the assessed value must be adjusted to equal the current market value.

This can mean that an increase due to the removal of the Cap may result in the doubling or even tripling of taxes, depending on how long the previous owner had an exemption.

NOTE: Refer to the rules for Capping and Exemptions in your municipality.

Configuration

NOTE: The following configuration can only be carried out by users with Administrator access rights.

Configuration of the capping rates occurs in two (2) locations in the Govern New Administration (GNA).

Codes will need to be set up through the User Validation Table editor. These codes are used to populate the Code column in the Capping Rates editor.

User Validation Table Setup

The User Validation Table editor is accessed in the Govern New Administration (GNA).

To configure the codes for the user validation table …

1. Open the GNA.

2. Click Editors (menu) > User Validation Table Editor > Tax Billing.

3. In the (Tax Billing) User Validation Table Editor, click New to create a new table.

4. Enter CAPPING_RATE as the Table Name.

5. Enter a Description.

6. Click Codes to create the codes that will be in the table.

For Example:

In a municipality where the two required codes are Non Save Our Homes (NSOH), and Save Our Homes (SOH), these codes will need to be created.

7. Click Create New Item.

8. Enter SOH as the Code.

9. Enter a Short Description of Save Our Homes, and a Long Description.

10. Click Save.

11. Repeat the above step to create another code for Non Save Our Homes (NSOH).

12. Click Save to save this record and close the editor.

Now that the codes required for the Capping Rate have been created in the user validation table, they can be accessed in the Capping Rates editor.

Capping Rates Editor

The Capping Rate editor is accessed in the Govern New Administration (GNA).

To access the Capping Rate Editor…

  1. Open the GNA.
  2. Click Applications Configurations (Menu) > Real Property > Capping Rates.
  3. In the Capping Rates editor, click New to create a new line record.
  4. Enter the Year.
  5. Select the applicable Code from the combo box.
  6. Enter a capping rate percentage (%) under the Rate column.
  7. Click Save to save the record.

 

 

103-re-parm-CappingRates

 

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

Rounding Value – Accepted Rounding Values are 01000000.

Architect Fee Percent – Valid values for the Architect Fee Percentage is 0.00100.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 PercentSee 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...

Batch Process Definition Setup V5

Batch Process Definition Setup – Version 5

Version 6.x | Version 5 and lower

Overview

The GNA Batch Process Definitions form is used to define how you want your batch processes to appear and run in Govern. This includes setting up the menus and submenus for organizing your batch processes, configuring whether each process is run on a single server or on multiple servers, associating one or multiple reports, and synchronizing the batch process definitions and adding permissions. When complete, the batch processes are displayed in Govern.
This procedure has two major steps:

  • Configuring Batch Process Definitions
  • Adding Batch Processes Definition to Govern.

 

Read More...

 

Configuring Batch Process Definitions

Configuring Batch Process Definitions describes the following topics:

Batch Process Definitions User Interface

This section provides a tour of the Batch Process Definitions UI. The interface is comprised of a treeview, the definition form, and a secondary window for creating the menus and submenus or categories.
To access the Batch Process Definitions form:

  1. Launch Govern New Administration (GNA).
  2. Select Batch Process > Definitions.

Once you create menus and define batch processes, the selected items are listed in a treeview on the left of the form. You can display or hide the treeview according to your preference.

About Batch Process Definitions

You can view, add, or modify a batch process definition, as described later in this section.
To display or hide the English and French long and short descriptions, click on the arrow beside the text box at the top of the form.

About the Menu Manager

The Menu Manager form is used for creating the menus and submenus for organizing your batch process definitions in Govern.NET.
To access the Menu Manager

  1. Launch Govern New Administration (GNA).
  2. Select Batch Process > Definitions.
  3. Click the ellipsis button beside the Category text box.

If categories are already created, they are listed on the left. You can expand a category to view secondary levels if they exist. The name of selected menu is displayed on the right. You can expand the name to view the English and French short and long descriptions.

Creating a Batch Process Category

The first step is to create categories for your batch processes. The categories are used for displaying the batch processes in the Govern .NET menu. Create as many categories as required in order to facilitate user input.
To create a Batch Process:

  1. Launch Govern New Administration (GNA).
  2. Select Batch Process > Definitions.
  3. Click the ellipsis button beside the Category text box. This opens the Menu Manager.The Menu Manager is used for creating categories for the batch processes. You can have multiple levels. For example, you could group batch processes by module, such as: Accounts / Receivable, Tax Billing, and Mass Appraisal. Then, you could add another level that groups processes according to when they need to be run; i.e., daily, monthly, or yearly. You can create any type of category that is useful for your organization.
  4. Enter a name for the category in the text box at the top right. This is automatically added to the English Long Description field.
  5. Click the button to the left of the text box where you entered the category name. This expands a menu with additional descriptions.
  6. Add an English Short Description and French Short and Long Description as required. These fields are optional.
  7. Click Save to add the category to the menu.

If you click the Select button without saving your new category, a confirmation message appears:

Deleting a Menu Category

To delete a menu category from the Menu Manager:
1. Launch Govern New Administration (GNA).
2. Select Batch Process > Definitions.
3. Click the ellipsis button beside the Category text box to open the Menu Manager.
4. Expand the applicable menu.
5. Select the category from the Menu list on the left.
6. Click the Delete button in the menu at the top right.
7. When the confirmation message appears, click Yes to delete the record.

Selecting a Category for the Batch Process

You need to define the processes under the categories to which they are assigned and will appear in Govern. Before defining a batch process, select the menu category where it will be saved.
To select a Batch Process:

  1. Launch Govern New Administration (GNA).
  2. Select Batch Process > Definitions.
  3. Click the ellipsis button beside the Category text box to select the category for the batch process. This opens the Menu Manager.
  4. Expand the root menu to display the submenus.
  5. Select the applicable submenu or category.
  6. Click the Select button .

The root menu and all submenus are displayed in the Category text box and in the Parent Path text box. The existing batch processes are listed on the left.

Defining a Batch Process

Use the following process to name the definition and to associate it with a Govern Batch process.

NOTE: You need to define the processes under the category to which they are assigned and will appear in Govern.

To define a Batch Process:

  1. Select the category where you are defining the process as described under Selecting a Category for the Batch Process. The batch processes already defined for the category are displayed in the treeview on the left.
  2. Click the New button.
  3. Enter a code for the new batch process definition. This is a required field.
  4. Select a Govern batch process from the Process drop-down list. This is a required field.
  5. Enter a name for the record in the text box at the top right. This is automatically added to the English Long Description field.
  6. Click the button to the left of the text box where you entered the name. This expands a menu with additional descriptions.
  7. Add an English Short Description and French Short and Long Description as required. These fields are optional.
  8. Click the Save button to add the category to the menu.
    If you click the New button without saving your modifications, a confirmation message appears:

Defining the Transaction Type
The Govern batch processes can be run synchronously or asynchronously. If they are run synchronously, they are run on the same server. If run asynchronously they are run on multiple servers at the same time.
Select Synch or Asynch as required. For processes with multiple transactions, it is recommended to use asynchronous processing as this spreads the load over multiple servers and makes for faster processing time.
Pool #: For Asynchronous processes only, enter the maximum number of transactions to be handled by the client servers at any one time.
This works as follows: If you are running asynchronous batch processing, there is one master server that manages all the transactions and is responsible for sending them to the client servers. The value In the Pool # field indicates the maximum number of transactions to send out by the master server at any one time.

Scenario: Running a Batch Process Asynchronously
The following scenario illustrates how asynchronous batch processing works.
The parameters are as follows:

  • Master server: one
  • Client servers: five
  • Transactions: 50,000
  • Pool #: 50

The master server sends out the first 50 transactions to the client servers. Each server is responsible for ten transactions. As soon as a server completes one transaction, the master server sends it another. This continues until all transactions have been processed. However, there are never more than 50 transactions being handled by the client servers at any given time.

Defining the Transaction Mode

Select one of the following transaction modes for the process.

  • Break If One Transaction Failed: the process terminates when the transaction fails.
  • Roll Back If One Transaction Failed: the process terminates when a transaction fails and all the transactions that were completed are cancelled. Computations are returned to the starting point.
  • Continue If One Transaction Failed: Continue to run the process even if a transaction fails.

Adding a Report

Use the following procedure to associate one or more reports with the selected batch process.
To add a report: to the batch process:

  1. Launch the Batch Process Definitions form.
  2. Select the category for the process as described under Selecting a Category for the Batch Process.
  3. Select the batch process from the treeview on the left.
  4. Click Add Reports.
  5. Select one or more reports from the Choose the Reports menu.
    TIP: You can select multiple reports using the left mouse button.
  6. Click Select Reports.

The selected reports are displayed in the List of Reports text box. The parameters for the report are displayed in the Report Parameters list box.
The List of Parameters text box displays the parameters that can be included in the report and that can be used to build an external report; for example, these could include Date To and Date From fields. The purpose is to give you the exact reference and wording of these fields.

Deleting a Batch Process Definition

To delete a batch process:

  1. Launch the Batch Process Definitions form.
  2. Select the category for the process as described under Selecting a Category for the Batch Process.
  3. Select the batch process from the treeview on the left.
  4. Click the Delete button .

 

Adding Batch Processes Definition to Govern

When you have defined your batch processes, you need to add them to Govern.NET. In order to do this, you need to launch the Govern Security Manager and synchronize your new processes between GNA and Govern. Then, you need to assign access permissions.

Synchronizing Batch Process Definitions

When you have synchronized your new batch process definitions, they appear on the Govern.NET menu.
To synchronize the new batch processes:

  1. Launch the MSGovern Security Manager (GSM).
  2. Select your database connection key.
  3. Right-click on Applications and select Synchronize menu from the dropdown list. A confirmation message appears.
  4. Click Yes on the confirmation message.

Permissions and Batch Processes

Use the following procedure to assign access permissions to the new batch process definitions. You can grant permissions by batch process, batch process menu, or by batch process definition.

  1. Launch the MSGovern Security Manager (GSM).
  2. Select your database.
  3. Expand Applications > MSGovern.NET > Batch Process > Batch Process.
  4. Continue to expand the menus until you are the level where you want to grant permission.
  5. Right-click on the item that you want to secure.
  6. Define the permissions and exclusions as required and as described in the Govern Security Manager.

See Also

Govern New Administration (GNA)

 

 

103-ed-013-v5

 

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 – Email Template Editor

Email Template Editor

Version 6.1 (1706)

Overview

The Email Message Template editor is designed for creating email message templates. These are the messages that can be used in Govern modules that offer an email functionality. For example, in the Workflow module there is an email activity function that when triggered can send a notification email message to specific users or groups. The advantage of the Email Template Editor is the ability for users to use variables and Expressions to modify specific fields. When the email message is sent, it can also be configured to include a report.

 

Read More...

Functionality

When created and configured in the OpenForms Designer, an email template can be launched from a form tab. In addition the email template can be configured as an activity action in the Workflow module. In the GNA Email Template editor, there are sub tabs, one of which allows users to preconfigure their email messages. The Predefined tab contains the list of predefined recipients of the email message. The TO field on the editor is a freeform field that allows the user to enter any email address. You are able to add recipients from the list of Govern Users or Govern Roles as they appear under the Predefined tab. An additional support function is that Email templates generated by the editor can be invoked through a Batch Process.

For more information, see:

Configuration

A recommended methodology for correct implementation is to take the following steps:

1. Design or Select an Email Template

Determine the format that your email message will take in the GNA Email Template Editor. In the Parameters Expression field, build the expression that will be used to extract the parameters needed for your email message. For example a message that is pertaining to overdue accounts might require some of the following pieces of information.
From and To fields for the email, account holder names and account numbers, dates, and so on.
Refer to the Email Template Editor Wiki page or user guide for details about using the editor.
When email templates are designed in the GNA Email Template Editor, expressions can be used to determine which fields are required to be populated in the template. Refer to the About Parameters Expression Field  section on this page.
As an example, an email message will be sent to all mailing addresses with a late filing. The information that is required will be retrieved by the Govern ID’s. Each record returned by the query will look through each column to see if it corresponds to a Govern ID; if this is the case, the Govern ID will be set. Then when the email is being sent via the template, the Govern ID will be passed to the template to be used directly within the email, or as a Parameter Expression that is passed to another query.
In our example, another query has been designed to extract information such as the naNameInfo, EMAIL, FULLNAME, ACCOUNT_NO, and so on.

Parameters Expression

As indicated earlier, build your query in the parameters expression, it is here that you will determine the required Govern ID’s.
For example…:
{
To = Query(‘naNameInfo’, ‘EMAIL’);
Name = Query(‘naNameInfo’, ‘FULLNAME’);
AccountNumber = Query(‘stAccountNo’, ‘ACCOUNT_NO’);
Category = Query(‘stCategoryCode’, ‘SHORT_DESC_EN’);
PeriodeCode = Query(‘stPeriodCode’, ‘SHORT_DESC_EN’);
PeriodeNumber = Query(‘stPeriodNumber’, ‘SHORT_DESC_EN’);
DueDate = Query(‘stDueDate’, ‘DUE_DATE’);
}
In the above expression, we need the NA_ID’s for name information, ST_ID’s for ST account information and due dates, and so on. Each required query must be created. Refer to the Appendix section below for a listing.

The SELECT query is now written to retrieve the Govern ID’s that are needed in the email template.

2. Design Your Query

The SELECT Query

It is within the SELECT query being used that the Govern ID’s are set.
Looking at the following query…:
SELECT top 100 f.st_acct_id,
f.na_id,
f.st_id
FROM st_filing_master f
INNER JOIN NA_NAMES n ON n.na_id=f.na_id
WHERE f.unfiled <> 0 AND
f.due_date < GETDATE() AND
(n.email IS NOT NULL AND n.EMAIL <> ‘ ‘)
ORDER BY f.st_acct_id, f.st_id;
The above query was designed in the Select Query Editor in GNA. It will list all filings that are late. An email will be sent to the NA_MAILING address. For this example, note that only the top 100 records are selected.

Appendix

List of Queries

The following queries were used as examples for demonstration purposes. They can used as a starting point and modified for other purposes.

— Query Expression:

{
To = Query(‘naNameInfo’, ‘EMAIL’);
Name = Query(‘naNameInfo’, ‘FULLNAME’);
AccountNumber = Query(‘stAccountNo’, ‘ACCOUNT_NO’);
Category = Query(‘stCategoryCode’, ‘SHORT_DESC_EN’);
PeriodeCode = Query(‘stPeriodCode’, ‘SHORT_DESC_EN’);
PeriodeNumber = Query(‘stPeriodNumber’, ‘SHORT_DESC_EN’);
DueDate = Query(‘stDueDate’, ‘DUE_DATE’);
}

— Email message

Dear @Name,
The following Account #@AccountNumber has registered a late payment for the @PeriodeCode period of @PeriodeNumber in the @Category.
The actual due date was @DueDate

— naNameInfo

SELECT EMAIL,
CASE
WHEN FORMAT_CODE=’c’ THEN COMPANY
ELSE FIRST_NAME || ‘ ‘ || LAST_NAME
END as FULLNAME
FROM NA_NAMES
WHERE NA_ID=@idna_id

— stAccountNo

SELECT ACCOUNT_NO
FROM ST_MASTER
WHERE ST_ACCT_ID=@idst_acct_id

— stCategoryCode

SELECT VT_USER.SHORT_DESC_EN
FROM ST_FILING_MASTER
INNER JOIN VT_USER ON VT_USER.YEAR_ID=ST_FILING_MASTER.YEAR_ID AND
VT_USER.DEPT=ST_FILING_MASTER.DEPT AND
VT_USER.CODE=ST_FILING_MASTER.CATEGORY_CODE
WHEREST_FILING_MASTER.ST_ID=@idst_idAND
VT_USER.TABLE_NAME=’ST_CATEG’

— stPeriodCode

SELECT (CASE WHEN ST_FILING_MASTER.PERIOD_CODE = ‘ST_INACTIVE_PER’ THEN ‘Inactive’ ELSE VT_USER.SHORT_DESC_EN END) AS SHORT_DESC_EN
FROM ST_FILING_MASTER
INNER JOIN VT_USER ON VT_USER.YEAR_ID=ST_FILING_MASTER.YEAR_ID AND
VT_USER.DEPT=ST_FILING_MASTER.DEPT AND
VT_USER.CODE=ST_FILING_MASTER.PERIOD_CODE
WHEREST_FILING_MASTER.ST_ID=@idst_idAND
VT_USER.TABLE_NAME=’ST_PER’

— stPeriodNumber

SELECT VT_USER.SHORT_DESC_EN
FROM ST_FILING_MASTER
INNER JOIN VT_USER ON VT_USER.YEAR_ID=ST_FILING_MASTER.YEAR_ID AND
VT_USER.DEPT=ST_FILING_MASTER.DEPT AND
VT_USER.CODE=(ST_FILING_MASTER.PERIOD_CODE + ‘_’ + CAST(ST_FILING_MASTER.PERIOD_NB AS VARCHAR))
WHEREST_FILING_MASTER.ST_ID=@idst_idAND
VT_USER.TABLE_NAME=’ST_PER_DETAIL’

— stDueDate

SELECT DUE_DATE
FROM ST_FILING_MASTER
WHERE st_id=@idst_id

Documentation

Click to view or download the current version of the user document:
103-ed-017_GNA_Email_Template_Editor.pdf

Related Topics

Email Notification
Email Notification Batch Process

 

 

 

103-ed-019

 

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