101-ar-brules-payment

Accounts Receivable (A/R) Payment Application Priorities Business Rules

Overview

The following explains the payment application and priority business rules.

Parameters

Mainly, the following parameters impact the payment priority order:

A/R Sub-System Priorities
Enter a number in the Priority field next to each subsystem to define the order in which bills are paid.
The higher the number, the higher the priority and the sooner the bill is paid.
Note: If a collection year is entered on the Accounts Receivable General Parameters form, no payments will be made on bills dated prior to this year.

Ignore Year:

Select Ignore Year to use only the subsystem priority when making payments.
Bills from the subsystem with the highest priority are paid first.
Otherwise, if this option is deselected, payments are made on all outstanding bills according to year; i.e., all bills from 2012 are paid before the bills from 2013.

Application Order

Payments application order:

Sub-System

  • Payments are made first to the subsystems with the Ignore Year option selected, according to Priority Number. The subsystem with the highest priority number is paid first.
  • Payments are then made to subsystems with the Ignore Year option deselected, according to Priority Number. The subsystem with the highest priority number is paid first.
    • Note: If a collection year is entered on the Accounts Receivable General Parameters form, no payments will be made on bills dated prior to this year.
  • If two subsystems have the same priority number, payments are made in alphabetical order.

A/R Class Code

Priority can be setup by Class code
Priority (Highest Number = Highest Priority)
The Class Code with the highest number is processed first; i.e., the class code assigned priority number 2 is processed before that with priority number 1.

Apply Before Installment/Apply Before Date
If two class codes have the same priority number, they are processed according to these 2 fields.
The following table defines the four possible combinations that can be set for these options:

 

Process Order Priority Number Apply Before Installment Apply Before Date
1 x x x
2 x x
3 x x
4 x

History / Inactive Account

(validated if in used for Cash Collection)
An account can be inactivated. This option is set in the Accounts Receivable A/R Inquiry Notes tab.
When turned on, no further Accounts Receivable transactions can be performed on the account.

 

101-ar-brules-payment

 

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-wm-upgrade

Workflow Management – Upgrade Notes

Module Overview, Configuration, Installation, OpenForms References, What’s New, wiki Map … Last Updated February 6th, 2017
VERSION 6.1 Under development
Upgrade Information
This page is intended for a master upgrade information page for existing customer upgrades to Workflow Management 6.1 OpenForms Technology.

UPGRADE PATH
For upgrades (prior to OpenForms Technology V6.1 or Govern for Windows)

  • 6.1 Module upgrade path requires OpenForms Technology v6.0 version
  • 6.1 GNA Conversion Utility from 6.0 to 6.1

TECHNOLOGY

  • Formulas and Logical Operands transformed to new Expressions
  • Transforming activity numbers to GUID (wikipedia)

See also

Module Impact Assessment | Upgrade | Install | Install from Scratch |

101-wm-frm-004

Workflow Management Form – Name Links

Version 6.1 (In Development)

Overview

The Name Links workflow form business entity (tab separator) provides all the different names that are linked to a workflow record (i.e Property Owner, Workflow Applicant, Primary Contact, etc.)

  • The types of links are user definable (see Link Type Editor).
  • The types of links available for a workflow Kind & Category are predefined by category (see Kind & Category Application Parameters – Supported Links)
  • Some links are created automatically when a Workflow record is created (new) if the option is setup (see Kind and Category Application Parameters) based on the Workflow (new)

The Form Name Links is the same as the Form Other Links for other properties, departments, buildings, workflows, inspections, hearings, miscellaneous billing, self reported tax, and personal property) and the only difference depends on the Form Entity Tab Controller properties MISC Configuration where Filter by Constants is added for names (Attribute ID Type is equal to NA_ID)

Name Links Entity (Tab Separator)

The workflow links controller adds a central location for all links associated with a workflow. There are two categories for these links:

  • Links to Names
  • Links to Everything Else: This category includes other properties, departments, buildings, workflows, inspections, hearings, miscellaneous billing, self reported tax, and personal property.

Configuration

See Link Type Editor and Workflow Linking Feature

Documentation

Workflow Linking Feature
101-wm-feature-Links.pdf
This document describes the following topics:

  • Configuring Links
  • Configuring links in the OpenForms Designer
  • Creating Link Types in GNA
  • Using Links in Govern

 

See Also

Workflow Other Links 101-wm-frm-005

 

 

