{//% unless portal.user.is_agent %} Tickets
Welcome
Login Submit a Ticket News {//% endunless %}

N-PBS 24.3 Bug Fixes

Introduction

N-PBS 24.3 Bugs 

N-PBS 24.3 Bugs 

We estimate that this will take 2 minutes to complete.


Detailed Explanation

D-41412 - ALL - IF/IF NOT not displaying correctly in Pairings Tab or Analyzer  

An issue where the IF NOT still displays when a Bidder is trying to bid for IF/IF NOT functions has been resolved. The issue occurs in the pairing analyzer where the IF NOT preferences were being included and in the Pairing Tab with IF NOT Redeyes/Landings In & Layovers displaying.

  

Example Bidder Preference: 

  • IF Departing On Monday, Tuesday, Wednesday, Thursday
  • IF NOT Any DUTY Between 01:00 And 04:59 
  • If Pairing Length Between 2 Days And 3 Days 
  • If Total Legs In Pairing (Counting Deadhead Legs) = 2 Legs

 

Note: In this example, it seems to still be pulling Pairings departing on.



D-42197 - ASA-P - Email Issues with Load and Eligibility 

We corrected an issue where the I5 file is populating the email database table, which caused the email import to populate the eligibility database table.

This occurred:

  • If the pilot has a crew status in the I5 file, that pilot is marked as ineligible (as expected). Any email address stored for that pilot is "replaced" with the crew status, which is seen only after marking him as eligible. 
  • If a pilot has an email address on file but is changed to "ineligible" status, that email address is removed. 
  • If a pilot is "ineligible" and the import feature to load an email address is used, that email address is NOT saved.          

 

D-43211 - ASA-P - Bid Analyzer : Option Not not taken into account for WoclTurn

An issue where the analyzer displays the same result for creating an Award Bidline "Award Pairings If Not WOCL Turn" has been resolved. This occurs whether the IF NOT option is selected or not.

 

D-39586 - JZA - FA able to bid too many GDOs in September/23 schedule 

We resolved an issue where the number of GDOs awarded was higher due to the days of the holiday blocks that were adjacent to each other not being grouped. By applying the existing solution that is used in the development of IDO, we have resolved this issue. 

 

When the flag PilotTreatEachAbsenceAsSeparateBlock = false before checking the number of GDOs, the blocks of vacations are grouped.

 

Example: A YYZ FA is able to bid for 6 GDOs with one stretch of vacation/BST time, which is illegal. The bid is for Sept 02-04 and 14-16. The bidder should have only been able to bid for 3 GDOs as their time off stretch was Sept 05-13.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.