DBC22-6585: enhancement advisory/bulletin publish options for new updates

[bcgov-brwang]

📝 Submitter

🔗 JIRA Ticket

• Ticket Link:
• https://moti-imb.atlassian.net/browse/DBC22-2706
• https://moti-imb.atlassian.net/browse/DBC22-6585
• https://moti-imb.atlassian.net/browse/DBC22-2690
• https://moti-imb.atlassian.net/browse/DBC22-2691

---

✅ Quality Assurance & Requirements

• Requirements Met: I have confirmed that all acceptance criteria from the JIRA ticket are fulfilled.
• Tested desktop in local or dev envs
• Tested mobile in local or dev envs
• Ran unit tests locally
• SonarCloud: I have verified that the SonarCloud analysis is clean/passing for this branch.

⚙️ Configuration & Environment

• New Env Variables: Does this PR require new environment variables? (Yes/No)

  If yes, please list them here and ensure they are added to secret manager, the .env.example. and the Vault by an STA.

🧪 How to Test (if required)

Advisory/Bulletin Update Notification Verification

Scenario 1: Highlighting and Numbered Pill Behavior

• Navigate to dev.drivebc.ca.
• Ensure all advisories and bulletins have been read and that no numbered pill is displayed on the Advisories or Bulletins header.
• Open the CMS admin page:
  https://dev.drivebc.ca/drivebc-cms/cms/advisory/, or
  https://dev.drivebc.ca/drivebc-cms/cms/bulletin/
• Update an advisory or bulletin and select Publish with notifications.
• Verify that a numbered pill appears on the corresponding Advisories or Bulletins header, indicating that new content is available.
• Click the Advisories or Bulletins header.
• Verify that the updated advisory or bulletin is highlighted in the list.
• Navigate to another page within the application.
• Verify that:
  The numbered pill disappears after navigating away from the list page.
  The highlighted state is cleared from the updated advisory or bulletin.
  The last Updated time updated.

Scenario 2: Publish Minor Update

• Update an advisory or bulletin in the CMS admin console.
• Select Publish minor update.
• Verify that:
  No numbered pill appears on the Advisories or Bulletins header.
  No advisory or bulletin row is highlighted in the frontend.
  The last Updated time is not updated.

Scenario 3: Advisory/Bulletin Detail Page Updates

• Navigate to an advisory or bulletin detail page in the frontend.
• In the CMS admin console, update the same advisory or bulletin.
• Select Publish with notifications.
• Verify that:
  The detail page reflects the updated content.
  A new overlay notification appears, informing the user that the advisory or bulletin has been updated.

Scenario 4: Minor Update on Detail Page

• Navigate to an advisory or bulletin detail page.
• Update the same advisory or bulletin in the CMS admin console.
• Select Publish minor update.
• Verify that:
  The detail page reflects the updated content.
  No overlay notification is displayed.

Scenario 5: Advisory Email Notifications

• Ensure a registered user has Advisory Notifications enabled.
• Update an advisory in the CMS admin console.
• Select Publish with notifications.
• Verify that the registered user receives an advisory email notification.
  Repeat the update using Publish minor update.
  Verify that no advisory email notification is sent.
  Verify that no email notification is sent if select Publish minor updates.

---

🔍 Reviewer Checklist

• Reviewed code for logic and cleanliness
• Re-tested desktop/mobile in local or dev envs
• Verified no new console warnings/errors
• Confirmed that any new env variables are understood/documented