101-wm-frm-004

 

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-wm-frm-005

Workflow Management Form – Other Links

VERSION 6.1 Under Development

Overview

The workflow form Other Links tab is used to link the workflow to parcels, other sub-systems, other workflow, etc.
Click here to return to the main workflow form

Link Types Configuration

The available link types that can be used on the workflow forms are defined in Govern Administrator, Application Configuration, Workflow Management, Link Types

Link Types Supported:

  • P_ID
  • ST_ACCT_ID
  • MB_ID
  • UB_ID
  • PP_ID
  • BLDG_ID and SEQ
  • WM_ID

 

Other Links

Under development

See Also

Workflow Management

 

 

101-wm-frm-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...

WM – Installation Queries

Workflow Management Installation Queries

Version 6.1 (In Development)

Overview

This page is intended for System Administrators, Business Analysts and Technical Service.
The following queries are used in OpenForms when installing or configuring the Workflow Management module.

System Queries for Workflow Management

For the complete list, see 101-wm-install-queries …

Navigation

The queries and views used to set up the workflow eSearch and the Tree Views.

  • Search Group, Styles, Objects
  • Tree Views

Workflow Form Link Types

Controller used to create workflow links to names (applicants, contacts, names, etc.) and other references (parcels, buildings, other workflow, etc.)
For examples of queries, click here (101-wm-install-queries-linktypes)
Suggested list results

Workflow View Query

Can be used on a form Tab, link, action button or on the Profile Cool Bar. This query needs to be customized in order to change its presentation in Govern.

 

 

101-wm-install-queries

 

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 – Table OFR – wm_parm_step

Workflow Management Table (wm_parm_step)

Version 6.1 (In Development)

Overview

This page is intended for internal use. It provides the structure of the standard tables related to STEPS creation. wm_parm_step SQL table structure.

WM_PARM_STEP

<table name=”WM_PARM_STEP” description=”Workflow step parameter table” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″>
<column name=”STEP_ID” type=”varchar” length=”36″ nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Step Id” />
<column name=”DEPT” type=”varchar” length=”2″ nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Workflow Department Code” />
<column name=”TYPE_CODE” type=”varchar” length=”15″ nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”TYPE Code (WM_PARM_TYPE.TYPE_CODE)” />
<column name=”STEP_NO” type=”smallint” nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Step number Unique for a DEPT and a TYPE CODE” />
<column name=”DESCRIPTION” type=”varchar” length=”30″ nonull=”False” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Description of Step” />
<column name=”DEFAULT_STATUS” type=”smallint” length=”” nonull=”False” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”DEFAULT_STATUS previously known as default_branch” />
<column name=”AUTO_INIT_NEXT” type=”smallint” length=”” default=”0″ nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”AUTO_INIT_NEXT” />
<index name=”GV_WM_DEPT_TYPE_STEPNO” unique=”True” primarykey=”true” columns=”DEPT, TYPE_CODE, STEP_NO” action=”add” gnaaversion=”6.1″ dbversion=”10.8″ />
<index name=”PK_WM_PARM_STEP” unique=”True” primarykey=”True” columns=”STEP_ID” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ />
</table>

WM_PARM_STEP_LK_STATUS

In the table WM_PARM_STEP_LK_STATUS we have the field STATUS_SEQ. Is it better to change the field COMPLETION_STATUS_SEQ to STATUS_SEQ in the table WM_ACTIVITY_STATUS ?
For COMPLETION_DATE I suppose we should not change it as we have STARTED_DATE field also ? – TO BE DETERMINED

WM_PARM_STEP_LK_ACTION

<table name=”WM_PARM_STEP_LK_ACTION” description=”Link between Workflow actions and steps” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″>
<column name=”TRIGGER_ID” type=”varchar” length=”36″ nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Trigger Id from USR_TRIGGER” />
<column name=”STEP_ID” type=”varchar” length=”36″ nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Step Id from WM_PARM_STEP_LK_STATUS” />
<column name=”STATUS_SEQ” type=”smallint” nonull=”true” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ description=”Status sequence from WM_PARM_STEP_LK_STATUS” />
<index name=”PK_WM_PARM_STEP_LK_ACTION” unique=”True” primarykey=”True” columns=”STEP_ID, TRIGGER_ID, STATUS_SEQ” action=”add” gnaaversion=”6.1.0.0″ dbversion=”10.8″ />
</table>

 

 

101-wm-ofr-wm_parm_step

 

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