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:

Remove the current selected item
Remove All items from the Dataset Treeview
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).

Mass Appraisal Product Map

Overview

The goal of the Product Map is to provide links to existing Mass Appraisal informational pages.
Grouped around the Form Functionality or other stand-alone OpenForms Component ( Batch Process, Report, View, etc.)

Business Rules

OpenForms	Govern Standards & Property Control	Mass Appraisal	Mass Appraisal Conversion
Database/Naming Standards Number Format Editor	Integrity Business Rules (Active/Inactive) Frozen ID/Roll Forward Split Merge Jurisdictions	MA Tables Rules LookUp Groups Validation Tables MA Values Rules MA Modif Stamp MA Compute Entity Configuration	Convert Mass Appraisal Parameters Convert Mass Appraisal Tables Convert Standard Formulas to Expressions

Parameters and Tables

Section	Product Code	MA Tables Options	MA Tables Business Rules	Other Information	Basic Tables
General Parameters & Table Standards	103-ma-parm-General Parameters 103-ma-parm-Tables	Appraisal Link Group Look-up by Matrix Links , Average & Group Option Unit/Area Lookup, ISRequired , Forced and Display Allow Table Sequences to use the same column by model	MA Tables BRules		103-pc-tables-jurisd 103-ma-tables-method 103-ma-tables-permadjreason
Mass Appraisal General Tables	103-ma-tables-nbhd 103-ma-parm-Tables-Depreciation 103-ma-parm-Tables-Rounding 103-ma-tables-multdist 103-ma-tables-l_assmt	MA Single Table Category All MA Tables – Depreciation MA Single Table Category All – Rounding MA Single Table Category All – Correlated Values MA User Table – Limited Assessment

Form Functions

Section	Product/Wiki Code	Description	Specification/Parameters	Supporting Info	R&D Technical Info/Test Plan
Property Master (frm-014)	101-ma-frm-014 101-pc-frm-012 101-pc-frm-017 101-pc-frm-018 101-ma-compute-Global	CAMA Property Information (Master) PC Parcel PC Area PC Legal Compute Total Values for the Property	Global Property Compute 103-ma-tables-method	103-pc-tables-jurisd 103-pc-tables-neighborhood 103-ma-tables-l_assmt 103-ma-tables-multdist	same
	101-ma-frm-071	CAMA Property Info Combined (Custom) includes: Area and Legal
-Audit –	101-ma-frm-019	CAMA Audit Information		103-ma-tables-maactv (activity) 103-ma-tables-maentry (entry) 103-ma-tables-mainfsrce (source) 103-ma-tables-adjtp (adj type) 103-ma-tables-ma_over (ov type)	101-ma-frm-019-Test (6.1)
-Exemption –	101-ma-frm-022	CAMA Exemptions	See Roadmap
– What If –	101-ma-frm-030	CAMA What IF (new)		Same tables as audit
– Value Override – (frm-021)	101-ma-frm-021	CAMA Value Override	See Roadmap	103-ma-tables-maover (ov type)
– Site – (frm-016)	101-ma-frm-016	CAMA Site Info.	Site Adjustment Computation Site Setup(Dev) 103-ma-parm-Tables-Sites		101-ma-frm-016 Form Setup (6.0) 101-ma-frm-016-TestPlan 101-ma-frm-016-UseCase
– Land – (frm-017)	101-ma-land 101-ma-compute-LandUnit 101-ma-compute-Land 101-ma-frm-017	General Land Information Compute Land Units Comnpute Land Value CAMA Land Information	Compute Land Units Compute Land Values 103-ma-parm-General-2 103-ma-parm-LandUse 103-ma-parm-LandSchedule 103-ma-parm-PlotUse 103-ma-parm-Tables-LandAdjust		101-ma-frm-017 Form Setup (6.0) 101-ma-frm-017-Test Plan 101-ma-frm-017-Use Case (needs to be updated) need to review Form Setup
	101-ma-frm-032	CAMA Land Ag. (NY)
	101-ma-frm-061	CAMA Land Ag. (PA)
– Buildings – (frm-025)	101-ma-buildings 101-ma-compute-Bldg 101-ma-frm-025	General Building information Compute Building Information CAMA Building Information	Compute Building Value 103-ma-parm-General-2 103-ma-parm-BldgUse 103-ma-tables-submodel		101-ma-frm-025 form Setup (6.0)
	101-ma-frm-005	CAMA Building Drawing			101-ma-frm-005 Form Setup (6.0)
	101-ma-frm-012	CAMA Building Area			101-ma-frm-012 Form Setup (6.0)
	101-ma-frm-026	CAMA Building Structural Elements BSE	103-ma-parm-Tables-BSE 103-ma-parm-Templates-BSE		101-ma-frm-026 Form Setup (6.0) Story #10-(4 Dimension Table) 101-ma-frm-026-TestPlan 101-ma-frm-026-UseCase
