Month: June 2009

FTMaintenance v9.7.0 Release Notes

Features

  • FTMaintenance Enterprise customers may now select from which printer a work order will Auto Print.
  • Database installation has become more simplified.
  • The FTMaintenance Mobile and Barcode Optional Modules have been redesigned for compatibility with Windows Mobile® equipped devices.
  • Microsoft SQL Management Studio Express is now included with the Optional Modules installation.
  • PM and DM security now have the option to restrict work orders to only allow edits by the originator of the work order and the originator’s supervisor.
  • FTMaintenance Expert functionality has been enhanced to include the following features:
  • Additional concurrent users
  • Email capabilities
  • Work order auto-activation
  • Data import capabilities
  • ProLink Web Browser Service Request
  • Additional security groups
  • Attachments
  • Place equipment out of service
  • Archive and purge records
  • Skip PM work order

Solutions

  • Demo time restriction is now properly removed upon full version installation.
  • M-Site no longer produces an ODBC error upon installation.
  • PM work orders that are scheduled to be active on a non-working day now properly reschedule to the next available working day without error.
  • Attempting to enter information in the State field in the Company Address option in Expert installations no longer produces an error.
  • Attempting to create a requisition in the Reorder List no longer produces a VENDORID error.
  • Setting the Drive for Attachments to C from a drive other than C now executes properly.
  • Installation for all versions of FTMaintenance no longer requires a reboot.
  • When adding an attachment, the File Open dialog now defaults to the proper drive.
  • Servers that may be missing certain shared components in the .NET assembly may now install ProLink III without error.
  • ProLink III error messages now contain the proper text.
  • Attempting to delete a pulled part from a work order or delete a work order that contains a pulled part now requires the user to restock the part before allowing the record to be deleted.