BP – Generate SSRS Reports by Groups

Batch Process – Generate SSRS Reports by Groups

Overview

Processing time is a factor where batch processes are concerned. In instances where a batch process is to be run on queries that result in an extremely large record set, processing time can be an issue. In order to manage long processing times for a single large record set, an SSRS report can be run that will break down the record set into multiple smaller, manageable groups. Each individual group will require less time to process. The Generate SSRS Reports by Group batch process will scan for any existing groups generated by the SSRS report, and print or save in the .PDF file format.

SSRS Report name: co_genssrsgprpt

Batch Process Name: Generate SSRS Report by Groups

 

Read More...

Functionality

Report

The report will provide the records of groups for the .PDF file. For example, a query generates 1000 records. In our report we will specify that the resulting record set of 1000 parcels be divided into N groups; where N = 10. The resulting record set is broken up into 10 groups consisting of 100 parcels per group. Both the number of groups to print (N), and the Year will be hard coded in the report as a parameter. During processing, the SSRS report will create a temporary table, (Table: PID_GROUP), to manage the breaking up of the parcels into groups.

NOTE: The temporary table name is selected at the users discretion.

The SSRS report will use the following SQL functions:

  • NTILE()
  • ROW_NUMBER()
  • RANK()
  • DENSE_RANK()

Batch Process

This batch process will print or save .PDF files of all groups it finds in a defined folder. For our example, the Batch Process will scan and locate the 10 groups, and will process 10 times, in order to generate the 10 .PDF files that will contain the record details.
To process, the groups, the user will need to set a path to the location where the .PDF files will be generated to.

NOTE: This is a standard batch process and definition that is designed exclusively for SQL Server Reporting Services (SSRS) reporting.

For more information see General OpenForms Batch Processing

 

 

101-std-bp-012

 

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

ST – Self Reported Business Tax Treeview

Self Reported Business Tax Treeview

Overview

The datasets that appear in the Dataset Treeview are populated with the results of searches made through the Search form.
The Treeview Explorer displays record information in a hierarchical arrangement. In the treeview panel, you are able to expand or contract a record with a click on the arrow beside the record icon.
For example, on a search that retrieves tax map records, when you double-click on the tax map, it lists name information at the next level. Each item can be expanded to show specific data on the property, such as owner and occupant names, parcel information and location, permits, utility billing and accounts receivable records.
The Self Reported Business Tax Treeview will display the ST requisite OpenForms, i.e. Self Reported Tax, Self Reported Tax Occasional, and the Self Reported Tax Zero Filer.

NOTE: The forms that are displayed in the treeview are dependent upon admin setup in the GNA Profile Editor and/or assigned access provided through the Govern Security Manager (GSM)

See also

 

 

 

101-st-fea-005

 

[rating]

Govern Standard Module Configuration

Govern Standard Module Configuration

Overview

 

 

101-std-config

 

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

100-ChangesDBStructure

Changes in Database Structure

Version 6.0 and 6.1

Overview

Standard Functions and Features

System and User Validation Tables

Version 6.0 and 6.1

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

 

Read More...

Userfile

Version 6.0

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

User Profiles

Version 6.0.1412

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

Roll Forward Exclusion Tables

Version 6.0

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

User Audit Trail New Tables (3)

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

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

Property Control (PC)

PC Parcel

Version 6.1

  • NON_PARCEL_FLAG and VIRTUAL_PARCEL cannot be set to null.

PC Sales
Version 6.0

  • PC_SALES is no longer used, only MA SALES

Accounts Receivable & Cash Collection (CC)

Version 6.0

Payer Name

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

Mass Appraisal (MA)

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

Building Changes

Version 6.1

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

Site Changes

Version 6.1
Site changes to support new override methodology

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

Income Changes

Version 6.1
Income changes to support new override methodology

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

Income changes to support new calculation method and configuration

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

 

Miscellaneous Billing

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

  • MB_INVOICE and MB_INVOICE_DET
  • MB_RECURRING and MB_RECURRING_DET

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

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

New Database Fields

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

Self Reported Business Tax (ST)

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

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

New Field added in ST_MASTER

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

New Tables added for Estimated Filings

  • ST_ESTIMATE_ID

New Table added for Corporate Account

  • ST_CORP_ACCOUNT

Name and Address (NA)

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

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

OpenForms Tables

Version 6.0

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

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

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

Release 5.x

Version 5.x

  • PC_LK_PARCEL has been replaced with PM_LK_MASTER

See Prior Database Changes (ref. v6.1.1508)

Related Topics

Govern Database DiagramsRefer to the List of Changed Tables section

 

 