– Misc. Structure –	101-ma-compute-Misc 101-ma-frm-020	Compute Miscellaneous Structure Value CAMA Miscellaneous Structure see Roadmap Requirement 14790	Compute Miscellaneous Value		101-ma-frm-020 From Setup (6.0
– Sales & Comps-	101-ma-sales 101-ma-frm-015	General Sales Information CAMA Sales
	101-ma-frm-029 101-ma-compute-Comps	CAMA Comparable Sales Compute Comparable Sales	Compute Comparable Sales
– Parcel Linking –	101-ma-frm-003 101-ma-compute-MA-Linking	CAMA Appraisal Linking (Condo +)	103-ma-parm- 101-ma-compute-MA-Linking
– Income –	101-ma-frm-023 101-ma-frm-023-fea-001 103-ma-parm-income 103-ma-parm-add 103-ma-parm-incqua 103-ma-parm-incadj 103-ma-parm-Tables-incitem 103-ma-parm-Tables-incexp 103-ma-parm-Tables-incsbcat 103-ma-parm-incmodel	CAMA Income CAMA Income – Apply Default Economic model MA Tables Single Entry – Income Category MA Tables Single Entry – Added Fields MA Tables Single Entry – Income Quality MA Tables Single Entry – Income Adjustments MA Tables Income Rental Items MA Tables Income Expense Items MA Tables Income Sub Categories MA Tables Income Models	101-ma-compute-Income 101-ma-compute-IncomeFields	Income Group 103-ma-tables-incunit (income unit)	101-ma-frm-023-(Dev Only)
	101-ma-frm-070	CAMA Income Rental Detail	103-ma-parm-Tables-IncRental
Multiple Regression Analysis – MRA (Fair Market) –	101-ma-frm-065 101-ma-compute-MRA	CAMA Fair Market Value (Multiple Regression Analysis – MRA) Compute MRA Fair Market Value	MRA Computation 103-ma-parm-MRAmodel 103-ma-parm-Tables-MRA		101-ma-frm-065-TestPlan 101-ma-frm-065-UseCase
– Personal Property- (Appraisal opt.)
– Discontinued –	101-ma-frm-004	CAMA Drawing (non apex)
	101-ma-frm-057	CAMA Multiple Assessment Rate
	101-ma-frm-059	CAMA SAMA Summary Values
	101-ma-frm-078	CAMA Property Distance Weight
	101-ma-frm-099	CAMA Value History

3rd Party Integration
		Apex Building Drawing			303-apex
		Marshall & Swift (Requirement )

Tags: [101] [ma] [ma-frm]

Standard Features (fea)

Mass Appraisal

Status	Product Code	Appraisal Specific	Additional Information	Developer	Test Plan
	101-ma-fea-001	Full Compute Controller/Action Button if manual		101-ma-fea-001	101-ma-fea-001
	101-ma-fea-004	Dynamic e-search – Appraisal	Dynamic e-search – STD
[To be verified]	101-ma-fea-010	Freeze & Audit
	101-ma-fea-011	Roll Forward Business Rules
	101-ma-fea-006	Saved Datasets
	101-ma-fea-017	Audit Trail

Batch Process (bp)

Module	Wiki Page	Batch Process Name	Batch Process Name	Test Plan
std	101-std-bp-001	Evaluate Expressions (Recompute)	co_	(pcode).s01-c.all
ma	101-ma-bp-001	Import APEX area codes	ma_impapexsketc	[to be verified]
ma	101-ma-bp-002	Mass Appraisal Batch Compute	ma_compute	Developers Page
ma	101-ma-bp-003	Finalize Assessment Close Year (History = yes)	ma_closeyear
ma	101-ma-bp-004	Batch Update	ma_batchUpdate	see Roadmap
ma	101-ma-bp-005	Batch Computation of Sales	ma_salescompute	Developers Page
ma	101-ma-bp-006	Transfer Appraised Value to Real Property Tax	ma_trnstotax	see Roadmap
ma	101-ma-bp-007	Generate Audit Pending	ma_auditpending	change long description to MA (currently listed as Real Property)
ma	101-ma-bp-008	Generate Audit Finalize	ma_auditfinalzd	change long description to MA
ma	101-ma-bp-012	Comparable Sales Extract	to be defined	see Roadmap

pp	101-pp-bp-001	Personal Property Computation	pp_compute	see Roadmap

ma	103-ma-bp-005	Copy Mass Appraisal Parameter Tables to Year	ma_copy	GA1609
ma	103-ma-bp-006	Initialize Mass Appraisal Next Year Data	ma_init_year
ma	103-ma-bp-010	Marshall And Swift – Copy To Year	ma_ms_copy_year

GNA Administrator

Application Parameters

Mass Appraisal

Status	Wiki Page		Name	Notes
		001	GENERAL PARAMETERS
	103-ma-parm-General-1	001	General Parameters – Page 1	Will be reviewed to remove unused parameters
	103-ma-parm-General-2	001	General Parameters – Page 2
	103-ma-parm-General-3	001	General Parameters – Page 3
	103-ma-parm-General-4	001	General Parameters – Page 4
	103-ma-parm-General-5	001	General Parameters – Page 5
[roadmap]	103-ma-parm-General-6	001	General Parameters – Page 6	Marshall & Swift
[to be verified]	103-ma-parm-Appraisers	002	MA APPRAISERS
	103-ma-parm-Tables-MASTER	003	MA TABLES (Master)
	103-ma-parm-Tables-Single	004	Tables – Single Entry
	103-ma-parm-Tables-BSE	005	Tables – Building Structural Elements
	103-ma-parm-Tables-Depreciation	006	Tables – Depreciation
	103-ma-parm-Tables-IncExpense	007	Tables – Income Expenses
	103-ma-parm-Tables-IncRental	008	Tables – Income Rental Details
	103-ma-parm-Tables-LandAdjust	009	Tables – Land Adjustments
	103-ma-parm-Tables-MRA	010	Tables – MRA
	103-ma-parm-Tables-COMPS	012	Tables – Comparable Sales Elements
	103-ma-parm-Tables-Sites	013	Tables – Sites

	103-ma-parm-Templates-BSE	050	BSE Templates
	103-ma-bp-005		Copy to Year	Copy Mass Appraisal Tables to Year
	103-ma-bp-006		Initialize to Year	Copy Mass Appraisal Data to Year

See GNA Product Map

101-ma-map

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

MA – Valuation Business Rules

Mass Appraisal Valuation Business Rules

Release 6.1 [In Development]

Overview

The following information provides the computation business rules.

Computation Trigger Business Rules

Computation occurs:

On Save in Govern
On Condition in the Batch Compute:
- If modif stamp of detailed record different than detail record modif stamp
- If force compute of components selected in the batch process
- If roll forward to other years
if MA Audit record is Finalized

Computation does not occur:

If Parcel Inactive – MA Records are deleted when inactivated
if Building inactive
if Parcel Linking inactive
if Building Linking inactive for the other linked buildings

History Only

If the history only is set to true (-1 or 1), it will be skipped when the computation is done using the Batch Computation program.
It will be ignored when a record is saved and computation will occur.

Parcel Linking

A parcel can receive values from other parcels or provide a portion of its value to others. Contrary to the VB6 version, we will only load the values provided by other parcels and it is assumed the parcels that are providing the values have been previously computed.
If possible, if the parcels to be loaded have a MA_MASTER.MODIF_STAMP set to NULL, we should be calling this compute (recursive call) for these parcels prior to complete this step. (to be verified)

IMPORTANT: A parcel cannot receive and provide a value at the same time. Parcels having the MA_MASTER.exclude_from_roll = <> 0 are providing values to other parcels and therefore they are not computed. However the modif stamps to all linked parcels are reset.

MA_MASTER.exclude_from_roll = -1 – The parcel provides all types of values to other parcels
MA_MASTER.exclude_from_roll = 1 – The parcel provides only a land value to other parcels (to be validated)
MA_MASTER.exclude_from_roll = 2 – The parcel provides only a misc. and a building value to other parcels.

Troubleshooting of Computation Errors

In case of errors during the computation process (for example, parameters not configured), all the system columns will be set to 0 and no timestamp will be attached to the appraisal records. (verify if at detail level only?)

TIP: Setup the console

Rounding Business Rules

General Rounding Method

OpenForms uses the standard Microsoft XXX rounding methodology.
Full column precision for type and sized is used at the database level

Appraisal Rounding Parameters

The following parameters impact rounding at different levels:
Final Appraisal Values
MA Round Table [ma_round]

Building, Land, Misc, Income, MRA [code = bldg., inc, land, misc, mra, sale]
Total Property Value [code = appval]

General Tax Parameters

Personal Property Round Total or Detail value

Linked Records

MA_SITE.LK_LAND_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘land’) – (to be validated)
MA_SITE.LK_LAND_AG_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘land’).
MA_SITE.LK_MISC_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘misc’).
MA_SITE.LK_BLDG_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘bldg’).
MA_SITE. LK_INC_GRM_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘inc’).
MA_SITE. LK_INC_DIR_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘inc’).
MA_SITE. LK_MRA_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘mra’).
MA_SITE.PP_LK_VALUE is rounded to 0 decimal.
MA_SITE. LK_COMP_VALUE is rounded based on the MA_PARM_MAROUND information (code = ‘compval’).

