Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »



2.1.18 19DEC18


Ticket

Linked

Function

Type

Subject

MT-2688

SP-3251

RAIDO Cloud (Web)

Bug

activity action not properly working in 2.2.2 hotfix

Description

Release notes

AUA reported that activity action ends up with error bar in test env 2.2.2

https://aua-test.cust.aviolinx.com

Hi, while testing the new version we found 3 problems. I will create seperate tickets for each bug. Most of the activity actions create an error message (attached) when used. these activity actions are: Shift/Training > P Shift/Training > §8 Shift/Training > FFK KRANK KRANK bestätigt rt > tag frei TF > RT/RTX 100% Dienstfreistellung kurzfristig one is not working but also not creating an error, is just ignoring us completely Pv > PvB without these activity actions we cannot go live, most of them we use on a daily bases. --------------------- How i reproduced: - ctrl+click on "RT" activity - right click and choose Acti - choose rt > tag frei and apply {code:java} Error in:

https://aua-test.cust.aviolinx.com/Raido/ErrorPage.aspx

Error Message: Sequence contains no matching element Stack Trace: at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate) at Aviolinx.WebRaido.Dialogues.HumanResources.ApplyRosterAction.btnApply_click(Object sender, EventArgs e) in E:\TeamCity\buildAgent2\work\b88ea20cf3c8593b\RAIDO_WEB\RaidoWebSln\Raido\Dialogues\HumanResources\ApplyRosterAction.aspx.cs:line 300 at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) {code}



Ticket

Linked

Function

Type

Subject

MT-2667


API

Bug

Missing API information

Description

Release notes

Information is missing from the API, namely Get Flights.

Fixed departure and arrival stations for GetFlights and multileg flights.


Ticket

Linked

Function

Type

Subject

MT-2660


RAIDO Cloud (Web)

Bug

HR Wizard crashes after creating new email type for a crew member

Description

Release notes

