Epic: Drip Irrigation Management System for Mobile

Table of Contents
1. UI Story (AT-16) ..................................................................................................................................... 5
2. Splash screen (AT-12)............................................................................................................................ 5
3. Language Setting (AT-14) ...................................................................................................................... 5
4. Sign In page (AT-13) .............................................................................................................................. 6
Update on 8-Oct-16 (AT-35) ..................................................................................................................... 7
5. Create Account (AT-2) ........................................................................................................................... 7
Update on 8-Oct-16 (AT-36) ................................................................................................................... 11
Update on 21-Dec-16 (AT-220) ............................................................................................................... 11
Update on 30-Dec-16 (AT-259) ............................................................................................................... 11
6. Edit Profile (AT-17) .............................................................................................................................. 12
Update on 31-Oct-16 (AT-95) ................................................................................................................. 13
Update on 28-Nov-16 (AT-168)............................................................................................................... 14
Update on 23-Jan-17 (AT-343) ................................................................................................................ 14
7. Login and Logout (AT-3) ...................................................................................................................... 14
Update on 8-Oct-16 (AT-37) ................................................................................................................... 15
8. Home Page – Admin (AT-101) ............................................................................................................. 15
9. Home Page - Dealer (AT-18)................................................................................................................ 16
Update on 22-Oct-16 (AT-85) ..................................................................................................................... 20
Update on 27-Jan-17 (AT-346) .................................................................................................................... 22
10. Common Updates to Mobile App on 16-Dec-16 (AT-215) .............................................................. 22
Update on 16-Dec-16 & 21-Dec-16 (AT-218) .............................................................................................. 23
Update on 27-Dec-16 (AT-249) ................................................................................................................... 24
11. Remove Device Delete Functionality for Dealer (AT-132) .............................................................. 24
12. Home Page - Customer (AT-19) ...................................................................................................... 25
Update on 21-Oct-16 (AT-83) ..................................................................................................................... 26
19. Navigation Menu (AT-20) ................................................................................................................ 28
Update on 20-Jan-17 (AT-211) ................................................................................................................ 28
Update on 06-Feb-17 (AT-358) ............................................................................................................... 29
20. Forgot Password (AT-15)................................................................................................................. 30
Update on 25-Oct-16 (AT-89) ..................................................................................................................... 31
21. Add Controller – Customer (AT-4) .................................................................................................. 32
Update on 8-Oct-16 (AT-39) ....................................................................................................................... 34
Update on 1-Nov-16 (AT-9) ......................................................................................................................... 34
22. View Controller – Customer (AT-60) ............................................................................................... 35
Update as on 28-Nov-16 (AT-142) .............................................................................................................. 40
Update as on 8-Dec-16 (AT-179)................................................................................................................. 42
Update as on 13-Dec-16 (AT-195)............................................................................................................... 42
Update as on 14-Dec-16 (AT-214)............................................................................................................... 43
Update as on 27-Dec-16 (AT-250)............................................................................................................... 43
Update as on 14-Feb-17 (AT-384) ............................................................................................................... 44
23. Common ID Settings (AT-182)......................................................................................................... 44
24. View New Nodes (AT-152) .............................................................................................................. 47
25. Add Controller or Node – Dealer (AT-61) ....................................................................................... 49
Update on 25-Oct-16 (AT-90) ..................................................................................................................... 50
26. View Controller or Nodes - Dealer (AT-84) ..................................................................................... 50
27. Add Nodes – Customer (AT-5) ........................................................................................................ 52
Update on 15-Dec-16 (AT-217) ................................................................................................................... 53
28. Edit/Delete Node – Customer (AT-86) ............................................................................................ 53
Update on 13-Dec-16 (AT-196) ................................................................................................................... 55
Can be reused (AT-271) .............................................................................................................................. 55
29. Edit Mapped Nodes – Customer (AT-123) ...................................................................................... 55
Update on 12-Dec-16 (AT-184) ................................................................................................................... 56
Update on 3-Jan-17 (AT-272) ...................................................................................................................... 56
30. Create Service Request (AT-134) .................................................................................................... 56
31. View Service Request (AT-204) ....................................................................................................... 57
Update on 24-Jan-17 (AT-345) .................................................................................................................... 59
Update on 01-Feb-17 (AT-353) ................................................................................................................... 59
Update on 02-Feb-17 (AT-356) for view and update SR pages................................................................... 59
32. Update Service Request Status (AT-205) ........................................................................................ 59
Update on 24-Jan-17 (AT-344) .................................................................................................................... 60
33. Add Zone (AT-96) ............................................................................................................................ 61
Update on 12-Dec-16 (AT-183) ................................................................................................................... 63
34. Edit / Delete Zone (AT-133) ............................................................................................................ 63
Update on 13-Dec-16 (AT-203) ................................................................................................................... 66
35. View Sub-users (AT-6) ..................................................................................................................... 66
36. Add/Edit/Delete Sub-users (AT-7) .................................................................................................. 67
Update on 25-Nov-16 (AT-169)................................................................................................................... 70
Update on 18-Feb-16 (AT-398) ................................................................................................................... 71
37. View Groups (AT-97) ....................................................................................................................... 71
38. Add Group (AT-98) .......................................................................................................................... 72
39. Edit/Delete Group (AT-99) .............................................................................................................. 73
40. Grouping of Controllers (AT-100).................................................................................................... 74
Update on 28-Nov-16 (AT-167)................................................................................................................... 75
41. SMS Communication – Create and Manage Primary User Contacts (AT-11) ................................. 76
Update on 17-Jan-17 (AT-315) .................................................................................................................... 77
42. SMS Communication – Create and Manage Sub-users (AT-251).................................................... 77
Update on 18-Feb-17 (AT-397) ................................................................................................................... 79
43. SMS Communication – Map Nodes (AT-252) ................................................................................. 80
Update on 13-Jan-17 (AT-310) .................................................................................................................... 80
44. SMS Communication – Controller Details (AT-253) ........................................................................ 81
45. SMS Communication – Operating Controller and Quick Menu (AT-254) ....................................... 82
46. SMS Communication – Create and Manage Zone (AT-255) ........................................................... 82
47. SMS Communication – Common ID Settings (AT-256) ................................................................... 84
Update on 19-Jan-17 (AT-317) .................................................................................................................... 85
48. SMS Communication – Manage Service (AT-257) .......................................................................... 86
49. Data Synchronization (AT-10) ......................................................................................................... 86
Update on 23-Jan-17 (AT-342) .................................................................................................................... 88
50. Settings Page – UI (AT-59)............................................................................................................... 88
Update on 27-Dec-16 (AT-248) ................................................................................................................... 90
Update on 12-Jan-17 (AT-309) .................................................................................................................... 90
51. Settings Page – Validation and Communication with Controller (AT-137) ..................................... 91
Update on 15-Dec-16 & 21-Dec-16 (AT-216) .............................................................................................. 93
Update on 22-Dec-16 (AT-226) ................................................................................................................... 94
Update on 21-Jan-17 (AT-322) .................................................................................................................... 95
52. Settings Page –Menu Configuration (AT-138) ................................................................................ 95
Update on 22-Dec-16 (AT-222) ................................................................................................................... 96
Update on 3-Jan-17 (AT-270) ...................................................................................................................... 97
53. Light Settings – Popup Info Messages (AT-181).............................................................................. 97
54. Agri Irrigation - Common Calibration Settings (AT-260) ................................................................. 97
55. Standalone Settings (AT-261).......................................................................................................... 98
56. View Settings (AT-323) .................................................................................................................... 99
Update on 01-Feb-17 (AT-354) ................................................................................................................. 100
57. QR Code Size Change (AT-210) ..................................................................................................... 100
58. CCTV (AT-221) ............................................................................................................................... 100
59. Call (AT-380) .................................................................................................................................. 100
60. Live Update (AT-382) .................................................................................................................... 101
61. Live Update 2 (AT-440) ................................................................................................................. 101
62. Toggle Pump Status Automatically (AT-441) ................................................................................ 104
63. Customer Service - Customer Chat (AT-227) ................................................................................ 104
Update on 6-Jan-17 (AT-271) .................................................................................................................... 106
Update on 12-Jan-17 (AT-308) .................................................................................................................. 107
64. Customer Service - Dealer Chat (AT-228) ..................................................................................... 107
65. Customer Service - Admin Chat (AT-229) ..................................................................................... 109
66. WI-FI Configuration (AT-347) ........................................................................................................ 111
Update on 7-Feb-17 (AT-376) ................................................................................................................... 113
Update on 13-Feb-17 (AT-383) ................................................................................................................. 113
Update on 14-Feb-17 (AT-391) ................................................................................................................. 113
Update on 20-Feb-17 (AT-400) ................................................................................................................. 114
67. WI-FI - App Communication with Controller (AT-379).................................................................. 114
68. Message Code Extraction (AT-381) ............................................................................................... 115
69. Controller Fault Messages (AT-163).............................................................................................. 116
70. Reports Page (AT-377) .................................................................................................................. 117
71. Change Request – SMS related changes (AT-427) ........................................................................ 118
72. Change Request – SMS related changes 1 (AT-430) ..................................................................... 120
73. Change Request – SMS related changes 2 (AT-442) ..................................................................... 121
74. Settings Module - Success Messages (AT-431) ............................................................................. 122
75. Settings Page - UI Update 3 (AT-439)............................................................................................ 123
76. Configure Notification (AT-473) .................................................................................................... 123
77. Change request and Issues reported on 11 July 17 (AT-479) ....................................................... 124

1. UI Story (AT-16)
Summary: This topic would explain about the color, theme and styles to be used in the Agritel app

Description:

 The color to be used in Agritel app is blue and green

 The app theme is drip irrigation

2. Splash screen (AT-12)

Summary: As an Agritel user, I would like to see splash screen in 2 seconds after I tap the Agritel app
icon so that I would know the app is in process of loading.

Description:

 The splash screen shall display an image in background and Niagara logo in foreground
 The logo shall be in portrait mode and big enough to quickly read the content

 The position of logo in splash screen and sign in screen should be same so that there is a smooth
transition between the two screens
 If the device do not have saved app password, the app should take the user to sign in page

 If the device have saved app password, the app should take the user to home page
Procedure:

1. User downloads and installs Agritel app.

2. User taps the app icon, splash screen gets displayed in 2 seconds

3. Language Setting (AT-14)

Summary: As an Agritel user, I would like to select language so that I can read and type in the
selected language within the app

Description:
 The language setting page shall have a list view selection with below options
o Engligh
o Tamil
o Hindi
o Telugu
o Kannada
o Malayalam
 The language names should be displayed in respective scripts
Procedure:

1. User downloads and installs Agritel app.

2. User taps the app icon, splash screen gets displayed followed by language setting page
3. User taps on the language in which he/she wants to read and type within the app
4. After user selects the language, the app ties the language to the device
5. All labels within the app shall be displayed in the selected language
6. Display of content and user input should be in English
7. The language setting would be effective until user changes the settings inside the app general
settings screen or user uninstalls the app

4. Sign In page (AT-13)

Summary: As an Agritel user, I want to navigate to sign in page so that I can login or create my
account in the app.

Description:

 Sign In page should have a background image and below fields and CREATE ACCOUNT and SIGN
IN buttons:
o Mobile number
o Password
 “Forgot password?” hyperlink shall be provided behind the password field

Procedure:

1. User downloads and installs Agritel app.

2. User taps the app icon, splash screen gets displayed followed by language setting page
3. User selects the required language
4. The app takes the user to sign in page
5. When user inputs mobile number and password and taps SIGN IN button, the app shall check
whether the mobile number and password combination exists in the database
6. Upon successful validation, the app takes the user to home page with the list of units that
belongs to the user
7. If the mobile number or password does not match with the app profiles, the app shall display
below error message:
“The mobile number or password you have entered is invalid. Please try again.” Error code: E041
8. When the user taps on CREATE ACCOUNT button, the app shall take the user to create account
page
9. When user taps the “Forgot Password?” hyperlink, user shall be taken to reset password page
10. A pin wheel shall be rotating with below message while the forgot password page is being
loaded:
“Forgot password page is being loaded. Please wait…"

Update on 8-Oct-16 (AT-35)

Description:
 Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared

Procedure:

Point 10 should be as below:

A pin wheel shall be rotating with below message while the reset password page is being
loaded:
“Reset password page is being loaded. Please wait…" Information message code: I019

5. Create Account (AT-2)

Subject: As an Agritel user, I should be able to register in Agritel app using valid data so as to get
access to the app.

Description:

 Please refer Field Level Specification

 User shall install and launch the Agritel app from app store. User shall register his/her profile in
create account page to use the app

 User has to input genuine information and complete the account creation successfully in order
to get access to the system. User can register to the app only if he/she is connected to the
database server

 Agritel allows three types of users Admin, Dealer and Customer. A user can register as admin
user only after their mobile number is validated against a specific list of authorized numbers in
database

 Mobile number shall have two fields in the same line, one for country and the other for mobile
number
  The country field should be dropdown list taken from database. The default country should be
selected based on the current location. Ex: If a user creating account from India, the app should
select “India” as default country. The same logic shall be applied wherever for all country fields
in the screen

 Upon selecting a country from dropdown list, corresponding country code would be retrieved
from database and stored with the user profile while saving the profile
 All values required for mobile number validation (Ex: minimum or maximum length) should be
stored in the database and retrieved upon country selection
 Mobile number is the unique key, user should enter a valid mobile number to create account

 Mobile number, password, user name and user type are mandatory fields for all users.
Additionally, Address1, Country, State, City or Town or Village, Postal code, at least one
Alternate phone number and email are mandatory for dealer
 A dealer can be customer also. In this case, dealer would have additional access to customer
functionalities
 User type shall contain static values Admin, Dealer and Customer. User is allowed to choose any
one value at a time
 Customer requested not to include email and mobile number verification to make it simple for
their consumers (users)
 The app shall allow user to enter additional phone number(s). The additional phone numbers
can be mobile or home phone number
 The app shall display one set of fields (country and phone number fields) for the first time and a
plus icon for adding more phone numbers. When user taps on the plus icon, an additional set of
fields shall be displayed
 Maximum five alternate phone numbers shall be added dynamically

Procedure:

1. User downloads and installs Agritel app.

2. User taps the app icon, splash screen gets displayed followed by language setting page
3. Upon selecting the language, the app takes the user to sign in page with below fields and
CREATE ACCOUNT and SIN IN buttons:
 Mobile Number
 Password
4. User taps on CREATE ACCOUNT button
5. Create account page displays with below fields and SUBMIT and CANCEL buttons:
 Mobile Number
 Password
  User Name
 User type
 Address1
 Address2
 Town
 Village
 Country
 State
 City
 Postal code
 Alternate Phone Number
 Email address
6. User inputs data for necessary fields
7. Upon taping SUBMIT button, the app performs client side validation as below:
 Checks whether mandatory fields are filled. If not, the app prompts to input mandatory
fields
 The app should validate (using API if required) whether the number is a mobile number and
it is a valid mobile number. It should also check whether the mobile number is being used by
any unit or controller
 Password shall be minimum of 6 and maximum of 10 alphanumeric characters
 User name shall be minimum of 4 and maximum of 30 alphabets
 The app shall allow user to select any one user type. The default display value shall be
“Select one”
 The two address fields shall have alphanumeric and maximum of 30 characters.
 State and city shall be populated from respective lists stored in database. User shall select
from the lists
 Country shall be auto populated based on state selection. It shall not be editable field
 Town and village are free text fields which shall allow alphanumeric and maximum of 20
characters
 Postal code shall be validated based on the selected country
 The app shall validate whether alternate phone number(s) is valid (using API if required)
 Email ID is an optional field which shall allow alphanumeric and maximum of 50 characters.
If user inputs email ID, the app shall validate whether it is valid ID. The email ID should have
local-part "@" domain
o Local-part is a locally interpreted string which can have dot-atom or quoted-string
or obs-local-part
o Domain is an Internet domain which can have dot-atom or domain-literal or obs-
domain
o A dot-atom is a dot delimited series of atoms
o An atom is a string of basic characters in below format
[CFWS] 1*atext [CFWS]
 o CFWS (Comment Folding White Space) shall be in below format