Detail Component Values

MA Round Table [ma_round]

Building Area
Building Look-up Area
Market Living Area [code = lareamk]

General Appraisal Parameters

Quality Points number of digits
Building Size
Land? (verify)
Drawing Area Code Rounding (deprecated in 6.1)

Field Level

Column precision and size

Mass Appraisal (MA) Tables Business Rules

Release 6.1 [under review]

Overview

MA Tables Basics

MA TABLES are used to calculate values and adjustments for the different type of components (property, site, land, building, misc. structures, income, mra and comparable sales). Different categories and table elements can be defined such as Features, Rates, Adjustments, etc. Click here for the Type/Category/Elements possibilities.

Table Type

All (all), Site (all), Land (land), Building (bldg), Sale (sale), Income (inc), MRA (mra)

Table Categories

Depends on Table Type

Table Element Categories

Depends on Table Type and Categories

Table and Column Names
When setting up the mass appraisal parameters, codes are created in new or existing validation tables while columns are created in the master component tables to record the code selected, the value calculated for this code, the override value if applicable… The following naming rules and standards apply:

Table Names and Columns Names should be created in UPPERCASE.
Table Names cannot be more than 8 characters long, MUST start with a letter and cannot contains special characters except the underscore ‘_’.
Column Names cannot be more than 15 characters long and must start with a letter.
Table Type for Mass Appraisal Validation Tables is 2. For the complete list of table types, See VT USER Table Type
When NO TABLE is entered, the Table Name is saved with 8 spaces (ex: Grid header records)
Columns Names are unique (business rule is now enforced in 6.1) – Some exceptions, contact R&D for more information

