CC – Voluntary Payments in Cash Collection

Voluntary Payments in Cash Collection

Version 6.0 | Version 6.1 Scheduled for 6.0.1611

Overview

Use the Govern OpenForms Cash Collection user form to accept advance or voluntary payments on Real Property and Personal Property tax accounts.

An Advance Payment or Voluntary Payment (VP) is an amount that is paid before a bill is received. This type of transaction can be useful for taxpayers who would like to cover bills during a predicted absence.

When a voluntary payment is saved, an Open Cash Credit (OCH) is automatically generated. When you post the Voluntary Payment (VP) using the Cash Collecting Posting batch process, the Open Cash Credit (OCH) is also posted. It is applied on the next bill generated for the account. The VP and OCH transactions can be viewed in the Detail section of the A/R Inquiry form, both before and after they are posted.

This wiki page describes the following:

  • Administrative Setup
  • Configuration
  • Setting Security on Cash Collection Parameters
  • Processing a Voluntary Payment
  • Viewing the Voluntary Payment Transaction in A/R Inquiry
  • Posting the Voluntary Payment

 

Documentation

To view the information on this page in pdf format, click on the following link.

CashCollectionVoluntary.pdf

Related Information

For further information, see the Cash Collection Form

Business Rules

Accounts

In Govern OpenForms, a Voluntary Payment can be applied on an account from any year, regardless of whether there is a balance or not.
An AR_ID must already exist for the person or property associated with the payment.

In Govern OpenForms, a Voluntary Payment can be applied on a transaction from any year, regardless of whether there is a balance or not.

Subsystems

The voluntary payment option is available to Real Property and Personal Property tax.

Administrative Setup

General Parameters

The following User Registry parameters are specific to Cash Collection:

  • Show Only Accounts with Balance
  • Year to Collect

These parameters are available on the User Registry Manager in Govern and in GNA > Application Configurations > Accounts Receivable > Cash Collection Parameters.

Showing Transactions for a Specific Year Only

In Govern OpenForms, Voluntary Payments can be accepted for any year. If you want to display existing transactions for a specific year only, perform the following set in the Cash Collection Parameters available in Govern.
To create a filter by year:

  1. Launch Govern.
  2. Open a Profile that contains the Cash Collection form.
  3. Select the Payment Data Entry tab.
  4. Click the Cash Collection Cashier icon.
    The Cash Collection Options form opens.
  5. Enter the year that corresponding to the transactions that you want to display in the Year to Collect parameter.
  6. Click Save.

Print Receipt

Follow the instructions for setting up the Print Receipt report as described in the Cash Collection documentation. See Print Receipt.

Configuration

The Cash Collection form contains custom search parameters for Real Property and Personal Property voluntary payments.
To view or modify the configuration for these custom searches:

  1. Launch the Govern OpenForms Designer (OFD).
  2. Open the Cash Collection form (CC01).
  3. Select the Payment Data Entry entity.
  4. Select the CCPaymnetDataEntry_Control.
  5. Expand Properties > Misc in the Properties explorer.
  6. Select AR008 – Accounts Receivable in the A/RInquiryForm parameter.
  7. Select arPayment – A/R Payment Data Entry in the SearchGroup parameter.
  8. Select ppPersonalP – Personal Property Search in the VpSearchGroupForPP property.
  9. Select pcProperty – Property Search in the VpSearchGroupForPP property.
  10. Click Save if you have made any changes.

Setting Security on Cash Collection Parameters

The security settings for Voluntary Payments are the same as for any Cash Collection transaction. This section describes those settings:
To view the security settings for Cash Collection:

  1. Launch the Govern OpenForms Designer.
  2. Open the Cash Collection form (CC01).
  3. Select the Payment Data Entry entity.
  4. Select the Security icon.
  5. The Payment Data Entry form includes the Cash Collection Payment Data Entry custom control, CCPaymentData_Control.
    As with all security permissions in the OFD, the majority of these settings are enabled by default. The option to Apply Late Charges is the exception.
    The settings are as follows:
    Can Edit Payment
    Can Edit Principal
    Can Edit Interest
    Can Edit Penalty
    Can Edit Fee
    Can Edit Discount
    Can Edit Change
    Can Edit Demand
    Allow Misc. Cash Receipts
    Allow A/R Cash Distribution
    Allow Apply Late Charges: This setting is disabled by default.
  6. Modify these permissions as described in the OpenForms Designer documentation.
    Note: Permissions must be defined separately for every combination of Security Type, Profile, and Role or user.
  7. Click Save if you have made any modifications.

