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  |   Cloud ERP  |   Home  |   qad.com



  |  
Next Page

Release Notes for Version 2.0.1
QAD Field Service Scheduler Version: 2.0.1
Date: June 2008
QAD Enterprise Applications Versions: QAD Enterprise Applications 2008 - Standard Edition, QAD Enterprise Applications 2008 - Enterprise Edition
Installation Changes
Installation setup is required for the .NET UI client and your QAD ERP application (QAD 2008 EE or QAD 2008 SE). These instructions replace the installation instructions contained in the User Guide: QAD Field Service Scheduler.
Note: QAD FSS version 2.0.1 is a maintenance release that replaces QAD FSS 2.0.
Perform the steps below to set up your .NET client and QAD ERP application.
.NET Client Setup
1
Remove any existing qad.plugin.fss folder under:
< .NET UI HomeServer >/packages/plugins/.
2
Extract Client/qad.plugin.fss-2.0.1.0.zip 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 .NET UI HomeServer, they will be prompted to load the new FSS plug-in.
Note: If you want to use the mapping capabilities of FSS, you must install Microsoft MapPoint 2006 locally on each PC.
QAD Enterprise Applications 2008 Enterprise Edition Setup
Customers that are currently using QAD Enterprise Applications 2008 – Enterprise Edition must replace their client plug-in and replace certain modified files/data on the server side using the instructions below.
1
Copy the contents of the Server/2008ee folder into a folder called ssmpatch under the
< QAD ERP InstallDir > folder.
2
Copy the programs from the < QAD ERP InstallDir >/ssmpatch/xrc folder into the
< QAD ERP InstallDir >/xrc folder where your source code resides. You might want to save the previous versions of these programs to uninstall the FSS bolt-on later.
3
Run QDT and choose Database|Load System Data into Database.
4
Connect to your main production database and enter < QAD ERP InstallDir >/ssmpatch/data as the input directory.
5
Accept the selected tables and click OK to load the data.
6
Repeat the data load for the administration production database.
7
Choose Programs|Compile Procedures.
8
In the Compile List File field, enter < QAD ERP InstallDir >/ssmpatch/ssmcompile.lst.
9
Click Compile to deploy the new programs. Answer Yes to any prompts and click Continue on the Summary screen.
QAD Enterprise Applications 2008 Standard Edition Setup
QAD FSS version 2.0.1 is a bolt-on install to the server side and to the .NET UI plug-in.
Note: QAD FSS version 2.0.1 is the first available release of QAD FSS on QAD Enterprise Applications 2008 – Standard Edition.
1
Stop all AppServers, WebSpeed Brokers and database servers; for example:
asbman –i qadui_AS –stop
wtbman –i qadui_WS –stop
stopProduction.bat or stop.Production
2
Copy the contents of the Server/2008se folder into a folder called ssmpatch under the
< QAD ERP InstallDir > folder.
3
Run MFG/UTIL and choose Database|Load Data Definitions.
4
Connect to your main production database and enter
< QAD ERP InstallDir >/ssmpatch/db/ssm2008se.df as the data definition file.
5
Click OK to load the new schema.
6
Repeat the schema load for the main empty database.
7
Choose Database|Load System Data into Database.
8
Connect to your main production database and enter < QAD ERP InstallDir >/ssmpatch/data as the input directory.
9
Accept the selected tables and click OK to load the data.
10
Repeat the data load for the administration production database.
11
If you have additional languages, repeat the data load into your main production database using
< QAD ERP InstallDir >/ssmpatch/data/<lang> as the input directory.
12
Perform a full system recompile to make use of the new schema changes.
13
Choose Programs|Compile Procedures.
14
In the Compile List File field, enter < QAD ERP InstallDir >/ssmpatch/ssmcompile.lst.
15
Include < QAD ERP InstallDir >/ssmpatch/xrc at the beginning of the compile PROPATH and enter < QAD ERP InstallDir >/ssmpatch as the destination directory.
16
Click Compile to deploy the new programs. Answer Yes to any prompts, and then click Continue on the Summary screen.
17
If you have additional languages, repeat the compile process using the appropriate QAD ERP language and language-specific compile database set.
18
Copy the compiled triggers from < QAD ERP InstallDir >/ssmpatch/triggers to
< QAD ERP InstallDir >/triggers.
19
Edit the PROPATH in all client scripts so that < QAD ERP InstallDir >/ssmpatch is listed before < QAD ERP InstallDir >; for example:
CharacterclientProduction.bat
Production.ini (two instances)
connmgrProduction.bat
telnetProduction.bat
qadui.chr
20
Edit ubroker.properties for the qadui AppServer as follows:
The PROPATH should have <QAD ERP InstallDir>/ssmpatch listed before <QAD ERP InstallDir> and <QAD ERP InstallDir>/ssmpatch/qra.pl added to the end
Add srvrStartupProc=mfaistrt.p
Add srvrStartupProcParam=qra
21
Restart the database servers, AppServers, and WebSpeed brokers.
startProduction.bat or start.Production
asbman -i qadui_AS -start
wtbman -i qadui_WS -start
22
Run the program < QAD ERP InstallDir >/ssmpatch/xrc/utssmse.p from a Progress editor that is connected to the main production database.
23
Launch QAD Enterprise Applications 2008 and select menu 36.4.19 – Field Help Load. Enter US as the language and < QAD ERP InstallDir >/ssmpatch/data/fieldhld.fhd as the Field Help Load File. Accept all other defaults and click Go to load the new help data.
24
Run Menu System Maintenance from the .NET UI and click the Refresh button to install the new menu options for SSM.
Application Changes
1
Searches in certain browses have been modified. In the All Calls browse during startup—and when a user switches between Call View and Engineer View—the system searches the BrowseSearches folder under the plug-in install directory for a file that matches the pattern *.fs060.xml. If multiple files match the pattern, the system runs the browse using the search condition saved in the first file. If no file is found, the system runs the browse without any search conditions.
The following FSS browses perform in the same way when the browse is initially loaded:
Gantt Chart – Scheduling browse. The search pattern is *.fs065.xml.
Engineer browse in List of Engineers tab. The search pattern is *.fs064.xml.
Inventory browse in Spare Parts tab. The search pattern is *.fs067.xml.
2
The selection functionality in the All Calls browse has been modified. Now only one row can be selected at a time.
3
The visit data and engineer downtime schedules are now available only from the Gantt start date – 7 to Gantt start date + 13 (a total of 21 days).
Fixes
1
Various fixes have been applied to correct the display of information and the user interface:
Text formatting in the Call Details tab has been corrected.
The labels on the End User Details tab and the Contract Details tab on the Call Details screen have been corrected. In addition, the search criteria drop-down has been corrected.
A scroll bar has been added to the Call Details – Installed Base tab.
Searches that involve matching parts now return the correct search results.
The travel time for reassigned service calls now displays correctly.
The orange SLA bar now remains visible when a call row is clicked in the Gantt Chart – Scheduling tab.
2
Various fixes have been made to correct scheduling irregularities:
The correct travel time is now calculated when an engineer—if already scheduled for a service visit that day—is assigned an earlier appointment.
Travel duration is now calculated correctly when—following a service engineer break—a later service call is scheduled for the same address as a previous service call.
A service call can now be reassigned to a different engineer using the same call schedule details.
3
The system now attempts to schedule a later appointment after a previous appointment for an engineer only if the later appointment begins and ends on the same day.
4
When the QAD FSS configuration file is loaded, the system now checks to determine if Microsoft MapPoint 2006 is installed. If Microsoft MapPoint 2006 is not installed, the QAD FSS mapping functions are disabled, and a message to this effect displays.
5
The system now uses the absence address to calculate the travel distance to a service call when a non-working schedule has been assigned to the scheduled engineer for that day. Previously the home address of the engineer was used.



  |  
Next Page