Issues resolved in FliteBrief 1.25

The following issues were resolved in version 1.25 of FliteBrief.

• EFFs are now uploaded to the EFF FTP Processor before the SQS message is sent.
• When editing information in the ETOPS ERA Information table on the ETOPS Release sheet, the values for Earliest and Latest time fields are now correctly populated.
• The following issues were resolved for users of the Aviator app:
  • When a tail swap OFP is released for a flight, a single update package is correctly released instead of multiple update packages.
  • The autoreleased OFP no longer removes previously assigned crew during processing.
• PDFs are now generated when a sector is released for an ETOPS flight.
• The buffer calculation is enhanced to make sure that airfields of interest with a significant margin of error are no longer excluded for flights that are closer to the north and south poles.
• When the flight plan in the EFF is updated, the AirportData.xml file no longer retains the previous OFP number. This enhancement makes sure that the updated runway is displayed.
• When adding valid ICAO values to an existing email rule in the NOTAM module, an error message for invalid ICAOs is no longer displayed.
• OFPs are no longer rejected when the value of ruleTime is set to 0.
• Push notifications are now correctly displayed.
• The EFF is now correctly generated when crew members are assigned the title OTHER.
• The text on the New OFP page is now enhanced to improve the user experience.
• FliteBrief now correctly processes a flight when the value of Average Wind Component is set to zero.
• FliteBrief now correctly populates the Planned By field in the PDF Briefing Pack.
• The pps-flights-data-consumer is now stored in the correct bucket in the default file.
• Route plots are now correctly displayed for long-haul flights.