Creating a Voluntary Payment

Voluntary Payments are created on the Cash Collection > Payment Data Entry form. The steps to creating a voluntary payment transaction are similar as those for a standard payment. The following difference applies.

When you create a Voluntary Payment, you need to enter the subsystem (either Real Property Tax or Personal Property Tax), the year, and the cycle code for the payments that you want to create.

For example, the following parameters could be entered for an advance or Voluntary Payment for Real Property taxes.

  • Subsystem: Real Property Tax
  • Year: 2018
  • Cycle Code: Municipal Tax

If a record matching the search criteria exists, it is displayed under Distribution. If no record exists for the year, one is created. A Voluntary Payment can be created for any year.

The record is displayed under Distribution.

Overview of the Voluntary Payment Transaction Process

The steps for creating a Voluntary Payment transaction are:

  • Selecting the Deposit Number for the Voluntary Payment
  • Performing the Search
  • Completing the Payment Parameters
  • Running the Cash Collection Wizard
  • Viewing the Payment in A/R Inquiry
  • Posting the Payment
  • Viewing the Posted Payment in A/R Inquiry

Selecting the Deposit Number for the Voluntary Payment

The following procedure is mandatory. All A/R transactions in Govern OpenForms must be associated with a deposit number.

  1. Launch Govern.
  2. Open a Profile that contains Cash Collection.
  3. Open the Cash Collection form.
  4. Select the Deposit Management tab.
  5. Create a new deposit number or select an existing one.

The Transaction Type must be Payments.

Creating the Voluntary Payment

To create the Voluntary Payment transaction on the Cash Collection form:

  1. Select the Payment Data Entry tab on the Cash Collection form.
  2. Click New.
    The deposit number you selected on the Deposit Management tab is entered automatically in the Deposit Number field.
  3. Select Voluntary Payment from the Transaction Type field.
  4. Select the subsystem from the Subsystem drop-down list.
  5. Only Real Property Tax and Personal Property Tax are available.
    Enter a year in the Year parameter.
    This is the year of fiscal year during which the transaction is applied.
    For example, if you are creating an advance or Voluntary Payment for a 2018 tax bill, enter 2018.
  6. Enter the cycle code in the Cycle Code parameter.

The Cycle Code is mandatory for the Real Property Tax and Personal Property Tax subsystems.

Performing the Search

You need to perform a search using a Dynamic Search group and criteria.
To perform the search:

  1. Select a Search group in the Search section.
  2. Enter the required criteria in the Criteria section and click Enter on your keyboard.

If a record matching all the search criteria is found, it is displayed under Distribution. If no record is found, one is created and displayed under in the Distribution section.
An A/R barcode is created for the transaction.

Completing the Voluntary Payment Distribution Parameters

To complete the transaction, you need to enter the effective date and the amount. The effective date is the date that the payment is effective. By default, this is the current date.
A voluntary payment is effective before it is applied on a tax bill.

To complete the Payment Distribution parameters:

  1. Select the effective date of the transaction in the Effective Date parameter.
  2. Select a transaction and enter the amount of the voluntary payment in the Amount field.

Completing the Payment

Once you enter an Amount in the Amount field beside the record, it is automatically entered in the Money section. You can select the method of payment, such as cash, check, certified check, credit or debit.
You can enter multiple payment types. For example, a payment can be made partially by credit card and partially by check.
To complete the payment:

  1. Select a method of payment in the Type drop-down list.
  2. Enter an amount if it is different from the displayed amount.
  3. Enter a reference, such as the check number in the Reference field.
  4. Repeat steps 1 to 3 as required if there are multiple payment types.

Payer

All Cash Collection transactions must include payer information.
To add payer information to the transaction:

  1. Click the ellipsis button in the Payer Name section of the Cash Collection form.
  2. Do one of the following:
    Click Search to search for a name in the database.
    Click New Name to add a name that is not in the database.
    If you want to add the name and address account directly, the Name and Address form must be included in the Profile.
  3. Click New Payer Name to a new payer.

Launching the Cash Collection Wizard