Table Name used by different MA Tables entries

The same Table Name and codes can be shared by different MA Tables Entries Sequences.
The sequences that use the same Table Name must have the same LOOK UP GROUP Type and MATRIX specification (to be validated)

No Table Name

When no table is specified for adjustments, rate adjustments and features the user will be able to add a code directly in the Land, Building, MRA and Site Grid. This code will be transformed to a numeric value and moved to the value column. (bse column to be reviewed)

Computation Sequences

Used to define the computation order sequence.

Column has changed to an integer in 6.1
Will be formatted with 6 digits 999999

Formatting
Used to define the number format that will be applied against the value column in grids for land, site, mra adjustments, income and building structural elements.

See Value Format Editor for more information on how to define a format.

MA Tables Standard Options

The standard options are applicable based on Table Type, Table Category and Table Element Category.

Look-Up Group Type

For all MA Table entries defined with a table name, it will be possible to use the MA Link Group Look-Up option.
A new change is implemented where it will be possible to link the Neighborhoods to the Jurisdiction to limit the size of the Neighborhood Look-up.

Is required Expression

An expression for the IS Required has been added. Available where explicit data entry by the user is possible.

Do Dot Display

MA Tables entries with this option are not displayed in the land adjustments and building structural element grids. Often used with Forced Unique

Forced Unique

MA Tables entries with this option will auto select the code of the Table Name specified, if the code is unique.
No interaction is needed when the user is presented with only one (1) code to choose from
- Example: A Table entry can be created to calculate the building Age (Current Year less Building Year) where no user input is needed. The result can be used for entries with a greater sequence for adjustments, etc.

Units Look-Up

For Land Tables, will also contain the APPLY TO codes for land (f-Frontage, d-Depth, u-Units)
For All tables with a table name, the UNITS LOOKUP Table (MA_LOOKUP) will contain all attributes numeric attributes from the COMPUTE BUSINESS ENTITY and with a sequence less than the current sequence and for all attributes tin the entity hat have a suffix not equal to _AM, _OV_VA, _VA, _VA2

Matrix Look-Up

For All tables with a table name, the UNITS Look-Up Table (MA_LOOKUP) will contain all attributes from the COMPUTE BUSINESS ENTITY with a sequence (excludes the HEADERS) less than the current sequence. Note: When creating a new matrix, complete the entry of all matrix sequence lookup before saving.

Link Option

For sequences with a table name, the UNITS TABLE LOOKUP option will be available. Table (MA_LOOKUP) will contain all attributes from the COMPUTE BUSINESS ENTITY with a sequence less than the current sequence.
Will only show the sequences from the same CATEGORY (so apples and oranges are not mixed)
Will only show the sequences with the same VALUE TYPE (Amount or %)

Average Option

Group Option (Land Only)

Group calculation is perform for all sequences that have a GROUP specified.
The goal of the group rate calculation is to come up with one rate adjustment for all groups.
The resulting rate adjustment is stored on the first entry having a group. Conceptually, the system process each entry in a group to come up with a group total.
The final value is the average of all group totals
The MATHS operator is ignored for the first amount of each group

Business Rules by Table Element Categories

h-Header – Used for display only. No table, codes or look-ups can be specified. It can be applicable by property type. land type, etc.
f-Feature – Can have a table or not, an expression and be setup as a matrix (new). It can be used to compute other elements, but the feature record is NOT processed by compute.
r-Rate Adjustment – No table option applicable, used by the compute to adjust the rate
a-CAMA Adjustment – No table option applicable, used by the compute to adjust the value

Business Rules for Modification Stamps

The master Modification Stamp table is used to record the last time a change was made to appraisal parameters that have an impact on property, site or component values.
It will be compared with the individual components modification stamp to determine what needs to be computed.

