I. Login Screen

All the Pre-defined users (users already configured by Admin) can login into the application.

User has to enter Mobile number and Password and tap on to login

II. Home Page

User successfully logs into the application, the Home Page consists of: A Toggle button, Projects list and a button to Request Switch users.

The details and screen are provided below.

Active/Inactive Toggle Button

2. The Toggle button is used to make the user Active or Inactive to receive the notifications. Upon making the user is inactive, user will not receive any incident notifications / switch requests which are assigned to him.

Project List

3. In the home page, list of projects will be displayed which are assigned to the user. The list comprises of 3 columns: Project Name, Level, Snooze Time and an Enabled/Disabled Switch user button. Against every Project Name there’s either a Green or Red bulb indicating On-duty and Off-duty projects of the user respectively.
  1. Project name: It is the name of the Project pre-configured by admin. User tap on the project name the users of all levels assigned to that particular project can be seen in pop-up.

  2. Level: It is the level of the current login user. Users are categorized into 4 levels, which implies, that if a level 1 user declines an incident, the incident gets escalated to level 2 . If the level 2 users declines the incident it will be escalated to level 3. But, the level 4 user is an observer and will not be assigned any incident. Also, only the level 4 user can access the Log tab (Refer point → V. Log).
  3. Snooze time: It the number of minutes the user doesn’t want to get disturbed, after which the application again notifies the user regarding the assigned incident. The snooze time is configured by the admin
  4. Switch User button: Against every On/Off duty project (Project against which is red/green bulb exists) there exists a Switch user button, taping it; user can request another user to work on the project.

Note: The switch user request button is enabled only for projects where the rotation type of users is daily, weekly and Monthly. For rotation type: All and nearest, switch user request button will remain disabled.


Switch User button

4. When the user tap the Switch user button, the user is prompted to enter from and to date time ranges. And finally when clicked on Search button, the users of the same level (i.e. for example: If the mobile user is of level 1, then the users visible in this step are all the level 1 users) available in the selected date time range gets populated. Below screenshot explains.


  1. The Rotation Type mentioned at the Top Right explains that the rotation type of the users allocated to the particular Project.

    Rotation type is the following types:

    • Daily
    • Weekly
    • Monthly



  2. User tap on a user from the populated users list, a calendar page pops-up prompting the user to select a date. Once the desired date is selected and tapped Ok, another page pops-up prompting the user to select time.



    Hours are selected and then Minutes. And finally AM/PM. Upon taping Ok, a pop-up message will ask for confirmation.
    Once button is tapped, switch request is sent to the desired user. Below Screenshot explains the switch request sent to Bill Gifford.




  3. Once the Switch request is sent, the recipient (in our example: Bill Gifford) will receive a push notification as explained in the below screenshot.

    Once the recipient tap the button, it implies that the recipient has accepted the incident. After accept the switch notification, it will be update in the notification tab.



Change Password

5. User has successfully logged into the application, the Password of the application has to be changed to the user desired password. User has to tap the Menu button available at top right corner of the home page. The screenshot below explains.




Once tapped on menu button, 3 options are available for the user: Change Password, Change Theme and Log out.




User tap on the Change password option, a pop-up can be seen prompting the user to enter the Old and New passwords and then to re-enter new password. Finally when tapped on button, the new password gets updated.




Theme Change

User tap on the Menu button then select the Change theme option, and then a list of themes can be seen, prompting the use to select a theme. Once a theme is selected and tap on SAVE, then the theme of the application changes as desired.


III. History

Incidents List

6. The history tab contains the list of all the incidents handled by the logged in User, previously. The list includes Declined, In-progress and Snoozed incidents. Screenshot below explains. Various symbols against the incidents in the list are provided below:
  1. Implies → Declined Incidents.

  2. Implies → Snoozed Incidents.

  3. Implies → In-progress Incidents.

In Progress Check box: When the "In Progress" check box is checked, then all the past incidents pertaining to the particular user gets filtered and only the In-progress incidents are seen.

When the "In Progress" check box is unchecked, then all the past incidents pertaining to the particular user are seen.




Resolving an Incident in History

7. User can update an In Progress incident as Resolved in the History tab by just tapping the In-progress incident, mention the comment and tap RESOLVE.

Note: Only In progress incidents can be resolved in the History tab.



IV. Notifications

The Notifications tab contains a new switch request or Incident on the top and all the Accepted and Declined Switch requests at the bottom.

Note: All incidents → accepted, declined or snoozed move to the History tab.

all switch requests either accepted or declined remain in the notifications tab.

8. When a New Incident is assigned to a user. A New incident is created at the top in the Notifications tab.
  1. When an incident is accepted by tapping the button, the incident moves to the History tab and in the Incidents list; it turns into In-progress mode i.e.

  2. When an incident is declined by tapping the button, the incident moves to the History tab and gets added to the Incidents list as a Declined incident

  3. When an incident is snoozed by tapping the button, the incident moves to the History tab and gets added to the Incidents list as a snoozed incident
9. And similarly, any New Switch request from another user (For example: Bill Gifford) gets populated in the notifications tab, below is the screenshot explaining both the cases
i.e. a new incident assignment and a new switch request.
  • All received notifications are indicated with a down arrow

  • All sent notifications are indicated with a up arrow



  1. User accepts the received switch request by tapping the button, the notification moves to the bottom with a symbol as: .


    Similarly if the user Declines the switch notification the notification moves to bottom with a symbol as:




  2. In another case: if a user sends Switch request to another user and when the recipient accepts the request, the notification moves to bottom with a symbol as: .


    If a user sends Switch request to another user and when the recipient Declines the request, the notification moves to bottom with a symbol as:



10. Based on number of Snoozes tapped by the User, the 'number of Remainders' is displayed in Brackets beside project name in notifications.


11. Note: When the user has logged in but is not using the App, then any notification received, will be visible similar to any other notification on the mobile phone and the user tap on the notification, the MyAlertX app opens and lands on the Notifications tab.

V. Log

Note : In Log tab only incidents can be seen. Only the level 4 users (Observers) can view the log.

12. The log screen contains the list of all the Open, In-progress and resolved incidents. For example, below screenshot explains.
  1. Indicates that the Incident is in open state, i.e. no user has accepted the incident as of now.

  2. Indicates that the incident is in In-progress state, i.e. a user has accepted the incident and is working on it.

  3. Indicates that the incident has been resolved.


13. For example: If 4 users have been notified regarding an incident and if 3 users have not responded for 2 minutes or have declined the incident then a mark is denoted against such user names.

And when 1 user accepts the incident, then mark is denoted against such user name.



14. A filter is provided for the user to filter all the incidents in the Log tab on specific criteria. When user tap the Filter button , then a pop-up can be seen where user can either search using an Incident ID or a combination of Project name, Engineer and Status of the incident.
  • Project name drop down contains the complete list of Project names.
  • Engineer dropdown contains the complete list of Engineers
  • Status drop down contains all possible statuses of an incident such as: open, In-progress and Resolved.

When an incident ID is entered and tapped on Apply, only the information pertaining to that particular incident gets populated. And when a Project name, Engineer and status are selected and tapped on apply button, then all relevant incidents get populated on the Log tab.



Legend

  1. → Declined Incidents

  2. → Snoozed Incidents.

  3. → In-progress Incidents.

  4. → Open state.

  5. → Resolved state.

  6. → Received a Switch Request

  7. → Sent a Switch Request

  8. → Action to Decline.

  9. → Action to Snooze.

  10. → Action to Accept.