2.3.14 XXJUL19
Ticket | Linked | Function | Type | Subject |
MT-3837 | Task | Add cache for caching automation requests via RaidoAPI |
Description | Release notes |
RAIDO API will need to cache requests to avoid unnecessary DB entries and further recalculations (e.g. legality). For example in case of massive amount of 'Set' requests within a specified time period. | We have added the possibility for caching for in RaidoAPI requests to avoid unnecessary DB and legality refreshes. Configuration available in 'RaidoAPICacheSettings'. 1. 'Cache timeout' - means how long (in minutes) the request will be stored in the RaidoAPI cache (0 - means no cache). The cache will only work for RaidoAPI Set functions.
|
Ticket | Linked | Function | Type | Subject |
MT-3649 | Bug | Crew unable to check in |
Description | Release notes |
We are receiving reports from crew that they are unable to check in for flights. | this issue has been corrected. |
Ticket | Linked | Function | Type | Subject |
MT-3585 | Task | Create a Hide split pairing option in the pairing gantt |
Description | Release notes |
| Add option in Block filters to be able to filter out split pairings | A new expression called 'IsSplitted (Bolean)' has been added in block filters to be able to filter out split pairings in the block (pairing) gantt.
|
Ticket | Linked | Function | Type | Subject |
MT-3574 | RAIDO Earth | Bug | Payroll Wizard reports not working |
Description | Release notes |
There are issues with the Payroll Wizard. We are unable to generate the pay reports. | This issue is resolved. |
Ticket | Linked | Function | Type | Subject |
MT-2863 | Task | Improve performance of historical legality values table |
Description | Release notes |
Planned work performed on data table for historical values in database to prepare it for huge amounts of data (possibly hundreds of millions of rows). | Work to Improve database performance for legality historical values complete. |
2.3.12 XX19
Ticket | Linked | Function | Type | Subject |
MT-3716 | Story | Timezone update 2019b |
Description | Release notes |
Add support for latest timezone update. | Version 2019b of the IANA Timezone database has now been implemented. |
Ticket | Linked | Function | Type | Subject |
MT-3748 | RAIDO Cloud (Web) | Bug | Schedule edit slot status bug. |
Description | Release notes |
A specific use case in schedule edit caused incorrect slot status indications in the schedule gantt. This only affected the color of the status indicators not the slots themselves. | This has been corrected. |
Ticket | Linked | Function | Type | Subject |
MT-2206 | RAIDO Cloud (Web) | Bug | RE: Irregularity msg |
Description | Release notes |
If you create a template in integration factory and use 'CrewOnBoardEmpnoRank1' to bring up the captains name and 'CrewOnBoardEmpnoRank2' for the name of the FO in the template, and one of the pilots is a down ranked captain. The down rank caused the order of the assigned crew to flip over, and show a cabin crew who is rank 20 as the captain = 'CrewOnBoardEmpnoRank1'. However it shows the right data in the preview inside integration factory, but sends out the wrong information when activated by automation factory. | Fixed ranks in AssignAdHoc event window according to template in Integration Factory. |
2.3.11 XX19
Ticket | Linked | Function | Type | Subject |
MT-3616 | Bug | LDAP - parallel authentication does not work |
Description | Release notes |
Please check and fix parallel authentication for LDAP | Fixed issue with parallel LDAP login |
2.3.10 XX19
Ticket | Linked | Function | Type | Subject |
MT-3687 | SP-3929, | Bug | Roster Block Gantt may cause RAIDO to freeze after 30 minutes. |
Description | Release notes |
Initiating the Roster Block Gantt may cause the application to freeze after about 30 min. A clearing of the cache can make it snap out of the 'frozen' state. | Roster Block Gantt lockup issue has been fixed |
2.3.9 XX19
Ticket | Linked | Function | Type | Subject |
MT-3201 | SP-3630 | Story | Add Voyage Landings to setFlightData method |
Description | Release notes |
Add No of Landings available in the Voyage report to the Voyage report section of the setFlightData | Added Landings (Voyage data) to SetFlightData. |
Ticket | Linked | Function | Type | Subject |
MT-3576 | SP-2379, MT-3699 | Sleipner | Task | SMS provider |
Description | Release notes |
As a user, I want to have possibility to send SMS from Raido using https://www.smsapi.comgateway. | Added SMSAPI provider for SMS sending purposes. |
Ticket | Linked | Function | Type | Subject |
MT-3583 | RAIDO Earth | Bug | Pairing creation in Earth creates double pairing |
Description | Release notes |
I did this in https://sil-uat.cust.aviolinx.com/Raido/MainPage.aspx#11 JUN19 Created a pairing in Roster Block The Base/rank and composition is wrong from the beginning so I had to changed it. Did the editing before I saved. After Save I have two pairings for the same flights. One with the correct (edited) composition and one with the incorrect initial composition and base The systems default to Base OCC and a full complement. I changed to FLL, and 1 FO Workaround is to save first and then change the composition | Fixed |
Ticket | Linked | Function | Type | Subject |
MT-3611 | MT-3664 | RAIDO Cloud (Web) | Bug | Duplicate postback sent in chrome 75 update |
Description | Release notes |
When creating new adhocs and schedules they become duplicated because of a change in chrome version 75 fixing a loose postback not finishing. | Fix for creating new adhocs and schedules becoming duplicated because of a change in chrome version 75 |
2.3.8 19JUN19
Ticket | Linked | Function | Type | Subject |
MT-3513 | Sleipner | Bug | FTP Export bug |
Description | Release notes |
If there is an issue with exporting a file using FTP or SFTP (Secure File Transfer Program) on the first attempt, there is a possibility that a field in the export job is updated incorrectly . 'JOBFILENAME' may be updated with a simplified export job message instead. Then, when the job is resent the application tries to find the file from JOBFILENAME causing a failure. | This has been corrected. |
2.3.7 10JUN19
Ticket | Linked | Function | Type | Subject |
MT-3237 | SP-3724, MT-3526, MT-3239 | Bug | Claims in 2.3 |
Description | Release notes |
We have noticed problem with the red line that is used when a crew is claimed by another user. It only shows up for other users inside the period that is loaded in the roster gantt for the user who has made the claim. | An notification has been added, if a user is trying to claim an already claimed crew. |
2.3.6 09JUN19
Ticket | Linked | Function | Type | Subject |
MT-3387 | RAIDO Cloud (Web) | Bug | Incorrectly named icon for Public Holiday Comp Wizard. |
Description | Release notes |
Please check and fix name of icon for Public Holiday Comp Wizard in Cloud. | The Public Holiday Comp Wizard now has an icon. |
...
Description | Release notes |
| Sleipner initializes Mimer "on demand" and store it in AvxLegalityUtils. Part of code responsible for reports uses Mimer directly from AvxLegalityUtils without checking if it's initialized or not. To avoid further issues, please add code to initialize Mimer at application startup. | Problem fixed |
Ticket | Linked | Function | Type | Subject |
MT-3164 | Bug | [CMP_RUAV_ACCUMULATEDVALUES] contains accumulated values with null values. |
Description | Release notes |
Starting with version 2.2.7 (fix has been added in this version which does not save accumulated values with null values) [CMP_RUAV_ACCUMULATEDVALUES] should not contain null values of accumulators anymore. On 16th of April during stand-up has been discussed to have a script in deployment which removes table entries where value of accumulators is null. It has been also mentioned that such script in deployment might not be possible and one should check with deployment responsible. | Accumulated values tables contains accumulators with null values and this fix will make sure that this won't be the case anymore. |
Ticket | Linked | Function | Type | Subject |
MT-3374 | Fire | Bug | Crew reporting problems with check-in on mobile |
Description | Release notes |
There have been problems with checking in via mobile:Looking at the Roster shows that some crew are marked with green check-in flags. | Fixed problem with old CIAO page and missing legacy CIAO SYFU. Fixed problem with triggering an CO. |
Ticket | Linked | Function | Type | Subject |
MT-3460 | SP-3814, SP-3249, MT-3476 | RAIDO Earth | Task | SSIM import-FUNC-saving lots of data |
Description | Release notes |
When saving huge data sets the SSIM import can crash and it would leave corrupted data in the system. It is mainly the modified records that give the error, but potentially it could happen to the others also.What I did to fix this was to update the records in chunks of 100 at a time. And that solved the problem of the SQL timeout. | SSIM import now handles huge amount of data much better when saving to DB. |
Ticket | Linked | Function | Type | Subject |
MT-3445 | RAIDO Cloud (Web) | Bug | OwnMessages not picking up Attributes |
Description | Release notes |
There are attributes missing when a new message is generated. | Fixed missing references for OwnMessage and Schedule (IATAPrefixString, ValidFromDate, OpNumber) |
Ticket | Linked | Function | Type | Subject |
MT-3384 | Fire | Task | Open time, does not allow drops but allows swaps. |
Description | Release notes |
We needs a new setting for Open time as it must be possible to disable drops, but still allows swaps. | Added new setting for swap |
Ticket | Linked | Function | Type | Subject |
MT-3239 | RAIDO Cloud (Web) | Bug | Multi delete |
Description | Release notes |
there is an issue with using multi delete. | We have fixed the inability to delete multiple acts when roster claims are enabled. |
Ticket | Linked | Function | Type | Subject |
MT-3461 | MT-3398, | Legality | Bug | Calculation of warnings. |
Description | Release notes |
An issue was found with the legality calculation in Sleipner. | This has now been corrected. |
Ticket | Linked | Function | Type | Subject |
MEXT-525 | Fire | Task | Incorrect Approval of (open time) Trade Request. |
Description | Release notes |
A trade was approved when the request was submitted less than 3 hours prior to showtime. | This has been corrected. |