creating a new email type before roster release or opening Hr Wizard leads to crash HR Wizard It can be avoided by reloading the dataholder each time and needs to be fixed in this ticket Steps to reproduce: 1. New Email type created: TEST, set a Priority 2 2. Assigned email to crew member 3. Tried to open HR Wizard Expected result: HR Wizard will be run [https://raidotest.smart-lynx.com/Raido] [https://art-test.cust.aviolinx.com/Raido/MainPage.aspx]

When saving email types, before it did not reload dataholder properly which made hrWizard crasch, because it tried to use an email type that was not present in the dataholder. Reloading of dataholder has now been fixed.


Ticket

Linked

Function

Type

Subject

MT-2648


RAIDO Cloud (Web)

Bug

Splitting periods for multileg flights makes schedule corrupt

Description

Release notes

apf prod 2.1.14 and apf-test 2.2.1 Steps to reproducte: Create or find a Multi-leg Flight HP100 AAA-BBB-CCC freq 12345.. # Schedule Edit # Select Freq 5 and press New Period # Then change times for all legs, press recalc times # Message are correct Currently the second leg is correctly displayed in the gantt, but the first leg is not adjusted in the gantt, and is pointing to the previous period with freq 1234...

Fixed legs not saving changes correctly when frequency changed schedule splitt in scheduleedit for web.


Ticket

Linked

Function

Type

Subject

MT-2647



Bug

Ctrl button is not acting correct

Description

Release notes

When you write the nickname for a crew member in the search field and then press Ctrl and click on a activity the marking disappear, but if you after writing the nickname and then click somewhere else on the Gantt you can use the Ctrl button and the marking don't disappear.

Issue when using the search box in crewgantt and selection of activities did not work properly has been corrected.


Ticket

Linked

Function

Type

Subject

MT-2644



Bug

Fixing the exceeded size of cookie in auto-rostering

Description

Release notes


Fixed. Local storage instead of cookies. No more cookies for AutoAssign dialog.


Ticket

Linked

Function

Type

Subject

MT-2626


Sleipner

Story

RAIDO to support NFP 18.7

Description

Release notes

RAIDO to support NFP 18.7. No new functionality. See new WSDL and XSD attached. Import new WSDL Get latest WSDL from Public not, internal Import WSDL file to Service References in RaidoCom Namespace com.NFP.V18_?.PublicService "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7 Tools\xsd.exe" NavtechCrew-18.?.xsd /classes /namespace:Aviolinx.Raido.Communication.NFP_XML.V18_?.Crew "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7 Tools\xsd.exe" NavtechMelCdl-18.?.xsd /classes /namespace:Aviolinx.Raido.Communication.NFP_XML.V18_?.MelCdl



Ticket

Linked

Function

Type

Subject

MT-2620


RAIDO Earth

Task

Fix bug where leg filter which selects activities to not be positioned on was returning something else than what it said.

Description

Release notes

Cannot be tested by support.



Ticket

Linked

Function

Type

Subject

MT-2619

MT-2620

RAIDO Earth

Bug

FilterIdFlightsWhichShouldNotBePositionedOn in CPO doesn't get the correct value after changing avxFilter

Description

Release notes




Ticket

Linked

Function

Type

Subject

MT-2613

SP-3205

RAIDO Cloud (Web)

Bug

Issues with checking in after the 2.2 upgrade.

Description

Release notes

Crew reported issues with checking in last evening (16th Jan), from both the mobile roster and web roster on the computers in the crew-room.



Ticket

Linked

Function

Type

Subject

MT-2610


RAIDO Earth

Task

Saved leg filter in CPO does not update

Description

Release notes

If we save a template with a leg filter in CPO and then modify that filter in the system, CPO won't update the leg filter.

Leg filter in crew pairing optimization updates now after filter is changed externally.


Ticket

Linked

Function

Type

Subject

MT-2608


RAIDO Earth

Task

Make sure user cannot press 'optimize' twice before process is done

Description

Release notes

In crew pairing optimization user interface, if RAIDO is slow, user can press 'Optimize' twice before the first round is done and this behavior is wrong. If user presses 'Optimize' once, the button should automatically become inactive so it cannot be pressed again until the process is done/failed/stopped



Ticket

Linked

Function

Type

Subject

MT-2583



Story

2018h and i release of tz code and data

Description

Release notes

The 2018h release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Qyzylorda, Kazakhstan moved from +06 to +05 on 2018-12-21. New zone Asia/Qostanay because Qostanay, Kazakhstan didn't move. Metlakatla, Alaska observes PST this winter only. Guess Morocco will continue to adjust clocks around Ramadan. Add predictions for Iran from 2038 through 2090. Changes to future timestamps Guess that Morocco will continue to fall back just before and spring forward just after Ramadan, the practice since 2012. (Thanks to Maamar Abdelkader.) This means Morocco will observe negative DST during Ramadan in main and vanguard formats, and in rearguard format it stays in the +00 timezone and observes ordinary DST in all months other than Ramadan. As before, extend this guesswork to the year 2037. As a consequence, Morocco is scheduled to observe three DST transitions in some Gregorian years (e.g., 2033) due to the mismatch between the Gregorian and Islamic calendars. The table of exact transitions for Iranian DST has been extended. It formerly cut off before the year 2038 in a nod to 32-bit time_t. It now cuts off before 2091 as there is doubt about how the Persian calendar will treat 2091. This change predicts DST transitions in 2038-9, 2042-3, and 2046-7 to occur one day later than previously predicted. As before, post-cutoff transitions are approximated. Changes to past and future timestamps Qyzylorda (aka Kyzylorda) oblast in Kazakhstan moved from +06 to +05 on 2018-12-21. This is a zone split as Qostanay (aka Kostanay) did not switch, so create a zone Asia/Qostanay. Metlakatla moved from Alaska to Pacific standard time on 2018-11-04. It did not change clocks that day and remains on -08 this winter. (Thanks to Ryan Stanley.) It will revert to the usual Alaska rules next spring, so this change affects only timestamps from 2018-11-04 through 2019-03-10. Change to past timestamps Kwajalein's 1993-08-20 transition from -12 to +12 was at 24:00, not 00:00. I transcribed the time incorrectly from Shanks. (Thanks to Phake Nick.) Nauru's 1979 transition was on 02-10 at 02:00, not 05-01 at 00:00. (Thanks to Phake Nick.) Guam observed DST irregularly from 1959 through 1977. (Thanks to Phake Nick.) Hong Kong observed DST in 1941 starting 06-15 (not 04-01), then on 10-01 changed standard time to +08:30 (not +08). Its transition back to +08 after WWII was on 1945-09-15, not the previous day. Its 1904-10-30 change took effect at 01:00 +08 (not 00:00 LMT). (Thanks to Phake Nick, Steve Allen, and Joseph Myers.) Also, its 1952 fallback was on 11-02 (not 10-25). This release contains many changes to timestamps before 1946 due to Japanese possession or occupation of Pacific/Chuuk, Pacific/Guam, Pacific/Kosrae, Pacific/Kwajalein, Pacific/Majuro, Pacific/Nauru, Pacific/Palau, and Pacific/Pohnpei. (Thanks to Phake Nick.) Assume that the Spanish East Indies was like the Philippines and observed American time until the end of 1844. This affects Pacific/Chuuk, Pacific/Kosrae, Pacific/Palau, and Pacific/Pohnpei. Changes to past tm_isdst flags For the recent Morocco change, the tm_isdst flag should be 1 from 2018-10-27 00:00 to 2018-10-28 03:00. (Thanks to Michael Deckers.) Give a URL to the official decree. (Thanks to Matt Johnson.) The 2018i release of the tz code and data is available. It reflects the following change, which was circulated on the tz mailing list: Briefly: S?o Tom? and Pr?ncipe switches from +01 to +00 on 2019-01-01. Changes to future timestamps Due to a change in government, S?o Tom? and Pr?ncipe switches back from +01 to +00 on 2019-01-01 at 02:00. (Thanks to Vadim Nasardinov and Michael Deckers.)

2018h and 2018i implemented Qyzylorda, Kazakhstan moved from +06 to +05 on 2018-12-21. New zone Asia/Qostanay because Qostanay, Kazakhstan didn't move. Metlakatla, Alaska observes PST this winter only. Guess Morocco will continue to adjust clocks around Ramadan. Add predictions for Iran from 2038 through 2090. Sao Tome and Principe switches from +01 to +00 on 2019-01-01.


Ticket

Linked

Function

Type

Subject

MT-2542

SP-2933, SP-2973, SP-2977, SP-2979, SP-2980, SP-3000, SP-2934, SP-2989, MT-2378


Bug

Vacation awarding doesn't load hr's children used by rotation groups

Description

Release notes

Hi, when importing the vacation days for LNZ, 1540 Dörflinger did not get her vac days, but as you can see in attached screen shot Bid rank 1 and available days off also 1..... why didn't she get awarded?

Fixed issue with vacations auto awarding not ranking human resources properly when rotation groups based on number of children were used.


Ticket

Linked

Function

Type

Subject

MT-2416

SP-3026


Bug

Swapping shifts is not functioning

Description

Release notes

The case in the document is relevant and gives the error described.

Swapping shifts is now functioning for periods in DEC


Ticket

Linked

Function

Type

Subject

MT-2312


Sleipner

Bug

SIL - FTP scanner doesn't use the sub directory setting

Description

Release notes

FTP scanner doesn't use the sub directory setting, and doesn't delete the file after download.

FTP scanner will now read the subdir setting and delete the file after download.


Ticket

Linked

Function

Type

Subject

MT-1862



Story

Remove inactive leg filters

Description

Release notes

Please remove inactive leg filters from User Group / SCHD- Schedule Thanks. Kind regards, Alina

Removed the inactive leg filters from User Group / SCHD- Schedule.(Should be tested in 2.2.2)

  • No labels