Express List "All Time" filter is not displaying all alerts listed in em_alertUser Carol Danvers was reviewing the Service Operations Workspace (SOW) Express List and noted that the "All Time" filter did not include all of the alerts listed in the em_alert list-view. After reaching out to ServiceNow Development teams internally, it was found that the "All Time" filter is actually filtering against the "Initial event generation time", and for performance reasons, only includes the past three months (current GlideDateTime [GDT] - 3 months time = the All Time filter range). As Carol had a use case for needing to include older alerts that transitioned from, say, a State of Warning to Critical (but still had an "Initial event generation time of 3+ months or older), Support provided two example ideas that Carol and her team could consider in their internal conversation of custom solutions: Creating a customization that generates a new em_alert record whenever an alert moves from Warning to Critical, thus "resetting" the "Initial event generation time" from some older date beyond the range of the "All Time" filter to the current GDT, thus including it in the Express List list-view in SOW.Create a custom field (which can be hidden via some UI Policy/Client Script), "u_initial_remote_time", with a label of "Original initial event generation time". For this suggestion, on the creation of an alert, the "Initial event generation time" would be stored in both the "initial_remote_time" (Initial event generation time) and "u_initial_remote_time" (Original initial event generation time [this one is for reporting against]). Then, as needed, and in such cases as when an alert transitions from Warning to Critical, the Business Rule would update the "Initial event generation time" to the current GDT. At this point, the alert would now show in the Express List view in SOW as it would fall within the 3 month range of the "All Time" filter.