The Cash Collection Wizard launches automatically when you click the Save button.
To launch the Cash Collection Wizard:

  1. Click the Save button on the Cash Collection form after completing the payment.
    The Cash Collection Wizard opens.
    The payment amount and type are displayed.
  2. Collect the payment and click Next.
    The full amount and payment type are displayed.
  3. Click the Print button to print the receipt.

Print Receipt

The Print Receipt can be customized. The default receipt is shown in the following screen shot.

Finishing the Payment

To finish the transaction:

  1. Click Finish. on the Cash Collection Wizard once you have printed the receipt and the transaction is complete.
    The completed transaction is displayed on the Cash Collection form.
  2. Hover your mouse over the transaction to view the barcode.

Viewing the Voluntary Payment Transaction in A/R Inquiry

You can view the Voluntary Payment transaction, once it is saved, directly in the A/R Inquiry form.
To view the Voluntary Payment transaction in A/R Inquiry:

  1. Do one of the following, according to your setup:
    Open the completed transaction in the Cash Collection form and double-click on the transaction.
    Launch the A/R Inquiry form and perform a search using the barcode of the transaction.

The Voluntary Payment and Open Cash Credit transactions are displayed in the A/R Inquiry Detail.

Posting the Voluntary Payment

A Voluntary Payment can be posted, as any other Cash Collection Payment, with the Cash Collection Posting batch process.

Prerequisites

Ensure that you have access to the Department responsible for the A/R transaction.

Running the Batch Process

To post a voluntary payment:

  1. Launch Govern.
  2. Open a Profile that contains the Cash Collection Posting batch process.
  3. and through which you can access the required A/R transaction.
  4. Select the Batch Process Explorer.
  5. Select the Cash Collection batch process.
  6. Select the Voluntary Payment.
  7. Click Run.
  8. Click the Processing tab to view the batch process logs.

For details, see Cash Collection Posting.

Viewing the Posted Payment

Once the payment is posted, you can view the Voluntary Payment and Open Cash Credit transaction on the A/R Inquiry form.
To view the Voluntary Payment transaction in A/R Inquiry:

  1. Do one of the following, according to your setup:
    Open the completed transaction in the Cash Collection form and double-click on the transaction.
    Launch the A/R Inquiry form and perform a search using the barcode of the transaction.

 

 

101-cc-frm-011

 

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

CC – Cash Collection Receipt Report

Cash Collection (CC) Receipt Report

Version 6.0 | Version 6.1

Overview

This is the standard receipt printed when using Cash Collection module.

Available in GA 1606.

Purpose of Receipt

– Undefined –

Process Name

cc-rpt-058

Sample Report

A sample report will be provided when available.

 

 

101-cc-rpt-058-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-rpt-060-CheckValidation

Cash Collection (CC) Check Validation Report

Version 6.0 | Version 6.1

Overview

This is the standard report used to print the check endorsement when using Cash Collection.
Available in GA 1609.

Process Name

cc-rpt-060

Sample Report

– To be provided when available –

 

 

 

101-cc-rpt-060-CheckValidation

 

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

 

Dataset Treeview

Dataset Treeview

Overview

Datasets that appear in the Dataset Treeview are populated with the results of searches made through the Search form. Records that are loaded into the Dataset Treeview may be appended to through the Saved Dataset pane, or deleted directly in the Treeview pane.

Populating the Dataset Treeview

To populate the Dataset Treeview with search results…

  1. When the Predefined Searches pane is in its default position, place your mouse pointer over the tab to display the search form (A).
  2. In the form perform a search type; for this example we will perform a property search by P_ID.
  3. Click Search for Result.
  4. Search results will be displayed in the lower portion of the search form.
  5. Click Load to the search result to transfer the search result records to the Dataset Treeview pane.
  6. If the Dataset Treeview pane is not displayed, click its tab at the bottom of the pane.

 

The Treeview Explorer

The Treeview Explorer displays record information in a hierarchical arrangement. In the Treeview panel, you are able to expand or contract a record by clicking on the arrowhead icons.
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.
As you select each level of information, the data is displayed in the appropriate OpenForm when it is displayed on the right hand side.

Record Edit Confirmation

When a dataset has been loaded, it is easy to select and begin to edit a record. This ease of selection may at times be a detriment as at times the wrong record may be selected, and the user immediately begins to edit in error. It has been determined that if a secondary confirmation is introduced during the record selection process, there is less chance of erroneously editing the wrong record.

