To download the latest Software Update, which includes the New Features, Enhancements and Fixes listed below, log in to PMXpert Support. Click on the Downloads tab and click on the PMXpert V10.6 (10.6.1.356) link.

You can also choose to abstain from adding the latest new and enhanced features at this time and still receive an upgrade to the software which provides the most recent bug fixes only. To do this, click on the link appearing under Previous Version(s).

Remember that Software Updates are only available to customers with a current Upgrade Protection Plan. If your Upgrade Protection Plan has lapsed, contact our Sales Department at Sales.uk@PMXpert.com or 0871 218 0912. They can provide you with information on how to reactivate your Upgrade Protection Plan so that you can continue to get the maximum advantage out of your PMXpert Software investment. 

Version 10.6.1.356

• Added the ability to hide the initial screen on the Work Order Service close wizard
• Added a Consumption Limit tab to the Asset screen to allow you to specify consumption limits on inventory items for an asset
• Added a 'Consumption Limit' report to show all assets that have gone over their limits
• Added a notification for PMXAlerts for assets that have gone over their limits
• Added the ability to specify a performed date on detail items when importing them to a Work Order

Version 10.6.1.356

• Users could not select a department in the Asset multi edit
• Error occurring when trying to edit the ‘Asset Snapshot’ report
• Error occurring when setting the Asset filter in the Copy Services Wizard
• The notes tab will be highlighted red if the Company/Contact/Work Order/Asset has notes attached to it
• Increased the size of the 'Description' field in the Asset’s Part/Fluid list to 100 from 50
• Asset Services that were more than 30 characters long were not being grouped on the ‘Service Forecast’ report (When the group by service option was selected)
• The ‘Service Forecast’ report was not showing the part breakdown correctly
• Related assets were not having their location updated when adding a location history record to the base asset