D-46649 - Community - Pairings List Printout Contains Only One Page in
Bid, Training
We have identified an issue where, after clicking the print button in the Bid tabs, only the first page is available for printing or generating, and it is not possible to print or generate all pages. A similar issue sometimes also occurs in the Training Tab and Bid Tab.
Resolution Details
The relevant variable in the printing functions within bidscontroller.js and trainingscontroller.js now ensures that the appropriate CSS styles are included. This enables multi-page printing in both the Training and Bid tabs. Also, new styles have been added to report-print.css to further enhance support for printing multiple pages.
D-45718 - JZA - Not Able to Resubmit Bid After Adding Additional Bids
We resolved an issue where users were not able to resubmit a bid after adding additional bids under specific conditions. This occurs when:
there is a vacationGDO bidline with only one day selected
the bid is submitted
the synchronize button is pressed.
At this point, the bidline is first stored in XML format, and then restored back to JSON format. Due to the non-symmetrical nature of the JSON→XML→JSON translation, as conversion does not work the same in both directions, an array with one Date object turns into just a single Date object. This prevents the bid from being resubmitted.
Resolution Details
To address this, the system has been updated to accept both an array with few Date objects or a single Date object. This ensures that bids can be resubmitted regardless of the format used during the translation process.
D-45929 - PBS 25.1 - Not Able to Mouse Scroll on the List View of WebApp Calendar with Smaller Resolution
We resolved an issue where ListView scrolling does not work when the screen resolution is less than 800px in height and less than 1012px in width.
Resolution Details
To resolve this issue, we applied the CSS scroller rule exclusively to the classic Calendar View, ensuring that ListView scrolling remains enabled at all screen resolutions.
In addition, CSS code changes were implemented to make the “Total Credit” section of the ListView table more responsive, ensuring a clear and user-friendly layout across various devices and resolutions.
D-45457 - PBS 24.7 (RH6) - Converting TOPS Absence - Credit Over 32767 Minutes is Not Processed
We resolved an issue where converting TOPS Absence credits over 32,767 minutes is not processed correctly. This occurs because the credit value converts from a string to a navsint16 (short int), which has a maximum value of 65,535. During conversion using sscanf, values up to 32,767 are handled correctly, however values above this threshold result in “value - 65,535,” producing a negative number that is not valid for credit.
Resolution Details
To resolve this issue, we updated the function ConversionHelper::ConvertToCredit(...) to use a navsint32 instead of a navsint16 for the TimeMins variable. This change ensures that credit values up to 99,999 can now be processed correctly without errors.
D-45080 - PBS 24.7 (RH8/RH6) - Offline Mode Warning Message Shows on the WebApp Login for a Locked Period
An issue where the Offline Mode warning message appears on the WebApp log in screen for a locked period has been resolved.
Resolution Details
This issue is fixed by implementing several small changes in multiple places:
The system now checks if the period is locked before attempting authentication.
If the period is locked, authentication is performed using local browser storage instead of asking the backend.
The pop-up warning message is corrected to display the appropriate information.
D-46621 - PBS - Pairings List Printout Contains Only One Page
We resolved an issue where printing the Pairings list from the Pairings tab in the WebApp generates only one page for printing. This prevents users from printing the complete list.
Resolution Details
This issue is now fixed by updating the relevant variable in the printing function (printedContents) within pairingcontroller.js (line 474), which is responsible for printing in Pairing Bid. The update ensures that the appropriate CSS styles are included, enabling more pages to be printed.
D-45753 - PBS (RH8/RH6) - Admin UI- The Version Number is Shown ‘HEAD’ Which is Not Correct on Pop-Up when Clicking on NAVBLUE Logo
We identified an issue where, in the Admin UI, clicking on the NAVBLUE logo displays the version number as ‘HEAD’ instead of the correct version on the pop-up. This occurs due to the rpm version not being set in all the required locations.
Resolution Details
We resolved this issue by updating the deployment process to ensure the rpm version is set in the additional necessary location. This change ensures that the correct version number now displays in the Admin UI pop-up when clicking on the NAVBLUE logo.
D-46198 - PBS - UCA Database Upgrade Failure on Trunk
An issue where the UpgradeFalconDb-1.762.pl script fails when attempting to create the DailyShortCallItem table has been identified and resolved. Typically, this problem does not occur during normal day-to-day operations, however,there are two specific scenarios where this is a problem:
when retrieving a customer database for local installation to do troubleshooting
when restoring a database for a customer from a backup after an upgrade.
As a rule, upgrade scripts checks if a table already exists when creating it. The root cause is that the upgrade script attempts to create the DailyShortCallItem table without this check. If the table already exists, this causes the script to fail, for all customers.
Resolution Details
To resolve this issue, we updated the upgrade script to include an IF NOT EXISTS clause, therefore changing the line from “CREATE TABLE DailyShortCallItem” to “CREATE TABLE IF NOT EXISTS DailyShortCallItem”. This ensures the script only creates the table if it does not already exist.
D-46438 - [RH8] SSO - AdminUI - LogoutUrl in localStorage is Not Clean Up During Logout of SSO
We corrected an issue that occurs when switching between SSO mode and Normal mode in AdminUI. After using SSO mode, the LogoutUrl parameter in localStorage is not removed during logout. This caused a wrong display during logout when switching back to Normal mode, due to the outdated LogoutUrl remaining in localStorage.
Please refer to ‘Steps to reproduce’
Resolution Details
We resolved this issue by modifying the logout process to ensure the LogoutUrl parameter from localStorage is removed during SSO logout. This fix ensures proper cleanup and correct logout display when changing modes.
D-43360 - ACA - Pairing Display Shows Code When It Was Not Previously Shown
We discovered an issue after the 24.1 update, where a hotel code (16K) appears in pairings, even though ACA-RGA does not have hotel file load capability. This issue results from the addition of the hotel name feature for ASAP (S-80697), which does not account for cases where an invalid hotel name is present in the input file. As a result, the 16K code displays in the pairing data and schema. This issue is now resolved, and invalid hotel codes no longer show in the pairing display for customers without hotel file load capability.
File load options in PBS:
Examples of issues that occurred:
The 16K hotel code appears in the pairing file data for July.
The 16K code is highlighted in the display of the schema used by the Jeppesen pairing optimizer.
***please see below Pairing file linked***
Resolution Details
We have resolved this issue by modifying the code to prevent the display of invalid hotel codes, such as 16K, when hotel file load capability is not available.
D-46437 - ASA - Pairing Import Carryover Credit on Wrong Date
We resolved an issue where Start and End times are assigned wrong values from the JCTE history file, resulting in credits being calculated for the current period even though the pairing started in the previous period. This issue occurs due to overlapping legs in the JCTE history file, where the file confuses sorting and assigning legs to the correct location, which causes problems with accurate time and credit calculation.
Changes to implement:
The sorting criteria for JcteConversionHelper needs to be updated to compare the departure times of two legs. Instead of comparing the arrival time of one leg with the departure time of the other.
Resolution Details
We resolved this issue by modifying the sorting criteria in the JcteConversionHelper. The new logic compares the departure times of two legs, instead of comparing the arrival of one leg and the departure of another.
As a result, pairings with overlapping legs are now correctly sorted by scheduleStartTime, eliminating issues caused by overlaps. With this change making sorting correct, start/end times and credits are now accurately calculated according to the correct location (and local time).
D-46697 - DAL SC-Submit multiple "ORDERED" identifier numbers
We have discovered an issue where submitting multiple “ORDERED” identifier numbers fails due to the way the bid is serialized to the backend. The main issue is that the backend Composite can not process fields that appear as a sibling to array fields. In this case, the array of Value is placed directly next to the Ordered field, causing the process to fail.
Resolution Details
We resolved this issue by modifying the serialization logic so that the Value array is now wrapped in a Values (non-array) parent, making Values a sibling to Ordered instead. This change ensures that the backend can correctly process the data, and submitting multiple “ORDERED” identifier numbers now works as expected.
D-46410 - Error when adding/editing category for non-DAL customer
An issue where an error message, “Unable to find the list of category options” appears when adding or editing a category for any non-DAL ALC, has been identified. This issue began after introducing the “Max TDA” option for Delta, alongside the existing “ALV” (also Delta-specific).
Previously, if these Delta-specific options were not found, the code did not display an error. However, with recent changes, the system now displays an error when it can not locate these category options, causing issues for non-DAL customers.
Resolution Details
We resolved this issue by implementing a check to determine the customer’s specific configuration before crafting the query. This ensures that only valid category options are requested, preventing any errors from occurring.
D-45244 - FFT - Total Credit - Carry Out
We resolved an issue where Total Credit is not correctly set to zero for pairings spanning two periods.
Example
The files for July and August were downloaded, and two periods were created: July 1–July 30, 2024, and July 31–August 30, 2024.
The pairing information, along with the Total Credit and Carry Out values, is sourced from the July CrewPlan file. The “In Period” value is then calculated using the formula: “Total Credit” - “Carry Out”(Total Credit - Carry Out= In Period).
Resolution Details
This issue is resolved by updating the logic to use the value from the CrewTrac Pairing file instead of defaulting to zero for the Total Credit when pairing is over two periods. As a result, both Total Credit and Carry-Out are now set correctly.
D-46768 - FLE Acclimatization wrong for Absences away from Base
We resolved an issue where the rules infrastructure (TripLineLineRep) always assumed the start and end location of Absences to be the base location. This bug has existed for many years without causing issues, however with FLE now having absences away from home base (such as for training), it has become necessary to update acclimatization status based on the actual absence locations. The rules infrastructure needs to be updated to recognize the actual start and end location of each absence.
Resolution Details
This issue is now fixed by modifying the code to ensure that the rules infrastructure now recognizes and processes the actual start and end location of each absence, rather than defaulting to the base location. As a result, the system accurately updates acclimatization status for absences occurring away from home base.
D-45288 - JBU UAT - Login with SSO token in URL
An issue where the SSO login process exposes the SSO token (parameter) in the PBS App URL, has been identified and resolved. This issue allows direct log in to the PBS app without authentication if the URL is copied on the network, and used in another browser or shared with anyone. This vulnerability also affects the Admin impersonating Bidder scenario by passing the token in the URL (where it is passed from the Admin UI to the Bidder WebApp to short-circuit SSO).
Resolution Details
A code modification is now implemented to resolve this issue by no longer passing the token as a URL parameter. Instead, the token is stored securely in cookies, ensuring it is not visible in the URL and can not be easily shared or intercepted.
D-46675 - JBU - TOPS Award Export
We have discovered an issue where the JBU TOPS Export file is displaying the first leg departure time and date instead of the actual pairing report (Duty Start) time and date under <Pairing><Start>. This issue is now resolved.
Resolution Details
The issue has been resolved by including the Duty start date/time under <Pairing><Start > not departure time. By updating the export logic to use the pairing report time and date, this ensures that the correct Duty Start information shows on the first day of the pairing rather than the first duty or leg departure. As a result, the JBU TOPS Export file now correctly displays the check-in time and date for each pairing.
D-08594 - NVEQ Add/Edit Absence Code Browser Exception Error
We have discovered an issue where attempting to add or edit an Absence Code using the Admin UI for NVEQ results in a browser error: “ERROR; Unable to process click event.” The Chrome Developer Tools displays “Uncaught TypeError: Cannot read property ‘contains’ of undefined” at AbsenceCodeAdditionalParameters.removeSlidableGroupAndLabel (absence_code_additional_parameters.js?version=HEAD:457) error. This issue occurs due to recent slide code that does not check whether the equity module is enabled. Previously, earlier code did these actions in “if (!this.isHasEquity)” checks.
Resolution Details
We have resolved this issue by adding a check for whether equity is enabled to all conditional widgets specific to the equity module. This ensures that slide-related code only runs when appropriate and prevents the error.
D-46397 - PbsData ExportBaseCrudInfo.pl syntax error
An issue where the ExportBaseCrudInfo.pl script fails with a syntax error referencing “VacIDOQualifying,” is resolved. The error occurs due to the code (./ExportBaseCrudInfo.pl) at line 600 not being correct, resulting in a compilation error and preventing the script from processing.
Example
Syntax error at ./ExportBaseCrudInfo.pl (line 600), near “my VacIDOQualifying =”
Execution of ./ExportBaseCrudInfo.pl aborted due to compilation errors at ./ExportBaseCrudInfo.pl (line 604).
Resolution Details
This has been resolved by updating the script to correct the syntax error, allowing it to compile and run successfully.
D-35385 - Post-Process Coloring counting shadows towards coverage
We corrected an issue where post process coloring is counting all Reserve Awards not correctly, including Shadow Awards, towards coverage numbers. This issue is due to an oversight (never considered) in the original specification and implementation of post-processing coloring, as Shadow Awards were not intended to be included. As a result, Shadow Reserve Days are being counted towards Short Call targets, and the Statistics Report. It similarly affects Long Call Awards as well.
Resolution Details
We resolved this by adding a check to determine whether the line is a Shadow. This ensures that only real Reserve Awards are counted, excluding Shadow Awards from the coverage calculations.
D-46024 - SAML - Removing the SignatureValue from SAMLRequest Does Not Block Authentication Process
We resolved an issue where the authentication process does not block the properly validate the SAML response signature, allowing the process to continue even if the signature is removed or altered.
Resolution Details
We have resolved this issue by enabling signature validation in the SAML response message when required. This reduces vulnerability to signature removal/change attacks and strengthens the security of the authentication process.
D-46435 - SCX - Absence Ending Month between 0000 and 0200 on 1st of Month
For SCX, we identified an issue where the import process functionality does not properly recognize a Midnight Offset when determining how much in-period credit to attribute to a Historical/Carry-In Absence. Specifically, absences ending between 00:00 and 02:00 on the first day of a new period are not correctly included in the InPeriod TotalCredit calculation.
To address this, changes in the absence calculation logic are now completed. This ensures that, for SCX, Absences ending within the Midnight Offset on the first day of the new period are treated as historical and not included in the InPeriod TotalCredit. As a result, an Absence that starts in the previous period and ends within the Midnight Offset has no credit value assigned to the current period.
AdminUI:
Schedule:
Resolution Details
We resolved this issue by including the Midnight Offset (set in minutes) in the calculation of the absence window when the absence ends in the new period.
D-46588 - SCX - System Flags Overlap of the Same Two Codes
We identified an issue regarding the import process not flagging a WARNING for overlapping activities, specifically between a RESP ending on the 27th at 00:59 and the OFF starting on the 27th at 00:01, as shown in the image below.
Resolution Details
To address this issue, we introduced a new parameter that controls the maximum number of warnings for overlapped activities. This parameter is currently set to 10. With this change, the system will now flag up to 10 warnings for overlapping activities during the import process, ensuring users are properly alerted to potential overlaps.
D-44836 - SCX - Import of CrewPlanPairings File That Contains Pairings In The Future Is NOT Rejected
For CrewPlan, we resolved an issue where the CrewPlan Pairings file could be imported even if it contained Pairings with start dates far into the future. This issue causes the Pairing Report to generate a very long calendar.
Note: Normally, CrewPlan2PairingConverter should not allow the import of Pairings with start dates in the future, instead the process should be stopped and an error reported.
Resolution Details
This issue has been fixed by modifying the CrewPlan2PairingConverter to prevent importing pairings with start dates later than the end of the period. Now, such pairings are rejected and an error is displayed: “ERROR Line #NUM : Pairing [PAIRING_NUM] starts further than period.”:
D-46157 - [SCX] FastCGI FalconConversionUI_SCX Process Fails During
AIMS Import
We corrected an issue where importing the AIMS Absences & History file (attached) over the December period in the SCX UAT and Production Environments RH8 results in a 500 Internal Server Error (import fails). This error occurs because the web server can not communicate with the FCGI process, /var/www/fcgi-bin/FalconConversionUI_SCX which is terminated due to a segmentation fault.
Resolution Details
We resolved this issue by adding an error message, “No duties found,” when no duties are added, thus preventing the segmentation fault and improving error handling during the import process.
D-46853 - Community - Locked Function
An issue where logging in directly as a Bidder works differently across different environments and SSO configurations has been identified and resolved. This occurs when attempting to log in on RH8 with SSO enabled, or when the period is locked, resulting in behavior that is not expected such as constant loading.
Example
When logging in directly as a Bidder, correctly works on 23.6 -18 (RH8 environment set up for load testing:
When logging in directly as a Bidder, the process works correctly on version 23.6-18 (RH8 environment set up for load testing):
When logging in directly as a Bidder on the latest version of RH6:
When logging in directly as a Bidder with SSO enabled on RH8 in the latest version:
Resolution Details
We resolved this issue by implementing several code updates. The login process now prevents access if the period is locked, and the application properly handles constant loading in cases when translations are not downloaded. In addition, for SSO mode, the system now performs a proper logout if the period is locked. These changes ensure a reliable login experience for Bidders across all environments and configurations.
D-47047 - Internal Server Error when SSO is Enabled in Combination to redirect_to_webapp
An issue where users are not able to log in as a Bidder when SSO is enabled and the new bidder interface (<REDIRECT_TO_WEBAPP>1</REDIRECT_TO_WEBAPP>) is activated is resolved. This issue occurs when attempting to log in, the application fails to complete the log in process and fails with an internal server error. This is due to a function call in the code that is not correct: Undefined subroutine &NAV::Class::GetClearSSOCookie called at /navtech/NWS/lib_perl/NAV/Class.pm (line 2253).
Resolution Details
We resolved this issue by updating the code to use the correct function call, NAV::Class::GetClearCookie. This fix ensures that users can now successfully log in as a Bidder when SSO is enabled and the new bidder interface is active, removing the internal server error.
D-46866 - SCX - Not Correct Per Diem
We resolved an issue where per diem values were not correctly displaying when loading a CrewPlan file into UAT with version 25.1 installed. This issue is caused by a bug in the code responsible for displaying per diem values. While internally the system stores the correct value, the report generated prints the dollars and cents separately. When the cents value is a single digit (ex. 01 to 09), the leading zero is skipped, resulting in the wrong value displaying.
Example - Loaded CrewPlan file into UAT with 25.1 installed. See image below.
Pairing M0C57/24 has a per diem value of $261.07, as indicated in the file (with columns 601 and 602 representing the cents, “.07” in this case)
Internally, the per diem is correctly stored as 261.07; however when generating the report, the zero is skipped. As shown below, the loaded pairing displays $261.70, which is not the correct value.
Resolution Details
We fixed this issue by updating the bug in the code to ensure that cents always display as two digits. As a result, per diem values now appear correctly in the report, matching the values in the input file.
D-46913 - SCX - Conversion Issue for Trip Start Date of 01JUN UTC to
31MAY Local
We resolved an issue where loading the Absence file for the Jun24 period in PROD does not convert the Carry-In Duty start date from UTC to the correct Local Base Time start date. While the system correctly converted the time from UTC to local, it failed to output the correct local date.
Example
Below is a snippet of the Absence Data file, with the UTC start date and time highlighted. The trips below begin on 5/31/24 and 6/1/24 UTC, respectively. After converting their start times to local time, the start dates become 5/30/24 and 5/31/24.
Using M0404 as an example, the trip starts on 6/1/24 at 01:10 UTC. When converted to local MSP time, the system correctly converts the time to 20:10 Central, however does not output the correct date. The system keeps the start date as 6/1/24, instead of updating it to the correct local date, 5/31/24.
Below is the output from NAVBLUE
Below is the output from NAVBLUE
Resolution Details
This issue is resolved by converting the pairing start date from UTC to local time and using the resulting local start date instead. The system now properly converts and displays the correct local start date.
D-46983 - ASAP - Vacation Opt-In Virtual Credit Counting Multiple Times Towards Running Total
We have identified an issue where “Virtual Credit” is counted multiple times towards the “Running Total” in ASAP reports. This results in wrong calculations, as “Virtual Credit” should only be added once. This occurs because the report generation code adds the “Vacation Opt-In Virtual Credit” to the “Running Total” for the used Bid Group, rather than limiting it to a single instance.
Resolution Details
We modified the Report Generation Code to only add the “Vacation Opt-In Virtual Credit” to the “Running Total” once (in the used bid group). In addition, the “Running Total” line now only displays under the corresponding bid in the used bid group.