Spira 4.8.12.11 Release Notes
View the latest release notes at
https://spiradatacorp.clientsection.com/
http://s3.amazonaws.com/SpiraReleaseNotes/index.htm
1 What’s New
Spira 4.8.12.x includes many new screens and features which improve the existing application and provide users with some exciting new functionality. In addition to the many visible features, Spira has committed to improved general functionality of the application to improve the user experience.
· 4.8.12.3 : a new install version
· 4.8.12.6 : additional backwards compatibility with 4.8.11.27 mobile units
· 4.8.12.11 : Additional Fixes
Please see the 4.8.12.6 Release Notes for specific changes from 4.8.11.27 to 4.8.12.6.
Below are the detailed specific changes and improvements that have been made to areas of the Spira application and plug-in interfaces. The adjoining numbers, for reference purposes, are feature requests, bugs and known issues in our bug tracking system.
1.1 New Features
1.1.1 Corporate
1.1.2 Mobile
1.1.3 Command
- 7122 : ‘Save Grid Layout’ saves settings in the config file based on Spira User login. This allows users in centralized Application servers (Terminal Server, Citrix, VDI, etc) to customize their layout.
1.1.4 Plug-ins
1.2 Bug Fixes
1.2.1 Corporate
1.2.2 Mobile
1.2.3 Command
- 7061 : 4.8.12.3 [Offline Store] ‘Publish’ uses ‘internal messaging’ connection. Command has been fixed in 4.8.12.6 to use the ‘external connection. This issue should only affect Spira Hosted customers (or customers with customized configurations) where ‘Internal’ Server IP/Name is different than ‘External’
- 7090 : [JobView] Fix Job Address Locations validation criteria to allow it to save.
- 7081 : [Payroll] Allow items on a non-posted ticket with individually posted items in a Ticket to be retrievable for Payroll. Removed ticket state criteria check where ticket state = posted.
1.2.4 Plug-Ins
- CL 22855 : Plugin extension to Spira Command to allow plugins to open Jobs on command.
1.3 Known Issues
1.3.1 Corporate
· 5528 : 4.8.12.x Corporate Server : Cannot support legacy 4.6 and 4.7 mobile communication.
1.3.2 Command
- 7041 : Spira Command that publishes an Offline Store is be tracked in t_QueueName. They will show on the Dispatch Queue Name screens. Users must NOT name these units for dispatch
- [Dispatch] ‘View/Edit Queues’ will crash if a unit has not been assigned a FingerPrintID (GUID)
- 6815 : Division code masking doesn't work the FIRST time you edit on the view. All subsequent edits honor the masking.
- 7068 : [Form Template] must have a valid ‘until’ date set for it to be usable on a Job.
1.3.3 Mobile
- 6904 : [Ticket Type] "multiple job type" feature an under development placeholder
- 4890 : [Spira.Express.Client] must be restarted after loading first offline store
- 6940 : [Spira Express Client] Finger Print Id is updated only on client startup
- 6877 : [Mobile] 4.8.11.27 mobile units will not be able to receive an Offline Store from 4.8.12.3 systems due to new serialization and compression.
2 Installation Instructions
Please Refer to Installation and Configuration Guide or The Help Manual bundled on the CD/ISO
3 Upgrade Instructions
3.1 Requirements
- You may upgrade to 4.8.12.11 from
- 11.27_TO_12.11
- 4.8.11.27
- 12.x_TO_12.11
- 4.8.12.3 or 4.8.12.6 or 4.8.12.8
- This section will outline upgrading a complete System with the following components:
1. Corporate
2. Command
3. Mobile
3.2 Instructions
3.2.1 Corporate
Corporate Server upgrade is manual and requires system knowledge. This guide will instruct you to upgrade the default corporate installation with all default installation directories and Databases.
Installation Directory: C:\Program Files\Spira Data Corp\Spira
Application Database: Spira
Messaging Database: SpiraMessaging
You must use OPTION2 where specified if you are running a multi-division configuration, \Spira_Training + \Spira_Production. Each step must be repeated for each of the above components.
Installation Directory: C:\Program Files\Spira Data Corp\Spira_Training
C:\Program Files\Spira Data Corp\Spira_Production
Upgrading your Corporate system involves patching:
· Application files
· Database(s)
Pre-Upgrade
1. Turn off Spira Services at services.msc
a. Spira Message Queuing
b. Spira Message Processor
2. Backup your databases:
a. Spira
b. SpiraMessaging
Steps
Obtain Corporate Upgrade Package
1.
Download 12.11-Update-Corporate.zip
https://s3.amazonaws.com/Spira.4.8.12/12.11-Update-Corporate.zip
2.
Extract 12.11-Update-Corporate.zip to a temporary location,
ie. C:\SOURCE\12.11-update-Corporate
It will contain folders & files:
a. \1 APP
b. \2 SQL
c. Spira 4.8.12.x Release Notes.pdf (this file)
Patch Corporate Application files
Default \Spira
1. Locate your \Spira instance, C:\Program Files\Spira Data Corp\Spira
2. Copy
a. FROM C:\SOURCE\12.11-update-Corporate\1 APP\Corporate481211.exe
b. TO C:\Program Files\Spira Data Corp\Spira
3. Execute Corporate481211.exe
IF you are running a Multi-Division configuration on one server:
1. Copy Files
a. FROM C:\SOURCE\12.11-update-Corporate\1 APP\OptionB-SpiraMultiCorporate\*.*
b. TO C:\Program Files\Spira Data Corp\Spira_Training
c. And TO: C:\Program Files\Spira Data Corp\Spira_Production
Cleanup Processors.zip
12.x no longer uses the .ZIP processors. These may be deleted.
1. Locate C:\Documents and Settings\All Users\Application Data\Processors
2. Delete \Spira and/or \Spira_Training
a. If you have upgraded all your multi-division instances to 12.x, you may delete the entire \Processors folder
Patch Database(s)
Connect to your MS SQL Server using SQL Management Studio (or tool of choice)
12.x_TO_12.11
1. Execute on Application Database, Spira
o \2 SQL\12.x_TO_12.11\Patch151-FormTemplateCompatibility.sql
o \2 SQL\12.x_TO_12.11\ProductVersion.sql
11.27_TO_12.11
1. Execute on Application Database, Spira
o \2 SQL\11.27_TO_12.11\Pre_Patch4811.sql
o \2 SQL\11.27_TO_12.11\Patch_4811_to_4812.sql
§ The individual patches included in the above cumulative patch, are included for completeness in sub folder \PatchXXX_to_YYY . You may wish to execute each patch individually
o \2 SQL\11.27_TO_12.11\ProductVersion.sql
2. Execute on Messaging Database, SpiraMessaging
o \2 SQL\11.27_TO_12.11\MPatch004-SpiraMessagingV2Upgrade.sql
Restart Messaging Services:
· Spira Message Processor
· Spira Message Queuing
3.2.2 Command
· If your command is 4.8.11.27 or older, you must upgrade to 4.8.11.27 first before attempting to proceed
o Please see Spira 4.8.11.27 Release Notes for more information
· If your system uses a TourSheet plugin, please ensure you obtain the correct NEW plugin and replace at C:\Documents and Settings\All Users\Application Data\Spira Data Corp\Plugins\
Pre-Requirements
· Your command is 4.8.11.27 OR newer
o The token loaded on your Command matches the version it is, ie 4.8.11.27
o You did NOT load a 4.8.12.11 (new) token into your 4.8.11.27 (OLD) Application
· Corporate had been upgraded to 4.8.12.11
o Database patches have been applied
o ProductVersion.sql has been applied (t_productVersion has 4.8.12.11)
Steps
1. Startup Command
2. (depends on system) Application Database Chooser: pick the DB that corresponds to the correct system
3. Command checks the Corporate Application Database, \Spira, to determine if it is required to update by comparing t_ProductVersion to your Command’s registry version
4. Spira.Client.Updater will startup,
1. Click ‘Retry’ to begin upgrade process
5. Follow
on screen instructions
You are now upgraded to 4.8.12.11
6. Restart Spira Command
7. Login
Send Update for Mobile Units: This step should only be completed ONCE.
1. Startup Command
2. Open Setup > Company
3. “Unlock URL”
4. Type in the Spira provided URL for mobile patch
1. Each customer may have a customized patch to facilitate upgrades of specific components. Please contact your Spira Representative for additional information before you “Send Update”
2. The generic Spira Mobile update URL is:
1. 12.x_TO_12.11
http://s3.amazonaws.com/Spira.4.8.12/12.x_TO_12.11-Update-Mobile.zip
2.
11.27_TO_12.11
http://s3.amazonaws.com/Spira.4.8.12/11.27_TO_12.11-Update-Mobile.zip
3. if your mobile units sit behind a proxy/firewall with restricted DNS, you may download the Spira provided mobile patch, 48126patch-Mobile.zip, to a server of your choice
5. “Verify URL” to ensure that the is correct and accessible
6. “Send Update”
1. The URL is inserted into the Application Database, Spira, in the table, t_ApplicationUpdate
2. t_ApplicationMobileUpdates tracks which mobile units have received the update.
3.2.3 Mobile
Pre-Requirements
· Corporate has been upgraded to 4.8.12.11
· Corporate has run ProductVersion.sql
· “Send Update” has been dispatched from Command
Steps:
1. Startup Spira Express Client
2. “Connect
Now” / Request Offline Store
You will be notified that your Application will upgrade on next startup
3. Run Start > Program Files > Spira Data Corp > Spira Mobile
4. You will be notified to exit:
1. Spira Mobile and
2. Spira Express Client
5. Exit Spira Express Client : right-click the tray icon, ‘Close/Exit’
6. Click ‘Retry’ to begin upgrade process
7.
Follow on screen instructions
You are now upgraded to 4.8.12.11
8. Restart Spira.Express.Client + Spira Mobile
COMPLETE