Version 10.1.0.1 - February 19, 2020

Top  Previous  Next

2020 UPDATE FEES RELEASE

 

Initial Software Release for 20202

 

This update is the first software release for 2020 and will require that the 2020 Update Fees are current.  AccuBuild Version 10.1.0.0 is the last update for the 2019 Update Fees renewal.  Please contact AccuBuild Support for more information on update renewals.

 

 

USER INTERFACE - CENTER SCREEN UPDATES

 

ENHANCEMENT -  New Warning Messages for Blank Fields [PMID Ref No 15473]

 

The Employee Center Screen has been updated to display a warning message if any of the employee name fields are blank when the Save Button is clicked.  All three name fields will be checked including the Last Name, First Name, and Middle Initial.

 

The Client Center Screen (Clients / Vendors / Customers) has been updated to display a warning message if the Name field is blank when the Save Button is clicked.

 

 

Corrections - New Validations to prevent Blank Records  [PMID Ref No 15473]

 

All of the Center Screens have been updated to prevent blank records from being added.  If a new record was added but NOT saved, and then the X Button was used to close the screen, the records were being saved.  The user will now be directed to either Save or Cancel the current record changes before they will be allowed to close the screen with the X Button.  The following Center Screens were updated with this new functionality:

 

oEmployee Center

oJob Center

oLedger Center

oOrders Center

oEquipment Center

oInventory Center

oClient Center

 

The Ledger Center screen was updated to prevent a zero account number from being saved and also to allow a zero account to be deleted if it was accidentally added in a previous version of AccuBuild.

This

 

 

ACCUBUILD TIME CLOCK APP

 

ENHANCEMENT - New Stored Procedures for ABTimeClock 400 App [PMID Ref No 14887]

 

Three new mobile stored procedures have been added to the stored procedure library which will be required by the new ABTimeClock 400 App.  These new stored procedures allow for the App to work in Dual Mode whereby each individual company device (phone or tablet) can function in 'Spread by Supervisor' mode or  'Spread by Employee' mode.

 

oabm_TimeCardLookupControlSettings_400

oabm_GetEmployeeSummary_400

oabm_GetEmployeeSummary_DeptFilter_400

 

 

ACCUIMPORTER

 

ENHANCEMENT - AccuImport Utility - New Version [PMID Ref No 15941]

 

The AccuImporter Utility has been updated to support three new spreadsheet target table options which include:

 

oAR Misc AR Invoices - Imported to User Batch

oPR TimeCard Worksheet Records - Imported to Company Table

oJC Job List Records - Imported to Company Table

 

In addition, a custom framework has been built into the utility to all for more flexibility with tailored solutions during the import process.  This new framework will be used by AccuBuild Consultants to make changes for specific company needs that can be handled via SQL Scripts much like the tailored solutions for MAR Reports.  

 

This new framework now includes a Process Results screen if any of the import spreadsheet data is invalid for the above three new import file types.  A new dialog screen will be displayed to show the errors when encountered.  A Summary option list of errors will be presented by default, and you can select the Detail option list to see individual row numbers where the errors were discovered:

 

AccuImporter_ProcessResults

 

Sample Import Files - A new folder called AccuImporter is included with the update which is kept under the Samples Folder of the AccuBuild Program Folder which contains sample import files to test with the AccuImporter Utility Program.

 

IMPORTANT NOTE: Please contact AccuBuild Support for more information if you have specific needs for importing spreadsheet data into your company in order to automate time consuming data entry processes.

 

 

PAYROLL

 

2020 Tax Table Updates - New Tax Tables and Software Changes for 2020 [PMID Ref No 15314]

 

The payroll withholding tables for the 2020 Calendar Year have been updated for the following states:

oArkansas - New Tables Released 01/22/2020

oMaryland - New changes to the Standard Deduction Amounts Updated 1/28/2020

oMinnesota - New Tables Released 01/06/2020

oMississippi - New Tables Released 01/10/2020

 

 

ENHANCEMENT - TimeCard Worksheet Backup Process for Rules Button [PMID Ref No 14020]

 

The backup process for the timecard worksheet company table (PMPERSONNEL) has been updated to use a new backup process which will now maintain the original values for the autoinc field (PERSONNELID) in the backup file.  This backup process takes place each time the Rules Button is clicked on the TimeCard Worksheet Screen.  NOTE: The backup file will set the autoinc field to an integer field type in order to preserve the original values from the company table.

 

 

PROJECT MANAGEMENT

 

Correction - Daily Report Screen - Production Units by Detail Item Tab [PMID Ref No 14999]

 

The task descriptions on the Production Units by Detail Item Tab of the Daily Report screen was showing the incorrect task description for tasks that were generated from the Change Order Request Screen.  These task descriptions are stored in the Bill_Desc field of the ESTDETL Table records and the Item_Desc Field was being displayed which caused the issue.  The stored procedure for this screen was corrected in this release to fix the issue:

 

oabm_Get_DPU_DailyReportTaskTotals_PMIDNo_ParentTaskItemNo

 

 

SYSTEM ADMINISTRATOR

 

ENHANCEMENT - User Maintenance Screen [PMID Ref No 16163]

 

The User Maintenance Screen has been updated to make sure the User Directory and the User Database Files are created automatically whenever a new user is added or an existing user’s information is updated.  Once the Save Button is clicked, a new process will be executed to make sure the user directory exists and that the user database tables BASEUSER.ADD, BASEUSER.AI, & BASEUSER.AM exist in the user directory.  In previous versions of AccuBuild, the user directory and database tables were only created the first time the user logged into the AccuBuild System.

 

This process will help to eliminate issues with AccuBuild Mobile users where a mobile user never logs into the AccuBuild System and attempts to connect to the AccuBuild Database when the user directory and / or user database tables do not exist.  

 

IMPORTANT NOTE:   If you have any issues with existing mobile users not being able to connect, you can simply click the Edit Button and then the Save Button to make sure the user directory and database tables are created without the need to login under the user name.

 

 

TAILORED STORED PROCEDURES

 

ENHANCEMENT - Consolidated Update Process for Tailored Procedures [PMID Ref No 16024]

 

The Update process for Tailored (Custom) Stored Procedures has been changed to handle the update process as a consolidated process so that ALL Companies are updated at the same time whenever the AccuBuild Stored Procedure Library has been updated in a software release.  This consolidated process is necessary for AccuBuild Installations where more than one company has been set up in the AccuBuild System.

 

In addition, the update process will create an audit trail of tailored stored procedures that exist for each company for both the Global Procedures (BASEGLOB Database) that serve ALL companies as well as the individual Company Procedures (BASECOMP Database) in each company folder.  If there are multiple companies with Global Procedures, a warning will now be displayed to alert the user.

 

Best Practices for Tailored Global Procedures:  It is always best to keep the global stored procedures on a single company and NOT on multiple companies in order to prevent any conflicts with the tailored solution library.  These tailored procedures are stored in the library as class number 112000.  When multiple companies have Global Procedures set up under class 112000, the stored procedures are created in the order of how the company scripts are processed which (see audit table results).  This can cause issues if two companies have the same stored procedure set up in class 112000 because the  last company to be processed will overwrite the previous company’s stored procedure.  This is why the recommended best practice is to place ALL Global stored procedures in a single company.  

 

Hint:  With the UserID parameter used in Global Procedures, you can create query commands to determine which company is making the procedure call in case you need to have different sets of business rules for different companies.

 

Refer to the Audit Trail Tracking features in the System - FAQs to review the various stored procedures that are set up for both global procedures (class 112000) and company procedures (class 113000).