100-ChangesDBStructure

 

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

 

100-USR-Registry

User and Machine Registry (USR_REGISTRY) Parameters

Version 6.0 | Version 6.1 (In Development)

User and Machine Registry

The KEY TYPE is used to identify USER and MACHINE registry parameters.

Key Type 1 = User ID registry, – IDENTIFICATION Code = User Id
Key Type 2= Machine registry – IDENTIFICATION Code = Machine Name
Payment Processors not updated

Cash Collection Parameters

By User ID

Registry Type Section Name Key Name Key Type Identification CD Key Value Encrypted Action Notes
Cash Collection Cashier Cash Collection Cashier auto collapse MCR Group and AR Class Distribution 1 user id 0 or 1 0
Cash Collection Cashier Cash Collection Cashier search style 1 userid Style lookup 0 Default lookup group in Cash Collection Form VERIFY conditions
Cash Collection Cashier Cash Collection Cashier real estate up to installment 1 userid 1,2,3,4,t 0
Cash Collection Cashier Cash Collection Cashier self reported tax breakdown by periods 1 userid 0 or 1 0
Cash Collection Cashier Cash Collection Cashier show only accounts by balance 1 userid 0 or 1 0 A/R with a zero balance will not be displayed in the grid
Cash Collection Cashier Cash Collection Cashier year to collect 1 userid YEAR, 0 or null 0 If a year is entered, only A/R for this year will be displayed
default collection type Missing (credit card, cash, etc.)
Cash Collection Parameters Cash Collection credit card type 1 userid Table Lookup will need to use the new table CC TYPE
Cash Collection Parameters Govern allow Misc. Cash Receipts 1
Govern allow xxx Data Entry (Fee, Demand, Discount…) 1 Deprecrated
Govern bill validation verify
Govern cashier Id Text verify
Govern check validation
Govern credit card data entry Automatic/Manual Deprecated?
Govern default access type Table Lookup Property Control, Real Property, SRT, Name … Still in use?
Govern default cycle
Govern default payment data entry year
Govern display cycle code Deprecrated
Govern display fiscal year field Deprecrated
Govern display installment field Deprecrated
Govern print credit card receipt to verify
Govern print receipt log see roadmap
Govern receipt group 3 letter
Govern use cash drawer
Govern slip driver, font, etc. To be reviewed
Cash Collection Parameters Payment Data Entry deposit to be reviewed

 

By Machine

Registry Type Section Name Key Name Key Type Identification CD Key Value Encrypted Action Notes
Cash Collection Cashier Cash Collection Cashier cash drawer name 2 machine name EPSON TM-H6000IV Receipt 0 As shown in Windows Printer names
Cash Collection Cashier open cash drawer sequence 2 machine name 27;105 0
Cash Collection Parameters All the same section names and parameters as by User ID

 

 

100-USR-Registry

 

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

 

101-cc-frm-001-ofr

Cash Collection OpenForms Setup

Version 6.0 | Version 6.1

Overview

This reviews the standard setup for the cash collection form.

  • Business Entities
  • OpenForms Designer Setup
  • Profile Setup

The form distributed uses the following controls that may need to be setup:

Business Entities

The following business entities are used in the form:

  • OpenForms Designer
  • Profile Setup

 

 

101-cc-frm-001-ofr

 

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

101-cc-frm-002

Centralized Cash Collection Form – Payment Data Entry Feature

Version 6.0 | Version 6.1 (In Development)

Overview

The following is a feature of the Cash Collection Form.

Payment Transactions Data Entry

Summary Information Group

  • Transaction Type: Displays the type of transaction in the deposit
  • Deposit Number: Displays the current Deposit Number
  • Deposit Total: Displays the Total Amount received so far for this Deposit – (deprecated?)

Payment Data Entry Fields – to be reviewed

  • Year: Enter the year of the transaction – deprecated
  • Effective Date: Enter the date that the interest charges will take effect. The current date is displayed by default.
  • A/R Balance: This field is used to enter the amount to apply to the bill. By default, the balance due is displayed.
  • Total to Pay: This field is enabled only if a value is entered in any of the following:
    • Class Amount Billed, Discount, Fee, Interest and Penalty,Charge and Demand.
    • It displays the total amount due on the bill, including any entries made in the previously mentioned fields.

Fields in the Grid vary by Transaction Type

  • The fields in the header section of the Payment Grid vary according to the selection made in Transaction Type drop-down list
    • Payment
    • Deposit (only …. )
    • Post-Dated Payment
    • Voluntary Payment

