Latest updates in Goelett

Previously users on the Goelett mobile app were encountering unclear validationmessages when encountering errors while filling out analytical fields. With thisbug fix users can clearly see information necessary to proceed with filling thefields correctly.

Previously, we encountered a problem where our search function was notcorrectly identifying the office location when a user selected a company hint.Instead, it would initiate a search around the city center, leading to incorrectresults. However, we have since resolved this issue and our search function nowaccurately identifies the office location when a …

When the user attempted to refine their search results by editing the filteroptions, they noticed that the checkboxes associated with their previousselections were automatically cleared, resulting in the filters not accuratelyrepresenting their initial preferences. This confused and made it difficult for theuser to find the desired results. Currently the filter is fixed …

Our users encountered a problem with displaying the negotiated rates in oursystem. Specifically, the rates weren’t appearing as expected when users clicked on the “show rooms” button. In some cases, clicking the “show” button was necessary to load additional rates. Now, we have implemented a fix that should resolve the issue once …

We have identified a discrepancy between the approval status of certainbookings. While the trip history displays these bookings as approved, theircurrent view continues to reflect a “pending approval” status. This issue havebeen identified and fixed in the user interface.

We identified an issue where the ITA Airways loyalty program name wasincorrectly displayed as “Mille Miglia” in certain areas of the application. Thishas now been fixed, and the program name will be accurately reflected as“Volare” going forward.

Previously, an error (code 66) occurred when booking SNCF tickets with validmilitary ID cards in EDA client profiles. This issue has been fixed. The systemincorrectly processed bookings using military fares, even though the ID cardswere valid. Military personnel can now book SNCF tickets using their IDs withinthe tool.

We have identified an issue where travelers were not receiving timelynotifications when their LCC bookings were not confirmed after 72 hrs frombooking request. This could lead to confusion for travelers who were unawaretheir booking final status.To improve transparency, we made the following enhancement:72-hour follow-up: If the booking remains unconfirmed after 72 hours, anemail …

Previously the picker incorrectly displayed a default time range of 10:00-18:00, despite the actual configuration being set to 08:00-18:00 in the main dashboard. We have identified and fixed this bug. The Rail Time Picker now accurately reflects the configured time range, ensuring correct data representation.

The bug involved displaying incorrectly negotiated rates. Users were not receiving negotiated rates when performing searches. Upon clicking “Show rooms,” only standard rates were displayed. Negotiated rates were only visible after clicking “Show more rooms.”