In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com



Previous Page
  |  

QAD Mobile Field Service Release Notes
March 2013
These release notes include information about the latest QAD Mobile Field Service fixes and changes. These changes may affect the way you implement and use QAD Mobile Field Service.
Review this document before proceeding with any phase of QAD Mobile Field Service implementation.
These release notes are cumulative, with the most recent changes displayed first. Review the notes for all releases after your currently installed release. Installation and configuration changes may have occurred in those intermediate releases, and unless otherwise noted, apply to the release where they were announced, as well as subsequent releases.
QAD highly recommends that you implement the latest QAD Mobile Field Service release available. Check the QAD Web site to make sure that you have the latest QAD Mobile Field Service release notes, installation guide, and installation media.
Use the following list to find a specific release:
Release Notes for Current Release
QAD Mobile Field Service Version: 3.3
Release Date: March 2013
QAD ERP Compatibility: QAD 2008 SE, 2009 SE, 2010 SE, 2011 SE, 2012 SE, 2009.1 EE, 2011 EE, 2011.1 EE, 2012 EE, 2012.1 EE, 2013 EE
QXtend Compatibility: 1.7 or later
Languages: English, French, Castilian Spanish, Latin American Spanish, German, Dutch, Italian, Polish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese
This release includes the following changes:
This release no longer supports MFG/PRO eB2.1 Service Pack 4.
This release requires Microsoft .NET Framework 4 instead of version 3 for Mobile Field Service 3.2.
Release Notes for Release 3.2
QAD Mobile Field Service Version: 3.2
Release Date: September 2012
QAD ERP Compatibility: MFG/PRO eB2.1 Service Pack 4, QAD 2008 SE, 2009 SE, 2010 SE, 2011 SE, 2012 SE, 2009.1 EE, 2011 EE, 2011.1 EE, 2012 EE, 2012.1 EE
QXtend Compatibility: 1.7 or later
Languages: English, French, Castilian Spanish, Latin American Spanish, German, Dutch, Italian, Polish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese
This release includes the following changes:
More information is displayed on the MFS client UI:
Project information defaulted from the corresponding contract data is displayed on the Detail tab of the call line. The use can change the project information when there is no call activity report for this call line. It is supported to synchronize project data with the server.
Contract and warranty information is displayed in the Installed Base List.
Address information is displayed in the End User List.
Call line serial number and other visits flag (x) are displayed in the Call List.
The search function is enhanced with search filters for all lists.
You no longer need to choose the directory for saving FSRs. The system defines the default directory.
During installation of MFS, the following directory is created for local cache files to avoid privilege restrictions:
%APPDATA% \QAD\MFS (%APPDATA% is user-specific.)
Release Notes for Release 3.1
QAD Mobile Field Service Version: 3.1
Release Date: March 2012
QAD ERP Compatibility: MFG/PRO eB2.1 Service Pack 4, QAD 2007, QAD 2007.1, QAD 2008 SE, QAD 2008.1 SE, 2009 SE, 2009 EE, and later
QXtend Compatibility: 1.7 or later
Languages: English, French, Castilian Spanish, Latin American Spanish, German, Dutch, Italian, Polish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese
This release includes the following changes:
MFS client no longer supports personal digital assistant (PDA) devices. Only laptops are supported.
Apache Tomcat replaces OneBridge Mobile Data Suite as the synchronization sever that synchronizes data between MFS client and QAD SSM. OneBridge Mobile Objects are also removed from the MFS client.
MFS now supports multiple domains. You can now switch among multiple domains they have access to on the client, based on the access control settings configured in MFS Workspace Configuration.
The MFS administrator can now use a new MFS Workspace Configuration utility to configure environment settings and set up user access rights to different QAD Enterprise Applications domains from the MFS client.
Changes have been made to QAD Mobile User Maintenance in QAD Enterprise Applications:
All OneBridge settings are removed.
You now use this program only to create records for individual users who access QAD Enterprise Applications from the MFS client.
Settings that manage how information is updated on the QAD Mobile FS client are moved to a new program, QAD MFS Control, in QAD Enterprise Applications.
You can now use workspace-specific Field Service Report (FSR) templates to tailor FSR reports for different domains. Where you do not specify workspace-specific FSR templates, a global template is used.
QAD Mobile Field Service Technical Reference Guide is now broken down into two books: QAD Mobile Field Service Installation Guide (70-3246-3.1) on installing and configuring MFS, and QAD Mobile Field Service User Guide (70-3247-3.1) on using MFS.
Release Notes for Release 3.0.4
QAD Mobile Field Service Version: 3.0.4
Release Date: September 2011
QAD ERP Compatibility: MFG/PRO eB2.1 Service Pack 4, QAD 2007, QAD 2007.1, QAD 2008 SE, 2008.1 SE, 2009 SE, 2010 SE, 2009 EE, 2009.1 EE, 2010 EE, 2010.1 EE, 2011 EE, 2011 SE, 2011.1 EE
QXtend Compatibility: 1.6.1 or later
Languages: English, French, Castilian Spanish, Latin American Spanish, German, Dutch, Italian, Polish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese
This release includes the following change:
This release supports QAD 2011 SE and QAD 2011.1 EE in addition to previously supported versions of QAD Enterprise Applications.
Release Notes for Release 3.0.3
QAD Mobile Field Service Version: 3.0.3
Release Date: March 2011
QAD ERP Compatibility: MFG/PRO eB2.1 Service Pack 4, QAD 2007, QAD 2007.1, QAD 2008 Standard, 2008.1 Standard, 2009 Standard, 2010 Standard, 2009 Enterprise, 2009.1 Enterprise, 2010 Enterprise, 2010.1 Enterprise, 2011 Enterprise
QXtend Compatibility: 1.6.1 or later
Languages: English, French, Castilian Spanish, Latin American Spanish, German, Dutch, Italian, Polish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese
This release includes the following changes:
This release supports QAD 2011 Enterprise Edition in addition to previously supported versions of QAD Enterprise Applications.
The new software requirements for PDA devices for this release of the QAD Mobile Field Service client are:
Windows Mobile version 6 or later
Microsoft SQL Server 2005 Compact Edition
Microsoft .NET Compact Framework 3.5
Microsoft ActiveSync (if installing from a connected PC)
The new software requirements for laptops for this release of the QAD Mobile Field Service client are:
Windows 2000 SP4 or later, Windows XP SP1 or later, Windows 7 (32 bit or 64 bit)
Microsoft Access (run-time version included with OS install)
Microsoft .NET Framework 3.5
Microsoft Visual J# 2.0 Second Edition
The profiles that ship with QAD Mobile Field Service have been modified so that only a predefined set of data objects and fields is monitored and published to QAD Enterprise Applications during synchronization through QXtend Outbound. It enhances system performance. Previously, all data objects and fields contained in the profiles were monitored and published during synchronization by default.
This release includes the following fixes:
Call reports that experience record locking at the time of synchronization are no longer marked as synchronized on the client. Previously, when you tried to synchronize multiple call reports linked to different calls and one of the calls was locked on the server, a record locked message was generated on the server. But all the reports were marked as synchronized on the client.
Fixed: Static data deletions or changes that made them ineligible for synchronization were not deleted consistently from the client.



Previous Page
  |