( 1*( [ FWS ] comment ) [ FWS ] ) / FWS
o atext can be any of the following
! $ & * - = \^ ` | ~ # % ‘ + / ? _ { }
o Quoted-string is a string of characters that include characters other than those
allowed in atoms may be represented in a quoted string format, where the
characters are surrounded by quote characters
o obs-local-part (obsolete local-part) shall be word *("." word) where word is an atom
or quoted-string
o domain-literal is a literal internet address of the particular host
o obs-domain (obsolete domain) shall be atom *("." atom)
o Comments are allowed in both local-part and domain name with parentheses at
either end
Example:
john.smith@(comment)example.com
john.smith@example.com(comment)

8. Create account screen shall clear the UI data when user taps CANCEL button
9. Once client side validation is completed, the app performs below validation:
 The app shall check for duplicate mobile number and throws error if the mobile number
already registered
10. After successful validation, the user account gets created (in both local DB and server) and
success message page shall be shown with the message “Welcome <Name>! Your account
created successfully!” and OK button
11. Once user taps on OK button Agritel home page would be displayed
12. If account creation failed, failure message page shall be shown with a message and OK and
CANCEL buttons
13. If user taps OK button, Create account page would be shown
14. If user taps CANCEL button, the app takes the user to sign-in page

List of possible error messages:

1. Mandatory fields empty: “Please enter <field name>” Warning Message code: W023
2. Invalid mobile number: “Please enter a valid Mobile Number” Warning Message code: W024
3. Invalid password: “The password must have at least 6 characters and not exceeding 10
characters.” Warning Message code: W025
4. User Name greater than 30 characters: “The name should not exceed 30 characters” Warning
Message code: W026
5. User did not select any user type and the field retains the default value ‘Select one’: “Please
select a user type” Warning Message code: W027
6. Invalid email address: “Please enter a valid email address Ex: name1@sample.com” Warning
Message code: W028
7. Mobile number already registered with the app: “The mobile number already registered! Please
use the credentials to login.” Error code: E042
8. No response from server for specific time: “Server timeout! Please try again after sometime.”
Error code: E001
9. Alternate phone number Invalid: “Please enter a valid Phone Number”
10. User selects the type as Admin but the primary mobile number does not exists in the authorized
mobile number list: “Your mobile number is not authorized for Admin access” Error code: E043

Update on 8-Oct-16 (AT-36)

Description:
 Email ID field shall allow alphanumeric and maximum size is 100
Last 3 points of description has been updated and 2 new points added:
 The app shall allow user to enter additional phone number(s). The additional phone numbers
can be India mobile number only
 The app shall display one field for the first time and a plus icon for adding more phone numbers.
When user taps on the plus icon, an additional field shall be displayed
 Maximum five alternate phone numbers shall be added in total. If any dynamically created field
is not required, the app shall allow user to delete the additional field(s)

 Display below text common for additional phone number fields:

“Please enter India phone numbers (mobile or landline). Landline should be entered with area
code.”

 Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared
List of possible error messages:

11. When user is not connected to server and tries to create account: “Internet connection appears
to be offline”

Update on 21-Dec-16 (AT-220)

1. Do not display non-mandatory fields for customer user type. This change applies for edit profile
(AT-17) also

Update on 30-Dec-16 (AT-259)

1. Do not display non-mandatory fields for admin user type. This change applies for edit profile
(AT-17) also
6. Edit Profile (AT-17)
Summary: As an Agritel user, I would like to edit my profile so that my profile data can be updated

Description:

 The edit page header shall have below items:

o Navigation icon on top right corner
o Agritel logo next to the navigation icon
 The edit page content shall render profile view with EDIT, SUBMIT and CANCEL buttons

 The fields which are not editable shall be differentiated from editable fields
 User can edit profile only if he/she is connected to the database server

 Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared
Procedure:

1. Please refer Field Level Specification

2. User downloads and installs Agritel app
3. User taps the app icon, splash screen gets displayed followed by language setting page
4. Upon selecting the language, the app shall take the user to sign in page
5. User inputs the user ID and password and taps SIGN IN button
6. The app shall take the user to home page
7. User taps on the navigation icon, he/she should be able to see the menu as in navigation
icon story
8. User selects Edit Profile menu option
9. The apps takes the user to Edit Profile page and render the profile view
10. Upon tapping EDIT button, below editable fields shall be changed to edit mode:
 Mobile Number
 User Name
 User type
 Address1
 Address2
 Town
 Village
 Country
 State
 City
 Postal code
 Alternate Phone Number
 Email address
 11. After user changes the required fields, he/she clicks on SUBMIT button the app performs
below validates updates the profile in database:
 Any user type can be changed to other user types with below constraints:
o When a dealer or customer user type is changed to admin, the app shall validate
whether the registered mobile number is one among the specific list of authorized
numbers in database. If not, the app shall throw below error message:
“You are not allowed to have Admin access.”
o When a dealer user type is changed to customer, the app shall validate whether the
dealer has any unsold units in his account. If yes, the app shall throw below error
message:
“You have <n> unit(s) associated to your account, so you are not allowed to have
customer only access.”
 When a customer user type is changed to dealer or admin, below fields shall be made as
mandatory:
o Mobile Number
o User Name
o Address1
o City or Town or Village
o Country
o State
o Postal code
o at least one Alternate phone number
o email
 Please refer create account story AT-2 for Mobile Number, User Name, User type,
Address1, Address2, City, Town, Village, Country, State, Postal code, Alternate Phone
Number and Email address field validation and other possible error messages
12. Upon successful validation, the user details should be updated in both local database and
server in parallel
13. In case of errors, after user taps OK in error window, the app shall reset the screen and
retains the same page
14. When user taps CANCEL button all fields in the screen should be reset and the same page
shall be retained
15. When user is not connected to server and tries to edit profile, below error message shall be
displayed
“Internet connection appears to be offline”

Update on 31-Oct-16 (AT-95)

Description:
 Edit icon not required. When user taps on Edit Profile from the menu, this page should be
directly shown in edit mode
 If the user updates his/her mobile number in Edit Profile, it should get updated in sub-user
module

Update on 28-Nov-16 (AT-168)

1. The app shall allow below user type changes only:

 Dealer to Customer

 Customer to Dealer
2. The app should not allow below user type changes:

 Dealer to Admin
 Customer to Admin

 Admin to Customer
 Admin to Dealer
3. If user tries to change the type which is not allowed, the app shall display below message:
Message: Warning message code- W043

Update on 23-Jan-17 (AT-343)

1. The app shall not allow the user to change the user type from dealer to customer if below
conditions matches

 The dealer has one or more devices (controllers or nodes) to be sold

 If already sold devices (controllers or nodes) belongs to the dealer

 If any open service request for the dealer

7. Login and Logout (AT-3)

Summary: As a user, I would like to login to Agritel so that I can perform drip irrigation activities

Description:

 Sign In page should have a background image and below fields and CREATE ACCOUNT and SIGN
IN buttons:
o Mobile number
o Password
Procedure:

1. User downloads and installs Agritel app

 2. User taps the app icon, splash screen gets displayed followed by language setting page
3. Upon selecting the language, the app shall take the user to sign in page
4. User inputs registered mobile number and password and taps SIGN IN button
5. App validates the mobile number and password
6. If the user credentials are successfully validates, the app takes the user to home page
7. User performs necessary action in the app
8. User taps the navigation icon or slides the slider menu and selects logout option
9. The app logs out and takes the user to sign in page
10. If the validation fails, the app shall throw below error message and stays in the sign in page:
“Invalid credentials, please try again!”
11. If no response from server for specific time, below error message shall be displayed
“Server timeout! Please try again after sometime.”
12. After login, the app should remember the user by default, remember me checkbox not
required

Update on 8-Oct-16 (AT-37)

Description:
Below point has been added
 Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared

8. Home Page – Admin (AT-101)

Summary: As an admin, I want to navigate to home page and be able to see customer issues
with status and access menu so that I can take necessary action on long pending service
requests

Description:
1. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
2. Home page – Admin shall have a grid view with 3 elements as below:

 Service Request

 My Devices
 Shared Devices
3. When user tap on any grid view element, the app shall take the user to corresponding page
4. Please refer AT-83 for My Devices and Shared Devices functionalities
5. Please refer AT-85 for Service Request functionalities
9. Home Page - Dealer (AT-18)
Summary: As a dealer, I want to navigate to home page to view devices and customer service
requests so that I can sell devices or take necessary action on open service requests.

Description:

1. Please refer field level specification for field details and error messages
2. Device means either controller or node
3. The home page header shall have below items:

 Navigation icon on top left corner

 Agritel logo next to the navigation icon
4. The page title should be “Home”
5. Please refer navigation menu story AT-20 for navigation menu details
6. Introduce Slider menu which shall slide from left to right. The content of slider menu shall be the
same as navigation menu
7. The home page content shall have four tabs:
 Issues tab – to display open issues sent from customer to the dealer
 Selling Devices tab – to display the devices to be sold by the dealer
 Customer Devices tab – to display the devices that are sold by the dealer
 My Devices tab – to display dealer owned controllers
8. The default tab shall be Issues tab
9. The home page header shall display a plus icon that shall be displayed on top right corner of the
home page. The plus icon shall be displayed only when dealer is in Selling Devices tab or My
Devices tab
10. When dealer is in Selling Devices tab, tapping on the plus icon shall take the dealer to Add
Controller or Node page
11. When dealer is in My Devices tab, tapping on the plus icon shall take the dealer to Add
Controller – customer page AT-4
12. Issues tab shall display the list of open service requests (issues) sort date field by descending
order. The issue list shall have customer name, issue open date and status. When dealer tap on
an issue, the app shall take the dealer to view issues page which displays the complete details of
the selected issue
13. Selling Devices tab shall display the device category list as shown below:

 Controllers
 Valves
 Lights or Fans
 Sensors
  Fertilizers
14. Each category shall be displayed in collapsed format
15. When dealer taps on a category, it should be expanded and sub-list shall be displayed in the
same page. The sub-list shall have list of devices that belongs to the selected category
16. The devices in sub-list are one which admin assigned to the dealer and to be sold
17. The sub-list shall have

 Checkbox
 Device QR Code
 DELETE icon
18. At bottom of each category, Sell to dropdown shall be provided which shall contain below static
values:
 Dealer
 Customer
 Myself
19. The QR code shall be sorted by ascending order
20. When user taps on a QR code, the app shall take the user to view controller or node – dealer
page
21. Each category shall have SELL and CANCEL buttons after Sell to dropdown
22. When dealer selects the dropdown option Dealer, below controls shall be displayed
dynamically:
 Dealer Name – Input field
 Dealer Mobile Number – Input field for dealer registered mobile number
23. Dealer shall sell device(s) to another dealer by performing below steps:

 Dealer selects required devices

 The dealer selects DEALER option from the dropdown
 Input new dealer name, mobile number and taps SELL button
24. When dealer selects the dropdown option Customer, below controls shall be displayed
dynamically:

 Customer Name – Input field

 Customer Mobile Number – Input field for customer registered mobile number
25. Dealer shall sell device(s) to a customer by performing below steps:
 Dealer selects required devices and CUSTOMER option from the dropdown
 He/She selects CUSTOMER option from the dropdown
 Input new dealer name, mobile number and taps SELL button
26. Dealer or customer name shall be minimum of 4 and maximum of 30 alphabets. If not, display
below message:
 Dealer: “Please enter dealer name between 4 to 30 characters”
Customer: “Please enter customer name between 4 to 30 characters”
27. Customer / Dealer mobile number validation:
 The mobile number should not be any controller SIM number. If not, below error message
shall be displayed:
“This mobile number is used by controller, please enter a different number”

 It can be a registered mobile number (not mandatory)

28. Dealer shall sell device(s) to himself by performing below steps:
 Dealer selects required devices and MYSELF option from the dropdown
 Dealer taps SELL button
29. Upon clicking SELL button (for all dropdown option), the controller or node sales should be
stored in both local database and server in parallel
30. When dealer taps on DELETE icon, corresponding device shall be delete upon confirmation
 Confirmation message: “Are you sure you want to delete the item <QR Code>?” with OK and
CANCEL buttons
 If dealer taps OK, that particular device shall be removed from the dealer account
 If dealer taps CANCEL, delete operation shall be cancelled and the category shall be
refreshed
31. Upon tapping CANCEL button within each category, the sell process gets cancelled and the
category shall be refreshed
32. Customer Devices tab shall display the customer name and his/her registered mobile number in
collapsed format with name sorted in ascending order
33. When dealer taps on a customer (customer and mobile number combination), it should be
expanded and sub-list shall be displayed. The sub-list shall have list of controllers that belongs to
the selected customer
34. The sub-list shall have controller name, QR Code and ON/OFF button. The sub-list should be
sorted by controller name in ascending order
35. App shall allow the dealer to switch the controller (belongs to customer) on or off using the
ON/OFF button
36. Upon switching the controller ON/OFF, below messages shall be displayed
ON: “<Controller Name> is switched ON”
OFF: “<Controller Name> is switched OFF”
37. When dealer tap on a controller, the app shall take the dealer to view controller – customer
page which displays the complete details of the selected controller
38. The view controller – customer page navigated from this page shall display the content that
belongs to the selected customer. All other operations in view controller – customer page is
similar to AT-60. The customer device and program setting records should not be duplicated for
the dealer. It should be shared by both dealer and customer
39. Customer Devices tab shall have a search field to search for customer names
40. My Devices tab shall have the list of controllers owned by the dealer. The controller list shall
have controller name, alert icon showing number of unread SMS and ON/OFF button. When
dealer tap on a controller, the app shall take the dealer to view controller – customer page
which allows the dealer to view controller details, map controller and nodes, create programs
and operate the controller
41. The list in My Devices tab should be sorted by controller name, ascending order.
42. App shall allow the dealer to switch the controller on or off using the ON/OFF button
43. Upon switching the controller ON/OFF, below messages shall be displayed
ON: “<Controller Name> is switched ON”
OFF: “<Controller Name> is switched OFF”
44. If Issues tab does not have open issues to display, below message shall be displayed:
“No open issues available. Have a nice day!”
45. If Selling Devices tab does not have any device to display, below message shall be displayed:
“No selling device available in your account. Please tap plus icon to add device”
46. If Customer Devices tab does not have any controller to display, below message shall be
displayed:
“You have not sold any device. Please tap Selling Devices tab to sell device”
47. If My Devices tab does not have any controller to display, below message shall be displayed:
“No owned controllers available for your account. Please tap plus icon to add controller”
48. The list name and other details shall not exceed the page width
49. If the list is beyond the page size, vertical scroll bar shall be provided
50. Home page shall display the content from local database if no server connection
51. Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared
52. Dealer should be able to change the sort order wherever necessary
Procedure:

1. Dealer downloads and installs Agritel app

2. Dealer taps the app icon, splash screen gets displayed followed by language setting page
 3. Upon selecting the language, the app shall take the dealer to sign in page
4. Dealer inputs the mobile number and password and taps SIGN IN button
5. The app shall take the dealer to home page
6. Dealer taps on the navigation icon, he/she should be able to see the menu as in navigation
icon story AT-20
7. By default the app shall display issues tab with the list of issues which has been sent from
customer to the dealer
8. The dealer taps the selling devices tab. The app shall display the list of all device category
9. The dealer taps on CONTROLLER category
10. The CONTROLLER category gets expanded and controller list gets displayed with checkboxes
11. The dealer sells first two controllers to a customer by performing below steps:
 Dealer selects required devices and CUSTOMER option from the dropdown
 Input customer name, mobile number and taps on OK button in popup window
 Dealer taps SELL button
 Confirmation message: “Sold devices cannot be returned, please verify the selected
devices before selling.” with OK and CANCEL buttons
 Dealer taps OK
12. The selected controllers are successfully sold to the customer. The app throws success
message:
“Selected device(s) has been sold successfully” with OK button
13. The dealer taps the navigation icon and selects exit from the navigation menu. The app
should remember the logged in dealer and close the app
14. Next time when the dealer taps the app icon, the app shall skip login page and directly lands
into the home page

Update on 22-Oct-16 (AT-85)

Updates from original story

Description:
1. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
2. Home page – dealer shall have a grid view with 5 elements as below:
 Service Request

 Selling Devices

 Customer Devices
 My Devices
  Shared Devices
3. When user tap on any grid view element, the app shall take the user to corresponding page
4. Please refer AT-83 for My Devices and Shared Devices functionalities
5. Major functionalities for Service Request, Selling Devices and Customer Devices are provided in
AT-18, below points are few updates from that
6. Referring to point 12 in original story: The service request(SR) list shall have customer name, SR
open date and status
7. Category in selling devices page should be changed as below:
a) Controller
b) Valve
c) Light
d) Fan
e) Moisture sensor
f) Level sensor
g) Humidity sensor
h) Temperature sensor
i) Flow meter sensor
j) Fertilizer pump
k) Fogger
l) Energy meter
8. Updates on message codes:
a) Scenario: If dealer name is not between 4 and 30 characters
Message: Warning message code- W006
b) Scenario: If customer name is not between 4 and 30 characters
Message: Warning message code- W007
c) Scenario: If the dealer mobile number is same as any controller SIM number
Message: Warning message code- W008
d) Scenario: If the customer mobile number is same as any controller SIM number
Message: Warning message code- W009
e) Scenario: Device delete confirmation message
Message: Confirmation message code- C001
f) Scenario: If Selling Devices tab expanded category does not have any device to display
Message: Information message code- I004
g) Scenario: Selling confirmation message
Message: Confirmation message code- C002
h) Scenario: Selling success message
 Message: Information message code- I013
i) Scenario: If Issues tab does not have open issues to display
Message: Information message code- I010
j) Scenario: If Customer Devices tab does not have any device to display
Message: Information message code- I011
k) Scenario: If My Devices tab does not have any device to display
Message: Information message code- I012
l) Scenario: If dealer name empty
Message: Warning message code- W010
m) Scenario: If customer name empty
Message: Warning message code- W011
n) Scenario: If dealer mobile number empty
Message: Warning message code- W012
o) Scenario: If customer mobile number empty
Message: Warning message code- W013
p) Scenario: If Sell-to option not selected
Message: Warning message code- W014
q) Scenario: If dealer country code not selected
Message: Warning message code- W015
r) Scenario: If customer country code not selected
Message: Warning message code- W016
Point 9 in original story description has been changed as below
9. The home page header shall display a plus icon that shall be displayed on top right corner of the
home page. The plus icon shall be displayed only when dealer is in Selling Devices page.
10. Plus icon is not required for dealer in My Devices page since dealer can sell to himself

Update on 27-Jan-17 (AT-346)

1. Allow sales only for registered users
2. Display below message if the mobile number is not registered:
Warning message code: W058 (This point is given in comments)

10. Common Updates to Mobile App on 16-Dec-16 (AT-215)

Description:
 Bullet point 1 and 2 applies to View controller - customer module
1. When user tries to input any node beyond the limit, below message shall be displayed:
Error message code: E051
2. The app should not allow dealer to delete customer controller. Delete option should be
hidden when dealer access customer controller
Bullet point 3 applies to home page dealer – selling devices module
3. When user taps on SELL TO dropdown

 Change of display order – first display mobile number followed by dealer or customer
name
 Dealer or customer name is display only field and mobile number is input field
 If dealer inputs mobile number, the app should trace it
 If mobile number does not exists, just store the mobile number in database
 If mobile number exists in database, retrieve dealer or customer name from user profile
and display the same below mobile number
Bullet point 4 and 5 applies to the modules wherever node category is being displayed
4. Below title and sort order should be followed for the node category list in all over the app:
 Valves
 Lights
 Fans
 Moisture sensors
 Level sensors
 Humidity sensors
 Temperature sensors
 Flow meter sensors
 Fertilizer pumps
 Foggers
 Energy meters
5. Dealer pages would have an additional category ‘Controllers’

Update on 16-Dec-16 & 21-Dec-16 (AT-218)

Referring to point 3 in original story (AT-215)

1. If the dealer select the SELL TO option as 'Dealer', but input a customer / admin mobile number,
display below message
Warning message code: W045
 2. If the dealer select the SELL TO option as 'Customer', but input a dealer /admin mobile number,
display below message
Warning message code: W046
3. Add ‘Admin’ as one of the dropdown options
4. If the dealer select the SELL TO option as 'Admin', but input a dealer / customer mobile number,
display below message
Warning message code: W047
Below point applies to View controller - customer module:
5. When dealer updates SIM number for customer controller, the app should send customer
mobile number as primary user mobile number

Update on 27-Dec-16 (AT-249)

Below change applies to Home page – dealer (AT-18) – SELL TO option

3. Admin user type – The mobile number should be available in the admin mobile number list
4. Dealer user type – The mobile number should be available in user profile table as a dealer only
5. Customer user type – The mobile number may or may not be available in user profile table. If
available, it should be a customer mobile number only
6. If the dealer select the SELL TO option as 'Dealer' or ‘Customer’ or ‘Admin’, but input his
registered mobile number, display below message
Warning message code: W044
7. If the dealer select the SELL TO option as 'Dealer', but input an unregistered dealer mobile
number, display below message
Warning message code: W058
8. If customer sells a controller to customer or admin who is not registered, the sold controller
should be displayed in My Devices page after customer or admin registers and login to the app

11. Remove Device Delete Functionality for Dealer (AT-132)

Summary: This story is for below tasks:
 Remove delete icon in dealer home page (AT-18)
 Remove delete action in view controller or node page (AT-84)

Description:

9. The DELETE icon in dealer home page - selling devices section shall be removed
10. Navigation to view controller or node page by tapping on QR code remains same
11. View controller or node page shall be for view device details purpose only. DELETE and CANCEL
buttons shall be removed. A back icon shall be provided to take the user to previous page

12. Home Page - Customer (AT-19)

Summary: As a customer, I want to navigate to home page and be able to see my controllers and
access menu so that I can perform drip irrigation activities.

Description:

1. Please refer field level specification for field details and error messages
2. The home page header shall have below items:
3. Navigation icon on top left corner
4. Agritel logo next to the navigation icon
5. Plus icon on top right corner of the home page
6. Please refer navigation menu story AT-20 for navigation menu details
7. Introduce Slider menu which shall slide from left to right. The content of slider menu shall be the
same as navigation menu
8. When customer taps on the plus icon, the app shall take the customer to Add Controller –
customer page
9. The home page content shall have a list of controllers (controllers) associated with the customer
registered mobile number
10. The controller list shall have controller name, alert icon showing number of unread SMS and
ON/OFF button
11. The list shall be sorted by controller name, ascending order
12. App shall allow the user to turn the controller on or off using the ON/OFF button
13. Upon switching the controller ON/OFF, below messages shall be displayed
ON: “<Controller Name> is switched ON”
OFF: “<Controller Name> is switched OFF”
14. If the customer did not add any controller, below message shall be displayed:
“No controllers available for your account. Please tap plus icon to add controllers.”
15. Upon taping the controller, customer shall be taken to view controller – customer page
16. The list name and other details shall not exceed the page width
17. If the controller list is beyond the page size, vertical scroll bar shall be provided
18. Home page shall display the content from local database if no server connection
 Procedure:

1. Customer downloads and installs Agritel app

2. Customer taps the app icon, splash screen gets displayed followed by language setting page
3. Upon selecting the language, the app shall take the customer to sign in page
4. Customer inputs the user ID and password and taps SIGN IN button
5. The app shall take the customer to home page
6. The app displays the list of controllers associated to the customer’s registered mobile
number
7. The customer taps on a controller, app shall be display view controller – customer page
8. The customer configures the selected controller
9. The customer taps the navigation icon and selects exit from the navigation menu. The app
should remember the logged in user and close the app
10. Next time when the customer taps the app icon, the app shall skip login page and directly
lands into the home page

Update on 21-Oct-16 (AT-83)

Updates from original story

Description:

1. Please refer [Agritel – Application

Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-
+Application+Messages] for message codes
2. Home page – customer shall have a grid view with 2 elements as below:

 My Devices
 Shared Devices
3. The home page shall have menu icon and slider menu
4. My device and Shared device pages shall have a back icon in page header. On tapping
back icon, the app shall take the user to home page
5. When user tap on My Devices element, the app shall take the user to My Devices –
page
6. My Devices page: Display controller group names. Please refer AT-100 for group display
functionality
7. Plus icon should be displayed on top right corner. If user taps on the plus icon, the app
shall take the user to Add controller page AT-4
8. Shared Devices page tab shall display all controllers shared to the logged in user
9. Share Devices page should display the primary user name(s) (in collapsed format) who
shared the controller(s) to the logged in user
10. When user taps on the primary user name, the name gets expanded and list of
controllers belongs to the primary user shall be displayed
11. If there is no shared device, below message shall be displayed in the home page itself,
no popup required:
Message: Information message code: I026
12. Referring to Point 10 in original story: The controller list in both My device and Shared
device pages shall have below items:
a) Controller name – First row
b) Alert icon showing number of unread SMS – First row
c) ON/OFF button – First row
d) A launch point for quick menu (an icon) – Second row
e) Controller SIM number – Second row
f) Latest unread SMS without date and time – Third row
13. If controller name is blank, QR code shall be displayed in place of controller name
14. The ON/OFF button should be disabled if controller SIM number is unavailable
15. When user toggle between ON and OFF, below messages shall be displayed:
Message after controller is switched ON: Information message code - I001
Message after controller is switched OFF: Information message code - I001
16. When user taps on quick menu icon, below menu options should be displayed in popup:
a) Motor ON
b) Motor OFF
c) Make a call to controller SIM number
d) Get controller status
e) Controller settings
f) Reports
17. Motor ON – Send controller ON SMS
18. Motor OFF – Send controller OFF SMS
19. Live update – Send live update SMS to controller
20. Settings - Settings launch point
21. Report – Reports launch point
 22. Upon tapping SMS alert icon, a new page should be displayed with list of all unread
messages (show preview only)
23. The message page should display only error messages. Error message codes would be
provided later
24. If user taps on a message preview in the list, the complete message should be displayed
25. After user views any message (one or more), the message status should be changed
from unread to read. This status should be reflected in the alert icon

19. Navigation Menu (AT-20)

Summary: As an Agritel user, I want to use navigation menu so that I can access the modules of
Agritel app

Description:

 Navigation icon shall be displayed on top right corner of the pages

 When user taps on the navigation icon, app menu shall be displayed
 The menu header shall contain user name and phone number
 The app menu shall be displayed based on the user type
 Customer should be able to see the menu as below:
o Unit settings
o Edit Profile
o Sub-users
o Switch user account
o General Settings
o Service Request
o Help
o Logout
o Exit

Procedure:

1. User downloads and installs Agritel app

Update on 20-Jan-17 (AT-211)

Navigation Menu:

1. Menu icon shall be displayed on top left corner of below pages:

  Home Page (all 3 user types)

 View Groups
 View Sub-user

 Reports
 Chat Page

 Call
 General Settings

 Edit Profile

2. Navigation menu shall be displayed when user taps on menu icon or swipes the screen
from left edge to right on the pages listed in point 1
3. The navigation menu shall contain user name and registered mobile number in menu header
4. Please refer [Navigation Menu
|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+Navigation+Menu+-+Mobile] for menu
items in each page
5. First diagram explains menu items for customer and the second one for dealer and admin
6. Title of each box represent the page name and list below provides the list of menu items to be
displayed for the selected page
7. LOGOUT option should logout user from the app. After logout, the app shall take the user to
sign in page
8. EXIT option should allow the user to quit from the app without logout
View Controller - Customer:

1. Introduce a back button on top left corner of the page. When user taps on the button, the app
shall take the user to previous page
Add Controller - Customer:

1. When user taps on CANCEL button, the app shall take the user to previous page

Update on 06-Feb-17 (AT-358)

1. Below menu options not required in navigation menu:

 Reports
 General Settings
20. Forgot Password (AT-15)
Summary: As an Agritel user, I want to reset my password so that I can regain access to the app

Description:

 The “Forgot Password” hyperlink should take the user to reset password page
 Reset password page should allow the user to input registered mobile number, new password
and confirm it

 Upon successful validation, the app shall take the user to sign in page for him/her to login
 Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared
Procedure:

1. User downloads and installs Agritel app

2. User taps the app icon, splash screen gets displayed followed by language setting page
3. Upon selecting the language, the app takes the user to sign in page
4. User could not remember his/her login password, he/she taps on “Forgot Password?” link
5. The app takes the user to reset password page with below details
 Heading: Reset Password
 Message: Please enter new password
 Input field: Registered Mobile Number
 Input field: New Password
 Input field: Confirm New Password
 Buttons: RESET PASSWORD and CANCEL
6. User inputs registered mobile number, new password and confirm new password
7. When user taps on RESET PASSWORD button, the app performs below validation:
 The app checks the database for mobile number existence
 If the mobile number does not exists, the app displays below message and prompts to
enter registered mobile number
“Please enter your registered mobile number”
 If the mobile number exists, the app checks for both new password and confirm new
password fields. Password shall be minimum of 6 and maximum of 10 alphanumeric
characters; new password should match with confirm new password
8. If the password validation fails, the app prompt the user to re-enter the password
9. Upon successful validation, the app resets password for the user and takes him/her to sign
in page to login
10. When user taps CANCEL button, app shall take the user to sign in page for him/her to try
login
Update on 25-Oct-16 (AT-89)

Updates based on client requirement:

Description:

1. On tapping “Forgot Password” hyperlink, the app should trigger an SMS to the registered
mobile number
2. The SMS should contain OTP for password reset
3. Reset password page should contain
 Below information:
Message: Information message code: I014
 Input field: Country code
 Input field: Registered Mobile Number
 Input field: OTP
 Input field: New Password
 Input field: Confirm New Password
 Buttons: RESEND OTP, RESET PASSWORD and CANCEL
4. Please refer AT-2 for country code and phone number validation
5. Upon lost focus of OTP textbox, the app should validate the OTP in textbox with the one in
SMS
6. After successful OTP validation, user should be able to update their new password
7. If the OTP validation is unsuccessful, user shall tap on RESEND OTP button to resend a new
OTP SMS
8. If user tries to input password without entering OTP, the app should display below message:
Message: Warning message code: W041
9. If OTP validation is unsuccessful, the app should display below message:
Message: Warning message code: W042

Updates on message codes from original story:

1. Scenario: Registered mobile number is empty after user taps SUBMIT button
Message: Warning message code: W002
2. Scenario: New password is empty after user taps SUBMIT button
Message: Warning message code: W003
3. Scenario: Confirm password is empty after user taps SUBMIT button
Message: Warning message code: W004
4. Scenario: If password length is not between 6 and 10 characters
Message: Warning message code: W005
5. Scenario: Message to display after password reset successful
Message: Information message code: I003
Procedure:

1. User downloads and installs Agritel app

2. User taps the app icon, splash screen gets displayed followed by language setting page
3. Upon selecting the language, the app takes the user to sign in page
4. User could not remember his/her login password, he/she taps on “Forgot Password?” link
5. The app sends an SMS with OTP and takes the user to reset password page
6. The user inputs registered mobile number with country code. The app sends SMS to the
registered mobile number
7. The user reads the OTP in SMS and inputs the same in reset password page. The app
validates the OTP
8. User input new password and taps on RESET PASSWORD button. The user receives success
message

21. Add Controller – Customer (AT-4)

Summary: As a customer, I want to add units so that I can associate it with valves and lights and
perform drip irrigation activities

Description:

 Please refer field level specification for field details and error messages
 This story is applicable for adding unit or controller only. A separate user story would be created
later for adding nodes (valve, light or sensor) for the unit
 The add unit page shall have below input fields:
o Device ID input box followed by SCAN button or icon which allows QR code scanning. User
can either type device ID or tap SCAN button to scan QR code
o Unit name to input a name for controller
o SIM number to input controller SIM number. This is the number which is used to
communicate with the Agritel app. SIM number shall have two fields in the same line, one
for country and the other for SIM number
o Please refer create account story AT-2 for country selection and SIM number validation
 All input fields are mandatory
 The page shall display below read only fields:
o Dealer Mobile Number
o Dealer Name
 This page shall have SUBMIT and CANCEL buttons
Procedure:
1. Customer downloads and installs Agritel app
2. Customer taps the app icon, splash screen gets displayed followed by language setting page
3. Upon selecting the language, the app shall take the customer to sign in page
4. Customer inputs the user ID and password and taps SIGN IN button
5. The app shall take the customer to home page
6. The app list all the units which belongs to the customer
7. Customer taps on the plus icon, the app takes the customer to add unit page which shall
have the fields in below order:
 QR Code or Device ID
 Dealer Mobile Number
 Dealer Name
 Unit Name
 SIM Number
8. Customer types the device ID in input field or taps SCAN button and scans QR code of the
unit
9. When the cursor moves out from QR Code or device ID field, app shall perform below
validation:
 QR code or device ID should be a registered code by admin. If not, below error shall be
displayed:
“Invalid unit ID, please contact your dealer.”
 The code should be associated to a dealer. If the unit is registered by admin but not
associated with dealer, below error message shall be displayed:
“The unit is not associated with dealer, please contact your dealer.”
 The code should be unique for the customer. If the unit is valid and associated to a
dealer but it already exists in the app, below error message shall be displayed:
“The unit already exists in user account!”
10. Upon successful validation of QR code or device ID, the apps shall display dealer name and
mobile number
11. Customer enters unit name and SIM number and taps SUBMIT button. The app performs
below validation:
 The SIM number should be a valid phone number. The app should validate (using API if
required) whether the number is a valid SIM or mobile number
 The SIM number should be a unique SIM number. If not, below error message shall be
displayed:
“The unit <unit name, QR Code> already holds this SIM number. Please enter a new SIM
number”
 It should not be a user registered mobile number. If the SIM number is already
registered by any user, display below message:
“This SIM number is a user registered mobile number. Please enter a new SIM number”
12. Upon successful validation, the unit details should be stored in both local database and
server in parallel
 13. In case of errors, after user taps OK in error window, the app shall reset the screen and
retains the same page
14. If the customer taps CANCEL button, the app shall reset the screen and retains in the same
page

Other possible errors:

1. Mandatory fields empty: “Please enter <field name>”

2. Unit Name greater than 30 characters: “Unit name should not exceed 30 characters”
3. No response from server for specific time: “Server timeout! Please try again after
sometime.”

Update on 8-Oct-16 (AT-39)

Below point has been added

Description:

 Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared
Procedure:

Below point has been added after point 11 (changed on 14-Oct-16)

1. Upon successful validation, the app sends SMS to the unit.

2. The unit acknowledges to the app SMS. (SMS format for point 1 and 2 would be provided later.)
3. After receiving acknowledgement SMS from the unit, the unit details should be stored in both
local database and server in parallel
4. In case of errors, after user taps OK in error window, the app shall reset the screen and retains
the same page
5. If the customer taps CANCEL button, the app shall reset the screen and retains in the same page

Other possible errors:

1. When user is not connected to server and tries to add unit: “Internet connection appears to be
offline”

Update on 1-Nov-16 (AT-9)

Description:

1. Controller name should be unique for the customer. If not, below message shall be displayed:
Message: Error message code: E036
2. If no server connection, the app shall display below message:
 Message: Error message code-E002

22. View Controller – Customer (AT-60)

Summary: As a Customer, I want to view controller details so that I can

 View controller, node and program details
 Map controller and its nodes
 Create programs

Description:

1. Please refer [field level

specification|https://iexemplar.atlassian.net/wiki/display/AW/Field+Level+Specification] for
field details and error messages
2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
3. Page title shall be “Controller”
4. This page shall have three sections:
 Controller details
 Nodes
 Programs
5. Controller details is the default section that shall have below fields:
 QR Code or Device ID
 Controller Name
 Controller SIM Number
 ON/OFF button
 Model
 Date of Manufacturing
 Dealer Name
 Dealer Mobile Number
 Mode of operation
6. Mode of operation should be a drop down and the drop down values shall be as below:
 SMS
 Voice call
 WI-FI
7. The default operation mode should be SMS
8. Controller details section shall have below buttons:
 Edit
  Delete
 Submit
 Cancel
 Replace Controller
 Settings
9. By default, all fields in controller details section is display only
10. When user taps on SETTINGS button, the app shall take the user to Settings page
11. Date of manufacturing shall be displayed in DD/MM/YYYY format
12. Upon tapping EDIT button, customer shall be allowed to change controller name and controller
SIM number
13. The app shall enable SUBMIT and CANCEL buttons only on edit mode
14. If user switches ON or OFF the controller, below messages shall be displayed:
Message after controller is switched ON: Information message code - I001
Message after controller is switched OFF: Information message code - I001
15. When customer taps SUBMIT button, controller name and SIM number should be updated upon
confirmation
16. Update confirmation message:
“Are you sure you want to update the controller details?”
17. When user taps OK from popup window, the app shall perform validation. Tapping on CANCEL
button, the app shall cancel the edit operation and takes the user to previous page
18. Controller name shall be unique for the customer. If not, display below message:
“This controller name already exists”
19. Controller SIM number validation:

 The SIM number should not be any other controller SIM number. If not, below error
message shall be displayed:
“This SIM number is already used by another controller. Please enter a different number”
 SIM number should not be registered mobile number or alternate phone number. If not,
below error message shall be displayed:
“This SIM number is a registered mobile number or alternate phone number. Please enter
a different number”
20. Upon successful validation, controller name and SIM number should be updated in both local DB
and server in parallel and the app should stay in the same page
21. When customer taps CANCEL button, edit operation should be cancelled and customer shall be
taken to previous page
22. When customer taps DELETE button, the controller and all its nodes and programs should be
deleted upon getting confirmation from the customer and the app shall take the user to
previous page
23. Delete confirmation message shall be as below:
“Deleting controller would delete all its nodes and programs associated to it! Are you sure you
want to delete controller?”
24. When customer taps REPLACE Controller button, the app shall prompt below message:
Message: Warning message code: W021
25. If user taps OK in popup window, the app shall display a popup with below 2 input fields:
 Controller QR code
 Controller SIM Number
26. Please refer AT-4 for controller QR code and SIM number validations
27. Nodes section shall have below collapsed categories:
 Valves
 Lights
 Fans
 Moisture sensors
 Level sensors
 Humidity sensors
 Temperature sensors
 Flow meter sensors
 Fertilizer pumps
 Foggers
 Energy meters
28. If the controller is inactive, a popup should be displayed with below message when user taps on
node section:
Message: Warning message code-W030
29. The Nodes section should have a collapsed list named Mapped Nodes as top item
30. Mapped nodes item behavior should different from all other categories
31. When user taps on Mapped Nodes category, the section should get expanded and all mapped
nodes which belongs to the selected controller should be displayed
32. The nodes should be sort by serial number ascending order
33. Mapped nodes list should have below display fields:
 Serial Number
 QR code of the node
 Name of the node
 Edit Icon
34. When user taps on Edit icon, the app shall take the user to Edit Mapped Nodes page
35. The app shall display below information (with information icon) near the node section title:
“To map controller with nodes”
36. The above list of categories is a standard list for each controller
37. The expanded details of each category should display all nodes belongs to the category and sold
by the dealer to the customer with SUBMIT and CANCEL buttons
38. The node list shall have below details:
 A checkbox
 QR code of the node
 Name of the node
  Edit Icon
39. After user selects (tick checkbox) node(s) and taps on SUBMIT button, the app maps the
selected node(s) to the controller. Tapping CANCEL button shall clear the selection and collapse
the node group
40. Mapping of nodes to controller can be done locally and synchronized to server when the app
gets connected to server
41. If user taps SUBMIT button without selecting any node, the app shall display below message:
“Please select node(s) to map to the controller”
42. The app should generate a unique three digit serial number for each node under a controller.
The serial number is unique within the controller. It shall restart from 1 for the next controller
43. If a node is unmapped from the controller (using Edit mapped nodes module), that serial
number can be reused while mapping new node
44. After a node is mapped to a controller, it should be displayed under mapped nodes collapsible
item
45. When customer completes adding nodes for first controller and tries to add nodes for the
second controller, the list of nodes which are already added to first controller shall not be
displayed for the second controller
46. When customer taps on a node, Edit/Delete node page shall be displayed showing all values as
display only
47. When customer taps on edit icon, Edit/Delete node page shall be displayed showing node name
as editable field. All other fields in Edit/Delete node page are display only
48. Fertilizer nodes (fertilizer pump) shall be treated as below:
 All fertilizer nodes can be re-used for any controller
 Serial number can be generated for controller and fertilizer combination hence a fertilizer
can have different serial number when it is added in different controllers
Ex: Controller1, Fert1 – 010
Controller2, Fert1 – 050
49. Node section should have a plus icon. When customer taps on the plus icon, the app should take
him/her to add nodes page
50. If no server connection, the app shall display below message:
Message: Error message code-E002
51. If primary user deletes the shared controller, it should be automatically deleted from sub-user
account also
52. Programs section shall have below collapsed program names:
 Program1
 Program2
 Program3
 Program4
 Program5
 Program6
53. The above list of programs is a static list for each controller
54. If the controller is inactive, a popup should be displayed with below message when user taps on
program section:
Message: Warning message code-W030
55. When customer taps on a program, it should get expanded. The expanded list should display all
zones created for this program
56. When customer taps on a zone, the app shall take the user to edit program page
57. If no zone available for the expanded program, below message shall be displayed:
“No zone created for this program. Please tap ADD ZONE button”
58. The expanded program should display ADD ZONE and CANCEL buttons after zone list
59. When user tap on ADD ZONE button, the app shall take the customer to create zone page.
Tapping on CANCEL button should collapse the program group
60. Add textbox clear icon for all input fields. Upon tapping the icon, the whole text box content
shall be cleared
61. If no response from server for specific time, below message shall be displayed:
“Server timeout! Please try again after sometime.”
62. Please refer AT-100 for grouping related changes

Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The app list all controllers which belongs to the customer
4. Customer taps on a controller, view controller page shall get displayed
5. View controller page gets displayed with controller details, nodes and programs sections
6. Customer is able to see below display fields:
 QR Code or Device ID
 Controller Name
 Controller SIM Number
 ON/OFF button
 Model
 Date of Manufacturing
 Dealer Name
 Dealer Mobile Number
 Mode of operation
7. Customer taps on the edit icon, controller name and controller SIM number fields are changed
to editable fields
8. Customer enters controller name and SIM number and taps SUBMIT button
9. Controller details are updated
10. Customer expands the Valves category in Nodes section
11. Customer is able to see all valves (that was sold by the dealer to this customer) with check boxes
for each valve
 12. Customer selects X valves and taps SUBMIT button
13. Customer expands Light or Fan category and adds Y Lights or Fans
14. Customer expands sensor category and adds Z sensors
15. Customer expands fertilizers category and adds N fertilizers
16. Customer expands mapped nodes section, he/she is able to see all the mapped nodes in this
section
17. Customer taps on Program1 in programs section
18. The program1 gets expanded but no zone details available. Below message shall be displayed for
this case
“No zone created for this program. Please tap ADD ZONE button.”
19. Customer taps CANCEL button within expanded program group, program section gets collapsed
20. Customer taps CANCEL button near controller details, he/she is taken to the previous page

Update as on 28-Nov-16 (AT-142)

Please refer [General

Specification|https://iexemplar.atlassian.net/wiki/display/AW/General+Specification] for Agritel related
general spec

A. Controller Details Tab:

Updates for point 24 to 26 in AT-60

1. When customer taps REPLACE Controller button, the app shall prompt below message:
Message: Warning message code: W021
2. If user taps OK in popup window1, the app shall display a popup window2 with below details:
 Controller QR code or device ID (This field should allow both keyboard and scan input)
 Controller SIM Number
 OK and CANCEL buttons
3. If user taps OK in popup window 2, below message shall be displayed:
Message: Confirmation message code: C012
4. Please refer AT-4 for controller QR code and SIM number validations
5. Mode of operation should be a drop down and the drop down values shall be as below:
 SMS
 Voice call
 WI-FI
 GPRS

New points

1. When controller is deleted

  All zones and settings corresponding to the controller should also be deleted. This is
applicable for all programs inside the controller
 All nodes mapped to the controller should be unmapped. The nodes should be customer
account
 The app should send controller reset SMS. SMS would be provided later

B. Nodes Tab:

1. The plus icon in view controller, nodes tab should be removed

2. A view icon should be displayed in mapped nodes section. Upon tapping the view icon, the app
should:
 Send view ID SMS (to be provided later)
 Display a popup
3. The popup window should display the controller response SMS and OK button. Upon tapping OK
button, the popup window should be closed
4. If “Mapped Nodes” category is empty, display below message:
Error message code: E046
5. If the expanded list of any other category is empty, display below message:
Error message code: E047
6. App shall perform below validation while mapping the nodes:
 Light – Optional, maximum lights allowed for a controller is two
 Fan – Optional, maximum fans allowed for a controller is two
 Humidity sensors – Optional, maximum humidity sensors allowed for a controller is two
 Temperature sensors – Optional, maximum temperature sensors allowed for a controller is
two
 Flow meter sensors – Optional, maximum flow meter sensors allowed for a controller is four
 Fertilizer pumps – Optional, maximum fertilizer pumps allowed for a controller is four
 Foggers – Optional, maximum foggers allowed for a controller is four
 Energy Meter - Optional, maximum foggers allowed for a controller is four

C. Programs tab:

1. If no mapped nodes available for the selected controller when user taps on Programs tab,
the app shall display below message:
Error message code: E048
2. If no valves mapped for the selected controller and user taps on ADD ZONE button, the app
shall display below message:
Error message code: E049
3. Add a new item on bottom of the page named “Common ID Settings”
 4. When user taps on “Common ID Settings”, the app shall take the user to Common ID
Settings page

Update as on 8-Dec-16 (AT-179)

Description:

1. When user tries to input any node beyond the limit, below message shall be displayed:
Error message code: E051
2. When user tries to delete a controller, the app should prompt for user password. The app
should not allow the user to delete the controller, if user inputs wrong password.
3. The popup should have below message and password text box:
Information message code: I034
4. The app should not allow dealer to delete customer controller. Delete option should be
hidden when dealer access customer controller

Update as on 13-Dec-16 (AT-195)

Description:

1. Controller replacement
a) When a controller is replaced, user input should be populated for below fields:
 QR Code or Device ID
 Controller SIM Number
b) Below fields can be populated from product profile:

 Model
 Date of Manufacturing
c) Below fields can be populated from old controller record:
 Controller Name
 Dealer Name
 Dealer Mobile Number
2. Delete controller
a) When a controller is deleted, the record should be marked as inactive in database
b) The same customer or another customer should be able to add the controller
 c) But when the controller is in active status, the app should not allow a customer to add
another customer controller

Update as on 14-Dec-16 (AT-214)

Description:

1. The controller ON/OFF button in controller details tab should be changed to DND ON/OFF
2. If user turns ON the ON/OFF button, the app should send DND ON (for primary user) SMS to
the controller and shows below message in toast:
Information message code: I042
3. If user turns OFF the ON/OFF button, the app should send DND OFF (for primary user) SMS
to the controller and shows below message in toast:
Information message code: I043

Update as on 27-Dec-16 (AT-250)

Controller Replacement:
1. Controller QR code validation when a controller is replaced:
 The replacement controller should be present in product profile. If not, display below
message:
Error message code: E067
 The controller should not be associated to any dealer. If not, display below message:
Error message code: E068
 The controller should not be owned by any other users (customers or dealer or admin). If
not, display below message:
Error message code: E069

 The controller should be unique for the logged in customer. If not, display below message:
Error message code: E070
2. User can input old controller SIM number or new SIM number. If user inputs new SIM number,
 SIM number should be validated (Please refer AT-4 for validation)
 SMS should be sent to the controller. Please refer AT-11 for SMS code
3. If user taps OK button without entering QR code, the app shall display below message:
Warning message code: W057
 4. If user taps OK button in replace popup without entering SIM number, the app shall feed old
controller SIM number for this field

Update as on 14-Feb-17 (AT-384)

Description:

1. Operation mode dropdown shall be removed

2. All operation mode shall have ON/OFF buttons
3. Below are operation modes for mobile:

 SMS
 Voice Call

 WI-FI
4. Among 3 mobile operation modes, user can select only one at a time
5. When one mode is already selected and user tries to select the next mode, the app should
automatically turns OFF already selected mode(s)
6. If user selects WI-FI mode, the app shall allow him/her to select either one of the below
operation modes:

 WAP
 WPS
7. Below mode is the only operation mode for web:
 GPRS (Web)
8. GPRS is independent from all mobile modes
9. Examples:
a) Turn ON both SMS and GPRS (Web) - Valid
b) Turn ON WI-FI, WAP and GPRS(Web) modes - Valid
c) Turn ON SMS and WAP – Invalid
d) Turn ON SMS and WI-FI – Invalid
10. Please refer AT-253 for operation mode SMS codes

23. Common ID Settings (AT-182)

Summary: As a user, I want to send serial number of nodes to the controller so that I can use it for
sending settings SMS to the controller

Description:

1. Page title shall be “Common ID Settings”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages]
for message codes
3. Please refer [General Specification|
https://iexemplar.atlassian.net/wiki/display/AW/General+Specification] for message codes
4. This page shall contain below categories in collapsed format:
 Lights and Fans

 Humidity and Temperature sensors

 Flow meter sensors
 Fertilizer pumps

 Foggers
 Energy meters
5. When user taps on the category – Light and Fan, the app shall display:

 All light(s) and fan(s) mapped to the selected controller

 The node list should contain:
o Node name (display only)
o Serial number of the node corresponding to the name. This should be a dropdown
list

 If the node is a light, the dropdown list should contain all light serial numbers mapped
to the selected controller

 If the node is a fan, the dropdown list should contain all fan serial numbers mapped to
the selected controller
 All lights should be displayed first (sorted by serial number in ascending) followed by
fans (sorted by serial number in ascending).
6. User should be able to change the serial numbers in dropdown list. When the serial number
is changed, the corresponding display name should be changed
7. The expanded section of Humidity and temperature sensor category should be similar to
light and fan category but light node should be replaced with humidity sensor and fan with
temperature sensor
8. When user taps on the categories - Flow meter sensors, Fertilizer pumps, Foggers or Energy
meters, the app shall display:
 All nodes corresponding to the category which is mapped to the selected controller. The
list should be sorted by serial number in ascending

 The node list should contain below fields:

o Node name (display only)
o Serial number of the node corresponding to the name. This should be a dropdown
list
9. The dropdown list should contain all serial numbers (sorted by ascending) corresponding to
the category which is mapped to the selected controller
10. User should be able to change the serial numbers in dropdown list. When the serial number
is changed, the corresponding display name should be changed
11. All expanded sections should have SEND, VIEW and RESET ID buttons
12. This page shall contain a back button on top left corner. When user taps on the button, the
app shall take the user to previous page
13. Upon tapping the VIEW button, the app should perform below actions:
 An SMS should be triggered to the controller
 When SMS is successfully sent from the mobile, a toast message should be displayed
 After the app receives controller response for view SMS, the response should be
displayed in popup window with OK button

 When user taps on OK button in popup window, the popup should be closed and the
app should stay in main window
14. VIEW button toast format - Information message code: I035
15. When user taps on SEND button, the app should send ID set SMS to the controller and the
same should be stored in database
16. The app should not allow the user to repeat the serial number selection
17. After sending SMS to the controller:
 The app should display a toast as below:
Information message code: I039
  When user select the category again, the nodes should be displayed in the same order
as in SMS
 The app should not allow customer to delete or un-map these nodes
18. User should be able to resend the ID settings using the SEND button
19. When user taps RESET ID button, ID reset SMS should be sent to the controller
20. After app sends reset ID SMS, the app should display a toast as below:
Information message code: I040
21. User shall un-map or delete the node(s) after sending reset ID SMS
22. SMS codes would be provided later in Controller Communication story (AT-11)
Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer taps on a group name, he/she is able to see the list of controllers belongs to
the selected group
4. The customer taps on a controller, the app took the user to View controller page
5. The customer goes to Programs section
6. The customer taps on Common ID Settings, the app took the user to Common ID Settings
page
7. Customer taps on Light and Fan category
8. The app displays 2 light and 2 fan nodes
9. Customer changes the serial numbers for light nodes and taps on SEND button
10. Customer is able to see SMS sent success message in toast

24. View New Nodes (AT-152)

Summary: As a user, I want to view new nodes so that I can see pending unmapped nodes, edit or
delete node details

Description:

1. Page title shall be “New Nodes”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages]
for message codes
3. Please refer [field level specification|
https://iexemplar.atlassian.net/wiki/display/AW/Field+Level+Specification] for field details
4. Home page grid view shall have one new element named “New Nodes” for all three type of
users
5. When user taps on New nodes in grid view, the app shall take the user to New Nodes page
6. The page shall have below collapsed categories:

 Valves
 Lights
 Fans
 Moisture sensors
 Level sensors
 Humidity sensors
 Temperature sensors
 Flow meter sensors
 Fertilizer pumps
 Foggers
 Energy meters
7. The expanded details of each category should display all unmapped nodes belongs to the
customer who has logged in
8. If the expanded category do not have any node, below message shall be displayed:
Error message code: E045
9. The node list should contain below details:
 QR code of the node
 Node Name

 Edit icon
10. The list should be sorted by QR code in ascending order
11. This page should have a plus icon on top right corner. Upon tapping on the plus icon, the
app shall take the user to add nodes – customer page (AT-5)
12. When user taps on a card, the app should take the user to Edit / Delete Node – Customer
page (AT-86) in view mode first. If user taps on edit icon, the app shall allow user to edit the
node
13. When user taps on a edit icon, the app should take the user to Edit / Delete Node –
Customer page (AT-86) in edit mode directly
14. If the mobile do not have internet connection, below message shall be displayed:
Error message code: E002
Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. The user taps on “New Node” element in grid view
4. The app takes the user to view new node page
5. The user is able to see all the categories
6. The user taps on a category, the app expands the category and displays all unmapped nodes
under the selected category
7. The user taps on edit icon, the app takes him/her to Edit/Delete node page with the
selected node details

25. Add Controller or Node – Dealer (AT-61)

Summary: As a dealer, I want to add controller or node so that I can sell it to customers or other
dealers

Description:

1. Dealer shall use this page to add controller or node when admin is unable to sell controller or
node to the dealer
2. Page title shall be “Add Controller / Node”
3. This page shall have controller or node ID input box followed by SCAN button or icon which
allows QR code scanning. User can either type the ID or tap SCAN button to scan QR code
4. After receiving ID or QR code, the app shall validate whether the ID or QR code is registered by
admin in product profile. If not, below error shall be displayed:
“Invalid QR Code, please contact admin.”
5. Upon successful validation, the app shall populate values for below display fields:
 Model number
 Date of manufacturing
 Category
6. Date of manufacturing shall be displayed in DD/MM/YYYY format
7. SUBMIT and CANCEL buttons shall be displayed followed by the display fields
8. Dealer shall verify the details and tap SUBMIT button to add the item
9. After dealer taps SUBMIT button, the controller or node details should be stored in both local
database and server in parallel
10. If dealer taps SUBMIT button without entering ID or QR code, below message shall be displayed:
“Please enter Controller / Node ID or QR Code”
11. When dealer taps CANCEL button, add operation gets cancelled and the app shall take the user
to previous page
12. If no response from server for specific time, below message shall be displayed:
“Server timeout! Please try again after sometime.”

Procedure:

1. Assuming the dealer already installed, used the app and quit it without logout
2. Dealer taps the app icon, splash screen gets displayed followed by the home page
3. The dealer is able to see all four tabs in home page and issues tab being selected
4. The dealer taps on selling devices tab, he/she is able to see the collapsed device categories
5. The dealer taps plus icon on top right corner of the home page, the app takes the dealer to add
controller / node page
6. The dealer scans QR code
7. The app validates the QR code and displays corresponding model number, date of
manufacturing and category fields
8. The dealer taps on SUBMIT button, the controller or node details gets stored in both local
database and server in parallel
9. The controller or node gets added and the app takes the user to home page selling devices tab
10. The app shall display the expanded category of the item which is added

Update on 25-Oct-16 (AT-90)

Updates from original story:

1. Please refer [Agritel – Application

Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
2. “Controller / Node ID” can be replaced with “Device ID” in all occurrences
3. “Model Number” label can be replaced with “Model”
4. The app shall have a verify icon near device ID field to trace device ID/QR code
5. Scenario: If dealer taps SUBMIT button without entering ID or QR code
Message: Warning message code- W017
6. Scenario: After device successfully added
Message: Information message code- I005
7. If no server connection, the app shall display below message:
Message: Error message code-E002
8. Provide back button in place of menu icon which takes the user to previous page

26. View Controller or Nodes - Dealer (AT-84)

Summary: As a dealer, I want to view controller or node details so that I can verify and delete it if
required

Description:

1. Page title shall be “Controller / Node”

2. All fields in this page are display only fields
3. The app display below fields with DELETE and CANCEL buttons:
 Controller or node ID
 Model
 Date of manufacturing
 Category
4. Date of manufacturing shall be displayed in DD/MM/YYYY format
5. When dealer taps DELETE button, the controller or node should be deleted upon confirmation
6. Delete confirmation message with OK and CANCEL buttons:
“Are you sure you want to delete this Controller or Node?”
7. When dealer taps on OK button, the controller or node gets deleted from dealer account and
dealer should be taken to previous page with refreshed list
8. Tapping on CANCEL button in popup window should cancel the delete operation and takes the
dealer to previous page
9. Upon tapping CANCEL button in main window, the app should take the user to previous page
10. Content of this page shall be displayed only if there is server connection
11. If server connection not available, the dealer shall be taken back to previous page immediately
and below error message shall be displayed for 5 seconds in previous page
“Internet connection appears to be offline”
12. If no response from server for specific time, below message shall be displayed:
“Server timeout! Please try again after sometime.”

Procedure:

1. Assuming the dealer already installed, used the app and quit it without logout
2. Dealer taps the app icon, splash screen gets displayed followed by the home page
3. The dealer is able to see all four tabs in home page and issues tab being selected
4. The dealer taps on selling devices tab, he/she is able to see the collapsed device categories
5. The dealer taps on Controller category, the category gets expanded and the app displays
controller list
6. The dealer taps on a controller QR code, the app takes the dealer to controller / node page
7. The dealer views the selected controller details and taps on DELETE button, the app prompts for
conformation
8. The dealer taps OK button, the controller or node gets deleted from the dealer account
9. The app takes the dealer back to home page, selling devices tab with refreshed list

27. Add Nodes – Customer (AT-5)

Summary: As a customer, I want to add node so that I can map it to a controller and perform drip
irrigation activities

Description:

1. Customer shall use this page to add node when dealer is unable to sell it to the customer or
when customer wants to quickly scan it
2. Please refer Agritel – Application Messages for message codes
3. Page title shall be “Add Node”
4. This page shall have device ID input box followed by SCAN button or icon which allows QR code
scanning. User can either type the device ID or tap SCAN button to scan QR code
5. After receiving device ID or QR code, the app shall validate whether the device ID or QR code is
associated with a dealer. If not, below error shall be displayed:
Error message code - E022
6. The app shall have a verify icon near device ID field to trace device ID/QR code
7. Upon successful validation, the app shall populate values for below display fields:
 Category
 Model
 Date of manufacturing
 Dealer Name
 Dealer mobile number
8. Node name field should be provided below the device ID field for the customer to input the
node name
9. Date of manufacturing shall be displayed in DD/MM/YYYY format
10. SUBMIT and CANCEL buttons shall be displayed followed by the display fields
11. Customer shall input node name and tap SUBMIT button to add the node
12. After customer taps SUBMIT button, the node details should be stored in local database and
stays in the same page to add more nodes. The data should be synchronized with server when
there is server connectivity
13. The newly created node should be mapped to the selected controller
14. The app should generate a unique three digit serial number for each node under a controller.
The serial number is unique within the controller. It shall restart from 001 for the next controller
15. Unused serial number should be used first. If unused serial number is not available, new serial
number can be generated
16. After node gets created successfully, below message shall be displayed:
Message: Information message code- I023
17. If customer taps SUBMIT button without entering device ID or QR code, below message shall be
displayed:
Error message code – W001
18. When customer taps CANCEL button, add operation gets cancelled and the app shall take the
user to previous page
19. If no response from server for specific time, below message shall be displayed:
Error message code - E001
20. Provide back button in place of menu icon which takes the user to previous page
Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer is able to see all controllers belongs to him/her
4. The customer taps a controller in home page, the app takes the customer to view controller
page. The customer goes to nodes section
5. The customer taps plus icon on top right corner of the page, the app takes the customer to add
node page
6. The customer scans QR code and taps verify icon
7. The app validates the QR code and displays corresponding node name, category, model, date of
manufacturing, dealer name and dealer mobile number fields
8. The customer enters node name and taps on SUBMIT button, the node details gets stored and
customer gets success message

Update on 15-Dec-16 (AT-217)

Message updates for E022 and I023:

1. Scenario: After receiving device ID or QR code, the app shall validate whether the device ID or
QR code is associated with a dealer. If not, below error shall be displayed:
Error message code - E022
2. Scenario: After node gets created successfully, below message shall be displayed:
Message: Information message code- I023

28. Edit/Delete Node – Customer (AT-86)

Summary: As a customer, I want to edit or delete nodes so that I can input names for the node or
remove the node from my account

Description:

1. Page title shall be “Edit / Delete Node”

2. This page shall display below fields with SUBMIT, CANCEL and DELETE buttons:
 QR Code or Device ID
 Node Name
 Category
 Model
 Date of manufacturing
 Dealer Name
 Dealer Mobile Number
3. Date of manufacturing shall be displayed in DD/MM/YYYY format
4. An edit icon should be displayed on top right corner of the page
5. By default, node name field is display only and SUBMIT button should be disabled
6. If user taps on the edit icon, node name field should be changed to editable and SUBMIT button
should be enabled. DELETE button should be disabled
7. If user updates node name and taps on SUBMIT button, the node detail should be updated in
local database upon confirmation. The data should be synchronized with server when there is
server connectivity
8. Update confirmation message:
Message: Confirmation message code- C007
9. Update success message:
Message: Information message code- I024

10. If user taps on DELETE button, the node shall be deleted from the user account upon
confirmation
11. Delete confirmation message:
Message: Confirmation message code- C008
12. Delete success message:
Message: Information message code- I025
13. Provide back button on top left corner which should take the user to previous page

Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer is able to see all controllers belongs to him/her
4. The customer taps a controller in home page, the app takes the customer to view controller
page. The customer goes to nodes section
5. The customer taps on the collapsed item - valves, the app expands and lists all valves belongs to
the customer
6. The customer taps on a particular node (valve), the app takes the user to Edit/Delete Node page
7. The app validates the QR code and displays corresponding node name, category, model, date of
manufacturing, dealer name and dealer mobile number fields
8. The customer updates node name and taps on SUBMIT button, the node details gets updated
9. The customer gets update success message

Update on 13-Dec-16 (AT-196)

Updates from original story:

1. The app should not allow the user to delete node if:
 The node exists in a zone
 The ID setup done for the node (using Common ID Settings page)
2. Handling inactive nodes:
 When a node is deleted, the record should be marked as inactive in database
 The same customer or another customer should be able to add the node

 But when the node is in active status, the app should not allow a customer to add another
customer node

Can be reused (AT-271)

1. If the user tries to delete a node which exists in a zone or ID setup done (using Common ID
Settings page) for it, below message shall be displayed:
Message: Error message code- E072

29. Edit Mapped Nodes – Customer (AT-123)

Summary: As a customer, I want to edit or un-map node so that I can

 Rename the node
 Remove the mapping of node with controller

Description:

1. Page title shall be “Edit Mapped Nodes”

2. This page is similar to AT-86 except DELETE. DELETE button should be renamed as UNMAP NODE
button
3. If user taps on UNMAP NODE button, the node should be unmapped from the controller upon
confirmation
4. Un-map confirmation message:
Message: Confirmation message code- C009
5. Un-map success message:
Message: Information message code- I027

Update on 12-Dec-16 (AT-184)

Updates from original story:

1. The app should not allow the user to un-map node if:
 The node exists in a zone
 The ID setup done for the node (using Common ID Settings page)

Update on 3-Jan-17 (AT-272)

1. If the user tries to un-map a node which exists in a zone or ID setup done (using Common ID
Settings page) for it, below message shall be displayed:
Message: Error message code- E071

30. Create Service Request (AT-134)

Summary: As a customer, I want to create Service Request so that I can report issues to my dealer
with controller details
Description:

1. Please refer [Agritel – Application

Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
2. Service Request creation should be allowed for customers only
3. Introduce a button or icon in view controller page. When user tap on the button, the app shall
automatically create a service request with below details:
 Controller QR Code

 Customer Name
  Customer Registered Phone Number

 Message
4. Message format should be as below:
Message: Information message code- I031
5. The app should prompt for a confirmation before creating service request
6. Confirmation message format should be as below:
Message: Confirmation message code- C013
7. After a service request is created successfully, below message shall be displayed:
Message: Information message code- I041
Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer is able to see all controllers belongs to him/her
4. The customer taps a controller in home page, the app takes the customer to view controller
page
5. Customer taps on service request button
6. The app prompts for a confirmation message. The customer taps OK button in popup window
7. Service request gets created and the customer receives success message

31. View Service Request (AT-204)

Summary: As a dealer / admin, I want to see the customer service request so that I can resolve
customer issues
Description:

1. Service Requests should be displayed for dealer and admin user types only
2. When user taps on Service Request grid item in home page, the app should display view service
request page
3. If the user is a dealer, view service request page should display service requests with below
conditions:
 Service request belongs to the dealer’s customers

 Service request with OPEN and IN-PROGRESS status only

4. If the user is an admin, view service request page should display service requests with below
conditions:
  Service request belongs to all customers

 Service request with OPEN and IN-PROGRESS status only

5. The service request page should contain below data elements:

 Service request message

 More icon

 Issue open date

 Flag

 Status

 Update status icon

 Dealer name (for admin user type only)
6. When dealer taps on the service request card, the app shall take the dealer to view controller
page with the corresponding controller QR code provided in the service request
7. When user taps on More icon, the app shall display service request message and remarks in a
popup
8. The popup window shall have two display fields "Message" and “Remarks” and OK button.
When user taps on OK button, the popup window should get closed
9. Any back navigations after database update or tapping CANCEL button should take the dealer to
home page – dealer, service request section
10. Flag indicates whether:
 My service request is assigned to another dealer (grey flag)
 Another dealer service request is assigned to me (red flag)
11. When user taps on update status icon, the app shall take the user to update service request
status page
12. View service request page should have a back button on top left corner of the page. When user
taps on the back button, the app should take the user to previous page
Procedure:

1. Assuming the dealer already installed, used the app and quit it without logout
2. Dealer taps the app icon, splash screen gets displayed followed by the home page
3. Dealer taps on service request grid element
4. The app takes the user to view service request page
5. The dealer taps on a service request, the app takes the user to view controller page
6. The dealer views the controller details and resolves the service request
Update on 24-Jan-17 (AT-345)

1. Display of service request transfer flag is not required for dealer and admin

Update on 01-Feb-17 (AT-353)

1. Display dealer name as one of the data elements for admin user type only

Update on 02-Feb-17 (AT-356) for view and update SR pages

View Service Request Page

1. Display service request date and time in below format:
DD/MM/YYYY HH:MM
Update Service Request Page
2. Display remarks update date and time in below format:
DD/MM/YYYY HH:MM
3. The app should throw below warning message if user taps SAVE button without changing status
Warning message code: W060
4. The app should throw below warning message if status changed but remarks column is blank
Warning message code: W061

32. Update Service Request Status (AT-205)

Summary: As a dealer / admin, I want to update the status of service request so that the request can
be tracked easily
Description:

1. Update Service Requests status should be allowed for dealer and admin user types only
2. This page should contain below fields:

 Controller QR Code
 Customer Name

 Service Request Status

 Remarks
3. Controller QR code and customer name are display only fields
4. Service request status should be a drop down with below options:
 Open

 In-progress
 Closed
5. The default value of status dropdown should be the current service request status
6. The app should allow user to change the status from dropdown
7. Remarks is a free text where user can input the remarks / comment related to the status change
8. The page shall contain SAVE and CANCEL buttons in bottom of the page
9. When user taps on SAVE button, the app should update the service request status and remarks
upon confirmation
10. Status change confirmation message:
Message: Confirmation message code- C014
11. When user taps on CANCEL button, the app should go back to the previous page
12. The page should have a back button on top left corner of the page. When user taps on the back
button, the app should take the user to previous page
Procedure:

1. Assuming the dealer already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. User taps on service request grid element
4. The app takes the user to view service request page
5. The user taps on an update status icon, the app takes the user to update service request status
page
6. The user changes the status from dropdown and inputs remarks
7. The user taps on SAVE button
8. The app updates service request and displays success message

Update on 24-Jan-17 (AT-344)

1. Service request remarks:

 Remarks is mandatory field
 Each and every status update should have a remark
Example:
a) Status changed from Open to In-Progress. Remarks – Valve has been taken for service
b) Status changed from In-Progress to Closed. Remarks – Valve issue has been fixed
  All remarks pertaining to a service request shall be displayed in the popup which would be
shown when tapping on More icon
 Each remarks shall be displayed in below format:
<User Name>, <Remarks update time stamp>: <remarks>
 If a service request has 2 remarks, both should be concatenated and displayed in below
format:
<User Name>, <Remarks update time stamp>: <remark1>
<User Name>, <Remarks update time stamp>: <remark2>
2. Status change shall be allowed as below:
 From Open to In-Progress
 From In-Progress to Closed
 From Open to Closed

33. Add Zone (AT-96)

Summary: As a customer, I want to create zones so that I can create settings based on the zone and
perform drip irrigation activities
Description:

1. Page title shall be “Add Zone”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
3. This page shall auto-generate zone name using below format:
 “ZONE<999>” where 999 is a three digit number from 001 to 128 that should be generated
in sequence
4. The auto-generated zone name should be displayed on top of this page
5. This page shall have below collapsed categories:
 Valves
 Moisture sensors
 Level sensors
6. Display an information on top of the node list with info icon:
“Please select the required node(s) and tap APPLY button in each category”
7. The above list of categories is a standard list for each zone
8. The expanded details of each category should display the list of nodes with below rules:
 Nodes that belongs to the selected program
 Nodes that belongs to the selected category
  Nodes that are not tied to any zone
9. Each expanded category should have a set of APPLY and CANCEL buttons
10. When user selects (tick checkbox) node(s) and tap on APPLY button, the list of selected nodes
can be buffered and the category shall be collapsed. Tapping CANCEL button inside the category
shall just collapse the category and stay in the same page
11. Add zone page should have one set of SUBMIT and CANCEL buttons common for all categories
12. After user taps on SUBMIT button, the nodes in buffer should be stored in database after
validation
13. The node list shall have below details:

 A checkbox
 Serial number of the node
 QR code of the node
 Name of the node
14. After user taps on SUBMIT button, the app shall perform below validation:
 Each zone should have at least one valve and maximum of four valves
 Level and moisture sensors are optional
 If user selects sensors, a zone may have two level and two moisture sensors
15. Tapping CANCEL button in main window shall take the customer to previous page. The auto
generated zone name should also be cancelled
16. If customer taps SUBMIT button, the app should perform below validation:
 If customer did not select any node, the app shall display below message:
Message: Warning message code: W031
 If customer did not select any valve but selected sensors, the app shall display below
message:
Message: Warning message code: W032

 If customer selects more than 4 valves, the app shall display below message:
Message: Warning message code: W032

 If customer selects one or more sensors, the app shall check whether the user selected two
level and two moisture sensors. If not, the app shall display below message:
Message: Warning message code: W033
17. After successful validation, the selected nodes shall be bind to the new zone. The data can be
saved locally and synchronized to server when the app gets connected to server
18. After successfully storing the data, the app shall display below message:
Message: Information message code: I028
19. Provide back button on top left corner which should take the user to previous page
 Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer taps on a group name, he/she is able to see the list of controllers belongs to the
selected group
4. The customer taps on a controller, the app took the user to View controller page
5. The customer goes to Programs section
6. The customer taps on Program 1, he/she is able to see the list of zones already created for this
program
7. The customer taps on ADD ZONE button, the app took him/her to add zone page
8. The customer selects required nodes and taps on APPLY button in each category
9. After selecting all required nodes, the user taps SUBMIT button
10. A new zone got created and the customer receives success message

Update on 12-Dec-16 (AT-183)

Description:

1. Level and two moisture sensors validation should be as below:

 Level and moisture sensors are optional
 If user selects level sensor, a zone may have one or two level sensors
 If user selects moisture sensor, a zone may have one or two moisture sensors
2. This validation applies to Add Zone (AT-96) and Edit / Delete Zone (AT-133)
Message code to be used: Warning message codes: W032 and W033

34. Edit / Delete Zone (AT-133)

Summary: As a customer, I want to edit zones so that I can create settings based on the zone and
perform drip irrigation activities
Description:

1. Page title shall be “Edit / Reset Zone”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
3. This page shall display the selected zone name same as add zone page
4. This page shall have below collapsed categories:
  Valves
 Moisture sensors
 Level sensors
5. The above list of categories is a standard list for each zone
6. Display an information on top of the node list with info icon:
“Please select the required node(s) and tap APPLY button in each category”
7. The expanded details of each category should display the list of nodes with below rules:
 Nodes that belongs to the selected program
 Nodes that belongs to the selected category
 Nodes that belongs to the selected zone
 Nodes that are not tied to any zone
8. The node(s) that belongs to the selected zone should be checked
9. The node(s) that does not belong to the selected zone should be unchecked
10. Each expanded category should have a set of APPLY and CANCEL buttons
11. When user selects (tick checkbox) node(s) and tap on APPLY button, the list of selected nodes
can be buffered and the category shall be collapsed. Tapping CANCEL button inside the category
shall just collapse the category and stay in the same page
12. This page should have one set of SUBMIT and CANCEL buttons for all categories
13. After user taps on SUBMIT button, the nodes in buffer should be stored in database after
validation
14. The node list shall have below details:
 A checkbox
 Serial number
 QR code of the node
 Name of the node
15. When the page is launched, SUBMIT, APPLY, CANCEL (in expanded window) buttons and check
boxes shall be disabled
16. This page shall have EDIT icon. When customer taps on EDIT icon, SUBMIT, APPLY, CANCEL (in
expanded window) buttons and check boxes shall be enabled and RESET ZONE button shall be
disabled
17. Tapping CANCEL button in main window shall take the user to previous page
18. Adding nodes to zone can be done locally and synchronized to server when the app gets
connected to server
19. If user taps SUBMIT button, the app should perform below validation:
 If customer did not select any node, the app shall display below message:
Message: Warning message code: W031
 If customer did not select any valve but selected sensors, the app shall display below
message:
Message: Warning message code: W032
  If customer selects more than 4 valves and taps SUBMIT button, the app shall display below
message:
Message: Warning message code: W032
 If customer selects one or more sensors, the app shall check whether the user selected two
level and two moisture sensors. If not, the app shall display below message:
Message: Warning message code: W033
20. After successful validation, the app shall update the zone details upon customer confirmation
21. Update confirmation message:
Message: Confirmation message code: C010
22. After the zone gets updated in the database, SUBMIT, APPLY, CANCEL (in expanded window)
buttons and check boxes shall be disabled and RESET ZONE button shall be enabled. The app
shall display update success message as below:
Message: Information message code-I029
23. If user taps on RESET ZONE button, all nodes belongs to that zone should be detached upon
confirmation
24. Reset zone confirmation message:
Message: Confirmation message code: C011
25. After the zone gets reset successfully, the app shall display below message:
Message: Information message code-I030
26. If no server connection, the app shall display below message:
Message: Error message code-E002
27. Provide back button on top left corner which should take the user to previous page
28. Provide a view icon on top left of the page
29. When user taps on view icon, an SMS should be sent to the controller (SMS would be provided
later)
30. The app shall display the controller response in a toast. If no response from the controller, the
app shall display below message:
Message: Error message code-E050
Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer taps on a group name, he/she is able to see the list of controllers belongs to the
selected group
4. The customer taps on a controller, the app took the user to View controller page
5. The customer goes to Programs section
6. The customer taps on Program 1, he/she is able to see the list of zones already created for this
program
7. The customer taps on a zone
8. The customer changes the node selection for the selected zone and taps on APPLY button for
each category
9. The customer taps on SUBMIT button after selecting all required node(s)
 10. The zone gets updated and customer sees update success message

Update on 13-Dec-16 (AT-203)

Description:

1. When a zone reset is done, all settings corresponding to the zone should deleted from the
system upon user confirmation
Message: Confirmation message code: C011

35. View Sub-users (AT-6)

Summary: As a user, I want to view sub-user details so that I can create or edit or delete sub-user if
required

Description:

1. Page title shall be “Sub-Users”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
3. Please refer field level specification for field details and error messages
4. View sub-user page shall have menu icon and navigation drawer menu
5. The app should display a sub-user list with 10 rows
6. The sub-user list should have below details:
 Sub-user code
 Sub-user name
 Sub-user mobile number
7. Sub-user code should be in below format:
REG<n> REG followed by a single digit, where the digit should be from 0 to 9. Ex: REG1.
8. The list should be sorted by sub-user code
9. When user taps on a sub-user, the app should take the user to Add/edit/delete sub-user page
10. This module should not be displayed for below scenarios:
  If the user does not have any controllers associated to his/her account. In this case,
display below message:
Message: Error message code- E038

 If the user does not have any active controllers associated to his/her account. In this case,
display below message:
Message: Error message code- E039
Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. The user taps on menu icon or swipes the screen from left edge to right to see the navigation
drawer menu
4. The user taps on the Sub-User option in the drawer menu
5. The app takes the user to view sub-user page
6. The user is able to see all 10 sub-user codes with respective name and phone numbers (if
created). He/she taps on a sub-user, the app takes him/her to Add/Edit/Delete sub-user page

36. Add/Edit/Delete Sub-users (AT-7)

Summary: As a user, I want to add or edit or delete sub-user details so that I can share my
controllers with them

Description:

1. The user can be an admin, dealer or customer

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages] for
message codes
3. This page shall display sub-user code in first row
4. Apart from sub-user code, the app should display below details:

 Sub-user mobile number

 Sub-user name (display only)

 List of controllers belongs to primary user with a check box

5. The controller list shall display controller name.
6. The controller list should have the controller(s) with below criteria only:
 Owned by the logged in user
  Active controller(s) (Inactive controllers cannot receive SMS from app)
7. The app shall have a verify icon near mobile number field to trace sub-user mobile number
8. The user should be able to enter sub-user mobile number and tap on verify icon
9. The sub-user name should be populated based on the mobile number
10. The user shall select the controller(s) that he wants to share with the sub-user
11. Scenario 1 - If sub-user is not created for the selected code, the app shall display SUBMIT and
CANCEL buttons
12. Page title for scenario 1 shall be “Add Sub-Users”
13. After selecting the required controllers, the user shall tap SUBMIT button to save the sub-user
details
14. One controller can be shared with multiple sub-users
15. Upon tapping the SUBMIT button, the app shall perform below validation:
 Sub-user mobile number should be a registered mobile number. If not, the app shall display
below message:
Message: Warning message code- W018

 Sub-user mobile number should not be empty

Message: Warning message code- W019
 At least one controller should be selected. If not, display below message:
Message: Warning message code-W020
 Sub-user mobile should not be duplicated for a customer. If duplicated, display below
message:
Message: Warning message code-W022
16. If the validation is successful, the sub-user details should be stored in both local database and
server in parallel and below success message should be displayed:
Message: Information message code- I006
17. DND mode should be set ON for the sub-user in the database during creation. It is not required
to display DND mode while adding sub-user
18. If user taps SUBMIT button without tracing mobile number, below message shall be displayed:
Message: Warning message code- W029
19. Scenario 2 - If sub-user is already created for the selected code, the app shall display SUBMIT,
CANCEL and DELETE buttons
20. Page title for scenario 2 shall be “Edit / Delete Sub-Users”
21. The app shall display an EDIT icon on top right corner
22. The app shall display DND mode ON/OFF button for every controller. The status of the ON/OFF
button should be set based on database value
23. If the controller is already assigned to this particular user, the check box shall be checked by
default
24. Below are the control status by default:
 All fields are display only

 Check boxes and SUBMIT button should be disabled

25. After user taps on EDIT icon, SUBMIT button and checkboxes should be enabled. DELETE button
should be disabled until user taps SUBMIT button
26. The user shall be able to select or deselect the controllers
27. When user taps SUBMIT button, below validation should be performed:
At least one controller should be selected. If not, display below message:
Message: Warning message code-W020
28. If validation is successful, sub-user details should be stored in both local database and server
upon confirmation
29. Update confirmation message:
Message: Confirmation message code- C003
30. After saving the details, the app shall display below success message and enables DELETE
button:
Message: Information message code- I009
31. When user taps on DELETE button, the sub-user and his/her details should be deleted upon
confirmation
32. Delete confirmation message:
Message: Confirmation message code- C004
33. If the user taps CANCEL button, the app shall take the user to view sub-user page
34. If no server connection, the app shall display below message:
Message: Error message code-E002
Changes for sub-user in other modules:
35. Below changes are applicable for Home Page – Customer and Home Page – Dealer:
 The app shall display a new tab name Shared Controllers
 The Shared controllers tab should display the list of controllers shared by primary user to
the logged in user
  Display of group name is not required

 The list of shared primary user name and mobile numbers shall be displayed in collapsed
format

 When the user taps on a primary user name, it gets expanded and the list of controllers
belongs to that user shall be displayed

 The controller list shall have controller name, alert icon showing number of unread SMS and
ON/OFF button
 Please refer AT-19 for alert icon and ON/OFF button functionalities
Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. The user taps on menu icon or swipes the screen from left edge to right to see the navigation
drawer menu
4. The user taps on the Sub-User option in the drawer menu
5. The app takes the user to view sub-user page
6. The user taps on plus icon, the app takes the user to Add/Edit/Delete sub-user page
7. The app displays new sub-user code
8. The user enters sub-user mobile number, the app displays sub-user name from database
9. The user selects all controllers that needs to be shared with the sub-user and taps SUBMIT
button
10. The selected controllers has been shared to the sub-user
11. The user sees success message and taps OK button. The page gets refreshed

Update on 25-Nov-16 (AT-169)

Change Request:

1. Sub-user ID format should be as below:

REG<00> REG followed by two digits, where the digit should be from 00 to 09. Ex: REG01
2. Restrict below right for all sub-users:
 Edit or Delete Controller
 Replace Controller
 Edit or Delete Node
 Mapping or un-mapping Nodes
 Add Sub-users for controller
Update on 18-Feb-16 (AT-398)

1. Allow customer to edit sub-user mobile number

2. If customer (primary user) changed sub-user mobile number, app shall send below SMS to all
checked controllers in sub-user module
 SMS Code: IDSET002
 Success Toast Message: Information message code- I052
 SMS should be sent one by one in 5 seconds interval. A toast should be displayed once
message sent is successful

37. View Groups (AT-97)

Summary: As a user, I want to view group names so that I can create or edit or delete group if
required

Description:

1. Page title shall be “Groups”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages]
for message codes
3. Please refer field level specification for field details
4. View group page shall have menu icon and navigation drawer menu
5. The app should display all group names created by the customer who has logged in
6. The list should be sorted in ascending order
7. This page should have a plus icon on top right corner. Upon tapping on the plus icon, the
app shall take the user to add group page
8. When user taps on a group name, the app should take the user to edit/delete group page
9. If the mobile do not have internet connection, below message shall be displayed:
Error message code: E002
Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. The user taps on menu icon or swipes the screen from left edge to right to see the
navigation drawer menu
4. The user taps on the group option in the drawer menu
 5. The app takes the user to view group page
6. The user is able to see all his groups. He/she taps on a group name, the app takes him/her
to Edit/Delete group page

38. Add Group (AT-98)

Summary: As a customer, I want to add group names so that I can group my controllers if required

Description:

1. Page title shall be “Add Group”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages]
for message codes
3. Please refer [field level
specification|https://iexemplar.atlassian.net/wiki/display/AW/Field+Level+Specification] for
field details
4. The add group page should have below controls:
 Group name
 SUBMIT and CANCEL buttons
5. Group name should be 20 alphanumeric
6. The app shall allow user to input group name and tap SUBMIT button
7. Upon tapping SUBMIT button, the app shall perform below validation:

 Group name should not be empty. If empty, below message shall be displayed:
Warning message code: W023
 Group name should be unique for the customer. If not, below error message shall be
displayed: Error message code: E044
8. After successful validation, the group name should be stored in both local database and
server in parallel.
9. After creating group in databases, the app shall display below message:
Message: Information message code- I021
10. If CANCEL button is clicked, the app should take the user to View groups page
Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
 3. The user taps on menu icon or swipes the screen from left edge to right to see the
navigation drawer menu
4. The user taps on the Group option in the drawer menu
5. The app takes the user to add group page
6. The user inputs group name and taps SUBMIT button, the app display success message

39. Edit/Delete Group (AT-99)

Summary: As a customer, I want to edit or delete group name

Description:

1. Page title shall be “Edit / Delete Group”

2. Please refer [Agritel – Application
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+Application+Messages]
for message codes
3. The app should display below controls:
 Group Name
 EDIT icon

 SUBMIT, CANCEL and DELETE buttons

4. Below are the control status by default:
 Group name field is display only
 SUBMIT button should be disabled
5. After user taps on EDIT icon, SUBMIT button should be enabled. DELETE button should be
disabled until user taps SUBMIT button
6. The user shall update the group name and taps SUBMIT button, the validation should be
done same as add group page
7. If validation is successful, group name should be stored in both local database and server
upon confirmation
8. Update confirmation message:
Message: Confirmation message code- C005
9. After saving the details, the app shall display below success message and enables DELETE
button:
Message: Information message code- I022
 10. When user taps on DELETE button, the group and his/her details should be deleted upon
confirmation
11. Delete confirmation message:
Message: Confirmation message code- C006
12. After deleting group name, the controllers that was linked to the deleted group should be
linked to ‘Agri Farm’ group

Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. The user taps on menu icon or swipes the screen from left edge to right to see the
navigation drawer menu
4. The user taps on the Group option in the drawer menu
5. The app takes the user to view group page
6. The user taps on a group and the app takes the user to edit/delete group page
7. The user taps on EDIT icon, the app enables SUBMIT button
8. The user updates the group name and taps SUBMIT button.
9. The app updates the group name and displays success message
10. The user taps OK button. The app took the user to view groups page

40. Grouping of Controllers (AT-100)

Summary: This module covers controller grouping logic wherever possible

Description:

1. Home page – dealer (AT-18) – Selling Devices tab

a) If dealer is selling to a customer, during selling process, all selling devices should be linked to
‘Agri Farm’ Category for the customer
b) If ‘Agri Farm’ group is not created for customer account, it should be created and controller
should be linked to it
2. Create account – AT-2
a) When a user account is created, a group named ‘Agri Farm’ should be created by default
b) If the ‘Agri Farm’ group name is already created while dealer sold the controller, it should
not be created again
3. Add Controller (AT-4), Edit/Delete Controller (AT-60)
 a) The add controller and edit / delete controller pages should display the group names in
dropdown
b) The default group name should be ‘Agri Farm’
c) When user creates or edits a controller, he/she can select a group and assign the controller
to it
4. Home page (both my devices and shared devices pages thru gridview elements) – AT-18, AT-19,
AT-101
a) Controller groups should be displayed in collapsed format
b) Display an icon on top right corner of the page to display the list with group or without
group. When user tap on the icon, the controllers list should be toggled to display with or
without group
c) When user taps on the group name, all controllers belongs to the selected group should be
displayed
d) The controller(s) which are not grouped should be displayed under the group name ‘Agri
Farm’
e) This change is not applicable for customer page (thru gridview element) in dealer home
page

Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. User taps the app icon, splash screen gets displayed followed by the home page
3. The user taps on menu icon or swipes the screen from left edge to right to see the navigation
drawer menu
4. The user taps on the Group option in the drawer menu
5. The app takes the user to view group page
6. The user taps on plus icon on top right corner, he gets into add group page
7. The user creates a group name and taps SUBMIT button
8. The new group has been added successfully
9. The user goes to add controller page and creates a new controller. He selects the newly created
group and taps SUBMIT button
10. The new controller is assigned to the newly created group
11. The user goes to home page, he is able to see all existing group names along with the newly
created group
12. The user taps on the newly created group, the newly added controller got displayed under the
new group

Update on 28-Nov-16 (AT-167)

Updates as on 28-Nov-16
1. Home page – dealer (AT-18) – Customer Devices section
a) When user taps on a controller in customer devices section, the view controller section
should not allow the customer to change group name

41. SMS Communication – Create and Manage Primary User

Contacts (AT-11)

Summary: As a user, I want to communicate with my controller to create and manage contacts

Description:

1. This story covers SMS format required for:

 Create and update primary user mobile number in controller
 Toggle DND mode for primary user (If DND ON, controller will not send any SMS to that
mobile number)
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. SMS code applicable for Add Controller– Customer (AT-4), View Controller – Customer (AT-60)
and Edit Profile (AT-17)
a) Scenarios 1: If user inputs SIM number while adding a new controller (AT-4)
SMS Code: IDSET001
Success Toast Message: Information message code- I050
Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E052
The app should not create controller if SMS is unsuccessful (if user did not input SIM
number, app shall create controller without SIM number)
b) Scenarios 2: Activating controller - If user updates SIM number while updating controller
details (AT-60)
SMS Code: IDSET001
Success Toast Message: Information message code- I050
Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E052
The app should not update controller if SMS is unsuccessful (if user did not input SIM
number, app shall update controller without SIM number)
c) Scenarios 3: When registered mobile number is changed in edit user profile (AT-17)
SMS Code: IDSET001
Success Toast Message: Information message code- I051
 Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E052
The app should not update profile if SMS is unsuccessful (if user did not change mobile
number, app shall update user profile with same old mobile number)
d) Scenarios 4: When user replace controller in view controller – customer (AT-60)
SMS Code: IDSET001
Success Toast Message: Information message code- I051
Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E052
The app should not replace the controller QR code if SMS is unsuccessful
Note: If user inputs the same mobile number used in old controller, app shall not send the
SMS
e) Scenarios 5: If user changes DND mode while updating controller details(AT-60)
Primary user DND ON SMS Code: IDSET003
Success Toast Message: Information message code- I042

Primary user DND OFF SMS Code: IDSET004

Success Toast Message: Information message code- I043
Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E035
The app should not update controller if SMS is unsuccessful (if user turns back the previous
status for DND mode, app shall update controller without DND mode)
Note:
1. When dealer updates SIM number for customer controller, the app should send
customer mobile number as primary user mobile number

Update on 17-Jan-17 (AT-315)

1. When the scenario b or c occurs, it is not necessary to wait for controller response. The app shall
update controller details once the SMS is sent out from the device.

42. SMS Communication – Create and Manage Sub-users (AT-251)

Summary: As a user, I want to communicate with my controller to create, edit or delete sub-users

Description:

1. This story covers SMS formats required to create, edit or delete sub-users
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. SMS code applicable for Add Sub-users (AT-7)
 Scenario: Create sub-user. The SMS should be sent to all select controllers
 SMS Code: IDSET002
 Toast Message: Message: Information message code- I053
 If SMS delivery is unsuccessful for 30 seconds, below message should be displayed:
Message: Error message code- E034. The app should not create the sub-user if SMS is
unsuccessful.
5. SMS codes applicable for Edit / Delete Sub-users (AT-7)
a) Scenario: Change DND mode for sub-users
 If DND mode is switched ON, the ON/OFF button shall be disabled until SMS delivery is
successful
 SMS Code: IDSET005
 Success Toast Message: Information message code- I007

 If DND mode is switched OFF, the ON/OFF button shall be disabled until SMS delivery is
successful
 SMS Code: IDSET006
 Success Toast Message: Information message code- I008

 If SMS delivery is unsuccessful for 30 seconds, below message should be displayed:

Message: Error message code- E035. The app should not update the sub-user if SMS is
unsuccessful

b) Scenario: Select a controller

 Send create sub-user SMS to the selected controller
 SMS Code: IDSET002
 Toast Message: Message: Information message code- I053
 If SMS delivery is unsuccessful for 30 seconds, below message should be displayed:
Message: Error message code- E034. The app should not update the sub-user if SMS is
unsuccessful
c) Scenario: Unselect a controller
 If a controller is unchecked, the app should compare the current and previous state of
the controller checkbox. If the previous state was checked and current state is
unchecked, sub-user reset SMS should be triggered to the unchecked controller.
Checking for checkbox status and sending SMS is applicable for all unchecked controllers
 SMS code for reset sub-user: IDSET002 with zeros instead of mobile number
Ex: REG<99>,<country code>,0000000000,
  Toast Message: Message: Information message code- I059
 If SMS delivery is unsuccessful for 30 seconds, below message should be displayed:
Message: Error message code- E037. The app should not update the sub-user if SMS is
unsuccessful

d) Scenario: Delete sub-user – Send sub-user reset SMS for all controllers assigned to him/her.
SMS should be sent only by one in 5 seconds interval
 SMS Code: IDSET002 with zeros instead of mobile number
Ex: REG<99>,<country code>,0000000000,
 Toast Message: Message: Information message code- I059
 If SMS delivery is unsuccessful for 30 seconds, below message should be displayed:
Message: Error message code- E037. Display one failure message for all SMS failures.
The app should not delete the sub-user if SMS is unsuccessful
5. SMS code applicable for Edit Profile (AT-17)
 Scenarios : If the user is a sub-user and he/she updates registered mobile number in edit
user profile (AT-17)
 SMS Code: IDSET002
 Success Toast Message: Information message code- I052
 Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E052
The app should not update profile if SMS is unsuccessful (if user did not change mobile
number, app shall update user profile with same old mobile number)

Update on 18-Feb-17 (AT-397)

Below point in original story shall be ignored:

5. SMS code applicable for Edit Profile (AT-17)

 Scenarios : If the user is a sub-user and he/she updates registered mobile number in edit
user profile (AT-17)
 SMS Code: IDSET002
 Success Toast Message: Information message code- I052
 Failure Message: If SMS delivery is unsuccessful for 30 seconds, below message should be
displayed: Message: Error message code- E052
The app should not update profile if SMS is unsuccessful (if user did not change mobile
number, app shall update user profile with same old mobile number)
43. SMS Communication – Map Nodes (AT-252)

Summary: As a user, I want to communicate with my controller to map or un-map nodes

Description:

1. This story covers SMS formats required for map and un-map nodes
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. SMS codes applicable for View Controller – Customer (AT-60), Edit Mapped Nodes – Customer
(AT-123)
a) Scenario: Map a node
 SMS Code: IDSET010
 Success Toast Message: Information message code- I056
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E053
 Note: User can map multiple nodes at one time. The SMS should be sent one by one with 5
seconds interval. Display one failure message for all SMS failures

b) Scenario: Un-map a node

 SMS Code: IDSET010 (populate the un-mapping node QR code with zeros)
Ex: IDSET000,123,456,789,012,345 - to un-map node with QR code 123,456,789,012,345
 Success Toast Message: Information message code- I057
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E054
 Note: User can un-map multiple nodes at one time. The SMS should be sent one by one with
5 seconds interval. Display one failure message for all SMS failures

c) Scenario: View a mapped node

 SMS Code: IDSET011
 Success Toast Message: Information message code- I035
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E055

Update on 13-Jan-17 (AT-310)

1. Un-map node SMS code should be as below:

 SMS Code: IDSET010 (populate the un-mapping node QR code with zeros)
 Ex: IDSET001,000,000,000,000,000 - to un-map node with serial number 001. The number of
zeros should be same as the number of digits in QR code

44. SMS Communication – Controller Details (AT-253)

Summary: As a user, I want to communicate with my controller to set operation mode

Description:

1. This story covers SMS formats required for controller operation mode
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. SMS code applicable for View Controller – Customer (AT-384)
a) Scenarios 1: If user selects SMS as Operation Mode
SMS Code: IDSET031

b) Scenarios 2: If user selects Voice Call as Operation Mode

SMS Code: IDSET032

c) Scenarios 3: If user selects WI-FI as Operation Mode

SMS Code: IDSET033

d) Scenarios 4: If user selects GPRS as Operation Mode

SMS Code: IDSET034

e) Scenarios 5: If user selects WAP as Operation Mode

SMS Code: IDSET035

f) Scenarios 6: If user selects WPS as Operation Mode

SMS Code: IDSET036

 Success Toast Message: Information message code- I058. The same toast message applies
for all operation modes
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E056
45. SMS Communication – Operating Controller and Quick Menu
(AT-254)

Summary: As a user, I want to communicate with my controller to switch it ON / OFF or get

controller status

Description:

1. This story covers SMS formats required to switch the controller ON / OFF or get controller status
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. SMS codes applicable for below modules:
I. Home page – Dealer (AT-18) Customer Devices, My Devices and Shared Devices;
II. Home page – Customer (AT-19) My Devices and Shared Devices
III. Home page – Admin (AT-101) My Devices and Shared Devices
Scenario: Controller ON or OFF
 If controller is switched ON, the ON/OFF button shall be disabled until SMS delivery is
successful
 SMS Code: IDSET007
 Success Toast Message: Information message code- I001

 If controller is switched OFF, the ON/OFF button shall be disabled until SMS delivery is
successful
 SMS Code: IDSET008
 Success Toast Message: Information message code- I002

 If SMS delivery is unsuccessful, ON/OFF button can be enabled after 30 seconds

5. SMS codes applicable for Home Page quick menu (AT-83) – Applies to all user types: Admin,
Dealer and Customer
a) Scenario: Motor ON – Please refer bullet point 9
b) Scenario: Motor OFF - Please refer bullet point 9
c) Scenario: Get controller status (Controller ON/OFF only)
 SMS Code: IDSET009
 Success Toast Message: Information message code- I054

46. SMS Communication – Create and Manage Zone (AT-255)

Summary: As a user, I want to communicate with my controller to create, edit and reset zones
Description:

1. This story covers SMS formats required to create, edit and reset zones
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. The number of parameters is mandatory in all SMS formats. Zeros can be added if no value for
any parameter. Please refer below example, zeros are added instead of third and fourth valve
parameters
Ex: IDZONESELP1001,123,124,000,000
5. SMS codes applicable for Add zone (AT-96)
 Scenario: Adding a new zone
 SMS Code: IDSET012 and IDSET014
 Success Toast Message: Information message code- I073
 Note: A zone can have valves and sensors. User can select all required nodes for a zone and
save it in one step. But the SMS for valve and sensor are different. So valve SMS should be
sent first followed by sensor SMS with 5 seconds interval
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E059
6. SMS codes applicable for Edit / delete zone (AT-133)
a) Scenario: Update an existing zone
 SMS Code: IDSET012 and IDSET014
 Success Toast Message: Information message code- I074
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E060

b) Scenario: View zone settings

 SMS Code: IDSET013 and IDSET015
 Success Toast Message: Information message code- I075
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E061

c) Scenario: Reset zone settings

 SMS Code: IDSET012 and IDSET014 with zeros for all node serial numbers
Below example shows reset zone001 for program 1
Ex: IDZONESELP1001,000,000,000,000
 Success Toast Message: Information message code- I076
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E062
 Note: The app shall send 2 SMS each for update, view and reset zone. So valve SMS should be
sent first followed by sensor SMS with 5 seconds interval. Display single failure message for both
SMS failures

47. SMS Communication – Common ID Settings (AT-256)

Summary: As a user, I want to communicate with my controller to add nodes to the controller
Description:

1. This story covers SMS formats required for setting node IDs which are not added to zone
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
4. The number of parameters is mandatory in all SMS formats. Zeros can be added if no value for
any parameter. Please refer below example, zeros are added instead of 2 fan parameters
Ex: IDLIGHTFANSET,001,002,000,000
5. SMS codes applicable for Common ID settings (AT-182) – This module includes ID set for nodes
which are not included in zone
a) Scenario: ID set for the category Lights and Fans
 SMS Code: IDSET016
 Success Toast Message: Information message code- I060

b) Scenario: ID set for the category Humidity and Temperature Sensors

 SMS Code: IDSET022
 Success Toast Message: Information message code- I061

c) Scenario: ID set for the category Foggers

 SMS Code: IDSET018
 Success Toast Message: Information message code- I062

d) Scenario: ID set for the category Fertilizer

 SMS Code: IDSET020
 Success Toast Message: Information message code- I063

e) Scenario: ID set for the category Flow Meter

 SMS Code: IDSET024
 Success Toast Message: Information message code- I064

f) Scenario: ID set for the category Energy Meter

 SMS Code: IDSET026
  Success Toast Message: Information message code- I065

 Failure Message: If the mobile device could not send SMS for any category, below message
should be displayed: Message: Error message code- E063

6. SMS codes applicable for Common ID settings (AT-182) – This module includes view ID set for
nodes which are not included in zone
g) Scenario: View ID set for the category Lights and Fans
 SMS Code: IDSET017
 Success Toast Message: Information message code- I067

h) Scenario: View ID set for the category Humidity and Temperature Sensors
 SMS Code: IDSET023
 Success Toast Message: Information message code- I068

i) Scenario: View ID set for the category Foggers

 SMS Code: IDSET019
 Success Toast Message: Information message code- I069

j) Scenario: View ID set for the category Fertilizer

 SMS Code: IDSET021
 Success Toast Message: Information message code- I070

k) Scenario: View ID set for the category Flow Meter

 SMS Code: IDSET025
 Success Toast Message: Information message code- I071

l) Scenario: View ID set for the category Energy Meter

 SMS Code: IDSET027
 Success Toast Message: Information message code- I072

 Failure Message: If the mobile device could not send SMS for any category, below message
should be displayed: Message: Error message code- E064

Update on 19-Jan-17 (AT-317)

1. SMS success toast message codes from I060 to I072 shall be ignored
2. Below toast message codes shall be used:
 I039 for Common ID set
 I040 for Reset common ID settings
  I035 for view common ID settings
3. Same common ID set SMS shall be used for ID reset also. Zeros shall be replaced in place of
node serial numbers.
Example: IDLIGHTFANSET,000,000,000,000 shall be used to reset common ID set for the
category Lights and Fans
 SMS Code: IDSET016
 Success Toast Message: Information message code- I040
4. Similarly, point 5 in AT-256 shall be referred for other category SMS codes

48. SMS Communication – Manage Service (AT-257)

Summary: As a user, I want to communicate with my controller to set service ON and OFF

Description:

1. This story covers SMS formats required for Service Request module
2. Whenever an SMS is sent from the app to controller, a toast should be displayed once message
sent is successful
3. For all modules, the app shall send SMS after successful validation only
7. SMS codes applicable for Create Service Request (AT-134)
 Scenario: After service request created
 SMS Code: IDSET029
 Success Toast Message: Information message code- I077
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E065

8. SMS codes applicable for Update Service Request Status (AT-205)

 Scenario: After dealer / admin close the service request
 SMS Code: IDSET030
 Success Toast Message: Information message code- I078
 Failure Message: If the mobile device could not send SMS, below message should be
displayed: Message: Error message code- E066

49. Data Synchronization (AT-10)

Summary: As an Agri-irrigation app, I want to synchronize data with server so that I can receive
latest data from server and vice versa

Description:
1. The app shall have a local copy of the database. Data collected by the app should be stored in
both local database and server
2. Data from below modules should be stored in both local database and service in parallel. If the
device could not connect to the server, the app data should not be stored in local database also.
 Create account / Profile
 Edit account / Profile
 Forgot Password
 Add Controller
 Edit Controller

 Delete Controller
 Add Node

 Edit Node
 Delete Node

 Add Sub-user
 Edit Sub-user
 Delete Sub-user
 Add Groups
 Edit Groups
 Delete Groups
 Add Zone

 Edit Zone
 Reset Zone
 Edit Mapped Nodes
 Chat
3. Data from below modules should be stored in local database first and then synchronized with
server whenever the device gets connected to internet:
 All settings modules

 Service Request
4. The app shall retrieve data from local database for all view pages (including reports)
5. A cron job shall be created to check the server connectivity and synchronize the local database
with server and vice versa if the app gets connected to the server
6. The job shall be executed every time when user opens the app and should be executed every 5
minutes when the user is using the app
7. The job should perform below tasks:
 Match the records between server and local database for tables related to below modules:
o All settings modules
o Service Request

 Data difference should be determined based on timestamp. Data with earlier timestamp
should be overwritten by data with latest timestamp
 The records which exists in the server but not in local database should be copied from
server to local database
 The records which exists in the local database but not in server should be copied from local
database to server

Update on 23-Jan-17 (AT-342)

1. Data synchronization between local database and server shall be executed every time when
user launches the app. When the user continues to use the app, it should check the internet
connectivity constantly and synchronize data
2. For any particular table or record, always the latest update should be sent to the server
Ex: If the initial value of SMS limit is 50 and it has been changed as below:
24 January 2017 10:00 - 70
24 January 2017 10:10 - 80
24 January 2017 10:20 – 100
The job shall send the value 100 to the server since it is the latest data

50. Settings Page – UI (AT-59)

Summary: As a customer, I want to view the settings menu so that I can navigate thru it and do
controller settings

Description:
1. Please refer [Main
Menu|https://iexemplar.atlassian.net/wiki/pages/viewpage.action?pageId=6717455] for menu
structure
2. The list of items in main menu and sub menus should be as in the confluence image
3. The menu should be a list view. Upon tapping a menu option, it should take the user to
corresponding sub-menu
4. Please refer below links for sub-menus:
 [Water Pump
Controller|https://iexemplar.atlassian.net/wiki/display/AW/Water+Pump+Controller]
 [Agri-Irrigation|https://iexemplar.atlassian.net/wiki/display/AW/Agri-Irrigation]
 [Light Settings|https://iexemplar.atlassian.net/wiki/display/AW/Light+Settings]
 [Water Level
Controller|https://iexemplar.atlassian.net/wiki/display/AW/Water+Level+Controller+Settin
gs]
 [Green House
Settings|https://iexemplar.atlassian.net/wiki/display/AW/Green+House+Settings]
 [Feedback Settings|https://iexemplar.atlassian.net/wiki/display/AW/Feedback+Settings]
 [View Settings|https://iexemplar.atlassian.net/wiki/display/AW/View+Settings]
5. Sub-menu list should be similar to main menu. The sub-menu may have another level sub-menu
or a setting page
6. The setting pages shall have controls as given in confluence page
7. All input boxes should have place holders. The place holders shall be as below:
 Hour – HH
 Minute – MM
 Second – SS
 Other numeric values – display 9 for number of digits
Ex: Placeholder for SMS Limit should be 999
 Target phone number – “Mobile number”
 Conference call number – “Customer care number”
 Controller SMS balance – “Mobile balance check number”
 Service number – “Mobile number”
 Voice feedback – “Mobile number”
8. The main menu should be configured based on the nodes purchased by the customer
a) Below menu items should be provided by default:
 Water Pump Controller
 Feedback Settings
 View Settings
b) If the user purchased at least one valve, the app shall display “Agri-Irrigation Menu”
c) If the user purchased at least one light, the app shall display “Light Settings Menu”
d) If the user purchased at least one flow meter sensor, the app shall display “Water Level
Controller Menu”
 e) If the user purchased at least one sensor (any sensor), the app shall display “Green House
Settings Menu”
9. The app should follow all menu items in below format:
 All menu items should be displayed in title case (first letter of each word should be in
capital)
 All menu items should be left justified
 Page titles should be centered

Update on 27-Dec-16 (AT-248)

Updates in Agri-Irrigation UI
1. Add the selected program name on top of the standalone screen
2. Skip days - The number of digits to input has been changed from 3 to 1
3. Rename the label “Valve cyclic restart” to “Zone cyclic restart”
4. Changes in day count RTC timer page
5. The format of display area for VIEW button has been changed:
 Earlier the view format was to extract data from SMS and display the same (Ex: High Level %
and Low Level %)
 Now the change is to display the entire message in view area same as other view
 Changes done in below modules:
o Program Settings <Program#> Water Level
o Program Settings <Program#> Moisture Level
o Program Common Settings  Adjust Percentage
o Program Common Settings  Fertilizer Flow Calibration
6. View mode page - Removed ON/OFF buttons and introduced dropdown and a view area
7. Display goto settings icon in all sub-menus (not required for end pages). This icon should take
the user to settings main menu

Update on 12-Jan-17 (AT-309)

Updates in Water Pump Controller UI

1. Change installation main menu in water pump controller main menu page
2. Changed Dry Run Amps value format as 000.0
3. Changed Power Factor Correction Volts format as 000
4. Changed Voltage Cal and Current Cal formats as 0.0000
5. Added a SEND button for time in Dry run occurrence page
6. App shall allow 10 digits and special characters (* or #) for Controller SMS balance field
7. App shall allow 10 digits for Conference call field
51. Settings Page – Validation and Communication with Controller
(AT-137)

Summary: As a customer, I want to do settings so that I can operate my controller as per the
settings

Description:

1. Please refer below links for SMS formats of all settings:

 [SMS for Water Pump Controller Settings|
https://iexemplar.atlassian.net/wiki/display/AW/SMS+-+Water+Pump+Controller]
 [SMS for Agri-Irrigation Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+Agri-Irrigation]
 [SMS for Light Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+Light+Settings]
 [SMS for Water Level Controller|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+WLC+Settings]
 [SMS for Green House Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+Green+House+Settings]
 [SMS for Feedback Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+Feedback+Settings]
 [SMS for View Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+View+Settings]
2. ON-OFF button
 If a particular setting is not available in the app, the button should be in yellow with OFF
state
 If the status is stored as ON in the app, the button should be in green with ON state
 If the status is stored as OFF in the app, the button should be in red with OFF state
3. Each SEND button should send an SMS to the controller
4. The CANCEL button should go back to the previous page
5. User shall enter data in input fields. SMS should be sent to the controller only if there is at least
single value in input field(s)
6. Each input field should show placeholder. Please refer the confluence settings page for
placeholder values
7. The VIEW or GET button should send an SMS to the controller, the response to VIEW or GET
SMS should be displayed in the text area with the title “Controller Response:”
8. Any numeric value entered should be > 0
9. Input box should have validation as below if value > 0:
a) Hour value should be between 1 and 24. If not below message should be displayed:
Message: Warning message code- W034
b) Minute value should be between 1 and 60. If not below message should be displayed:
 Message: Warning message code- W035
c) Second value should be between 1 and 60. If not below message should be displayed:
Message: Warning message code- W036
d) Percentage should not exceed 100. If not below message should be displayed:
Message: Warning message code- W037
e) Zone numbers should not exceed 128. If not below message should be displayed:
Message: Warning message code- W038
f) Program number:
 If user the settings page in confluence shows single digit, it should not exceed 6. If not
below message should be displayed:
Message: Warning message code- W039
 If user the settings page in confluence shows double digit, it should not exceed 12. If not
below message should be displayed:
Message: Warning message code- W040
g) Please refer SMS format confluence page for phone number validations
10. Wherever decimal value exists, the SMS should be sent to controller without dot (.). But storing
in database and display in setting pages should be with dot (.)
11. Standalone mode:
 If a zone n is turned on, all other zones should be automatically turned off in the standalone
page. Zone OFF state inside the controller would be taken care by the hardware in this
scenario
 If user would like to turn OFF all zones, user can turn OFF the standalone mode ON/OFF
button
12. When an SMS is triggered from the app, the app shall check for SMS sent status. If SMS send is
successful, display a toast and store the setting in local database
13. The settings should be synchronized to server when the app gets connected to the server
14. The toast message shall have below text:
a) If SMS triggered for ON with SEND button, the message can be in below format:
“<Page title> ON SMS sent”
b) If SMS triggered for OFF with SEND button, the message can be in below format:
“<Page title> OFF SMS sent”
c) If SMS triggered for just SEND button, the message can be in below format:
“<Page title> SMS sent”
d) If SMS triggered for VIEW button, the message can be in below format:
“View <Page title> SMS sent”
e) Below are exception pages:
 Installation Settings  Status SMS page: “Status SMS ON sent” or “Status SMS OFF
sent”
 Installation Settings  Controller SMS Balance: “Controller SMS balance value sent”
 SMS for Feedback settings  SMS page
o ON SMS message: “SMS ON Sent”
 o OFF SMS message: “SMS OFF Sent”
 SMS for Feedback settings  View Valve Condition page: “View valve condition sent”
 SMS for Feedback settings  View Test page: “View test sent”
 SMS for Feedback settings  View Setting for DNDSMS page: “View Setting for
DNDSMS sent”
 SEND button in Feedback Settings, Light Settings  Controller SMS Limit: “Controller
SMS Limit ON sent” or “Controller SMS Limit OFF sent”
 Input value and tap SEND button in Feedback Settings, Light Settings  Controller SMS
Limit: Controller SMS Limit sent
 View button in Feedback Settings  Controller SMS Limit: View controller SMS Limit
sent
 When user taps on GET HUMIDITY button in Green House settings  Humidity
Temperature Calibration page, message should be: “Get Humidity SMS sent”
 When user taps on GET TEMPERATURE button in Green House settings  Humidity
Temperature Calibration page, message should be: “Get Temperature SMS sent”

Procedure:

1. Assuming the customer already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The app list all controllers which belongs to the customer
4. Customer taps on a controller, view controller page shall get displayed
5. View controller page gets displayed with controller details, nodes and programs tabs. Controller
details tab has been selected by default
6. Customer taps on SETTINGS icon. Settings page gets displayed with main menu
7. Customer taps on LIGHT menu option. Light sub-menu gets displayed
8. Customer taps on CONTROLLER SMS LIMIT menu option. The app takes the user to controller
SMS limit page
9. Customer turns ON the ON/OFF button and taps on SEND button. He/she receives toast
message
10. Customer inputs value for SMS limit and taps on SEND button. He/she receives another toast
message

Update on 15-Dec-16 & 21-Dec-16 (AT-216)

1. Time validation should be as below:

a) Hour value should be between 1 and 23. If not below message should be displayed:
Message: Warning message code- W034
b) Minute value should be between 1 and 59. If not below message should be displayed:
Message: Warning message code- W035
c) Second value should be between 1 and 59. If not below message should be displayed:
 Message: Warning message code- W036
d) If FROM value is greater than TO value, below message should be displayed:
Message: Warning message code- W052
e) If FROM value is greater than TO value, below message should be displayed:
Message: Warning message code- W052
2. The requirement to show ON/OFF button in yellow has been removed
3. If SMS send is successful, store the setting in local database and display a toast. Toast message
updated from original story as below:
a) If SMS triggered for ON with SEND button, the message can be in below format:
Message: Information message code- I045
b) If SMS triggered for OFF with SEND button, the message can be in below format:
Message: Information message code- I046
c) If SMS triggered for just SEND button, the message can be in below format:
Message: Information message code- I047
4. The VIEW or GET button send or response shall not be stored in database. Toast message when
SMS triggered for VIEW or GET buttons:
Message: Information message code- I048
5. When user taps SEND button but all required parameters are zero, less than zero or blank, the
app shall display below message:
Message: Warning message code- W050
6. When user taps SEND button but target phone number is empty in water level controller
module, please display below message:
Message: Warning message code- W053
7. If target phone number is invalid in water level controller module, please display below
message:
Message: Warning message code- W054
8. SMS shall be sent for the below scenario (this applies for all settings):
a) Customer selects Humidity set menu item and inputs minimum value as 080 and maximum
value as 090
b) Customer just taps SEND button without changing maximum or minimum value

Update on 22-Dec-16 (AT-226)

1. Time validation should be as below:

a) If ON time is greater than OFF time, below message should be displayed:
Message: Warning message code- W034
b) If FROM time is greater than TO time, below message should be displayed:
Message: Warning message code- W035
c) If both FROM and TO or ON and OFF values are empty or zeros, below message should be
displayed because controller is not configured to read 00:00 as 12:00am:
 Message for Mobile: Warning message code- W050
Message for Web: Warning message code- W052

Update on 21-Jan-17 (AT-322)

Description:

1. Each settings SMS page contains:

 The settings pages where the SMS applies
 How to navigate to the page
 SMS format from the app to controller
 SMS response from controller to the app
 An explanation about the SMS format or validation

52. Settings Page –Menu Configuration (AT-138)

Summary: As a customer, I want to configure the settings menu so that I can have the frequently
used menus in my menu list

Description:

1. Please refer [Main

Menu|https://iexemplar.atlassian.net/wiki/pages/viewpage.action?pageId=6717455] for menu
structure
2. Please refer below links for sub-menus:
 [Water Pump
Controller|https://iexemplar.atlassian.net/wiki/display/AW/Water+Pump+Controller]
 [Agri-Irrigation|https://iexemplar.atlassian.net/wiki/display/AW/Agri-Irrigation]
 [Light Settings|https://iexemplar.atlassian.net/wiki/display/AW/Light+Settings]
 [Water Level
Controller|https://iexemplar.atlassian.net/wiki/display/AW/Water+Level+Controller+Settin
gs]
 [Green House
Settings|https://iexemplar.atlassian.net/wiki/display/AW/Green+House+Settings]
 [Feedback Settings|https://iexemplar.atlassian.net/wiki/display/AW/Feedback+Settings]
 [View Settings|https://iexemplar.atlassian.net/wiki/display/AW/View+Settings]
3. Please refer [Settings Menu
Configuration|https://iexemplar.atlassian.net/wiki/display/AW/Settings+Menu+Configuration]
4. Settings sub-menu pages should have a configuration icon on top right side of the page. The
icon is not required for Settings main menu
5. First time when customer login to the app, the app should show all menu items predefined for
the customer
6. When the user taps on configuration icon, a popup should be displayed with below details:
 Popup title should be “Menu Configuration”
 The list of active menu items in current page for the logged in user
 A checkbox for each menu item. The check boxes should be selected
 Show hidden settings and cancel icons
 SAVE button
7. User should be able to deselect the menu item(s) and tap SAVE button to hide the menu items
8. When user taps on show hidden settings icon, below details should be displayed:
 Popup title should be “Menu Configuration”
 All hidden menu items in current page for the logged in user
 A checkbox for each menu item. The check boxes should be deselected
 Show active settings and cancel icons
 SAVE button
9. User should be able to select the menu item(s) and tap SAVE button to change it to active menu
items
10. In either case, after the menu items get updates, the app shall close the popup and display
refreshed settings menu
11. When there is no active menu item for a sub-menu, the page should display below message:
Message: Information message code- I032
12. When there is no hidden menu item for a sub-menu, the page should display below message:
Message: Information message code- I033
13. The updated menu item should be displayed even when the customer logout and login
14. When customer taps CANCEL button, the app should close the popup

Update on 22-Dec-16 (AT-222)

1. When the configuration page is displaying hidden settings, the user taps SEND button without
selecting any menu item, the app shall display below message:
Message: Warning message code- W055

2. When the configuration page is displaying active settings, the user taps SEND button without
unchecking any menu item, the app shall display below message:
Message: Warning message code- W056
Update on 3-Jan-17 (AT-270)

1. Configuration icon shall be displayed in all sub-menus except for the below:
 <Program#> - Time based
 <Program#> - Flow based
 <Program#> - Fertilizer
 <Program#> - Fertilizer Time based
 <Program#> - Fertilizer Flow based
 <Program#> - <Fertilizer#> Time based
 <Program#> - <Fertilizer#> Flow based

53. Light Settings – Popup Info Messages (AT-181)

Description:

1. Popup page info for Settings → Light Settings → Date and Time: Information message code-
I036
2. Popup page info for Settings → Light Settings → Check Signal Strength: Information message
code- I037
3. Popup page info for Settings → Light Settings → Controller Status: Information message code-
I038

54. Agri Irrigation - Common Calibration Settings (AT-260)

Description:

1. This page shall display the list of nodes

2. Node list shall have below elements:

 Node Name (Display only)

 Node Serial Number (Display only)

 Calibration value (Input field)

 SEND and VIEW button

3. If node name is blank, the app shall display node QR code in first column
4. Node list shall be sorted by Node serial number in ascending order
5. User shall input calibration value and tap SEND button to send calibration SMS (for each node)
to the controller
6. Please refer the confluence diagram for calibration value format
7. Upon tapping VIEW button, SMS should be sent to the controller with node serial number and
response should be displayed in the view area
8. When user taps on CANCEL button, the app shall take the user to Agri irrigation menu

55. Standalone Settings (AT-261)

Description:

1. Please refer [SMS - Agri Irrigation|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-+Agri-

Irrigation] for Standalone settings
2. This page shall display below data elements or controls:
 Selected program name (Ex: Program 1) as title. The title should be displayed from Drip
Common Settings  Program Select page. If no program has been selected, display
Program 1 as default
 Standalone mode ON/OFF button with SEND button

 List of zones for the selected program

 Zone ON/OFF button for each zone
 One set of SEND and CANCEL buttons
3. Enable zone list only when standalone ON/OFF button is switched ON and corresponding SMS is
sent out
4. User can switch ON a zone and tap SEND button to send standalone SMS
5. From the list of zones, only one zone can be switched ON at a time. When user tries to turn ON
the next zone, previous zone should be turned OFF. When user tries to turn OFF a particular
zone, standalone mode OFF should be triggered
6. When user turns OFF the standalone mode ON/OFF button:
 The active zone should be turned OFF

 Working zone turn OFF SMS should be sent to the controller

 Zone list should be disabled

7. CANCEL button should take the user to previous page
8. When any zone is active in standalone mode, program selection should not be allowed in Drip
Common Settings  Program Select page. Below message shall be displayed if user tries to
change program:
Message: Warning message code- W059

56. View Settings (AT-323)

Description:

1. Please refer [View Settings| https://iexemplar.atlassian.net/wiki/display/AW/View+Settings] for

view settings screen
2. Please refer [SMS for View Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+View+Settings] for SMS codes
3. As described in the [diagram | https://iexemplar.atlassian.net/wiki/display/AW/View+Settings],
all view settings pages shall contain:
 Page title – Please refer the [diagram |
https://iexemplar.atlassian.net/wiki/display/AW/View+Settings] for page title
 A VIEW button - SMS should be sent to the controller when user hits VIEW button
 CANCEL button - The app shall take the user to previous page when the user hits CANCEL
button
 Controller response shall be displayed in the view area
4. Controller may return one or more responses against one view SMS
5. The app shall display all responses (against the view SMS) in the view area
6. Each view response would contain an indicator for SMS number and total number of SMS
7. Below is the indicator format
M<Pg number>/<Number of pages>
Ex: M1/3
Where 1 represents the current SMS number and 3 represents total number of SMS response
for a particular view SMS
8. Niagara would provide the indicator at the end of each SMS
9. The view settings from 1 to 11 are for future use. For now, the app need not send any SMS for
those options
Update on 01-Feb-17 (AT-354)

1. SMS shall be sent for the view settings from 1 to 11

2. Please refer [SMS for View Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-
+View+Settings] for view settings 1 to 11 SMS codes

57. QR Code Size Change (AT-210)

Description:

1. Remove clear icon in all editable QR code fields

58. CCTV (AT-221)

Summary: As a customer, I want to access CCTV app so that I can observe my farm using phone

Description:

1. Add a button (CCTV) or icon in View Controller – Customer (AT-60) page

2. First time, when customer taps on CCTV button / icon, the agritel app shall take the user to ‘Play
store’. This is to make the customer install third party CCTV app
3. When the user taps CCTV after installing the third party app, agritel app should directly open the
third party CCTV app
4. Add a new page in Setting  Water Pump Controller  Installation Settings, to turn ON or OFF
CCTV. The page name shall be “CCTV Configuration”
5. CCTV Configuration is not an SMS to controller
6. When it is ON, the View Controller – Customer (AT-60) should have a launch point for CCTV
7. When it is OFF, no launch point required for the controller
8. After agritel app renders the third party CCTV app, coming back from CCTV app to agritel app is
not in scope

59. Call (AT-380)

Summary: As a customer, I want to call my dealer so that I can

 Clarify my doubts
 Report an issue
 Check status of a service request
Description:

1. When user taps on Call option in navigation menu, the app shall take the user to select dealer
page
2. Select dealer page shall contain below elements:
 Page title “Call - Select Dealer”
 Info icon with the message – “Please select a dealer to place a call”
 Navigation icon on top left corner of the page
 List of dealers from whom the customer purchased his devices
3. When user selects a dealer, the app shall place a call to the registered mobile number of the
selected dealer upon confirmation
4. Confirmation message:
Message: Confirmation message code- C017
5. When user taps the navigation icon or slides the slider menu, the app shall display navigation
menu

60. Live Update (AT-382)

Summary: As a customer, I want to see live update of my controller so that I know the complete
current status of my controller

Description:

1. When user taps on ‘Controller Status’ in quick menu, the app shall send live update SMS to the
controller
2. SMS code as below:
• SMS Code: IDSET009 from [SMS for ID Settings
link|https://iexemplar.atlassian.net/wiki/display/AT/Agritel+-+SMS+for+ID+Settings]
• Success Toast Message: Information message code- I054
3. The controller response against live update SMS should be displayed in a new page
4. The new page title shall be ‘Live Update’
5. The new page shall have an OK button. When user taps on the button, the app shall take the
user to my devices page

61. Live Update 2 (AT-440)

Description:

1. Live update controller response might be split and sent in 2 messages

2. If the message is split,
3. Sample live update message:
P1 V=000 ON
VT=00:00:00
R=000 V
Y=000 V
B=000 V
RY=000 V
YB=000 V
BR=000 V
RA=00.0 A
YA=00.0 A
BA=00.0 A
CSQ=16
GPRS=1
LIMITSMSCOUNT=080
TCPSTAT=GPRS M1/2

$L, MOTOR ON II ,VRB:

000 AMP:00.0
, WPS MODE=ON
TIMER-100
FLOW-080
MOISTURE-090
FERT-070
MOISTURE MODE ON M2/2
4. Live update page shall be revamped with below sections
5. Section – Display area:
 Display area should show the content from controller display panel
 Display area content should be highlighted
 It contains 2 lines
 First line content should be extracted between the string “$L,” and second occurrence of
comma (,)
 Second line content should be extracted between second occurrence of comma (,) and third
occurrence of comma (,)
 Ex:
First line: MOTOR ON II
Second line: VRB: 000 AMP:00.0

6. Section – Zone status: This section should display below 3 particulars horizontally delimited by a
white space:
Ex: P1 ZONE=001 ON RT 02:10:00
  Program number – First 2 literals
 Zone number and status –
o KW_Valve = “V=”
o KW_ValveRT = ”VT=”
o The app shall check for KW_Valve. If found, retrieve 6 literals after KW_Valve and
display “ZONE=” followed by the extracted 6 literals
Ex: ZONE=001 ON
o If KW_Valve not found, display the string “ZONE OFF”
 Remaining Time – Extract 8 literals after KW_ValveRT and display “RT “ followed by the
extracted result
RT 02:10:00

7. Section – RYB: This section should display RYB values in three columns
 Column 1
o Display 3 digits after “R=”. The label shall be “R”
o Display 3 digits after “Y=”. The label shall be “Y”
o Display 3 digits after “B=”. The label shall be “B”
 Column 2
o Display 3 digits after “RY=”. The label shall be “C1”
o Display 3 digits after “YB=”. The label shall be “C2”
o Display 3 digits after “BR=”. The label shall be “C3”
 Column 3
o Display the decimal number after “RA=”. The label shall be “RA”
o Display the decimal number after “YA=”. The label shall be “YA”
o Display the decimal number after “BA=”. The label shall be “BA”
o All decimal numbers would contain 2 digits and 1 decimal place with decimal separator
(00.0)
 Ex:
R 280 C1 230 RA 30.1
Y 310 C2 140 YA 52.2
B 200 C3 240 BA 41.4
8. Section – CSQ & GPRS:
 Display 3 digits after “CSQ=”, the label shall be “CSQ”
 GPRS shall be displayed in the same line next to CSQ. It shall be single digit after “GPRS=”
 Ex: CSQ 016 GPRS 1
9. Section – SMS Count:
 Display 3 digits after “LIMITSMSCOUNT=”. The label shall be “Limit SMS Count”
Ex: Limit SMS Count 080
10. Section – TCP Status:
 Extract the value between the string "TCPSTAT=" and “M”. The result shall be displayed
without white space. The label shall be "TCPSTAT”
  Ex: TCPSTAT GPRS
11. Section – Additional content:
 Display the complete content after display area content (i.e.) after third occurrence of
comma (,) except the page indicator
 Ex: WPS MODE=ON
TIMER-100
FLOW-080
MOISTURE-090
FERT-070
MOISTURE MODE ON

62. Toggle Pump Status Automatically (AT-441)

Summary: As a controller, I want to toggle pump ON/OFF status in the app automatically

Description:

1. Controller ON/OFF button in home page shall be turned OFF when controller sends message
with below codes: 03, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 37, 38, 39, 40, 41, 42, 43, 101, 102,
103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113 and 114
2. The button should be turned OFF if the button is ON
3. Controller ON/OFF button in home page shall be turned ON when controller sends message with
below codes: 01, 02, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19
4. The button should be turned ON if the button is OFF
5. If controller ON/OFF button was automatically changed to OFF due to any of the error message
codes, following manual ON message should be sent as below:
 Motor OFF message followed by motor ON
6. Error message codes: 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113 and 114

63. Customer Service - Customer Chat (AT-227)

Summary: As a customer, I want to chat with my dealer so that I can get my issue(s) resolved

Description:

1. Chat page shall contain below elements:

 The page title shall be “Chat”
 Menu icon
 New message icon
 List of chat messages
2. New message icon shall be provided on top right corner of the page. When user taps on the
icon, the app shall take the user to select dealer page
3. Chat message list shall display the dealer name in first row and chat message in second row
4. The font style of dealer name should be bold
5. The chat message list shall be sorted in descending order
6. The latest received chat message between the dealer and customer should be display in single
line (if the message exceeds one line, … should be displayed at the end)
7. When user taps on the chat card, the app shall take the user to chat user page
8. If no chat message in the chat page, below message shall be displayed:
Message: Information message code- I049
9. Select dealer page shall contain below elements:
 Page title “Select Dealer”
 Info icon with the message – “Please select a dealer to chat with”
 Back button
 Dealer selection dropdown
 SUBMIT button
10. The dealer dropdown list should contain the list of dealers from whom the customer purchased
his devices
11. When customer taps SUBMIT button, the app shall take the user to chat user page
12. Chat user page shall contain below elements:
 Page title “Chat - <Recipient name>”
 Back button
 Message display area
 Message input field
 SEND button
13. Message display area shall display all chat messages in detail
14. Each message shall be displayed in below format
“<Sender name>: <Message>” (a white space should follow the colon)
15. If the sender is customer, display the customer name
16. If the sender is dealer or admin, display the text “Nayagara” instead of name
17. The font style of sender name should be bold
18. The message should be sorted in ascending order
19. The app shall allow customer to input new message in the input box
20. The input box shall have a clear icon to clear the input box content
21. When user taps the SEND button, the app shall send the message to the selected dealer
22. The same message should be send to all admin users and shall be displayed in chat user page
23. When user taps on menu icon, the app shall display drawer menu
24. Back button should be displayed on top left corner of the page. If user taps on the back button,
the app shall take the user to previous page

Procedure:
1. Assuming the user already installed, used the app and quit it without logout
2. Customer taps the app icon, splash screen gets displayed followed by the home page
3. The customer taps on menu icon or swipes the screen from left edge to right to see the
navigation drawer menu
4. The customer taps on the Chat option in the drawer menu
5. The app takes the user to customer service chat – customer page. No chat message displayed.
Below message got displayed:
Message: Information message code- I049
6. Customer taps on new message icon, the app navigates to select dealer page
7. Customer selects a dealer and taps SUBMIT button, the app navigates to chat user page
8. Customer inputs the change message and taps SEND button
9. The message has been sent to the selected dealer and all admin users. The message got
displayed in chat user page also

Update on 6-Jan-17 (AT-271)

Chat page
3. Bullet point 3 in original message should be as below:
Chat message list shall display:
 The customer name, date and time in first row
 Chat message and number of unread messages in second row
4. The number of unread messages should be highlighted
5. The chat message list shall be sort by date and time in descending order

Chat user page

6. The app shall display time at the end of each message
7. The messages shall be grouped by date. The date shall be displayed on top of each group
8. The message should be sort by date and time in ascending order
9. When a customer send message, it should be:
 Sent as push notification to the selected dealer
 Moved to all admin user accounts, push notification is not required
10. Push notification should be displayed as below:
 When customer is not using the app - The number of unread messages should be displayed
as a superscript in app icon
 When customer is using the app but not in chat user page – The message shall be displayed
as a banner with notification sound. The banner should be closed automatically after 5
seconds
 When customer is in chat user page, - The message shall be directly displayed in message
display area
Update on 12-Jan-17 (AT-308)

Chat page
1. First row of the chat message list shall contain dealer or admin name whoever replies to the
customer request

Chat user page

2. The app shall not display ‘Nayagara’ instead of dealer or admin name. The dealer or admin name
(given in profile) shall be displayed as sender name
Below 2 points added in comments since the ticket already added to sprint:
3. Display below message if message input box is empty and user taps SEND button. The same
validation applies for AT-228 and AT-229 also
Message: Warning message code- W062

Select Dealer Page

4. Below message shall be displayed if no dealer in the select dealer page list:
Message: Information message code- I068

64. Customer Service - Dealer Chat (AT-228)

Summary: As a dealer, I want to view customer messages and respond to the same so that I can
answer to the customer queries or solve their issues

Description:

1. Chat page shall contain below elements:

 The page title shall be “Chat”
 Menu icon
 List of chat messages
2. Chat message list shall display:
 The customer name, date and time in first row
 Chat message and number of unread messages in second row
3. The number of unread messages should be highlighted
4. The font style of dealer name should be bold
5. The chat message list shall be sort by date and time in descending order
6. The latest received chat message between the dealer and customer should be display in single
line (if the message exceeds one line, … should be displayed at the end)
7. When user taps on the chat card, the app shall take the user to chat user page
8. If no chat message in the chat page, below message shall be displayed:
Message: Information message code- I079
9. Chat user page shall contain below elements:
 Page title “Chat - <Customer name>”
 Back button
 Message display area
 Message input field
 SEND button
10. Message display area shall display all chat messages in detail
11. Each message shall be displayed in below format
“<Sender name>: <Message>” (a white space should follow the colon)
12. The app shall display time at the end of each message
13. The messages shall be grouped by date. The date shall be displayed on top of each group
14. The message should be sort by date and time in ascending order
15. The font style of sender name should be in bold
16. The message should be sort in ascending order
17. The app shall allow dealer to input new message in the input box
18. The input box shall have a clear icon to clear the input box content
19. When user taps the SEND button, the app shall send the message to the customer
20. The same message should be send to all admin users and shall be displayed in chat user page
21. When user taps on menu icon, the app shall display drawer menu
22. Back button should be displayed on top left corner of the page. If user taps on the back button,
the app shall take the user to previous page
23. When a dealer send message, it should be:
 Sent as push notification to the customer
 Moved to all admin user accounts, push notification is not required
24. Push notification should be displayed as below:
 When dealer is not using the app - The number of unread messages should be displayed as a
superscript in app icon
 When dealer is using the app but not in chat user page – The message shall be displayed as
a banner with notification sound. The banner should be closed automatically after 5 seconds
 When dealer is in chat user page, - The message shall be directly displayed in message
display area

Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. Dealer taps the app icon, splash screen gets displayed followed by the home page
3. The dealer taps on menu icon or swipes the screen from left edge to right to see the navigation
drawer menu
4. The dealer taps on the Chat option in the drawer menu
5. The app takes the user to customer service– dealer chat page
6. The list of customer names and corresponding chat messages are displayed
7. The dealer taps on a chat card, chat user page got displayed with the chat messages sent
between the dealer and the customer
8. The dealer enters a response in the input box and taps SEND button
9. The message got displayed in the message display area

65. Customer Service - Admin Chat (AT-229)

Below points should be after point 5 in the story:

1. If dealer list is empty in the chat page, below message shall be displayed:
Message: Information message code- I069
2. Below message shall be displayed for the scenario: Admin selects a dealer, but no chat message
between the selected dealer and his customer(s):
Message: Information message code- I070

Summary: As an admin, I want to view customer messages and corresponding dealer response so
that I can answer to customer pending queries or solve their issues

Description:
3. Chat – By Dealer page shall contain below elements:
 The page title shall be “Chat – By Dealer”
 Menu icon
 List of dealer names
4. Chat message list shall display dealer name and number of unread messages
5. The number of unread messages is among all customers for a dealer
6. Dealer list shall be sort by number of unread messages in descending order
7. When user taps on a dealer name card, the app shall take the user to Chat – By Customer page
8. Chat – By Customer page shall contain below elements:
 The page title shall be “Chat - <Selected dealer name>”
 Back button
 List of chat messages
9. Chat message list shall display:
 The customer name, date and time in first row
 Chat message and number of unread messages in second row
10. The number of unread messages should be highlighted
11. The font style of customer name should be bold
12. The chat message list shall be sort by date and time in descending order
13. The latest received chat message between the selected dealer and customer should be display
in single line (if the message exceeds one line, … should be displayed at the end)
14. When user taps on the chat card, the app shall take the user to chat user page
15. If no chat message in the chat page, below message shall be displayed:
 Message: Information message code- I079
16. Chat user page shall contain below elements:
 Page title “Chat - <Customer name>”
 Back button
 Dealer tab
 Admin tab
17. Back button should be displayed on top left corner of the page. If user taps on the back button,
the app shall take the user to previous page
18. Dealer tab shall contain Message display area
19. Admin tab shall contain below elements:
 Message display area
 Message input field
 SEND button
20. Message display area in both dealer and admin tabs shall display all chat messages in detail
21. Each message shall be displayed in below format
“<Sender name>: <Message>” (a white space should follow the colon)
22. Sender name can be customer and dealer / customer and admin based on the tab selection
23. The app shall display time at the end of each message
24. The messages shall be grouped by date. The date shall be displayed on top of each group
25. The message should be sort by date and time in ascending order
26. The font style of sender name should be in bold
27. Message Input field
28. The app shall allow admin to input new message in the input box
29. The input box shall have a clear icon to clear the input box content
30. When user taps the SEND button, the app shall send the message to the selected customer
31. The message should be pushed to the customer

Procedure:

1. Assuming the user already installed, used the app and quit it without logout
2. Admin taps the app icon, splash screen gets displayed followed by the home page
3. The admin taps on menu icon or swipes the screen from left edge to right to see the navigation
drawer menu
4. The admin taps on the Chat option in the drawer menu
5. The app takes the user to customer service– admin chat page
6. The list of dealer names with number of unread messages got displayed
7. The admin taps on a dealer name, the app takes the admin to Chat – By customer page
8. Chat – By customer page displays the list of customer names and corresponding chat messages
9. The admin taps on a chat card, chat user page got displayed with the chat messages sent
between the dealer and the customer
10. The admin taps on admin tab and enters a response in the input box and taps SEND button
11. The message got displayed in the message display area
12. The same message is being sent to the customer

66. WI-FI Configuration (AT-347)

Summary: As a customer, I want to configure WI-FI module so that I can communicate with
controller without sending SMS

Description:

1. The launch point for WI-FI configuration is Settings  Water Pump Controller
Installation settings  WI-FI configuration
2. The page title shall be “WI-FI Configuration”
3. Back icon should be displayed on top left corner of the page. If user taps on the back icon,
the app shall take the user to previous page
4. This page shall have below input fields:

 WLAN SSID
 WLAN PASSWORD
 TCP IP
 TCP PORT
 MY WIFI SSID
 MY WIFI PASSWORD
 APN NAME
 Device IP
 Device Port
5. Validation for input fields shall be as below:
a) Value of below fields shall be alphanumeric uppercase characters and the maximum
number of characters the app should allow is 32:
o WLAN SSID
o MY WIFI SSID
o APN NAME
b) Value of below fields should be characters with combination of lower-case, upper-case,
and Unicode. The maximum number of characters the app should allow is 20:
o WLAN PASSWORD
o MY WIFI PASSWORD
 c) Value of TCP IP and Device IP fields shall be combination of digits and dots (.). The
maximum number of characters the app should allow is 21
d) Value of TCP and Device PORT fields shall be digits and the maximum number of
characters the app should allow is 10
6. All controls shall be arranged in four sections as shown below:
 Section 1: WLAN SSID and password with a SEND button

 Section 2: TCP IP and port with a SEND button

 Section 3: My WI-FI SSID and password with a SEND and GET IP button
 Section 4: APN NAME with a SEND button

 Section 5: Device IP and Device Port with a SEND button

7. When user taps on SAVE button in any section, input values in that section should be stored
in database after successful validation only
8. SMS codes applicable when user taps on section 1 SEND button:
 SMS Code: WIFI001 and WIFI002
 Success Toast Message: Information message code- I060 which should be displayed
when message is successfully sent
 The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures
9. SMS codes applicable when user taps on section 2 SEND button:

 SMS Code: WIFI003 and WIFI004

 Success Toast Message: Information message code- I061 which should be displayed
when message is successfully sent
 The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures
10. SMS codes applicable when user taps on section 3 SEND button:
 SMS Code: WIFI005 and WIFI006
 Success Toast Message: Information message code- I062 which should be displayed
when message is successfully sent
 The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures
11. SMS codes applicable when user taps on section 3 GET IP button:
 SMS Code: WIFI008
 Success Toast Message: Information message code- I064 which should be displayed
when message is successfully sent
12. SMS codes applicable when user taps on section 4 SEND button:

 SMS Code: WIFI007

  Success Toast Message: Information message code- I063 which should be displayed
when message is successfully sent
 The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures
13. SMS codes applicable when user taps on section 5 SEND button:

 SMS Code: WIFI009 and WIFI010

 Success Toast Message: Information message code- I065 which should be displayed
when message is successfully sent
 The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures

Update on 7-Feb-17 (AT-376)

1. GET IP button shall be provided after section 5. The response for GET IP button should be
displayed in a controller response area below the button

Update on 13-Feb-17 (AT-383)

1. Below new input fields shall be added in WI-FI Configuration page:

 WLAN IP (Shall be added in Section 1)
 WLAN Port Number (Shall be added in Section 1)
 My WI-FI IP (Shall be added in Section 3)
 My WI-FI Port Number (Shall be added in Section 3)
2. Please refer section 2 for IP and port validations
3. It is not required to send above 4 fields to the controller
4. Below input fields shall be removed:
 Device IP
 Device Port

Update on 14-Feb-17 (AT-391)

SMS Changes in section 1 and 3:

1. SMS codes applicable when user taps on section 1 SEND button:
 SMS Code: WIFI001, WIFI002, WIFI009 and WIFI010
 Success Toast Message: Information message code- I060 which should be displayed
when message is successfully sent
  The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures
2. SMS codes applicable when user taps on section 3 SEND button:

 SMS Code: WIFI005 and WIFI006, WIFI011 and WIFI012

 Success Toast Message: Information message code- I062 which should be displayed
when message is successfully sent
 The SMS should be sent one by one with 5 seconds interval. Display one failure message
for both SMS failures

Update on 20-Feb-17 (AT-400)

Allow all special characters in SSID and password fields

67. WI-FI - App Communication with Controller (AT-379)

1. The app should be able to communicate with controller in below scenarios:

 Scenario 1: Controller and app both are within same local network (Communication
between app and controller is via router)

 Scenario 2: Hot spot connectivity. No internet required

2. The operation mode should be WI-FI for scenario 1 and Hot Spot for scenario 2
3. When customer turns ON WI-FI mode, the app should check whether values for below fields
are populated since it is required for WI-FI communication:
 WLAN SSID
 WLAN PASSWORD
 WLAN IP
 WLAN Port Number
4. If any of the WLAN fields are empty, the app should display below message. The app should
not turn ON the WI-FI mode:
Message code: Information message code- I066
5. When customer turns ON Hot Spot mode, the app should check whether values for below
fields are populated since it is required for Hot Spot communication:
 MY WIFI SSID
 MY WIFI PASSWORD
 MY WIFI IP
 MY WIFI Port Number
 6. If any of the MY WIFI fields are empty, the app should display below message. The app
should not turn ON the Hot Spot mode:
Message code: Information message code- I071
7. If values for all WLAN fields are available, WI-FI mode should be turned ON
8. If values for all MY WI-FI fields are available, Hot spot mode should be turned ON
9. The app allows controller response against an already sent message. It cannot receive
message from controller automatically in WI-FI mode (It is not recommended to keep socket
opened)
10. The app shall send messages with customer registered mobile number, controller QR code
and message code
11. The app shall use all message codes same as SMS codes
12. Similar to SMS, all send and receive messages to and from the controller should be stored in
database

68. Message Code Extraction (AT-381)

Description:

1. The app should read controller responses via all operation modes
2. SMS response format for status and fault conditions:
Message code: Information message code- I067
3. WIFI socket response format for status and fault conditions:
Message code: Information message code- I072
4. If the message received via SMS, app should:
 Check whether first 5 literal in the message are digits, then it would be a controller status or
fault message
 Extract last 3 digits from the 5 digits, the result is the message code
 Check sender SIM number and retrieve corresponding controller code from the app. The
message should be stored under that controller code
5. If the message received via WIFI:
 Delim_Code = “ $D,”
 If the message contains the string Delim_Code, then it would be a controller status or fault
message
 Look for the string Delim_Code and retrieve the string preceding Delim_Code. The result is
controller code
 The message should be stored under the extracted controller code
  Retrieve 5 digits after the string Delim_Code. Extract last 3 digits from the 5 digits, the result
is the message code
6. If the message is a static status or fault message, it would contain:
 Five digit numeric codes instead of complete description
 Date, time and other real-time details
7. Example:
 Description for the error message code 101 is “MOTOR OF BECAUSE OF STARTER TRIP
MOTOR STARTED WITH 3 PHASE ,(MSG)”
 But the controller response is “31101 TRIP-1 DATE=01/01/04 TIME=00:03:31
FROM:NIAGARA MT = 00:02:11-006/000” which does not have the error description
8. If the message is a dynamic status or fault message, it would contain:
 Five digit numeric codes
 Complete description
 Date, time and other real-time details
9. Example:
 Description for the status message code 044 is “P1 ZONE= 999 CLOSE ZONE= 999 OPEN
TIM=00:00:00”
 Controller response is ”57044 P1 ZONE= 001 CLOSE ZONE= 002 OPEN TIM=00:00:00
DATE=01/01/04 TIME=00:03:57 FROM:NIAGARA MT = 00:02:11-006/000”
10. The app should extract the code from the message string and retrieve corresponding message
description from [Controller Status or Fault Messages
Page|https://iexemplar.atlassian.net/wiki/display/AT/Controller+Status+or+Fault+Messages]
11. The message codes from 001 to 100 are status messages from controller
12. The message codes from 101 to 120 are fault messages from controller

69. Controller Fault Messages (AT-163)

Summary: As a customer, I want to view controller fault messages so that I can take necessary
action

Description:

1. The alert icon in home page shall be changed to button with alert image
2. The new alert button should show the number of new messages as superscript, if any
3. Please refer [Agritel – Controller Status or Fault
Messages|https://iexemplar.atlassian.net/wiki/display/AT/Controller+Status+or+Fault+Message
s] for controller fault messages
4. The alert button in home page shall display the number of latest unread messages (with fault
condition only) from the controller
5. When user taps on alert button in home page, the app shall take the user to controller fault
messages page
6. The page title shall be “Controller fault messages”
7. The page shall have a back button on top left corner of the page. When user taps on the button,
the app shall take the user to previous page
8. Once user navigates back to home page, the alert button count should be zero until a new
response received from the controller with fault condition
9. Controller fault messages page shall display fault messages only
10. The page shall display latest 50 messages. It shall include both old and new messages
11. The new messages should be differentiated from old messages until it is read by the user
12. Message code shall be extracted using the logic in AT-381
13. Look for message description in confluence page using the message code
14. This page shall display the list of message description retrieved from confluence page followed
by the actual message with comma delimiter
Ex:
AUTO ON POWER ON MOTOR ON MOTOR STARTED WITH 3 PHASE, 09001 DATE=29/03/2017
TIME=11:03:31 OPERATED BY:7373745677 FROM:NIAGARA MT = 00:02:11-006/000
15. The list shall be sort by message sent (by the controller) timestamp in descending order
16. The list shall contain
 Received timestamp left aligned in first row
 Message description in second row
17. Timestamp format shall be the date followed by time which would be in the controller message.
Timestamp font style shall be bold
Ex: 29/03/2017 11:03:31

70. Reports Page (AT-377)

1. Introduce a button or icon named REPORTS in view controller – customer page

2. When user taps on REPORTS button, the app shall take the user to reports page
3. Reports page shall have a static menu with below elements:

 Pump Runtime

 Zone Runtime
 Fertilizer Pump Runtime
 Green House Runtime
 Standalone Zone Runtime
 Mapped Nodes
 Moisture Sample
  Send and Receive Messages
4. When user taps on a menu element, the app shall take the user to corresponding report
5. Mobile app should call responsive web page of all above reports based on the date criteria.
Please refer report stories (AT-395, AT-390, AT-396, AT-435, AT-355, AW-40, AW-41, AW-42)
for date criteria
6. The page shall have a back button on top left corner of the page. When user taps on the
button, the app shall take the user to previous page
7. The reports icon in quick menu should also take the user to reports page

71. Change Request – SMS related changes (AT-427)

1. Drip common settings: Rename Valve scan to Valve in Common valve scan page
2. Agri-Irrigation: Fertilizer time in program settings should be in minutes and seconds
3. Green House: View message added for Program Start from page (Change in SMS only not
new)
4. Agri-Irrigation: View added for fertilizer flow calibration in Program common settings
5. Drip Common Settings:
a) View added for Maintain PH value
b) ON/OFF button added for Program Cycle Selection
c) View added for Program Cycle Selection
6. Agri-Irrigation: Remove below pages in Program Common Settings:
a) Time mode
b) Flow mode
c) Moisture mode
d) Level mode
e) View mode
f) Sensor rate
g) Flow calibration
h) Level calibration
i) Moisture calibration
j) Light Density calibration
7. Agri-Irrigation: Calibration sub-menu for Program Common Settings can be removed
8. Agri-Irrigation: New menu list for Program Common Settings is as below:
a) Adjust Percentage
b) CT PT Calibration
c) Fertilizer Calibration
d) Green House Calibration
9. Agri-Irrigation: New page shall be added in program settings. The page shall have 3 sections
with below controls:
a) Section 1: Mode ON / OFF
 Dropdown with options - Timer, Flow, Level and Moisture. Default is Timer
 ON/OFF button
 SEND button. When user taps on send button, ON/OFF shall be send to the
controller for the selected mode
b) Section 2: Sensor Rate ON / OFF
 Labels - Flow, Humidity, Temperature and Moisture
 Four ON / OFF buttons for each label
 SEND button for each label. When user taps on send button, ON/OFF shall be send
to the controller for the corresponding mode
c) Section 3:
 VIEW and CANCEL buttons
 When user taps on VIEW button, SMS should be sent to the controller and response
should be displayed in view area
10. Feedback Settings: SMS changed for Complete Controller Status
11. View Controller page:
a) View icon for Operation mode SMS. When user taps on it, view SMS should be sent and
response should be displayed in a view area
b) A new operation mode should be added with ON/OFF button – SMS Application Mode
12. Light Settings:
a) New page for entering Latitude and Longitude values
b) The app shall allow user to input numeric values between 0 and 99
c) The app shall allow positive values only
13. Water Pump Controller: SMS changed for below pages in Installation Settings module:
a) Conference call
b) Register for service
 c) Target Registration
14. Green House Settings: SMS changed for below pages:
a) Humidity
b) Temperature
c) Light Density
d) Program Cycle Selection
15. Green House Settings: View added in Light Density page
16. Label rename:
a) Green House: Rename the labels Program <#> to Program Cycle <#> in Program Cycle
Selection page
b) Green House: Add the label "Green Program Cycle" for ON/OFF button in Green House
RTC Timer page
c) Feedback and Light Settings: Rename the label SMS Limit to SMS Limit per Day

72. Change Request – SMS related changes 1 (AT-430)

1. View controller page:

 Provide a button near operation mode section
 Button name should be WIFI Reset
 When user taps on WIFI Reset button, below message should be sent to the controller:
Message Code: IDSET039
 Message code for the operation mode “SMS Application Mode” is IDSET037
 Message code for View icon in Operation mode is IDSET038
2. Change from original story: Green House Calibration not required in Agri-Irrigation -
Program Common Settings
3. Remove DND SMS Scan page from Feedback Settings
4. Add label “Program Cycle” for ON/OFF button in Light  RTC Timer page
5. When user tries to turn ON WIFI mode without selecting either WAP or WPS mode:
Warning message code: W062
73. Change Request – SMS related changes 2 (AT-442)

1. Points 6, 7, 8 and 9 in original story (AT-427) shall be ignored

2. Below is the revised menu for Program Common Settings module:
 Adjust Percent

 Timer Mode
 Flow Mode
 Moisture Mode

 Level Mode
 View Mode

 Sensor Rate
 Calibration
3. Program common settings module can be navigated thru program settings menu. User can
select a program number before navigating to program common settings. The selected
program number shall be displayed in below pages along with the title:

 Timer mode
 Flow mode

 Moisture mode
 Level mode
4. Similarly program number shall be displayed in sensor rate page
5. SMS for below pages has been changed, please refer [Agri-irrigation
SMS|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-+Agri-Irrigation] for updated
SMS codes:

 Timer mode
 Flow mode

 Moisture mode
 Level mode
 Sensor Rate
6. Below pages shall be removed from the application. It is no longer required:
 Flow calibration
 Level calibration
  Moisture calibration

 Light density calibration

7. View shall be added for fertilizer flow calibration page. Please refer [Agri-irrigation
SMS|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-+Agri-Irrigation] for SMS code

74. Settings Module - Success Messages (AT-431)

1. Below format should be followed for all success messages in settings module:
a) If SMS triggered for ON with SEND button, the message can be in below format:
“<Page title> ON controller message sent”
b) If SMS triggered for OFF with SEND button, the message can be in below format:
“<Page title> OFF controller message sent”
c) If SMS triggered for just SEND button, the message can be in below format:
“<Page title> controller message sent”
d) If SMS triggered for VIEW button, the message can be in below format:
“View <Page title> controller message sent”
e) Below are exception pages:
 Installation Settings  Status SMS page: “Status SMS ON sent” or “Status SMS OFF
sent”
 Installation Settings  Controller SMS Balance: “Controller SMS balance value sent”
 SMS for Feedback settings  SMS page
o ON SMS message: “SMS ON Sent”
o OFF SMS message: “SMS OFF Sent”
 SMS for Feedback settings  View Valve Condition page: “View valve condition sent”
 SMS for Feedback settings  View Test page: “View test sent”
 SMS for Feedback settings  View Setting for DNDSMS page: “View Setting for
DNDSMS sent”
 SEND button in Feedback Settings, Light Settings  Controller SMS Limit: “Controller
SMS Limit ON sent” or “Controller SMS Limit OFF sent”
 Input value and tap SEND button in Feedback Settings, Light Settings  Controller SMS
Limit: Controller SMS Limit sent
 View button in Feedback Settings  Controller SMS Limit: View controller SMS Limit
sent
 When user taps on GET HUMIDITY button in Green House settings  Humidity
Temperature Calibration page, message should be: “Get Humidity controller message
sent”
 When user taps on GET TEMPERATURE button in Green House settings  Humidity
Temperature Calibration page, message should be: “Get Temperature controller
message sent”
  If SMS triggered for VIEW button with page title “View Set <n> where n represents a
numeric values from 1 to 11, the message can be in below format:
“<Page title> controller message sent”

75. Settings Page - UI Update 3 (AT-439)

1. Settings - Agri-Irrigation - Drip Common Settings - Program start:

The app should receive zone number input from user. The zone number should be 3 digits
and maximum value should be 128. The zone number should be sent to the controller using
message code: 22 in [Drip Common
Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-+Agri-Irrigation#space-menu-
link-content]

2. Settings - Water Pump Controller - Installation Settings - Voice Feedback:

The app should allow user to toggle voice feedback and send the same to the controller.
Message code: 24 in [Installation
Settings|https://iexemplar.atlassian.net/wiki/display/AW/SMS+-+Water+Pump+Controller]

76. Configure Notification (AT-473)

Summary: As a customer, I want to configure error notification so that I can suppress unwanted
message in my inbox (fault message page)

Description:

Settings Main menu

1. A new menu option shall be added in settings main menu

2. Name of the menu item shall be “Notification”
3. The new menu item shall be a default item. User will not be able to remove it from the settings
main menu
4. When user taps on the new menu item, Configure notification page shall be displayed

Configure Notification page

5. The page name shall be “Configure Notification”

6. Configure notification page shall list all [fault message (Message Code Description
column)|https://iexemplar.atlassian.net/wiki/display/AT/Controller+Status+or+Fault+Messages]
with error codes between 101 and 120
7. The list shall have a checkbox prior to the fault message
8. All checkboxes should be checked by default
9. SUBSCRIBE and CANCEL buttons shall be displayed at bottom of the page
10. When user unchecks a particular fault message and subscribes it, that message shall be filtered
out while displaying it in fault message page
11. Upon successful subscription, the app shall display below message:
Message: Information message code- 1082
12. The unchecked message shall still be displayed in toast and send & receive report
13. If a user unchecks a fault message, that message should be filtered out for primary user and all
sub-users
14. The app shall allow user to select or deselect all items in one tap
15. CANCEL button shall cancel the operation and takes the user to previous page
16. A back button shall be provided at top left corner of the page. When user taps on it, the app
shall take the user to previous page
17. This functionality should be accessible thru My Device and Shared device tabs

77. Change request and Issues reported on 11 July 17 (AT-479)

Description:

1. The app to send #GETMOS SMS

Module - Mapped node report
a) When user taps on GENERATE button in the report, mobile app shall send the SMS
#GETMOS to the controller and web app shall send the same message thru http
b) Regardless of operation mode, mobile app shall send the message thru SMS only
c) It is not required to display controller response against this message

2. Display both menu options when 2 Phase is ON

a) If 2 phase on, the app shall display both 2 phase and 3 phase menus
b) If 2 phase off, the app shall display 3 phase menu only
c) This is applicable for both mobile and web

3. The app to send #SETSERIAL SMS

Module - Feedback Settings
a) Rename “Network status settings” label to "Set Serial"
b) When user hit the send button in this page, the app should send the SMS
#SETSERIAL to the controller
c) This is applicable for both mobile (all modes) and web
4. Fault message section in view controller page does not get refreshed
a) This functionality is working fine. No change required

5. Send And Receive report

a) The report content shall be displayed in descending order (controller response date)

6. The fault notification content shows 999 as node number

a) The standard description for the fault message with code 114 shall be changed to
"ZONE SKIPPED BECAUSE OF NO FEEDBACK, ZONE NUMBER…"

7. Live update content display

a) Mobile app - Live update is left aligned instead of center
b) Web app - Live update message is concatenated with a + symbol at the end

8. The app throws server error during the process of node unmapping
a) Server error is due to poor network connection. The device should be connected to
uninterrupted network

9. Configure CCTV app link

a) The change request is to have an input field to enter CCTV link at controller level

10. The app to send SM#8185 during replace controller

a) AS IS - to send SMS only when SIM number changed
b) TO BE - to send SMS when either of the data element changed (SIM number or QR code)

11. Controller ON/OFF in web

a) AS IS – Controller status can be changed in edit mode only
b) TO BE – Controller status shall be changed both in view and edit mode

12. Resend IDSET SMS

a) AS IS – Once a node is mapped to a controller, the node map SMS (IDSET) cannot be
resend
b) TO BE – The app to allow sending node map SMS even after it is mapped to a
controller
 When user taps on a mapped node, the app takes the user to view mapped node
page
 Send icon/button will be provided in view mapped node page
 When user taps on it, corresponding map node message will be sent to the
controller in the selected mode

13. RESET ID SMS

Module – Edit / Delete Zone & Common ID Settings
a) RESET ZONE and RESET ID SMS unsuccessful
b) Both functionalities are working fine. No change required
14. Country code input
a) The app shall provide input area to enter country code for below screens:
 Registration for service
 Conference call
 Target number in WLC

15. Issue description

Module - Service Request
a) The app shall provide input box to enter issue description

16. Shortcut for edit zone functionality

a) The change request is to provide 'RESET ZONE' and 'View' button/icon in the view
zone page

17. Issue in WPS functionality

a) This functionality is working fine. No change required

18. Default Current date

Module – Add product
a) To display current date as default date for date field

19. Report screen theme color

a) The theme color for report screen does not match with other screens

20. Node name – duplicate check validation

a) AS IS – The app allows unique node for a user
b) TO BE – The app shall allow unique node name for a controller (user + controller
combination)
o When user creates a new node or edit it, the node name can be made unique for
a user only
o When user maps the node to a controller, it can be set unique for a user and
controller
o As per client confirmation, the functionality to enter a name for new node while
creating and editing will be removed
o Customer can enter node name in mapped node module only

21. Delete controller functionality

 a) AS IS scenario: When a customer deletes his controller, the controller will be deleted
and all nodes, zones and programs associated to it will also be deleted
b) TO BE scenario: When a customer deletes his controller, all nodes, zones
and programs associated to it will be deleted but the controller should not be
deleted

Comments:
1. Label for ON/OFF button: CCTV access
2. Label for app URL: CCTV Link
3. Place holder for app URL input box: Please enter CCTV Link