TRAVELTRAX Web Reporting Release Notes 6.3 November 04, 2011

Transcription

1 TRAVELTRAX Web Reporting Release Notes 6.3 November 04, 2011

2 TABLE OF CONTENTS SECTION I: Conventions... 2 SECTION II: Introduction... 3 SECTION III: Features and Enhancements... 4 SECTION V: Appendix A - Addressed Issues SECTION I: Conventions This document covers features and addressed Change Requests that are being delivered as part of TRAVELTRAX Web Reporting v6.3. This manual references other company names, trademarks, brands and service marks. Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor. The software described and referenced in this manual is furnished under a license agreement and may be used or copied only in accordance with the terms of the License Agreement. Reproduction of this documentation or documentation mentioned above by any electronic or analog means is subject to the rights, restrictions and permissions as outlined by TRX. TRAVELTRAX is a service mark of TRX, Inc. Document is subject to change and is not a commitment of future features. Page 2

3 SECTION II: Introduction TRAVELTRAX Web Reporting v6.3 Release Notes Release Date Introduction November 16, 2009 The v6.1 Release of TRAVELTRAX Web Reporting contains 4 new features or feature enhancements to the original TRAVELTRAX application. The following is detailed in these Release Notes: 1. SSO Functionality Single sign on functionality to access TRAVELTRAX Web Reporting. 2. User-Acceptance Prompts Custom user-acceptance prompts at login to allow clients to manage their own user agreements, security notices, etc. 3. Password Requirements Enhancement to comply with a client s requirements. 4. Outer-join Capability Ability to create outer joins using proper SQL 92 syntax. 5. Multi-threaded Environment Instead of queries being submitted one at a time, report queries are submitted simultaneously. Format The description for each feature includes the following fields: Purpose The purpose of the feature. Summary The functionality of the feature. Functional Details More information on how the feature/enhancement works in TRAVELTRAX Web Reporting Client Considerations Necessary client-supplied material for the feature and setup considerations. Page 3

4 SECTION III: Features and Enhancements Feature #1 Purpose Summary True SSO Functionality Add the ability for partners and clients to use single sign-in functionality to access TRAVELTRAX Web Reporting. Functional Details Client Considerations Page 4

5 Feature #2 Purpose Summary Client Configurable, User-Acceptance Prompts at Login. Clients now have the ability to create custom user-acceptance prompts when a user logins. This will allow clients to manage their own user agreements, security notices, corporate alerts, etc. Functional Details Client Considerations There will be a sub menu item (Edit Agreements) under System, for system level agreements; A menu item under the Edit Meta Layer Settings for Meta Layer level agreements A menu item under the Edit Entity Settings for Entity level agreements. Each of these menu item options will display an Agreement admin/config screen where the client can reorder the agreements and edit the agreement name, main text, and prompt text as well as whether an acceptance to the agreement (checkbox) is required. In edit portion of the screen, it will allow the user to update the agreement text (name and prompt) for any of the currently supported languages. These new menu items will be grayed out (disabled) when the user does not have access to edit that level (when the Edit Meta Layer/Entity menu items are grayed out/disabled). Page 5

6 Feature #3 Purpose Password Requirements Enhancement Summary Functional Details Enhance password requirements for GSA migration from Datatrax to TRAVELTRAX. Must not contain more than 2 consecutive characters (eg., Password1 is allowed, but Passsword1 is not) Must not contain certain special characters. Specifically, escape characters are to not be allowed. The application does not currently discriminate against any characters entered into the system. The prohibited special characters are common escape characters. The following escape characters shouldn t be used:, \ % Password can only be changed once per day (24 hours). (Exception: it can always be changed immediately following a reset by the helpdesk.) The above requirements are optional and should be configurable in administration. Client Considerations Page 6

7 Feature #4 Purpose SQL-92 Outer Join Capability Summary Functional Details Ability to create outer-joins in SQL. This change would apply to both the Rocket in TRAVELTRAX Web Reporting and TRAVELTRAX Desktop Reporting Proper SQL-92 Standard Syntax: LEFT OUTER JOIN LEFT JOIN RIGHT OUTER JOIN RIGHT JOIN SQL Server - Legacy syntax was to use *= and =*. These should no longer be used. Oracle / DB2: - For clarity, (+) is a legacy operator and should not be used. On top of that, there are restrictions inherent when using the (+) operator that do not exist for the SQL-92 syntax. - (+) operator cannot be placed on both sides of the "=" sign. - (+) operator cannot be used within an "IN" condition - (+) operator cannot be used on both sides of an "OR" condition. Client Considerations Page 7

8 Feature #5 Purpose Multi-threaded Environment to increase overall report performance. Summary Functional Details Instead of being run in a linear fashion, queries run all at once. Previously, a 5 section report would submit each query individually. Now, it will submit them all at once. This results in quicker processing (5x or greater). Client Considerations Page 8

9 Page 9

10 SECTION V: Appendix A - Addressed Issues Below is a list of reported issues that have been addressed in this release (6.0A Release). Note: For Questions on items marked Verified Cannot Reproduce or Verified As Designed further discussions may be necessary. Verified Cannot Reproduce Validated that issues cannot be reproduced in the version of code scheduled for deployment. Verified As Designed Validated that issues are intended per original design. The below is the list Addressed Issues in this version. ID State Synopsis Notes Verified Fixed Verified Fixed Verified Fixed Fixed When using Multiselect or Scheduled Tasks and a prompt is used in more than one report, the information the user enters into the prompt was only being applied to the first report that ran instead of all the reports that contain that prompt. When the user changes a profile, the view changes back to a report view. Request to add the Scheduled Task name to the subject line of the . Level 2 and Level 3 users are able to change their own password more than once a day by using checking the Force Password box. The prompt information entered by the user will now be applied to all reports that share the same prompt. The view will no longer change when the user changes a profile. The company administrator can now add the scheduled task name to the subject line of the Level 2 & 3 users will now receive an error message if they try to change their own password more than once a day. ID Instructions 1. Mouse over Admin, Meta Layer, the meta layer name, and the entity name. 2. Click on Edit Entity. 3. On the first page, enter the subject in the Mail Subject box. Page 10