NIMBUS REGRESSION

GIVEN a call taker is logged onWHEN a CPE signal is sent to a position that does NOT have the Call Taker Form open, and the contact number does not belong to an open incidentTHEN the signals counter will be incremented (see image Signal A)and the signal will appear in Settings - Signals (see image Signal B)

GIVEN that I have Administration permission that I navigate to .../System/SignalsWHEN navigate to .../System/Signal and view the signals on the gridTHEN I should see the timestamp (date & time) the signal came in under Created Time

GIVEN an incident is openWHEN the incident is closedTHEN the user will be presented with an option to CLEAR assigned units or to CLOSE the incident

GIVEN an incident is closedWHEN re-activating the incidentTHEN the incident will be re-opened

GIVEN an incident is open and Vehicle x is submitting location informationWHEN assigning Vehicle X to the incidentTHEN the approximate ETA of that vehicle must be displayed (see image ETA)

GIVEN Dispatcher is logged inWHEN Incident details are saved, and vehicle and responders are assignedTHEN Life maps is showing the responder pin

GIVEN Dispatcher is logged in and on Live Activity/ Live Maps pageWHEN Legend icon is clicked, and Vehicles checkbox is checkedTHEN Life maps is showing vehicles that are currently responding.

GIVEN Dispatcher is logged in and on Live Activity/ Live Maps pageWHEN Legend icon is clicked, and Traffic checkbox is checkedTHEN Life maps is showing the current traffic

Support Subscriber Groups Notifications by Agency Response Area (Jurisdiction) Nimbus now supports the ability to set notifications to occur only when a certain incident type occurs within an Agency’s jurisdictional boundary (response area). This important feature helps administrators to define recipient notifications to subscribers, only when an event occurs in their area/region. This functionality reduces confusing notifications across the platform and allows for alerting for the user’s agency operations and command. Administrators can define Subscriber Groups with or without the Agency filter now to allow increased flexibility. Changes in incident location or event Call-Type will also support triggering an SMS notification, based upon rules set above for ease of automation. 

Support Subscriber Groups Notifications accounting for internal, external users and permission groups Subscriber Notifications via SMS have been extended to allow easier selection of internal Nimbus Users and continued support of manual subscribers and external users. This provides an easier means of managing internal recipients and eliminates maintaining user SMS profiles in two different Admin screens 

Identify an Asset with there Workforce Status set as Available (we used LBE1) - do not set it as AvailableLoad the Asset Grid and search for the Asset using the search boxObserve the Asset in the grid, with the Workforce Status set as AvailableSelect Filter Available AssetsObserve that the asset no longer show on the gridNavigate to the Workforce Management Page (.../Workforce/LiveActivity) and locate your assetChange Workforce Status (does not matter to what) and wait for onscreen confirmationVerify on Asset grid that the new Workforce status has been appliedOn the Workforce Management Page, change the status for your asset back to AvailableOn The Asset Grid, apply the Filter Available Assets filter againObserve that your asset remains on the grid

Nimbus: Support Custom (Non-Provider/Facility) Destination for Units Nimbus CAD now supports the ability to indicate a unit’s Secondary Location as an ad-hoc verified address, rather than the previous limit to pre-defined Providers and Facilities. This feature increases the flexibility of Nimbus CAD in providing location details when units are still maintaining assignment to the original CAD Event location but may need to temporarily update their location to accommodate further investigation or a transport to a non-provider location. This increases situational awareness for dispatchers and responder safety in the field. 

Cluster numbers will increase with new closed incidents the next day.when testing, take a screen shot at the time of regression testing and then 24 hours later check clusters map again to ensure increase in numbers is present