Through the Govern New Administration (GNA), the Record Edit Confirmation option can be enabled to add a secondary confirmation. When Record Edit Confirmation is enabled, after the user selects a record, they are obliged to click on a secondary icon (A), to fully unlock the record for editing.

To enable Record Edit Confirmation…

  1. In GNA, select System Parameters (tab) > General Connection Parameters.
  2. In the General Connection Parameters form, locate the Organization Parameters group and select The user must explicitly enable editing for each parcel option.
  3. Click Save to save the option.
  4. To close the form, click Exit.

When this option is enabled, after loading a dataset, users may still select a record for editing, but the selected record will have an icon beside it. The user must click the icon in order to fully unlock the record for editing.

System Architecture

For all details regarding the Govern Treeview Architecture, refer to 101-std-fea-005-Treeview_Architecture.

What’s New

Context Menu in Dataset Treeview

NEW! Users of the Dataset Treeview will note that when it is populated with one or more records, there is a description for each record. This description can be a Parcel ID, an Account Number, and so on. A quick method of deleting individual records is to hover the mouse pointer over a record. When the width of the Dataset Treeview pane is wide enough, placing the mouse cursor over the description will display an “x” that can be used to remove the record. Unfortunately when there is insufficient space, i.e. the space is not wide enough to display the full description, the “x” is not visible. To address this situation a context based menu has been added to the interface.
TreeviewContextMenu00.png
To display this menu…

  1. Right click on the record of interest in the Dataset Treeview.
  2. In the floating menu, you now have option for additional functions that appear beside the record when the entire line is visible.

By default, there will be an option to “[x] Remove”. When there are other options, e.g. Edit, they will also be presented in the menu.
This feature is available in the following releases: 6.0.1611.0067 / 6.0.1702.0080 / 6.1.1611.0060 / 6.1.1702.0121

Reposition

Previously, when performing a search of records with the same NA_ID but multiple ST Account numbers, when you copy the record to the Treeview, the system would only select the first account. Now the selected record will be sent to the Treeview. (Available in release 6.0.1503)

Hibernate Mode

This behavior of selecting only the first account also applies to the Hibernate process. As Govern is restored from a hibernation if a second or third account is selected before hibernation, when the application is restored, although the NA_ID is correct, only the first account will be displayed.

Load to Treeview and Add (Append)

As data is loaded or appended to the Treeview from the Search, or the Saved Datasets form, the following rules apply:

  • When a record is selected for append, only new files will be loaded. If previously loaded, the file will not be reloaded into the Treeview.
  • If no search result is selected, the Add to Search Results button will be disabled.

Hibernate

Previously the Hibernate would store the NA_ID of the records displayed in the various panes that are opened in the interface. Now to maintain the fidelity of the hibernated user environment, all Govern ID’s are used; i.e. NA_ID, P_ID, ST_ID, and so on.

NOTE: User Hibernate information is stored by user in (Table: USR_HIBERNATE). The following query will display the hibernation information for “userName”

SELECT *
FROM USR_HIBERNATE
WHERE USR_ID = ‘userName’;

Treeview Synch
In Govern for VB6, external tables (PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL), were used by external applications and reports to automatically know the current recordset and currently viewed parcel. In Govern release 6.0 and upwards, these external tables are being phased out and the functionality provided by them will need to be reproduced.

NEW! The Treeview sync. feature saves the contents of the current profile in (Table: USR_SAVED_DATASETS) with a “Saved Dataset” name of “AUTOSAVE” under (Column: USR_SAVED_DATASETS.SAVED_SET_NAME). Should a profile be changed, the dataset loaded in the Treeview will be automatically synchronized to (Table: USR_SAVED_DATASETS).
This feature recreates the functionality provided by the three (3) external tables that were used in Govern for Windows, (Tables: PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL). For example users could run a batch process on a saved external dataset as opposed to a set range.

NOTE: In release 6.0 a simultaneous save will be made to (Table: PC_EXTERNAL) and (Table: USR_SAVED_DATASETS), Tables NA_EXTERNAL and PM_EXTERNAL are no longer supported.
In release 6.1, all three (3) tables PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL will not be supported.

  • PC_EXTERNAL (Supported in release 6.0; not supported in release 6.1)
  • NA_EXTERNAL (Not not supported in release 6.0 and 6.1)
  • PM_EXTERNAL (Not not supported in release 6.0 and 6.1)