Fields in the grid may include:

  • Discount: The current Discount value to apply on the A/R Balance. It is possible to change this amount only if you have the proper permission rights
  • Fee: The current Fee to apply on the A/R Balance. It is possible to increase or decrease this amount only if you have the proper permission rights
  • Interest: The current Interest value to apply on the A/R Balance. It is possible to change the amount if the user has the proper permission rights
  • Penalty: The current Penalty value to apply on the A/R Balance amount. It is possible to change the amount if the user has the proper permission rights
  • Charge: The current Charge value to apply on the A/R Balance amount. It is possible to change the amount if the user has the proper permission rights
  • Demand: The current Demand value to apply on the A/R Balance amount. It is possible to change the amount if the user has the proper permission rights

Receipt Information – roadmap

  • This section displays information regarding the transactions associated with the current bill. This is not the layout of the printed bill but the log of the current transactions.

OpenForms Action Buttons

  • New Payment: Click on the ADD button to create a new payment or transaction and clear the screen of previous values entered. – outstanding defect
  • Save a Payment: Click on Save to save the modifications made after a payment was accepted; for example, changing the payer’s name or distributing the paid amount into different payment types from the Money section. – to be validated that once save no more change possible
  • Deleting a Payment: Click Delete to remove the current payment.
  • Cancelling a Payment: Click Cancel to cancel the payment process and reset the form with the default values.- behavior to be validated
  • Browsing Payments:
    • Click the Browse button to display all the non-posted payments accepted by the current cashier or userid for the current deposit. – to validate
    • Click the Record Descriptor to list and select a payment record. Fields listed can be customized
  • Accepting a Payment: Click Accept to confirm the data on the screen, finalize the payment and to display all the other information required to process a payment. – deprecated? on save it is finalized?
  • Completed Transactions: Click Completed to complete the transaction using the default payment type and set the screen with the default values to start another transaction. To split the payment into different types, select the Money section. – No longer works this way

Payment Distribution

The following payment distributions are available UNDER CONSTRUCTION

  • Proportional Distribution
  • Non-Proportional Distribution (Pay this amount)
  • Payment Distribution by Detail Transaction (Class Code) – See roadmap

Once you have made a selection in the Access by field and your record(s) have been located, one of the following happens: – no longer works this way –

  • if only one record is found, a new series of fields appear on the Payment tab
  • if more than one record is found, the Receivable tab is automatically Selected

Redistributing the payment total

  • If the displayed total is different from the A/R total:
    • 1. Click New to add a new distribution.
    • 2. Select the record you want to modify. The information for this payment type is displayed at the bottom of the screen.

More Payment Entries

  • Use the Search to select More payments to process in the current transaction. This may be from another account, permit, license etc. or applied to a different bill.

Delete

  • Click Delete [X] to remove payment data entries from the list.

 

Payment Distribution by Detail Transaction

The Distribution tab of the Payment Data Entry function is used for processing payments by transaction type. – to change

Payment Data Entry With Proportional Distribution

To distribute payments using proportional distribution:
Note: Ensure that the Use Proportional Distribution option is selected

  • 1. Select the Receivable tab on the Payment Data Entry function.
  • 2. Select the applicable account.
  • 3. Enter the amount you are paying in the Pay this amount field.
  • 4. Click the Pay this amount button. This amount appears in the Total to Pay field. The amounts displayed in the Penalty and Interest text boxes are subtracted from the total. The balance appears in the A/R Balance text box.
  • 5. Double-click on the account in the upper part of the tab. The Distribution tab is displayed. Select the applicable account. All the transactions for the account are displayed by Transaction Type, A/R Class Code, Balance and Due Date. The A/R Balance is displayed as the Total Undistributed amount, along the bottom of the form.
  • 6. Select the transactions for which you are accepting payment or click Select All to select all transactions.
  • 7. Click Distribute Amount. The A/R Balance is divided according to the percentage of the total owed on each transaction.
  • 8. To accept the displayed distribution, click Save. Alternately, you can modify amounts by entering new data directly in the Amount Paid field.
  • Then, click Save.

 

Payment Data Entry Without Proportional Distribution

Note: Ensure that the Use Proportional Distribution option is deselected

For this type of distribution, enter the amounts to pay for each transaction directly in the Amount Paid column. By default, the balance for the transaction is displayed when you click in the column.

  • 1. Follow steps under 1 to 6 under Payment Data Entry With Proportional Distribution
  • 2. Click Save to return to the Receivable tab where you can process other payments under a different subsystem.
  • 3. Open the Payment tab to process the payment. The total of all amounts entered on the Distribution tab is displayed in the Money Received field, as well as on the receipt.

 

 

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

 

101-cc-frm-002