1. Home
2.  > 
3. Guide
4.  > 
5. How To
6.  > 
7. Editors
8.  > 
9. Admin
10.  > 
11. Alerts

Alerts

Use Alerts to notify users across the site of urgent information. 

Update Sitewide Alert

1. Edit Alert File: http://a.cms.omniupdate.com/10/#oucampus/simons-rock/www/preview/_resources/includes/alert.pcf 
2. Check out file by toggling light bulb on
3. Set Properties/Parameters
4. Save
5. Edit Tab, Info Button
6. Edit Content and Save
   1. If editing Warning, may need to select the expand button at bottom right of WYSIWYG
7. Publish (describe changes)
8. Review on devices and browsers, adjust as necessary
9. When ready to turn off, check out
10. Set Properties/Parameters
11. Publish (describe changes)

• Publish to Development Site

Update Alert Detail Page

• Edit Alert Detail Page: http://a.cms.omniupdate.com/10/#oucampus/simons-rock/www/preview/alerts/index.pcf
• During an emergency, the detailed page can be updated with an ongoing time stamp post
• After an emergency, the detailed page can be archived by changing the URL and creating a new index page

• How to A Edit Page

SPECIFICATIONS

The alert is a pcf file. It is published as an include file to _resources/includes/alert.inc. This include file is included on almost all pages of the site at all times. The pcf file is not included on pages with minimal navigation - and therefore an alert won't display.  

The only time that the alert is visible on a live page is when page parameter for the alert.pcf file is toggled to display the alert. In addition to the show/hide toggle there is also a toggle to choose the level of alert, info, warning or danger. Each of these types has its own editable region where you can build out the alert message using the WYSIWYG.

Use Style Dropdown a - alert link for the link. 

Add the » with the special character in the WYSIWYG

Governance

• At the onset of an emergency, Alert Editors and Security should get in touch and communicate who will update the website.
• The more urgent an issue is, the more urgent it is that Alert Editors act quickly and post. 
• As time permits, follow the order of succession. For example, if Alert Editor #1 is unavailable, #2 should take the lead.
• As time permits, work with Security and Marketing and Communications to create a plan.
• If information evolves during the course of an emergency, keep a running log on the 'more information' page. 
• At the conclusion of an emergency, work with Security and Marketing and Communications to determine how, and if, the emergency alert should archived.
• Alert Editors will practice posting alerts monthly and on a range of devices and locations.