Enabling “Synchronize Dataset Treeview”

This feature is enabled in the User Registry through the User Registry Manager. The Options button is located below the Govern suite button in the Govern User Interface.

  1. Click the Options button; click Options.
  2. In the Registry Manager form, verify that the Registry Filter is set to User ID.
  3. Under the Section Name column, locate Synchronize Dataset Treeview; click to select the option under the Key Value column.
  4. Click Save to save your changes.

When you return to the Govern interface, the Treeview Sync. icon will be enabled. This is a toggle, i.e. ON/OFF button that will enable or disable the feature.

Location of Data

As indicated above, all data will saved in (Table: USR_SAVED_DATASET). Associated columns are as follows:

COLUMN DESCRIPTION
USR_ID User ID
SAVED_SET_NAME By default will be AUTOSAVE
REF_TYPE “P_ID”, “NA_ID”, etc. Based on the profile Key Type
SORT_SEQ Order in the Treeview
IS_CURRENT TRUE if the current item in the Treeview

NOTE: All data will be saved based on the Key Type of the profile. This is done so as to support multiple Key Types at the same time.

  • The data is not saved by profile, so the synchronization for a Key Type will be done on the last active profile using that key type.

The desired behavior when there is more than one Treeview dataset for the same ID Type is to perform a reload when the user switches from one instance to another.

Business Rules

Programmers should note the following Business Rules.

When Parameters Change:

  • From TRUE to FALSE – Delete all SAVED_SET_NAME that have a status of “AUTOSAVE” and replace the value with the current USR_ID
  • From FALSE to TRUE – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with the current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
    – Starts monitoring Dataset tree view changes

When Opening Govern (Before opening Profiles):

  • Starts monitoring Dataset tree view changes if Flag is on

When monitoring Dataset tree view changes:

  • If Active profile changes – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
  • If Treeview is replaced (By eSearch / QueryTool / Matix/…); i.e. a Load…
    – Delete All SAVED_SET_NAME equal to “AUTOSAVE” for current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the Treeview datazzz
  • If an item is added into the Treeview (By eSearch / QueryTool / Matix /…); i.e. Add Or AddAndReposition
    – Insert the new item into USR_SAVED_DATASET
  • If an item is removed from the Treeview (using the X button); i.e. Remove
    – Delete the new item into USR_SAVED_DATASET
  • If the active item changes in the Treeview; i.e. Reposition()
    – Update IS_CURRENT in USR_SAVED_DATASET
NOTE: This is done by setting the current id to -1 and setting the prior id to 0

 

NOTE: Always hide AutoSave SAVED_SET_NAME from saved dataset functions

  • V6.0 (only) – PC_EXTERNAL will need to be maintained at the same time
  • V6.1 – All three (3) tables, PC_EXTERNAL, PM_EXTERNAL, and NA_EXTERNAL are to be removed.

Related Topics

Dataset Treeview Temporary Records

Forms Explorer
Reports Explorer

 

 

101-std-fea-005

 

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

 

Multimedia

Multimedia

Version 6.1 (In Development)

Overview

The Multimedia OpenForm is used for linking multimedia files to property, name, permit and sales records; for example, building drawings can be linked to a property record, photographs or video files to a complaint, building plans can be scanned and linked to a permit or the property deed to a sales record. PDF documents and unlimited text lines can used as annotations to the file. Each property control OpenForm can create and maintain customized multimedia links. The Multimedia tab can be configured with any number of different OpenForms in order to create a link to the following:

  • Parcel
  • Name
  • Inspection
  • Hearing
  • Permit
  • Workflow
  • Offense
  • License
  • Sale
  • Activity

Multimedia can be recorded by property, name or by a multitude of reference ID’s (Account Number, Sale, Building, Inspection, Split Merge Transaction, Permit, Complaint, and so on.)

For setup information, see Standard Feature Installation of the Multimedia control.

 

NOTE: The Multimedia tab can be found in numerous profiles as it is a general usage form that allows users to attach multimedia files to records as needed.

 

Multimedia Document Types