When a change is made in MA TABLES, the MA_MODIF_STAMP for that component is updated with the current date and time.
Click here for MODIFICATION STAMP SPECIFICATIONS (101-ma-brules-ModifStamp)

101-ma-brules

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

MA – Feature 012 – Roll Forward BRules

Mass Appraisal Feature 012 – Roll Forward Business Rules

Overview

The Roll Forward feature (parameter) is used to duplicate the creation of records, deletion of records and changes made to existing records for future years that are already initialized. The option is enabled in the Govern New Administration (GNA)

Roll Forward

An example of the use of the Roll Forward feature is a situation where the current year is 2012 and 2013 year data has been initialized to start preparing for next years assessment or tax roll. In the event of an appeal in 2012, any changes made will be rolled forward to 2013 if answered yes when prompted by the system to roll forward this change. It is important to know that only the CHANGE will be brought forward.

Roll Forward Data: Select the Roll Forward Data option if you make modifications to records in earlier years that you want to carry forward to
records in the future years that are open. For example, the current year is 2019. The user returns to 2016 and changes a record. A confirmation message appears each time you save a new record or modify an existing one when there are records for future or more recent years.

When making property appraisals you may need to have open the current fiscal year and several years in the future. For example, if the current fiscal
year is 2015, you may have open 2016, 2017, and 2018. The configuration parameters and property records from 2015 are copied to the future years,
2016, 2017, and 2018.

Modification in Future Years

If there is a change made in 2019, such as an extension to a porch, you can update the record for the year in which the change occurred and then roll the
change forward to the future years, without having to open and modify each record. The changed field is copied from the current year to the future years.
Structures that have not changed are not rolled forward.

Table Details

Table Function	Mass Appraisal Table Name
MA Land	MA_LAND
MA Land	MA_LAND_1 to MA_LAND_9
MA Land	MA_LD_INFO (NOTE: Deprecated in 6.1)
MA Property Info	MA_MASTER
MA Value Override	MA_VALUES_TABLE
MA Override	MA_OVERRIDE
MA Building Structural Element (BSE)	MA_BUILDINGS
MA Building Structural Element (BSE)	MA_BUILDINGS_1 to MA_BUILDINGS_9
MA Building Structural Element (BSE)	MA_BLDG_DRAWING
MA Building Structural Element (BSE)	MA_BLDG_INFO
MA Building Structural Element (BSE)	MA_BLDG_AREA (NOTE: Deprecated in 6.1)
MA Building Drawing	MA_BLDG_AREA (NOTE: Deprecated in 6.1)
MA Misc Structure	MA_MISC_STRUCTURES
MA Site	MA_SITE
MA MRA	MA_MRA
MA MRA	MA_MRA_1 to MA_MRA_9
MA Income	MA_INCOME
MA Income	MA_INCOME_1 to MA_INCOME_9
MA Income	MA_LK_INC_FIELD
MA Income	MA_INC_INFO (NOTE: Deprecated in 6.1)
MA Income	MA_INC_SIMULATION Only Create and delete mode MA_INCOME_DETAIL (NOTE: Deprecated in 6.1)
MA Link Percent	MA_LINKS_PERCENT

101-ma-fea-011

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

MA Modification Stamps – BRules

Mass Appraisal Modification Stamps – Business Rules

Release 6.1 [under review]

Overview

For system performance, business rules are applied to identify what needs to be reloaded and/or recomputed.
The appraisal detail records have a modification stamp that contain either:

date & time – the last time a computation was completed successfully
null value – the record needs to be recomputed do to a modification in the record or one of it’s dependencies

The master modification stamp table (single record) contains the date & time of when a change was made to parameters that can impact value.

MODIF STAMP vs LAST MODIFICATION date

The last modification date is updated ONLY when a physical change is made to a record, and only to this record.

Tables and Fields

PARAMETERS Modification Stamp Table [ma_modif_stamp]

The modification stamps contain the date when changes were made to parameters that impact value.
Global fields:

[ALL_STAMP]
- Updated when changes to basic parameters, general equalization factors between CAMA and Tax …
- Updated after any changes in MA_TABLES ‘Sites’ or MA_PARM_SITE
[SITE_STAMP] same as [ALL_STAMP]
[VALUE_STAMP]
- No longer used in version 6.1. Only the ALL_STAMP will be used.

Detail component fields:

[BLDG_STAMP] for buildings
[INC_STAMP] for income
[LAND_STAMP] for land
[MISC_STAMP] for miscellaneous structures
[SALE_STAMP] for comparable sales
[MRA_STAMP] for MRA
[PP_STAMP] for personal property (see roadmap)

Click here for the List of Parameters Tables when changed, updates the modification stamp flags of this table.

IMPORTANT NOTE: When there is a change in General Parameters, the stamps are NOT Flagged for recompute. When a change is made that impacts value, such as changing the Depreciation Year, it will be mandatory to do a FORCE batch compute.

