Product Update – Feb 2021

Since early January 2021, Pilot has experienced several product issues, which we have tried to rectify via various quick ‘fixes’.

This was done in the interests of getting sites running a 100% uptime PoS platform.

It seems we shot ourselves in the foot with this quick fix attempt, and many sites are still experiencing daily software glitches and increased frustration.

We unreservedly apologize for the problems you may be experiencing with your Pilot product, we must do better.

We’ve laid out the essential list of issues, potential fixes, and latest version release notes.

This version 4.4.16 is not commercially available yet. Once it’s been through the QA/QC/Alpha/Beta process we expect to make it available to all sites by no later than Monday 1 st March 2021.

ISSUE 1: PILOT API DOWN MESSAGE – RESOLVED IN BUILD TO BE RELEASED

  • Most sites will not be able to resolve this issue themselves as there is typically no access to the BlackBox Server.
  • Our helpdesk has remote access (on approval) and can reset the API
  • Only sites with no BlackBox, that run just an FS1 or a waiter station, can resolve the issue themselves

Possible causes:

  • The PilotAPI Service is not running
  • The database connection between the workstations and server
    disconnected and couldn’t be re-established correctly
  • The PilotAPI Service is installed and running on one or more other computers than the server

Remedy:

  • Restart the PilotAPI service on the server and confirm that the PilotAPI Station is the correct machine (the nominated server)
  • Uninstall all PilotAPI and re-run the Pilot Install on the server machine

Latest Pilot updates

ISSUE 2: BATCH UPDATE ISSUE ON PILOT 4.4.15 – RESOLVED IN BUILD TO BE RELEASED

  • When batch updates are run, either at Day End or manually via System Update, the PLU, Master File and Count Sheet Items become hidden – as if they were sent as hidden
  • These items would need to be set to be visible again to display correctly on the count sheets and Master File
  • A patch version of 4.4.15 was released end of January to correct this problem
  • In dev’s haste, they named the patch version the same number as the faulty version – so there is theoretically no way to know if you are running the buggy or patched version!
  • You can check on your System Update version to determine if you have the correct build, go to Admin/Setup/Import Data:

The System Update version number with the fault:

The System Update version number of the patch release:

 

  • The patch System Update version does not automatically get installed on the workstations, so AutoUpgrade.exe needs to be run on the waiter stations
  • Once AutoUpgrade.exe is run on a workstation, it will then have the correct version of System Update to prevent the incorrect hiding of Master File and PLU items
  • In the case that the workstation that Day End was done on does not have the new System Update and items are hidden, our Support and Deployment staff will be able to assist by running a script which targets the System Update backup files, to retrieve the show/show off flags from the backup files that System Update creates when a batch update
    is ran.

PILOT VERSION 4.4.16 PATCH RELEASE NOTES

RELEASE DATE: First week March 2021

New Features:

ADMIN

  • Day end – Request Manager authorization if Z-date is moved into the future/past calendar date

BUG Fixes:

ONLINE ORDERS

  • Online Order Times – Order times not showing on the Online Order screen – Resolved
  • Online Orders remain in Pending state – Resolved

POS

  • PilotAPI Down message showing frequently – Resolved
  • Waiter Cash up re-tender– When using the re-Tender functionality on the Waiter Cash up, the cash due amount does not change – unless you enter a figure in the pay/commission column and then clear it – Resolved

ADMIN

  • Day end failure – update turnover exception – Resolved

TOUCH DESIGN

  • Limit to Pop-ups allowed on a button – Resolved

PILOTAPI

  • Pilot WebAPI not sending Pilot and PilotAPI version numbers to Pilot Central – Resolved

3 rd PARTY EXPORTS

  • Navision Export – Stops on Seqfld “ZZ” causing the export task to fail –Resolved

 

Author : Rudi Badenhorst

SHARE