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 Field Service Scheduler Release Notes
March 2013
These release notes include information about the latest QAD Field Service Scheduler (QAD FSS) fixes and changes. These changes may affect the way you implement and use QAD FSS.
Important: Review this document and the QAD FSS errata before proceeding with any phase of a QAD FSS implementation.
QAD highly recommends that you implement the latest QAD FSS release available. Check the QAD web site to make sure that you have the latest release notes, user guide, installation guide, and installation media:
Use the following list to find a specific release:
Release Notes for Current Release
QAD Field Service Scheduler Version: 3.1
Date: March 2013
QAD Enterprise Applications Version:
FSS 3.1.1 supports QAD 2008 SE (.NET UI 2.9.4.41), 2009 SE (.NET UI 2.9.4.41), 2010 SE (.NET UI 2.9.4.41), 2011 SE (.NET UI 2.9.4.41), 2012 SE (.NET UI 2.9.4.41), 2011 EE (.NET UI 2.9.3.65), 2011.1 EE (.NET UI 2.9.3.79), 2012EE (.NET UI 2.9.5.123), and 2012.1 EE (.NET UI 2.9.5.123).
FSS 3.1.2 supports QAD 2013 EE (.NET UI 3.0) only.
About This Release
This release of QAD FSS consists of two subversions: FSS 3.1.1 and FSS 3.1.2.
The changes made against the last version, FSS 3.0.6, are as follows:
Microsoft MapPoint 2013 is supported.
You can no longer edit the existing comments. A read-only field has been added to list all comments of a call record. Use any of the following ways to add new comments:
Use the Call Comments field on the Call Information tab of the Call Details tab.
Use the Call Comments option on the right-click menu against a call record.
Release Notes for Release 3.0.6
QAD Field Service Scheduler Version: 3.0.6
Date: September 2012
QAD Enterprise Applications Version: 2012 SE (.NET UI 2.9.4.47), 2012.1 EE (.NET UI 2.9.5.123)
Fixes
Added time stamp information for call comments entered through FSS client.
In the previous version, when you changed the status of a closed call visit to open and modified the fix time and travel duration repeatedly, the information of start date, visit date, and fix date did not show correctly, and the ERP application did not respond to your operation. This issue has been fixed.
In the previous version, if a call was canceled from FSS, the visits for this call were not closed or removed. This issue has been fixed.
Release Notes for Release 3.0.5
QAD Field Service Scheduler Version: 3.0.5
Date: March 2012
QAD Enterprise Applications Version: 2012 EE (.NET UI 2.9.5.87)
About This Release
This release of QAD FSS only supports QAD 2012 EE and has no new or changed features. If you are not using QAD 2012 EE, please implement an earlier version of QAD FSS.
You require a license code from QAD Support to unlock and use QAD FSS with QAD EE.
Release Notes for Release 3.0.4
QAD Field Service Scheduler Version: 3.0.4
Date: September 2011
QAD Enterprise Applications Versions: 2010.1 EE (.NET UI 2.9.3.65), 2011 EE (.NET UI 2.9.3.65), 2011 EE (.NET UI 2.9.3.79), 2011 SE (.NET UI 2.9.4), 2011.1 EE (.NET UI 2.9.3.79)
Fixes
In previous versions, the system only displays the visits scheduled for the engineer for the selected day correctly when visit start and end date are the same. When you right-click a day other than the visit date and time on the visit bar that spans several days on the Gantt chart and select the Engineer Visits for a Day command, the system displays a message: No engineer schedule found. This issue has been fixed.
Installation Changes
You require a license code from QAD Support to unlock and use QAD FSS with QAD EE.
Setup is required for the QAD .NET UI client. See “.NET Client Setup.”
Complete the setup instructions described in “QAD Enterprise Applications.”
.NET Client Setup
1
Remove any existing qad.plugin.fss folder under:
< .NET UI HomeServer >/packages/plugins/.
2
This release contains a QAD FSS client package:
Client\2.9.3\qad.plugin.fss-3.0.4-2.9.3-ee.zip for .NET UI 2.9.3.65
Client\2.9.3.79\qad.plugin.fss-3.0.4-2.9.3.79-ee.zip for .NET UI 2.9.3.79
Client\2.9.3.4\qad.plugin.fss-3.0.4-2.9.4-se.zip for .NET UI 2.9.4
Extract the required .zip file into < .NET UI HomeServer >/packages/.
3
Update < .NET UI HomeServer >/packages/plugins/manifest.qpkg and add the following line to the end of the package element:
<package ref="${Repos}/plugins/qad.plugin.fss/manifest.qpkg"/>
The next time that clients connect to the QAD .NET UI HomeServer, they are prompted to load the new FSS plug-in.
Note: To use the mapping capabilities of FSS, you must install Microsoft MapPoint 2006 or 2009 locally on each PC.
QAD Enterprise Applications
Note: If you are also installing MFS 3.0.4, use the steps in User Guide: QAD Mobile Field Service to update the ERP server and then perform the steps in “.NET Client Setup,” above.
1
Stop all servers, including Tomcat Webapps, WebSpeed brokers, and QAD Enterprise Applications database servers.
2
Copy all the files from the /Server/SSM/ QADERPVer directory on the QAD FSS installation media into the QADERPInstallDir \ssmpatch directory.
3
Run MFG/UTIL and choose Database|Load Database Schema to load the following schemas into the QAD Enterprise Applications databases.
Load QADERPInstallDir /ssmpatch/db/ssmpatch.df and QADERPInstallDir /ssmpatch/db/mfstriggers.df into the production database.
Load QADERPInstallDir /ssmpatch/db/ssmpatch.df and QADERPInstallDir /ssmpatch/db/mfstriggers.df into the empty database.
4
Run QADERPInstallDir /ssmpatch/xrc/utssmbrw.p from a Progress editor that is connected to both the main production database and admin database.
Note: Perform this step only if you are using QAD 2011 SE.
5
In MFG/UTIL, choose Database|Load System Data into Database to load data into the QAD Enterprise Applications databases.
a
Load data from QADERPInstallDir /ssmpatch/data into the production database. Accept default selected tables in the process.
b
Load data from QADERPInstallDir /ssmpatch/data into the administration database. Accept default selected tables in the process.
c
If you have implemented additional languages, load data from QADERPInstallDir /ssmpatch/data/LanguageCode into the production database. Accept default selected tables in the process.
6
Perform a full system compile. The Compile PROPATH should include the QADERPInstallDir /ssmpatch/xrc directory before the QADERPInstallDir /xrc directory.
7
Compile SSM bolt-on code.
a
Choose Programs|Generate Compile List File.
b
Use QADERPInstallDir /ssmpatch/xrc as the Source Directory.
c
Choose Programs|Compile Procedures.
d
Enter the compile list file from the previous step. Use the following PROPATH:
QXOAdapterInstallDir , QXOAdapterInstallDir /src,
QADERPInstallDir /ssmpatch/xrc, QADERPInstallDir /
xrc
Specify QADERPInstallDir /ssmpatch as the destination directory.
Note: If you do not use QAD Mobile Field Service, do not include QXOAdapterInstallDir , QXOAdapterInstallDir /src in the PROPATH.
e
If you have implemented additional languages, repeat the compile process using the appropriate language and language-specific compile database set.
8
Compile QAD Enterprise Applications Desktop code. In MFG/UTIL, choose UI|Build UI Configuration and add QADERPInstallDir /ssmpatch/xrc, QXOAdapterInstallDir in front of the PROPATH.
9
Edit the PROPATH in all client scripts to add QADERPInstallDir /ssmpatch, QXOAdapterInstallDir in front of the PROPATH.
10
Add a database connection for qxevents (alias_qxevents as logical name) in the server startup/shutdown scripts and .pf files.
11
Modify the ubroker.properties file.
If you use QAD .NET UI, add QADERPInstallDir /ssmpatch, QXOAdatperInstallDir in front of the PROPATH. Also, add srvrStartupProc=mfaistrt.p and srvrStartupProcParam=qra to the qadui AppServer.
If you do not use QAD .NET UI, manually create an AppServer entry. Use the following example as a guide:
[UBroker.AS.qadui]
srvrLogFile=QADERPInstallDir/qadui/qadui.server.log
brokerLogFile=QADERPInstallDir/qadui/qadui.broker.log
portNumber=39795
initialSrvrInstance=2
maxSrvrInstance=5
operatingMode=Stateless
autoTrimTimeout=600
appserviceNameList=qadui
controllingNameServer=NS1
environment=qadui
uuid=2993d17cfa993b70:-2eefabaf:11c88180435:-8000
description=AppServer Transaction server for qadui
srvrStartupParam=-pf QADERPInstallDir/qadui.pf (include the qxevents db with logical name alias_qxevents and the qxo db with logical name qxodb)
PROPATH=QXOAdapterInstallDir:QADERPInstallDir/ssmpatch:QADERPInstallDir:QADERPInstallDir/ssmpatch/qra.pl:.
srvrStartupProc=mfaistrt.p
srvrStartupProcParam=qra
12
Restart all QAD Enterprise Applications database servers, WebSpeed brokers, AppServers, and Tomcat Webapps.
13
Load procedure and field help.
a
Log in to QAD Enterprise Applications.
b
Go to Field Help Load (36.4.19).
c
Specify US as the language and QADERPInstallDir /ssmpatch/data/fieldhlp.fhd as the field help load file.
d
Press Go.
Release Notes for Release 3.0.2
QAD Field Service Scheduler Version: 3.0.2
Date: September 2010
QAD Enterprise Applications Versions: 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
Installation Changes
You require a license code from QAD Support to unlock and use QAD FSS with QAD EE.
Setup is required for the QAD .NET UI client. See “.NET Client Setup.”
Complete the setup instructions described in “QAD Enterprise Applications.”
.NET Client Setup
1
Remove any existing qad.plugin.fss folder under:
< .NET UI HomeServer >/packages/plugins/.
2
This release contains a QAD FSS client package:
2.5.3\qad.plugin.fss-3.0.2-2.5.3.zip for QAD eB2.1 SP4, QAD 2007 SE, QAD 2007.1 SE
2.7.3\qad.plugin.fss-3.0.2-2.7.3.zip for QAD 2008 SE and 2008.1 SE
2.8\qad.plugin.fss-3.0.2-2.8.zip for QAD 2009 EE
2.8.1\qad.plugin.fss-3.0.2-2.8.1.zip for QAD 2009 SE
2.8.2\qad.plugin.fss-3.0.2-2.8.2.zip for QAD 2009.1 EE
2.9\qad.plugin.fss-3.0.2-2.9.zip for QAD 2010 EE
2.9.1\qad.plugin.fss-3.0.2-2.9.1.zip for QAD 2010 SE
2.9.2\qad.plugin.fss-3.0.2-2.9.2.zip for QAD 2010.1 EE
Extract the required .zip file into < .NET UI HomeServer >/packages/.
3
Update < .NET UI HomeServer >/packages/plugins/manifest.qpkg and add the following line to the end of the package element:
<package ref="${Repos}/plugins/qad.plugin.fss/manifest.qpkg"/>
The next time that clients connect to the QAD .NET UI HomeServer, they are prompted to load the new FSS plug-in.
Note: For QAD eB2.1 SP4, QAD 2007 SE, and QAD 2007.1 SE, FSS must be installed locally onto each client that will need to run the application from the QAD .NET user interface. To do this, extract 2.5.3\qad.plugin.fss-3.0.1-2.5.3.zip into the plugins folder of your QAD .NET UI client installation. Your QAD .NET UI client installation is typically found in C:\Program Files\QAD.
Note: To use the mapping capabilities of FSS, you must install Microsoft MapPoint 2006 or 2009 locally on each PC.
QAD Enterprise Applications
Note: If you are also installing MFS 3.0.2, use the steps in Technical Reference: QAD Mobile Field Service to update the ERP server and then perform the steps in “.NET Client Setup,” above.
1
Stop all servers, including Tomcat Webapps, WebSpeed brokers, and QAD Enterprise Applications database servers.
2
Copy all the files from the /Server/SSM/ QADERPVer directory on the QAD FSS installation media into the QADERPInstallDir \ssmpatch directory.
3
If you are using eB2.1 SP4, QAD 2007 SE, or QAD 2007.1 SE, copy the files from the /Server/QADUI directory on the QAD FSS installation media into the directory:
QADUIInstallDir /com/qad/shell/interface
4
Run MFG/UTIL and choose Database|Load Database Schema to load the following schemas into the QAD Enterprise Applications databases.
Load QADERPInstallDir /ssmpatch/db/ssmpatch.df and QADERPInstallDir /ssmpatch/db/mfstriggers.df into the production database.
Load QADERPInstallDir /ssmpatch/db/ssmpatch.df and QADERPInstallDir /ssmpatch/db/mfstriggers.df into the empty database.
5
Run QADERPInstallDir /ssmpatch/xrc/utssmbrw.p from a Progress editor that is connected to both the main production database and admin database.
Note: Perform this step only if you are using QAD 2009 SE, QAD 2010 SE, or QAD 2009 EE.
6
In MFG/UTIL, choose Database|Load System Data into Database to load data into the QAD Enterprise Applications databases.
a
Load data from QADERPInstallDir /ssmpatch/data into the production database. Accept default selected tables in the process.
b
Load data from QADERPInstallDir /ssmpatch/data into the administration database. Accept default selected tables in the process.
c
If you have implemented additional languages, load data from QADERPInstallDir /ssmpatch/data/LanguageCode into the production database. Accept default selected tables in the process.
7
Perform a full system compile. The Compile PROPATH should include the QADERPInstallDir /ssmpatch/xrc directory before the QADERPInstallDir /xrc directory.
8
Compile SSM bolt-on code.
a
Choose Programs|Generate Compile List File.
b
Use QADERPInstallDir /ssmpatch/xrc as the Source Directory.
c
Choose Programs|Compile Procedures.
d
Enter the compile list file from the previous step. Use the following PROPATH:
QXOAdapterInstallDir , QXOAdapterInstallDir /src,
QADERPInstallDir /ssmpatch/xrc, QADERPInstallDir /
xrc
Specify QADERPInstallDir /ssmpatch as the destination directory.
Note: If you do not use QAD Mobile Field Service, do not include QXOAdapterInstallDir , QXOAdapterInstallDir /src in the PROPATH.
e
If you have implemented additional languages, repeat the compile process using the appropriate language and language-specific compile database set.
9
Compile QAD Enterprise Applications Desktop code. In MFG/UTIL, choose UI|Build UI Configuration and add QADERPInstallDir /ssmpatch/xrc, QXOAdapterInstallDir in front of the PROPATH.
10
Edit the PROPATH in all client scripts to add QADERPInstallDir /ssmpatch, QXOAdapterInstallDir in front of the PROPATH.
11
Add a database connection for qxevents (alias_qxevents as logical name) in the server startup/shutdown scripts and .pf files.
12
Modify the ubroker.properties file.
If you use QAD .NET UI, add QADERPInstallDir /ssmpatch, QXOAdatperInstallDir in front of the PROPATH. Also, add srvrStartupProc=mfaistrt.p and srvrStartupProcParam=qra to the qadui AppServer.
If you do not use QAD .NET UI, manually create an AppServer entry. Use the following example as a guide:
[UBroker.AS.qadui]
srvrLogFile=QADERPInstallDir/qadui/qadui.server.log
brokerLogFile=QADERPInstallDir/qadui/qadui.broker.log
portNumber=39795
initialSrvrInstance=2
maxSrvrInstance=5
operatingMode=Stateless
autoTrimTimeout=600
appserviceNameList=qadui
controllingNameServer=NS1
environment=qadui
uuid=2993d17cfa993b70:-2eefabaf:11c88180435:-8000
description=AppServer Transaction server for qadui
srvrStartupParam=-pf QADERPInstallDir/qadui.pf (include the qxevents db with logical name alias_qxevents and the qxo db with logical name qxodb)
PROPATH=QXOAdapterInstallDir:QADERPInstallDir/ssmpatch:QADERPInstallDir:QADERPInstallDir/ssmpatch/qra.pl:.
srvrStartupProc=mfaistrt.p
srvrStartupProcParam=qra
13
Restart all QAD Enterprise Applications database servers, WebSpeed brokers, AppServers, and Tomcat Webapps.
14
Run QADERPInstallDir /ssmpatch/xrc/utssmse.p from a Progress editor that is connected to the main production database and admin database to perform data conversion.
Note: Do not perform this step if you are using QAD 2009 SE, QAD 2009 EE, or later.
15
Load procedure and field help.
a
Log in to QAD Enterprise Applications.
b
Go to Field Help Load (36.4.19).
c
Specify US as the language and QADERPInstallDir /ssmpatch/data/fieldhlp.fhd as the field help load file.
d
Press Go.



Previous Page
  |