Loading ...

QQube 7.7 (Build 521) Release Details | CLEARIFY

QQube 7.7 (Build 521) Release Details

QQube 7.7 (Build 521) Release Details

 /5
0 (0votes)

QQube™ Version 7.7 (Build 521) Release Details

(Release Date: January 27, 2021)

Release Overview

This build enhances several pieces for the BOM analytic, fixes several bugs with regard to BOM and Open SO, as well as several smaller bugs.  It also simplifies the installation options and overrides using feedback from our installation overhaul in the previous version. 

We anticipate that this will be the final 7.x build.  All other enhancements will be rolled into Version 8.x due this spring

Bug Fixes and Enhancements

Customer, Job, Vendor, Employee

  • Fixed issue where the URL field(s) in the customer:job list contained UNC url's  e.g. starting with two slashes - and QQube only returned one slash.

Budget Information in General Ledger Detail

  • Fixed issue where May, 2021 data was missing, and incorrectly labeled as 5-18-2021 instead of the expected 5-1-2021. 

BOM Explosion

  • Fixed issue for BOM in multi-company implementations.  Each company is now accurate. 
  • Provided enhancement to cases where assemblies have no items.  The assembly will now show in the list of sub-assemblies.  Previously it would only show as an item to accommodate Bug 097.
  • Sub-Assemblies now show quantity.

In this example:

  • The items in pink are sub-assembly quantities
  • The items in yellow are top level assemblies with no items
  • The item in turquoise is a sub-assembly with no item

Open SO

  • Fixed issue where Discount Items were not showing in Open Sales Orders.  We also changed the original quantity to 0 and open quantity to 1 to reflect how QB shows discounts on its open SO reports.
  • Fixed issue where assemblies with no items in Open SO with "is BOM explosion" option turned on would show incorrect status. 
  • Fixed issue where Open SO would return incorrect amounts when "is BOM explosion" option was turned on. 

QQube Database Components

  • SQL Anywhere components have been updated to version 17.0.10.6230

Installer

In Build 508 we included many enhancements and fixes to the installer routine, and based upon customer feedback we have refined and simplified the options as follows:

WORKSTATION

  • If QuickBooks is installed on the workstation, it defaults to all options (No Switches).

  • If QuickBooks is NOT installed on workstation, it defaults to client only, with no ability to get beyond the blank database list if it can't be found.

  • If QuickBooks is either installed or not installed, and you want to install client AND get by no database found window, use OVERRIDENODBSERVER=1 to default to client only, with ability to get beyond database, and set the actual ip address once installed.

SERVER

  • If QuickBooks is installed on the server, it defaults to multi-user server with no other options.

  • If QuickBooks is not installed on the server, it defaults to client only, with no ability to get beyond the blank database list if it can't be found.

  • If QuickBooks is either installed or not installed, and you want to install client AND get by no database found window, use OVERRIDENODBSERVER=1 to default to client only, with ability to get beyond database, and set the actual ip address once installed.

For all installations:

  1. If Framework .NET 4.8 is not installed, it gives a warning message.

TABLE OF AVAILABLE OVERRIDE SWITCHES

SWITCH

 

Override Intention

Workstation

Server

Notes

 

 

 

 

 

 

EXCELADDINOFF=1

 

Not Install Excel Add-In

YES

YES

 

OVERRIDENOQB=1

 

QuickBooks Not Present

YES

YES

Some reason we can't see QB installed

OVERRIDENODBSERVER=1

 

Default to client only, with ability to get beyond database

YES

YES

QuickBooks is or is not installed

REMOVED

We no longer check for processor speed and power.  In the first days of QQube, customers would have a tendency to put QQube on the older slower machines, when in fact they needed the fastest they could possibly get - because of the strain that the Intuit SDK puts on the processor.

We kept it in the Version 6.x and 7.x releases because there were people with Windows 7 machines, that just did not have the horsepower.

We don't feel it is necessary to continue this option given the speed of the processors most likely in use at this time.

Overrides removed from previous version:

  • OVERRIDESERVERCLIENT=1 (not necessary)

Comments (no comments yet)

Top Announcements