...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
TraCS FAQ—Additional Instructions for Fall 2021
...
| Info |
|---|
NOTE: These instructions revised 3/9/2022. Please replace any previous version with this one. |
...
The “As-Built” documentation template that you can use to document key configuration settings in TraCS. It is available here: https://trust.dot.state.wi.us/tracs/documentation/tracsdocumentationtemplates.zip
Training Software— the training software has been updated. It is permissible to install the training software on a computer that is also running the production version of TraCS; the two may now run side-by-side. We do not recommend installing the training software on your master computer. See Task 4.4 in the Maintenance Guide for information on downloading and installing the new version of the training software.
Task: Upgrading TraCS Software to Fall 2021 Release
Get an updated copy of TraCS10.zip
Download latest version of tracs10.zip: https://trust.dot.state.wi.us/tracs/software/tracs10.zip
Extract the contents of the file to a folder of your choosing on your network or to a USB Flash Drive.
Copy the TraCS - Baseline Install XX.XX.exe, and InstallTraCS.bat to your distribution folder.
Remove any older baseline installation files in your distribution folder.
Ensure that all TraCS Office users are logged out. (Field units, or squad cars, running the mobile version may continue to operate during the upgrade.)
Web Services Only: If your agency uses TraCS in Web Services mode you must email TraCS badgertracs@dot.wi.gov to enable update and, follow step 1 of Task 5.2(c) of the Maintenance Guide and then continue as below. Important: If you use Web Services, the new version of TraCS—Server Edition must be installed on your TraCS server prior to downloading any updates. Failing to do this may cause your TraCS server to become inoperable.
SQL Server Only: Create new Database called CustomàNOTE: This is new for this year and needs to be completed prior to starting the update (Agencies using Access Databases can skip down to step #5)
This follows task 1.4(c) in the installation guide.
Start SQL Server Management Studio (SSMS).
Copy the following script in and run it. (Also attached)
...
7. Edit the database connection for the Custom database. In the Database Location field, prefix the network folder, using the UNC naming convention, to the file path. Example: \\myserver\sharename\TraCS\DBData\Custom.mdb
a. Access example NOTE: the access database will not be created yet so the test function will not work properly until after the update.
...
c. You will receive notifications in your Windows task bar that files are downloading.
d. When you receive the notification that the download is complete, close the TraCS application.
e. Restart TraCS by right clicking and choosing the ‘Run as Administrator’ option.
f. Log into TraCS with your System Admin account.
g. Click Yes to start the update.
h. The update will now begin to run.
...
b. Create additional tables in the tracs_data database needed for the new Supplement, Incident, and Evidence forms along with any form that contains statute information by running the new “Delta” SQL script. The script will be in the TraCS network folder (from Task 1.2, step 6b in the Installation Guide) under the DBData\SQLScripts folder. The name of the script takes the form of <Timestamp> Delta.sql. If there is more than one “Delta” script present, run the one with the most current timestamp.
11. REQUIRED: This fall the agency tables will be upgraded and move to a separate database called custom. All agency tables will reside in this database separating the agency tables from state tables. There are 2 steps to moving to the custom database.
...
| Info |
|---|
NOTE:This is required if you plan on exporting the Incident, Supplement and Evidence forms to your RMS. |
a. Log into TraCS Configuration Manager with the System Admin access Level.
...
i. Navigate to Transmission | Import/Export.
...
ii. Expand Export Instructions and Select Export RMS.
...
iii. Click the
...
Import button.
iv. Select No, Let me Choose.
...
v. Click OK
...
b. Expand Forms.
i. Hold down the CTRL key and select:
(a) incidentV2.frm.exml
(b) supplement.frm.exml
(c) propertyV2.frm.exml
ii. Click OK.
iii. Click OK.
14. REQUIRED if exporting to RMS: If you export crash data or citation data to your Records Management System (RMS), you are required to configure the export rules for new forms to match the requirements of your RMS. Refer to Task 3.14in the Badger TraCS Maintenance Guide and your RMS Documentation for more information on configuring RMS export instructions.
...
If form is Active, ensure the new version of the form is Active as well (match the settings from the old version of the form).
Verify the report type using the Reports button (shown below), ensuring the file type, file name extension, and all other settings are the same (needed for ImageToRMS settings.)
...
...
| Info |
|---|
NOTE: The new Incident and Property/Evidence forms only supports exporting data in the TraCS 10 format. |
...
...
15. Import new Communications Instructions. NOTE:Required if you export the supplement form to your RMS. The other 2 forms would have been set up last year.
a. Select the Transmission ribbon menu.
b. Click the Communications button.
...
c. Expand Communications Instructions.
...
d. Highlight the instruction named TransComm
...
e. Set up the new form to RMS
i. Click the Import button.
...
ii. Choose No, Let Me Choose.
...
iii. Click OK.
iv. Expand Instructions.
v. Select multiple items by holding down the ctrl key while you select.
...
supplementToRMS
vi. Click OK.
vii. Click OK.
viii. If your agency defined a web proxy server in Task 1.4of the Installation Guide, you will need to enable its use for transmissions to the state. If you do not use a web proxy server, you may skip this step.
(a) Expand Communication Instructions and then TransComm.
(b) Select the all previous forms item.
(c) Click the Communications Options tab.
...
(d) Check the Use Defined Proxy box.
...
16. ***DO NOT SKIP THIS STEP*** Create new distribution file. ***DO NOT SKIP THIS STEP*** Note this distribution is to export new user files.
a. If you do not complete this step your field units will receive the following error message.
...
b. Start the Configuration Manager if it is not already running.
c. Export user files so that they may be distributed to field units.
| Info |
|---|
(Note: this step is not needed for Web Services units). |
d. Click the Users taband then click the User Editor button.
...
i. Clear the Inactive User field.
...
e. Click the Search button.
...
f. Select user accounts to export.
...
g. If you use TraCS to manage your users, click the Select All
...
button to select all users.
...
h. If you use Active Directory to manage your users, only select the #AD_AU_USER# and #AD_TEMPLATE_USER# users. IMPORTANTNOTE:DO NOT SELECT ALL USERS
i. Click the User Files
...
button.
i. The file path will be preselected to your TraCS user folder.
ii. Click OK.
iii. Wait for confirmation that the user files have been created.
...
j. Start TraCS
...
k. Sign in with a System Administrator account.
l. Click the Configuration and Distribution button in the Tools ribbon menu.
...
m. Click Create Distribution.
n. Enter your agency’s 3-digit Location ID number and click OK. (NOTE: Some agencies have a different name for their distribution configuration form; use whatever is appropriate for your agency).
...
o. Press the Edit button, notice the Version Number field automatically updates.
p. Now press the Validate button to create the distribution.
| Info |
|---|
(There is no longer a need to press the New button to generate the version number, this is done automatically once you press the Edit button.) |
| Info |
|---|
NOTE: Each successive distribution that runs on a computer must have a higher version number than the previous distribution. Distribution files that have a lower version number than the previously installed distribution files will not install on the target computer. NOTE: The version number that is created when you press the new button is based on the current date. If for some reason you wind up needing to create two different distributions on the same day, for example, because you made an error in the first distribution, press the new button again to increment the last digit of the version number. NOTE:This version of TraCS includes settings requested by the Forms Advisory Committee on using the TLT. These steps are required and both an office and a mobile distribution needs to be completed for the settings to take affect agency wide. |
q. REQUIRED: Ensure the Distribution Type field has both Mobile and Office. (NOTE: You do not have to complete both office and mobile distributions on one form).
...
r. Ensure the Automatic Download field has both Mobile and Office if distributions are downloaded automatically
...
.
| Info |
|---|
(If your Agency is using a USB (thumb drive) to end shift, you can ignore this step.) |
...
s. Press the validate button. If the form validates without error, you will receive a message requesting to create the distribution files. Click Yes to generate the distribution files and place them in the distribution folders for deployment.
t. Click OK when the deployment message appears.
...
u. Start TraCS on your master computer. Click Yes to allow other computers to begin receiving the update.
| Info |
|---|
NOTE:Field units will receive a warning that their installation is incomplete until they run the new distribution. If this message persists after running the new distribution, it means that user files were not exported correctly when the distribution was made. The user files contain the new access level for the 2021 crash form and this error message must be cleared up before they can use the new form. Contact badgertracs@dot.wi.gov for assistance if you are having difficulties getting this error message to go away. |
17. Alternative Install Instructions for Fields Units
a. If your agency normally receives updates over the Internet, but you are concerned about the size of this update, you may use theses instructions for your field units.
| Info |
|---|
NOTE: We strongly encourage you to use the TraCS Update server on your TraCS Mobile computer if possible since it is automatic and much faster and easier than the manual download method. The update files are smaller and take less time to install compared to the full WIPack. |
b. In your distribution folder, create a new folder called WIPack
c. Go to https://trust.dot.state.wi.us/tracs/extranet.htm, click on the software link, and scroll to the WI Pack section.
d. Download WIPack.zip.
e. Unzip (extract the files) WIPack.zip to the Distribution\WIPack.
IMPORTANT: do not unzip to your Distribution Mobile folder.
f. You should now have the newest pkg file in the Distribution\WIPack folder: WIPackYYMMDD -WIPackYYMMDD.tracspack.pkg, WIMapPackYYMMDD -Full-WIMapPackYYMMDD -Full.tracsmap.pkg (where YYMMDD is the most recent patch number) and WIPack.bat file.
g. Delete any older pack numbers in the Distribution\WIPack folder that are present from the last time you did this task.
h. On each field unit with no connectivity:
i. Run InstallTraCS.bat, which can be found in the Distribution folder. (See task 3-12, step 6b for location.)
ii. Accept all defaults and click next on all subsequent dialog boxes
iii. Click Finish on the final screen.
iv. Open the distribution folder.
v. Double click MobileDistribution.bat to run it. The customizations from the master computer will be copied to the machine.
vi. Run Distribution\WIPack\WIPack.bat.
vii. The update will run.
...
i. After running the install on each of your field units, start TraCS on your master computer. Click Yes to allow other computers to begin receiving the update.
...
1
...