Export optimisation
As part of the gradual evolution of the volumes of exports from users of the Orchestra platform, optimisations have been put in place to reduce the memory load of these exports and increase their efficiency.
As part of the gradual evolution of the volumes of exports from users of the Orchestra platform, optimisations have been put in place to reduce the memory load of these exports and increase their efficiency.
The connectivity to the Channel Manager Siteminder has been improved in order to be able to manage the occupations created manually in the Orchestra Administration.
Feeding of prices for manual occupancies
In addition to feeding automatically created occupancies when the hotel is synchronized with Siteminder, it is now possible to feed prices for manually created occupancies (provided you have received the base prices and additional prices needed to calculate these prices).
Standardization: modification of the Price API to adopt the generic OTA :
Transpartent for distribution, now the Prices API uses an OTA format to perform price updates.
The Tracer tool is the analysis tool of the “logs” of the Orchestra platform, that is to say the written traces left by the various algorithms and programs to allow the understanding and analysis of their actions retrospectively
Before this evolution, the analysis of payments was done via the raw log files of connectors and the booking process. The integration of this new type of file into Tracer allows for an improvement in the efficiency of the teams when analyzing these files.
In addition, PSP errors have been “typed”, which improves the depth of the analysis.
Internal flights are now accessible via the Transport Switch, in the same way and with the same rules as flights from external sources.
These flights are thus accessible in the Transport process, in the Package process (as pre-package flights, in the cache, and as alternative flights), in the Dynamic Package process (Flight + Hotel)
