Sabre is deprecating a version of the cryptic command call “SabreCommandLLSRQ”, which Softrip uses. We have now upgraded to their latest version of 2.0.0 in order to keep using this command.
Why it’s important:
Keeps Softrip up to date on latest Sabre security
Prevents Softrip customers from having an interruption in their Sabre processing
Who it Affects:
Sabre air users
Multiple areas of the system where cryptic commands are used
Retrieval of PNR
Cancellation of PNR
Native GDS commands
Softrip has added additional validation to the Move Funds screen within the Groups area. This is to ensure that the users (whether internal or a group leader) are not creating bad transactions in the system and causing issues with the Received amounts on the group child reservations.
The system will now validate that the “Amount to Move” on each reservation is either 0 or a positive number and will not allow the user to move a negative amount to a reservation. We have also updated the 2 buttons (Waterfall and Split Evenly) to skip any reservations in the list that have a negative amount due so as to make those buttons more efficient for the user.
Why it’s important:
Keeps UI more intuitive and prevents users from creating data the system does not expect
Who it Affects:
Groups Next users
Both internal and external users
Only if the Move Funds menu option is enabled
A new filter has been added to the Tour Services screen to help exclude ad-hoc groups from the results. A new checkbox called “Hide Tour Series Groups-Only Services” will now be displayed and not checked by default.
When checked during the search, the system will filter out any services that are only on 1 group within the Tour. Meaning, if a service is on a Group Product within the Tour but not on any other Products within the Tour, that service will not be returned or displayed on the screen.
If not checked, the search will work as normal and return all services for the given Tour that is being searched for.
Softrip has also added a setting to allow this to be checked by default, please contact Softrip if you would like to make this change.
Why it’s important:
Allows more flexibility for operators, especially ones who have many ad-hoc groups that are managed separately
Who it Affects:
Operations Next users
Various improvements have been made to the air contract setup screen to improve efficiency and intuitiveness. The below changes have been implemented on this screen:
In the Add Contract popup, if there is only 1 departure date to choose from, the system will automatically select that date rather than give an error to make you specifically select that 1 date
Fixed issue where some of the date fields were not getting auto-filled in every scenario based on the setup of the contract
Fixed issue where the one way checkbox was not setting all of the values behind the scenes correctly to shop for one way air
Open Jaw checkbox has now been moved to the header area, similar to the One Way and Inner Block checkboxes to make it easier to find
The Destination and Block Return From City fields will now do a lookup of the correct city code based on the airport codes entered in to the legs. This is needed for the air shop to work correctly
Ex: JFK is an airport code but NYC must be the value entered in to Destination and Block Return From City. This lookup will now happen automatically without the user needing to know the translation needed
If the user creates a Contract with only 1 leg, the system will automatically validate the One Way checkbox. If it is not checked, the system will auto-select this to be sure that the contract is set up correctly to shop for air
This will only happen on the creation of a new contract, not the edit of an existing contract
If the user creates a Contract with an Open Jaw itinerary, the system will automatically validate the Open Jaw checkbox. If it is not checked, the system will auto-select this to be sure that the contract is set up correctly to shop for air
This will only happen on the creation of a new contract, not the edit of an existing contract
If the user creates a Contract where the itinerary’s first leg is set to an On Day > 1, the system will automatically validate the Inner Block checkbox. If it is not checked, the system will auto-select this to be sure that the contract is set up correctly to shop for air
This will only happen on the creation of a new contract, not the edit of an existing contract
Added support for shopping and booking NDC Fares for Sabre within Net Reservations. This includes displaying an NDC logo within the air results and cart of a reservation, as well as a confirmation popup requiring the user to confirm that they are booking an NDC airfare option.
Why it’s important:
Keeps Softrip and their customers up to date on the competitive rates and nature of air
Who it affects:
Net Reservations with Sabre Air
Due to setup and implementation needs, please contact Softrip if interested in starting this project
Due to issues around max child age at hotels and how that interacts between Softrip and external hotel interfaces (HBSI, SYNXIS, DINGUS, HOTELBEDS, etc), Softrip is now adding a feature to tell the system how to treat children and when to consider the max child age loaded in Softrip against the service.
A new Default ID RecalcMaskForInterfaces has been introduced which allows the operator to determine which interfaces should check the max child age in order to correctly calculate the mask to be sent to that interface. Ex: If a user shops for AAC15 in Softrip and the max child age of the loaded service is 14, we may want to treat that child as an adult when sending to an interface like Dingus (sending a mask of AAA to them). If the interface code is loaded in to the Default Text of this Default record, the system will recalculate accordingly. If the interface code is not loaded in to the Default record, the system will send the mask as is to the interface and rely on their system to handle it appropriately.
Why it’s important:
Allows for more flexibility around who is responsible for checking child ages (External interface or Softrip operator)
Who it affects:
Net Reservations using External Hotel Interfaces
HBSI, SynXis, Dingus, HotelBeds
A new button for “Add Payment” has been added directly to the shop cart header when in mobile view instead of being hidden in a menu. This will provide a better UI experience to the user and reduce confusion and/or questions to the operator.
This will only display to the user when the Total Due on the reservation is > 0.
Why it’s important:
Reduces confusion and makes it quicker and more efficient to pay for a reservation
Who it affects:
Everyone using Reservations Next
The cart summary in mobile view is now changed to be a little more compact as well as more consistent with the desktop view. Changes to this section include:
Combine all 3 sections of data in to 1 section, that is still expandable/collapsible
Contact information will hide if no contact is assigned yet (happens on new reservations) to reduce confusion
Brand/Market information will only display for Internal users to reduce confusion for external users
Header colors to now match the branded styling to be consistent with other areas of the system
Why it’s important:
Provides a better UI experience for mobile users
Who it Affects:
Reservations Next users using mobile view
To make the mobile view more consistent with the desktop view, many areas of the system will now follow the custom brand styling that has always displayed in the desktop view. The following areas have been updated in mobile view so that the headers will display in the correct background and font colors:
Package Landing Page
Shop Results
Reservation Overview
Contact Search (both CRM and in the reservation flow)
Passenger Page
Why it’s important:
Provides a more consistent view between desktop and mobile view of the reservation system
Provides better confirmation that the user is still on the correct site due to the matching color schemes
Who it Affects:
Reservations Next users using mobile view
The shop results summary (dates, passengers, total price, etc) will now be anchored to the top of the page and stay with the user as they scroll down the page. This will allow the user to always see their summary with the total prices as they add/remove services, reducing the need to scroll up and down the page to see how it affects their price.
Why it’s important:
Provides for a better UI experience with a more efficient view of the pricing
Who it Affects:
Reservations Next users
The Softrip Payments form will now allow for the user to select the Country of their billing address. This will help with the ability to enter the correct address of the card holder in order to verify the card information.
Why it’s important:
Allows for all addresses to be considered during the payment processing
Who it Affects:
Reservation Next users on Softrip Payments
If Daily Itinerary is built with date ranges, the package landing page will display only the valid itinerary records for the selected departure date - Res Next only
Fixed issue with confirming a service not showing the memo popup in certain scenarios and giving an error instead
One way checkbox in Main Air Segment setup will now save the value correctly to the database
Fixed departure dates & prices screen to add departures through the last date of a range if adding multiple dates using a date range parameter (was previously stopping 1 day early)
Create Book By dates in the departure dates & prices screen will now save new records created by the input form
The Product History form will now display the Results of a failed mass change in the Results textbox
Next Documents will now reflect the appropriate currency sign based on the selling currency of the reservation (Invoices, Reservation Quote Letter, Group Statement)
Air Request default preferences will now display in the special requests section without requiring Frequent Flier preferences to also be set up - Res Next only
Fixed duplicate warnings displaying on the page when an external user completes a passenger name change (using the text from Rule Area PAXNAMECHANGEWARNINGTEXT) - Res Next only
Completing passenger forms for all passengers will now mark the form as complete correctly (previously only marking the 1st passenger’s form as complete) - Res Next only