# Task #74: E-Hailing App Provider Gazetting

Deployment scripts for 14-day gazette notice period and Bypass button visibility for e-hailing applications.

## Scripts

- **System_Settings_GazetteEhailing.sql** – Inserts into `[System].[Settings]`:
  - `GazettePeriodDaysEhailing` = `14` (notice period for **NPTR** gazettes that contain e-hailing applications 60, 61, 62; **PRE** always uses default 21 days).
  - `AllowBypassGazetteExpiryForEhailing` = `TRUE` or `FALSE` (dev/test: TRUE to show Bypass for e-hailing; production: FALSE or omit row).

## Release steps

1. Run **System_Settings_GazetteEhailing.sql** before deploying the application code (code expects these settings to exist for the 14-day logic; missing `AllowBypassGazetteExpiryForEhailing` is treated as FALSE for production safety).
2. For **production**, set `AllowBypassGazetteExpiryForEhailing` to `FALSE` (or delete/update the row after running the script). For **dev/test**, keep `TRUE` so the Bypass expiry date button is visible for e-hailing applications for training.

## Behaviour

- When a gazette is set as published (status → AwaitingNoticePeriodExpiry), the application sets `GazetteNoticeExpiryDate`: **NPTR** gazettes that contain e-hailing applications use print date + 14 days; **PRE** and all other gazettes use print date + 21 days (from `GazettePeriodDays`).
- The Gazette Console “Bypass expiry date” button is shown for e-hailing applications only when `AllowBypassGazetteExpiryForEhailing` is TRUE and the user has the Bypass securable.