Govern can support a variety of Multimedia documents. These documents can range from image formats such as .BMP, .TIF, .JPG, to Adobe Acrobat .PDF, or Microsoft Word .DOC files, etc.

Displaying the Image

When a multimedia image document has been linked to the current record, the document will be displayed in the right hand pane when you open the form. Otherwise, click Open Document or doubleclick on the image the Preview pane to display the document. The document will be displayed with the application that is set as the default for viewing the file type that is selected. For example if you have
Microsoft Word installed and you preview a .doc file, Microsoft Word will be launched. Use the controls of the previewing application to close the window and return to the Multimedia tab.

Setup Options
Depending upon the business requirements, through the parameters, the same form controller can be configured with different keys and for different multimedia types.

Technical information

Below is the technical setup and configuration document for the Govern Multimedia Documents custom entity.
See – 101-std-frm-001 Govern 6.0 Multimedia Documents

 

 

101-std-frm-001

 

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

WM Technical Specification and Information

Workflow Technical Specification and Information

(In Development)

Description

Generally, the workflow function can be imagined as a container with all the data related to a process (inspection, collection, verification) as well as a list of steps and tasks (activities) needed to complete this process.

What’s New

[to be validated] The same function is now used for all workflow types (kind). Prior to version 5.0, there was a different container for each kind (i.e. complaints, workflow, permits, licenses, hearings, etc.)
Workflow can be linked to a property, name, account, etc. (See key ?references? [to be validated] )

Database Modifications
The following modifications were made to the database in order to enable this feature.

  • Table PM_LK_MASTER: has been linked to Table PM_COMPLAINT in version [6.0]
  • Table PM_TYPE: 2 new fields ENTRY_KEY_TYPE and CATEGORY in version [5.1] and over [5.1 to be validated]

 

Setup Instructions

After the workflows have been created and setup, the administrator needs to MANUALLY set the following fields in the database.

TABLE = PM_TYPE

  • ENTRY_KEY_TYPE: The main KEY (root) database attribute name: p_id, na_id, account_id?, bldg_id?, user_id?, etc.
  • CATEGORY: Used to classify the workflow types. Used to populate the combo box custom control.

Use the Access Attach Table or SQL Manager to modify.

Database Diagrams

Govern for OpenForms Release 6.x – Database Diagrams

The following links to the page for Database Diagrams for Govern OpenForms modules.
Link to Land Management in the Land Management 6.1 section
PM_LK_PERMIT_TYPE

* The “KIND” field in the PM_MASTER table should determine what table to use:

KIND Description
b Building Permits (PM_BLDG_PERMIT)
bn Bonds
a Approvals (PM_APPROVAL)
bl Business License (PM_BUSINESS_LIC)
al Animal License (PM_ANIMAL_LICENSE)
e Electrical Permits (PM_ELECTRICAL)
d Decisions (PM_DECISION)
g General Permits (PM_GEN_PERMIT)
p Plumbing Permits (PM_PLUMBING)
pa Prosecution / Appeals (PM_PROSECUTION)
l License
lp License Parcel

** For license (l) there is no need to go through the PC_PARCEL and PC_LK_PARCEL_PM tables.

Product Specification

Workflow types

  • Unlimited number of workflow types can be defined
  • Unlimited user added fields can be tied to a workflow type
  • Up to 3 auto-generated unique workflow escalation numbers (Permit example: Application no. A0001, Permit no. P0001, Certificate no. C0001)
  • Steps in the processes (activities) can be auto-generated, initiated ?

Workflows can be linked to:

  • Unlimited properties (Not currently available in 6.0)
  • Unlimited names (Not currently available in 6.0)
  • Other related properties (if property base)
  • Other related names (if name base)

Activities can triggers multiple actions and interact with different groups

  • Generate inspections
  • Schedule meetings, hearings, inspections, etc.
  • Generate fees
  • Generate AR
  • Create multimedia documents
  • Run reports (Crystal Report / SSRS) – Send and Attach
  • Generate global messaging
  • Execute queries (update, validate, etc.)
  • Etc.

User actions:

  • Create, Update, Save and Delete
  • Override capabilities by security access type
  • Pre-defined information can be overridden on Create and Delete
    • ex: Link to Names, Standard emails, Fees, Inspections, etc.
  • AR and GL Accounts can be overridden on Create and Delete and also during fee override

 

101-std-frm-002-spec

 

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