STARK 5.1.35.8255 - 8257 Bug Fixes

This Help File Page was last modified on 07/02/2021

<< Click to Display Table of Contents >>

Navigation:  STARK Version 5.1.35.XXXX New Features >

STARK 5.1.35.8255 - 8257 Bug Fixes

This Help File Page was last modified on 07/02/2021

Using the "Bug Fixes" List - Several "bug fixes" which have been completed during the 5.1.35.8255 update are shown in the table below:

Modules with Issues - All of the Program Module(s) and Forms that were Corrected are listed.

Chapter Links - The Chapter Links are provided for finding the revised instructions, illustrations, and details on the operational and/or usage of those corrections.

Anomaly (Bug) Fixes - A brief Description of the Issue and the correction is shown, sometimes with additional Chapter Links.

 

Program Module(s) Affected

Chapter Links

Description of the Big Fixes, and/or Anomaly Corrections

 

 

 

Module(s) with Issue

Forms Affected

8255 - 8257 Anomaly (Bug) Fixes

 

 

 

MKMS STARK

Various

There were several Forms which did not have the Access Rights feature correctly implemented.

The causes of these issues have been identified and corrected where reported.

MKMS STARK

Documents

The Subscriber, Prospect, and Vendor Documents options were not properly launching URLs.

The cause of this issue has been identified and corrected

 

 

 

Accounts Receivable

E-Payment

When adding a new Credit Card on the E-Payment Form the Card Type was defaulting to AMEX rather than beiing Blank

The cause of this issue has been identified and corrected

Accounts Receivable

Accounts Receivable

The problem with getting an error message if a User would Double-Click on a Detail Line Item on the Accounts Receivable report to open the associated Subscriber record has been resolved.

Accounts Receivable

E-Payment

Pay Methods

The Pay Method set as the Default was not always being presented as such when the E-Payment Form was opened.

The cause of this issue has been identified and corrected

Accounts Receivable

Edit View on the Subscribers Form

Receivables Section

The Terms field was being included in the Receivables section of the Edit View on the Subscribers Form which was incorrect.  

The Subscriber's Terms field is now only present on the Receivables Section in a Billing Address record [either the Subscriber's only location where the Billing Address is also the Service Address (i.e., a one Location Account), or when there is an assigned Billing Payer Address record].

Accounts Receivable

Subscriber Options

When first opening MKMS, the first Subscriber record was not including Service option, Payment Methods, Recurring Revenue and Receipts options were not showing in the Subscriber Options sub-menu.

The cause of this issue has been identified and corrected

Accounts Receivable

Receipt Posting

The Remaining amount on the Receipt Posting Form was not calculated (updated) correctly when allocating an amount to Invoices

The cause of this issue has been identified and corrected

Accounts Receivable

Receipts

Bounce

Subscriber options - Receipt - a Bounced Receipt was not updating the corresponding ePay transaction.

The cause of this issue has been identified and corrected

Accounts Receivable

Contacts Form

Selecting a Contact in the Contacts Form and then choosing Add Contact presented an error message:

"Table Contact: Data set not in edit mode"

The cause of this issue has been identified and corrected

 

Trying to save a Contact in the Contacts Form before specifically saving Contact Details (Phone, Email) cause the record to be saved without the Phone and/or Email information.

The cause of this issue has been identified and corrected

 

The Contacts Form was not respecting the CRUD settings assigned in the Employee Group and/or User Rights Forms

The cause of this issue has been identified and corrected

Accounts Receivable

Receipts Posting

Email Notification - When the Email Notification box is Checked on the Receipts Posting Form, and an Email address was inserted in the Email field, the system should create an Email Receipt Notification for that Subscriber but multiple account's receipts were being emailed to one Subscriber.

The cause of this issue has been identified and corrected

Accounts Receivable

Payment Method - Credit Card

The Enter/Edit Credit Card Form has been updated to correct a tab ordering issue

Accounts Receivable

Payment Method - Bank Account

The Enter/Edit Bank Account Form has been updated to correct a tab ordering issue

Accounts Receivable

Invoice - Export

When exporting the Invoice data the program was raising the error:

"RichEdit line insertion error"

The cause of this issue has been identified and corrected

Accounts Receivable

(Print) Invoices

The second page of an Invoice (when one was required) started printing very slowly causing the printer to add extra pages.

The cause of this issue has been identified and corrected

Accounts Receivable

Allocating Receipts

When Allocating Receipts, was unable to un-allocate itemized Receipt Allocations  to an Invoices.

The cause of this issue has been identified and corrected

Accounts Receivable

Post Auto Drafts

Post Auto Drafts process was sometimes creating Payment Requests for old Invoices

The cause of this issue has been identified and corrected

 

 

 

 

 

 

Accounts Payable

Auto Pay

The Auto Pay process was not deactivating a Fixed Payment Term for a Recurring Purchase once repayment had been completed.

The cause of this issue has been identified and corrected

 

 

 

 

 

 

Accounts Receivable

Service Tracking

 

Work Order Ribbon Menu Options

When trying to Order Inventory from within a Work Order using the Order Icon on the Work Order's Ribbon Menu, any User without Super User Access Rights was presented with an "Insufficient Rights to view form" message.

The cause of this issue has been identified and corrected

Service Tracking

Work Order Invoicing/Review

When Installed Equipment was identified for a Work Order record in the Work Order Invoicing/Review Form it was sometimes posted to the wrong Subscriber.

The cause of this issue has been identified and corrected.

Service Tracking

Work Orders

When Printing a Work Order with certain Rich Text Edit formatting in Comment fields, the internal RTF formatting characters were included in the printout and also included when printing the Invoice for that Work Order.

The cause of this issue has been identified and corrected.

Service Tracking

Quick Work Order

While attempting to create a Quick Work Order, the system displays the error:

Type mismatch for field Comments expecting Memo actual: String

The cause of this issue has been identified and corrected

 

 

 

Inventory Tracking

Inventory Usage Report

The Inventory Usage Report was not calculating the Extended Amount (Ext.Amount) correctly.

The cause of this issue has been identified and corrected

 

 

 

General Ledger

Accounts Payable

Trial Balance

Payroll Import

The Trial Balance was becoming Out of Balance after running a Payroll Import process.

The cause of this issue has been identified and corrected

 

 

 

 

 

 

Central Station Monitoring

Special Monitoring Info sub-tabs

In the Subscriber Panels section in the Monitoring tab of the Edit View of the Subscribers Form, when a User scrolled down below the Subscriber Panels section to the Special Monitoring Info sub-tabs the Action Plans, Notifications, CS Commands, and Holidays would disappear.

The cause of this issue has been identified and corrected.

Central Station Monitoring

Call Order

On the Monitoring tab of the Edit View of the Subscribers Form, within the Call Order sub-tab of the Subscriber Panels section: without selecting any Contact, Clicking on the Up or Down arrow presented an Access Violation error.

The cause of this issue has been identified and corrected.

Central Station Monitoring

Place an Account On Test

When an Operator (or any User) would Place an Account On Test, an incorrect Account might be placed On Test.

The cause of this issue has been identified and corrected.

Central Station Monitoring

Open/Closed Report

The Open/Closed Report was not returning the expected results.

The cause of this issue has been identified and corrected.