DATA Modification Stamp fields [ma_xxx.modif_stamp]

Each detail appraisal component records has a modification stamp attribute that gets set to null when a change is made that requires the record or its dependencies to be recomputed.
Once the compute has when with an impact on value has a modification stamp field [MA_component.MODIF_STAMP]:
MA Master Property Value record [ma_master]

[VALUE_STAMP] Updates when the property has been computed successfully. Note: The VAUE_STAMP is no longer used in Version 6.1 since the MODIF_STAMP was added in MA_MASTER.
[MODIFICATION_STAMP]

All Appraisal Components [ma_xxx]

[MA_Site.MODIF_STAMP]
[MA_Bldg.MODIF_STAMP]
[MA_Land.MODIF_STAMP]
[MA_Misc.MODIF_STAMP]
[MA_Inc.MODIF_STAMP]
[MA_MRA.MODIF_STAMP]
[PP_ASSESSMENT.MODIF_STAMP]

Click here for the List of Tables Changes and their impact on the stamps.

Modification Stamps Business Rules

The modification stamp of a component record contains either:

The CURRENT DATE & time when last computed
- The detail component modification stamp is set to the current date after the record has been successfully computed
- Computation triggered on creation or modification or when running the Batch Compute
NULL
- When one of it’s child (see Hierarchy) has been created, modified or deleted
- When a record was rolled forward to a new year – to be tested

The modification stamp is not updated when:

Computation has not been completed
Computation was completed but not successful (values are set to zero)
- Invalid or missing parameters
- Invalid record values
- Invalid expressions
- Invalid mathematical operations (division by zero or missing parameters)

IMPORTANT NOTE: The Modification Stamps are set to null when a roll forward is made, however they are NOT computed. To be verified

Parent Child Stamps Update Hierarchy

General

When a change occurs (add, delete, mod) to a child entity, the parent modification stamp is set to null until successfully computed.
If all the property needs to be recomputed, the MA_MASTER.Modif_stamp attribute is set to null.

Property Control Changes (Jurisiction, Property type, neighborhood and income neighborhood) updates ALL
Component Child (ex: Building Area, Building Misc.Structures) updates Root entity Building Modif Stamp
Component Detail Record (ex: Building, Land, Misc.) updates
- Component Detail Record linked to other Component Detail Record (ex: MRA or Income)
- Component Detail Record linked to Site
Site Values (all)
Global Property Value
- Property Value linked to
  - Building linking (verify impact)
  - Parcel linking (Distributes or receive)

Detail Record Linked To Income or MRA

Buildings, Land, Miscellaneous Structures and Personal Property (see roadmap) can be linked to MRA or INCOME records.
When a change occurs in a detailed record that is linked to another component, the following occurs:

[MA_xxx.MODIF_STAMP] is updated
[MA_xxx.MODIF_STAMP] of the linked component (MRA or Income detail and root entity)
[MA_SITE.MODIF_STAMP] of the linked component linked site
[MA_MASTER_MODIF_STAMP] of the property record

Detail Record part of a CAMA Parcel or Building Linking

Depends on the LINK TYPE

A parcel cannot receive and provide a value at the same time. Parcels having the MA_MASTER.exclude_from_roll = <> 0 are providing values to other parcels and therefore we should not further perform this step. However we need to reset the modif stamps to all linked parcels by performing the following SQL:
update ma_master set MODIF_STAMP = null where year_id = (current parcel year id) and frozen_id = (current parcel frozen id) and p_id = ( select malk.p_id from MA_LINKS_PERCENT malk, PC_PARCEL_LINKS lktype where malk.LINK_ID = lktype.LINK_ID and malk.P_ID = lktype.P_ID and year_id = (current parcel year id) and frozen_id = (current parcel frozen id) and MASTER_PID = -1 and malk.p_id <> (current parcel P_ID) and exists (select 0 from PC_PARCEL_LINKS pclk where pclk.LINK_ID = malk.LINK_ID and (MASTER_PID = 0 or master_PID is NULL) and P_ID = (current parcel P_ID)))
update ma_master set MODIF_STAMP = null where year_id = (current parcel year id)and frozen_id = (current parcel frozen id) and p_id <> (current parcel P_ID) and exists (select 0 from MA_LINKS_PERCENT where p_id = ma_master.p_id and year_id = ma_master.year_id and frozen_id = ma_master.frozen_id and LINK_ID = (select link_id from PC_PARCEL_LINKS where MASTER_PID = -1 and p_id = (current parcel P_ID)))

Global and Site Changes

When a change is made to the site adjustments or to the fields that compose the site group description (i.e. site liability, site exemptions, etc.) or when a change is made in a component linked to the site, the following occurs:

[MA_SITE.MODIF_STAMP] of the detail record is updated
[MA_SITE.MODIF_STAMP] of the other site records with the same combination
[MA_MASTER_MODIF_STAMP.ALL_STAMP] of the property record

