STARK Updates 8253

This Help File Page was last modified on 05/24/2019

<< Click to Display Table of Contents >>

Navigation:  STARK Version 5.1.35.XXXX New Features >

STARK Updates 8253

This Help File Page was last modified on 05/24/2019

Welcome to the Summary Page with the New Features in the MKMS Version 5.1.35.8253 Release.

Several "bug fixes" have been completed during this series of updates.

The major changes and enhancements are included in the Features List below.

 

HelpFilesStark

Understanding the Features List:

All of the Program Module(s) that are Affected are listed.

The Chapter Links are provided for finding the instructions, illustrations, and details on the operation and usage of the new feature(s).

A brief Description of the Enhancement is shown, sometimes with additional Chapter Links.

 

Program Module(s) Affected

Chapter Links

Description of the Enhancement

 

 


Accounts Receivable System

Fully Automated Recurring Billing

Automatic Billings Setup Wizard

MKMS now provides a Fully Automated Recurring Billing process which identifies and Invoices those Subscribers who have Recurring Revenue records defined, every day.  

An Automatic Billings Setup Wizard is also provided.

Accounts Receivable System

InnoEPay

Multiple InnoEPay PINs are now supported based on the number of Banks into which InnoEPay must deposit Receipts.

 

When using InnoEPay as your Company's Payment Gateway and your Company is using more than one Bank for making Deposits via InnoEpay transactions, each InnoEPay Payment Gateway will make deposits directly to only one Bank.

Therefore, when your Company is using additional Banks for depositing InnoEpay transactions, your Company will need to get additional keys and have additional Payment Gateways defined - one for each Bank that will get those Receipts..

As those additional Payment Gateways are identified, consider a naming method such as InnoEPay-Bank1, InnoEPay-Bank2, etc., with the actual Bank Name used in each case.

Also, if your Company will tokenize Credit Cards, all Tokens will be based on the default, so the other InnoEPay Payment Gateway will automatically recognize those Token. 

Accounts Receivable System

Billing Cycles

The Billing Cycles Form has been substantially updated to accommodate a variety of Payment Gateways and other automatic payment methods relating to the available Automatic Billing process.

Accounts Receivable System

Auto Billing

The original Auto Billing process which is selected and run manually, will now use the more powerful Fully Automated Recurring Billing engine.

Accounts Receivable System

Auto Billing

When ePay transactions are created as the Auto Billing process runs, the Batch Number for a Receipt will be comprised of the Receipt Type Code "#" followed by the Month "99" and Day "99" on which it is actually Deposited  such as "80301" for a Check that was deposited on March first.

See the Defining your Company's Batch Numbers discussion in the E-Payments chapter for more information.

Accounts Receivable System

Customer History Grid

Email Notifications for Invoices will now be inserted into the Customer History Grid,

Accounts Receivable System

Customer History Grid

Email Notifications for Receipts will now be inserted into the Customer History Grid,

Accounts Receivable System

Customer History Grid

Normally, when the History Options Date Range is selected (e.g., Last 30 Days, Last Year, etc.), only those transactions dated within that selected Date Range will be displayed.

However, there are times when your Company may post-date transactions to some future date, and those future transactions were never listed until they came within the selected Date Range.

Now, when the All History Date Range is chosen, transactions as much as two years into the future will be displayed.

Accounts Receivable System

Printing Invoices

Added a "Dealer" option in the Details section of the Print Invoices dialog.   Choosing this option provides the following functionality:

The Invoice report's Dealer format will have an initial summary page with the Dealer's Name and Sale Items that were Invoiced based on the other specified parameters, grouped by Sale Item ID and Price, displaying how many there were for that Sale Item at that Price.

Thereafter, the Invoice report's Dealer format shows subsequent pages with detailed sales information.

 

 


Service Tracking System

Technician Scheduling

Using the Pending Work Orders Grid

 

The Pending Work Orders Grid now offers a Dept (Name of the Department to which the Work Order is assigned) as an available column option.

Service Tracking System

Completing a Work Order

Services Performed - This field on the Work Order Form is used to enter a detailed description (up to 500 characters) of the work that was performed.  

This field may new be updated even after a Work Order is Completed and Invoiced because additional information may - and frequently does - become available later.

 

 


Inventory Tracking/Job Costing

Job Task Templates

There is a new Job Task Template option in the Miscellaneous sub-menu of the General Maintenance Menu.

Each Job Costing record will typically have many Job Task entries.

To speed up data entry and make these type of Job Task entries consistent, a number of Job Task Templates may be defined.

 

A Job Task Template definition may represent a specific set of one or more Job Tasks which your Company frequently is required to perform when installing and/or upgrading specific types of systems.

Multiple Sets of this combination of Service Type, Task, Contracted and Amount entries may be included in each Job Task Template.

Each set may have any combination of Service Type, Task, Contracted and Amount entries.

Inventory Tracking/Job Costing

Job Tasks

Due Date - This field will be now populated with the Estimated Completion Date identified in the heading of the Job Costing record when it is initially entered.  It may be changed as appropriate.

Use the Drop-Down Calendar/Date Entry field to revise the Date when this Job Task should be finished.

 

Estimated Completion Date - This field will still be populated with the Estimated Completion Date identified in the Job Costing record when it is initially entered.

Use the Drop-Down Calendar/Date Entry field to change the Date when this Job Task is expected to be finished.

This date is used in the Job Tasks Aging As Of Report to track how the Service/Installation Department(s) are keeping up with their work (Job Task) requirements.

Inventory Tracking/Job Costing

Job Tasks Report

The Job Tasks Report has been revised by adding a Due Date field and a new Due Date selection option.

Inventory Tracking/Job Costing

Job Task Aging As Of Report

The Job Task Aging As Of Report has been revised by adding a Due Date field.  Age of Job Task represents the number of Days between the Due Date and the As Of Date selected.

 

 

 

Central Station

 

Main Form - Optionally, How to Refresh current User's Alarm Group assignments

   HOW TO TEST:

 

   1. Log into CS

 

   2. Start Signal Processing

 

   3. Go to %LOCALAPPDATA%\MKMS and open the most recent CS Log file.

 

   4. You should not find the following text in the file:

 

   Signal Processing-NonRestoredTimerTimer - Refreshing Alarm Groups for SAW

 

 

   Signal Processing-NonRestoredTimerTimer - Alarm Groups for SAW refreshed.

 

   OR

 

   Signal Processing-NonRestoredTimerTimer - Refreshing Oper Skills for SAW

 

 

   Signal Processing-NonRestoredTimerTimer - Refreshing Oper Skills for SAW refreshed.

 

   5. Stop Signal Processing and log out of CS.

 

   6. Go to Company Settings and set one or both values for "RefreshSkillList" or "RefreshAlarmGroups" to T

 

   7. Restart CS and Signal Processing. You should find the above verbiage in then CS Log file.

 

 

   Other Checks

 

   - Verify operation by adding a new alarm group and employee skill and assigning it to an operator. Generate a signal with the newly added information and confirm the operator is presented the signal.

 

   - Verify operation when one flag is on and the other is off.