Other Entity Field Changes

Some changes made in other forms and business entities that can impact value will set the MA_MASTER.MODIF STAMP to Null.
Changes made to the fields that are used in the MA LINK GROUP lookup:

PC_PARCEL.Jurisdiction
PC_AREA.Neighborhood
PC_AREA.Income Neighborhood
PC_LEGAL.Property Type

Changes made to other custom fields used in expressions or queries that can impact value:

IMPORTANT: Currently, stamps are not updated.

101-ma-brules-modif_stamp

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

Standard Feature – Sequential Batch Process

Version 6.0 and Version 6.1

Overview

Available in Release 6.0 and 6.1

A standard feature that is available in version 6.0 and 6.1 of the Scheduler Console is sequential batch process scheduling. This feature may be configured to allow users to execute multiple batch processes without human interaction. This feature is convenient for launching batch processes during periods where there is less impact on users accessing the network. As an example, these sequenced batch processes could be initiated and set to run overnight, over a weekend, or through the extended periods of a holiday.

The Sequential Batch Process feature allows users to configure a list of Schedules in order to create a linked sequence of Batch Processes in the Govern New Administration (GNA). As each batch process is successfully completed, i.e. no errors generated, it will automatically initiate the next pre-configured batch process in the user defined sequence.

NOTE: Sequential Batch Processes are initiated, and monitored in the Govern Scheduler (SC). The status of the execution of each batch process is displayed through the console of the Govern Batch Scheduler application.

Example of a Sequential Batch Process

The following is an example of a possible Sequential Batch Process. The example will demonstrate a basic batch process that, upon successful completion, will initiate two (2) child batch processes. Each of the two child processes will in turn trigger other processes, and so on. Refer to the example below.

Example

Batch process A is configured to run daily.
When Batch process A ends it will initiate batch processes B and C
Batch process B initiates batch processes D and E
Batch process E initiates batch process G
Batch process C initiates batch process F
Batch process F initiates batch process H

All batch processes B, C, D, E, and F are configured to be triggered upon successful completion.

Configuration

Read More...Read Less...

Sequential batch processes are configured in the Govern New Administration (GNA). Preview and execution of the batch processes are presented in the Govern Scheduler.

For further detail Govern batch process scheduling, refer to the Govern Schedule user guide for details (106-gs-all-GovernScheduler.60.pdf).

Govern New Administration (GNA)

To configure Sequential Batch processes it will be necessary to first create a new batch process or use an existing one. You would next need to create a schedule for that Batch Process. This batch process will then be configured to, upon completion, trigger the next batch process in the sequence.

TIP: When planning sequential batch processes, it is recommended that a flowchart of sorts is sketched out to use as a guide to visualize your setup. In addition, as each schedule is associated with a batch process, the batch process used should also be noted.

Using the example flowchart of schedules, i.e. A, B, C, D, E, and F, we will say that Batch Process A is associated with Schedule A. Batch Process B will be associated with Schedule B, and so on.

Parent Schedule

With our flowchart drawn out for our example, we will say that the Batch Process A schedule will be called Schedule_A. Schedule A is also the parent batch process that will trigger all subsequent processes. As the parent process its configuration is different from all subsequent processes.

Creating the Parent Schedule

To create the first schedule called Schedule A in the GNA…

On the GNA ribbon, click Editors (tab) > Batch Process Definition Editor.
In the Batch Process Definition Editor select the batch process that will be the parent.
On the Batch Process Definition tab, either select an existing batch process, or click Create a new item to create a batch process.
Click to select the Scheduling sub tab.
Click Add.
The form to configure the schedule is displayed.

NOTE: If the batch process requires parameters to be configured, this must be completed first. The save action is required before you can schedule the batch process.

Click to select the Schedule
Enter a Name, and a Description.

NOTE: Name and Description are required parameters; you will not be able to save without completing them.

In the Settings group below, set a frequency for the schedule; select One time, Day, Week, or Month. Additional settings allow you to specify a Start Date, and expiration date, i.e. Expires on:. For our example, this will be a one time schedule so select One time.

NOTE: As this is the first batch process, the option for Triggered should not be selected.

Click Save Changes on the Schedule.
Click the Close button [X] in the upper right hand corner to close the form.

Creating the Child Schedule

Configuring B and C

Referring back to our flowchart, we see that the Children batch processes, B, and C, are at the same level and are triggered by batch process A. We will need to configure Schedule B to trigger batch process D, and E. Batch process C will trigger batch process F. As batch processes B and C are both at the same level, they will be run simultaneously.

To create any Children schedules, e.g. Schedule B, C, and all other subsequent processes…

On the GNA Batch Process Definition Editor, click to select the batch process that will be designated as Schedule B.
On the Batch Process Definition tab, click to select the Scheduling sub tab.
Click Add to display the Schedule
If the batch process requires parameters to be configured, this must be completed first. The save action is required before you can schedule the batch process.
Select the Schedule
Enter a Name and a Description for the schedule; for our example we will use Schedule B, and “Schedule B triggered by Schedule A” for the Name and Description:

We now need to specify that Schedule B is to be triggered by the successful completion of the batch process that is attached to Schedule A.

In the Settings group, click the Triggered radio button.
In the Parent group, select the batch process for Schedule A from the combo box, i.e. Batch Process A.
Select the Schedule; the combo box will display Schedule A.

NOTE: If the batch process is also associated with other schedules, they will also be listed. It is important that you select the correct schedule.

On the Schedule tab, click Save Changes, to save the setup.
Click the [X] in the upper left hand of the form to close the form.

Configuring Sequential Schedules D and E

Referring back to the workflow sketch, we see that Schedule C / Batch Process C is at the same level as Schedule B, it will be necessary to select the batch process that will be associated with Schedule C. For the Parent you will specify Schedule A. For the configuration, it will be necessary to repeat all steps for configuring a Child Schedule; see above steps. Schedule D / Batch Process D and Schedule E / Batch Process E are triggered by Batch Process B, and should be configured accordingly.

Govern Scheduler Console Preview and Execution

Viewing the setup in Govern Scheduler

When complete the final sequential batch processes can be seen in the Govern Scheduler group of the Govern Scheduler console. Looking at the interface, we can see that Schedule A is at the top of the list as the parent process. Schedule B and Schedule C are at the same level, both have their sub processes which they will trigger. Schedule D and Schedule E will be triggered by Schedule B, and Schedule F is triggered by Schedule C. Finally Schedule G is triggered by Schedule E, and Schedule F triggers Schedule H.

If a Batch Process fails…

During execution of the batch processes, if a batch process in the sequence fails, all subsequent children processes in that chain will not be executed. For example, if Batch Process B for Schedule B fails to execute, it will need to be corrected. After rectifying the error with the process, it will be necessary to execute Batch Process B again. After which all subsequent processes will then be triggered. It is not necessary to execute the entire process flow again, i.e. Schedule A.

Executing the Batch Process

To execute the Batch Processes in the Scheduler Console

Click to select the process in the console.
Click Execute.

NOTE: Refer to the Govern Scheduler user guide for additional configuration details, and running Batch Processes.

Business Rules

Deletions of Processes in Batch Scheduler and GNA

In the Batch Scheduler or in GNA, trying to delete a schedule with Child schedules will generate an error message. This message will indicate that in order to proceed, you must first delete the child schedules before you can delete the parent.

Deleting Parent Schedules in the Batch Scheduler

An error will be generated when attempting to delete parent schedules that are linked to sub schedules, i.e. schedules that they trigger.

Documentation

Click to view the .PDF document detailing this feature. (101-std-fea-046_SequentialBatchProcesses.pdf)

101-std-fea-046

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

Dataset Treeview Feature – Temporary Records

Overview

Temporary Records

Business Rules

Duplicate of an Existing Key

Context Menu

Remove

Remove All

Remove All But This

Related Topics

Mass Appraisal Product Map

Overview

Business Rules

Parameters and Tables

Form Functions

Standard Features (fea)

Mass Appraisal

Batch Process (bp)

GNA Administrator

Application Parameters

Mass Appraisal

Mass Appraisal Valuation Business Rules

Overview

Computation Trigger Business Rules

Parcel Linking

Troubleshooting of Computation Errors

Rounding Business Rules

General Rounding Method

Appraisal Rounding Parameters

Detail Component Values

See Also

Mass Appraisal (MA) Tables Business Rules

Overview

MA Tables Basics

Table Name used by different MA Tables entries

No Table Name

Computation Sequences

Used to define the computation order sequence.

MA Tables Standard Options

Look-Up Group Type

Is required Expression

Do Dot Display

Forced Unique

Units Look-Up

Matrix Look-Up

Link Option

Average Option

Group Option (Land Only)

Business Rules by Table Element Categories

Business Rules for Modification Stamps

Mass Appraisal Feature 012 – Roll Forward Business Rules

Overview

Roll Forward

Modification in Future Years

Table Details

Mass Appraisal Modification Stamps – Business Rules

Overview

Tables and Fields

PARAMETERS Modification Stamp Table [ma_modif_stamp]

Modification Stamps Business Rules

Parent Child Stamps Update Hierarchy

General

Detail Record Linked To Income or MRA

Detail Record part of a CAMA Parcel or Building Linking

Global and Site Changes

Other Entity Field Changes

Standard Feature – Sequential Batch Process

Overview

Example of a Sequential Batch Process

Configuration

Govern New Administration (GNA)

Parent Schedule

Creating the Parent Schedule

Creating the Child Schedule

Configuring B and C

Configuring Sequential Schedules D and E

Govern Scheduler Console Preview and Execution

Viewing the setup in Govern Scheduler

If a Batch Process fails…

Executing the Batch Process