Mobile Application Functional Specification Document...x Provide consistency in user experience for...

Attachment 1

Child Support Mobile Application 1 Functional Specification Document

Attachment 1:

Mobile Application Functional Specification Document

Attachment 1


Table of Contents

1. Overview ........................................................................................................................ 8

Kony Guidelines and Patterns Used for Mobile Application Design ..................... 8

Child Support Web Portal Current & Projected Statistics....................................... 8

Current & Projected Web Portal Users .......................................................................... 8

Child Support Customer Web Portal Pages .................................................................. 9

Current Architecture, Web Services and WSDLS ....................................................... 10

Styling & Branding Requirements ........................................................................... 10

ODJFS Logo ................................................................................................................. 11

Core Elements Color Palette ....................................................................................... 11

Typography ................................................................................................................... 12

Fonts ............................................................................................................................. 12

Photography ................................................................................................................. 12

Images .......................................................................................................................... 12

Iconology ...................................................................................................................... 12

Kony Visualizer Supported Devices and Software ................................................ 13

Apple Devices & iOS .................................................................................................... 13

Android Devices ........................................................................................................... 15

App Marketing ............................................................................................................ 15

Apple Mobile Application .............................................................................................. 15

6.1.1. Apple App Store Badge ................................................................................................ 15

6.1.2. Apple App Store Product Name ................................................................................... 15

6.1.3. Apple App Store - URL address naming...................................................................... 16

Android Mobile Application........................................................................................... 16

6.2.1. Google Play Badge ...................................................................................................... 16

6.2.2. Google Play Product Name.......................................................................................... 16

6.2.3. Google Play - URL address naming ............................................................................ 16

Mobile App Design ..................................................................................................... 16

UX & UI Features ......................................................................................................... 16

Native Device Functions .............................................................................................. 17

FUNCTIONAL REQUIREMENTS................................................................................ 18

Mobile App Platform ..................................................................................................... 18

Branding ....................................................................................................................... 18

Attachment 1


User Experience/User Interface (UX/UI)...................................................................... 19

User Profile/Demographics .......................................................................................... 19

App Icon ....................................................................................................................... 20

Menus ........................................................................................................................... 20

Splash Screen .............................................................................................................. 20

Login Screen ................................................................................................................ 20

Touch ID Screen .......................................................................................................... 21

User Login Validations ................................................................................................. 22

Forgot User ID Screen ................................................................................................. 22

Forgot Password Screen .............................................................................................. 23

Registration .................................................................................................................. 23

Need Help Screen ........................................................................................................ 23

Change Password ........................................................................................................ 23

Change E-mail .............................................................................................................. 23

Home Screen................................................................................................................ 24

Support Order Detail Screen ........................................................................................ 25

County Agency Directory Screen ................................................................................. 26

County Agency Screen ................................................................................................ 26

Personal Screen ........................................................................................................... 26

Contact Information Screen ......................................................................................... 27

Child Information Screen .............................................................................................. 27

Employer Information Screen ...................................................................................... 28

Health Insurance Screen .............................................................................................. 29

Messaging .................................................................................................................... 29

County Bulletins ........................................................................................................... 30

Customer Alerts ............................................................................................................ 31

Upload Documents ....................................................................................................... 31

Alerts and Notification Preferences.............................................................................. 31

Mobile Application Performance Metrics ..................................................................... 32

Prototypes and Use Cases Targeted for 1st Mobile Application Release ............ 32

App Menu .................................................................................................................... 33

App Menu Overview ..................................................................................................... 33

UI & Widget Overview .................................................................................................. 33

Use Cases .................................................................................................................... 33

Attachment 1


Hamburger Menu ........................................................................................................ 34

Screen Overview .......................................................................................................... 34

UI Overview .................................................................................................................. 35

Widget Behavior ........................................................................................................... 35

Splash Screen Specifications ................................................................................... 35

Screen Overview .......................................................................................................... 35

UI Overview .................................................................................................................. 35

Widget Behavior ........................................................................................................... 35

Use Cases .................................................................................................................... 36

Login Screen Specifications ..................................................................................... 36

Screen Overview .......................................................................................................... 36

UI Overview .................................................................................................................. 37

Widget Behavior ........................................................................................................... 37

Touch ID Screen Specifications ............................................................................... 42

Screen Overview .......................................................................................................... 42

UI Overview .................................................................................................................. 43

Widget Behavior ........................................................................................................... 43

Use Cases - iOS Biometric Test Scenarios ................................................................. 43

Use Cases - Android .................................................................................................... 44

Forgot User ID Screen Specifications ..................................................................... 46

Screen Overview .......................................................................................................... 46

UI Overview .................................................................................................................. 46

Widget Behavior ........................................................................................................... 46

Use Cases .................................................................................................................... 47

Forgot Password Screen Specifications ................................................................. 49

Screen Overview .......................................................................................................... 49

UI Overview .................................................................................................................. 49

Widget Behavior ........................................................................................................... 49

Use Cases .................................................................................................................... 50

Home Screen Specifications ..................................................................................... 52

Screen Overview .......................................................................................................... 52

UI Overview .................................................................................................................. 52

Widget Behavior ........................................................................................................... 53

Use Cases .................................................................................................................... 55

Attachment 1


County Bulletins Screen Specifications .................................................................. 57

Screen Overview .......................................................................................................... 57

UI Overview .................................................................................................................. 57

Widget Behavior ........................................................................................................... 58

Use Cases .................................................................................................................... 58

Customer Alerts Screen Specifications .................................................................. 59

Screen Overview .......................................................................................................... 59

UI Overview .................................................................................................................. 59

Widget Behavior ........................................................................................................... 59

Use Cases .................................................................................................................... 60

Support Order Detail Screen Specifications ........................................................... 61

Screen Overview .......................................................................................................... 61

UI Overview .................................................................................................................. 61

Widget Behavior ........................................................................................................... 63

Support Order Detail – Explanation of Terms .............................................................. 63

Use Cases .................................................................................................................... 65

Payment History Screen Specifications .................................................................. 67

Screen Overview .......................................................................................................... 67

UI Overview .................................................................................................................. 67

Widget Behavior ........................................................................................................... 68

Personal Screen Specifications ............................................................................... 68

Screen Overview .......................................................................................................... 68

UI Overview .................................................................................................................. 68

Widget Behavior ........................................................................................................... 69

Use Cases .................................................................................................................... 69

Contact Information Screen Specifications ............................................................ 70

Screen Overview .......................................................................................................... 70

UI Overview .................................................................................................................. 70

Widget Behavior ........................................................................................................... 71

Use Cases .................................................................................................................... 71

Health Insurance Screen Specifications ................................................................. 72

Screen Overview .......................................................................................................... 72

UI Overview .................................................................................................................. 72

Widget Behavior ........................................................................................................... 72

Attachment 1


Use Cases .................................................................................................................... 73

Employer Screen Specifications .............................................................................. 73

Screen Overview .......................................................................................................... 73

UI Overview .................................................................................................................. 74

Widget Behavior ........................................................................................................... 74

Use Cases .................................................................................................................... 74

Child Information Screen Specifications ................................................................ 75

Screen Overview .......................................................................................................... 75

UI Overview .................................................................................................................. 75

Widget Behavior ........................................................................................................... 76

Use Cases .................................................................................................................... 76

County Agency Directory Screen Specifications ................................................... 77

Screen Overview .......................................................................................................... 77

UI Overview .................................................................................................................. 77

Widget Behavior ........................................................................................................... 77

Use Cases .................................................................................................................... 77

County Agency Specifications ................................................................................. 78

Screen Overview .......................................................................................................... 78

UI Overview .................................................................................................................. 78

Widget Behavior ........................................................................................................... 79

Use Cases .................................................................................................................... 79

Change Password Specifications ............................................................................ 81

Screen Overview .......................................................................................................... 81

UI Overview .................................................................................................................. 81

Widget Behavior ........................................................................................................... 81

Use Cases .................................................................................................................... 82

Change E-mail Address Specifications ................................................................... 83

Screen Overview .......................................................................................................... 83

UI Overview .................................................................................................................. 84

Widget Behavior ........................................................................................................... 84

Use Cases .................................................................................................................... 84

Need Help Screen Specifications ............................................................................. 86

Screen Overview .......................................................................................................... 86

UI Overview .................................................................................................................. 86

Attachment 1


Widget Behavior ........................................................................................................... 86

Use Cases .................................................................................................................... 87

Screen Layouts ........................................................................................................... 88

Figure 1 – Splash ......................................................................................................... 89

Figure 2 - Login ............................................................................................................ 90

Figure 3 – Touch ID...................................................................................................... 91

Figure 6 - Registration .................................................................................................. 92

Figure 7 – Need Help ................................................................................................... 93

Figure 8 - Home ........................................................................................................... 94

Figure 9 - County Bulletins ........................................................................................... 95

Figure 10 - Customer Alerts ......................................................................................... 96

Figure 11 - Support Order Detail – Case, Support & Balance Information ................. 97

Figure 12 - Support Order Detail – Payments ............................................................. 98

Figure 13 – Payment History ....................................................................................... 99

Figure 14 – Message Center ..................................................................................... 100

Figure 15 – Message (threads) .................................................................................. 101

Figure 16 - New Message .......................................................................................... 102

Figure 17 - Reply ........................................................................................................ 104

Figure 18 - Hamburger Menu ..................................................................................... 105

Figure 19 - Change Password ................................................................................... 106

Figure 20 - Change E-mail Address .......................................................................... 107

Figure 21 - County Agency Directory ......................................................................... 108

Figure 22 - County Agency ........................................................................................ 109

Figure 23 - County Agency – Get Directions Permissions ........................................ 110

Figure 24 - County Agency – Get Directions Launch Native Map ............................ 111

Figure 25 – Personal .................................................................................................. 112

Figure 26 – Contact Information ................................................................................ 113

Figure 27 - Health Insurance ..................................................................................... 115

Figure 28 – Employer Information.............................................................................. 116

Figure 29 – Child Information – Obligee .................................................................... 118

Figure 30 – Child Information – Obligor ..................................................................... 119

References ................................................................................................................ 120

Attachment 1


1. Overview The State of Ohio, Office of Child Support (OCS), has undertaken a project to enhance the ODJFS Child Support system by expanding the availability of information beyond the Customer Service Web Portal to a mobile platform. The effort has been broken into several statements of work.

SOW.01: Mobile Application Functional Specification Document SOW.02: Mobile Application Technical Design Document SOW.03: Message Center Document Upload Functional Specification Document SOW.04: Customer Service Web Portal Registration Enhancements BRD

Kony Guidelines and Patterns Used for Mobile Application Design Provide standard views and controls that user is typically accustomed to Keep the solution lightweight and direct. Provide consistency in user experience for similar functionality. Ensure application design is information and technology driven for best user

experience. Design solution considering speed, efficiency and reassurance. Ensuring consistency in user interface workflows, menu types and buttons. Use appropriate readable fonts, large icons and large enough touch mode “hit

areas.” Ensure less click to reach the required information [3 clicks !!!!]. Involve users in UI design process to ensure the application is designed

appropriately to their needs. © Copyright 4/20/17 Kony, Inc.

Child Support Web Portal Current & Projected Statistics Current & Projected Web Portal Users

The following statistics, as of May 2017 month-end, were provided by OCS.

Current number of web portal users: 396,378 unique participants

Projected users: 1,293,079 Total unique child support participants eligible to use web

portal. Of that: 299,486 currently registered 993,593 remaining eligible child support participants that have not

registered

Attachment 1


Child Support Customer Web Portal Pages In addition to features such as e-mail notifications for payments and missing information (which customers can opt into receiving), the customer web portal provides registered customers with online access to important child support data. The following customer web portal pages were considered in this effort to identify the best way to provide the information and functions in a mobile app experience: new user registration; activation; and the authentication processes (including the Forgot Password and Forgot User ID processes).

New User Registration & Activation Existing User

Forgot Password Forgot User ID

State Newsflash (displayed on customer web portal Login screen) County Bulletin Board Customer Dashboard

Customer Alerts Recent Payment Information New Messages from the County New Messages to the County

Message Center Message List View Message Threads Send and respond to a message

Personal My Contact Information My Employer My Health Insurance Child Information Change Password Change E-mail Address E-mail Notification Preferences

Payments My Payment Information View Payment History How My Payments are Received

Cases My Support Order(s) and Balance Information My Cases

Attachment 1


Current Architecture, Web Services and WSDLS

The current architecture, web services, and WSDLS for the web portal are depicted below. This technical platform was considered when evaluating the web portal access to SETS data and the complexity of providing this data to a mobile platform. Please refer to the D02 Mobile Application Technical Design Document for further information.

Styling & Branding Requirements The Ohio Department of Job and Family Services (ODJFS) Office of Communications is responsible for ensuring that the agency presents a consistent image at all times to make it clear that their offices and programs are part of ODJFS and part of Ohio’s state government. This includes all logos, colors, fonts, and images in websites and mobile applications.

Attachment 1


The following ODJFS Branding Guideline information will be applied within the Child Support mobile application.

Please note that the Contractor shall not do the following without prior, written consent from the State:

1. Advertise or publicize that the Contractor is doing business with the State;

2. Use this Contract as a marketing or sales tool; or

3. Affix any advertisement or endorsement, including any logo, graphic, text, sound, video, and company name, to any State-owned property, application, or website, including any website hosted by Contractor or a third party.

ODJFS Logo The logo has color, black and white, and reversed-out white versions. The logo is a unique design and cannot be modified in any way.

The ODJFS logo will be included on the Splash screen along a banner displaying “The Office of Child Support.” The Splash screen background will also contain the same image as the Child Support web portal login screens.

Core Elements Color Palette To ensure that the Ohio brand communicates consistently and true to brand equity, the following 9-color palette has been developed by ODJFS for use in all applications. The core colors for the Ohio logo are Pantone 186 red and Pantone 195 red. The other colors complement the core colors.

These colors will be applied throughout the mobile application screens.

Attachment 1


Typography 4.3.1. Fonts The mobile app text will utilize the core pantone font colors. The font size will be identified based on the best mobile app screen display.

Photography 4.4.1. Images ODJFS must own the rights for all images used in the mobile app.

Iconology The following icons are utilized in the Child Support Customer Web Portal:

Image Description

“Hamburger Menu” – mobile application menu for options not displayed in the app menu at the bottom of the screen.

Switch widget to turn on / off feature (e.g., Touch ID)

Attachment 1


Image Description

Navigate to screen from hamburger menu.

New message to customer from county

Number of county bulletins or customer alerts

The total number of unread messages.

New message button control, to create a new message.

Capture image to attach to message.

Delete (Archive) message thread

More

Previous

Pop-up available on tap.

User selection

State newsflash alert.

Kony Visualizer Supported Devices and Software Device support will be limited to the supported mobile device operating systems as documented by Kony.

Apple Devices & iOS The following is a list of supported devices for the iOS platform along with the corresponding form factors. However, the Child Support mobile app will perform best with iOs 7 +.

Note: iPhone 4 will not be supported with the OCS mobile app design, nor will the app be tested on an iPhone 4.

Attachment 1


Device/Family Form Factor iPhone

iPhone 5 1136×640 iPhone 5C 1136×640 iPhone 5S 1136×640

iPhone 6 1334×750 iPhone 6 Plus 1920×1080

iPhone 6 S 1334×750 iPhone 6 S Plus 1920×1080

iPhone SE 1136×640 iPhone 7 1334×750

iPhone 7 Plus 1920×1080 iPhone 8 1334×750

iPhone 8Plus 1920×1080 iPad

iPad 2 1024x768 iPad 3 2048×1536 iPad 4 2048×1536

iPad Air 1 2048×1536 iPad Air 2 2048×1536 iPad Pro 2732×2048 iPad mini 1024×768

iPad mini 2 2048×1536 iPad mini 3 2048×1536 iPad mini 4 2048×1536

Kony supported versions for iOS

iOS Versions Kony Release

Version 7.x

iOS 7.0.6* onwards

iOS 8.x

iOS 9.x

iOS 10.x iOS-GA-7.1.1.3

Attachment 1


Android Devices All devices, which are compliant to CDD are supported. All those devices with Google Play client software can be assumed as CDD compatible devices. However, the Child Support mobile app will perform best with Android Version 5 +.

Supported versions for Android OS

Kony Release Version 7x

Android Versions

4.0 - 4.0.2

4.0.3 - 4.0.4

4.1

4.2

4.3

4.4

5

6 AND-GA-7.1.1.1 7

App Marketing Apple Mobile Application

Based on App Store Marketing Guidelines

https://developer.apple.com/app-store/marketing/guidelines/#appstore

6.1.1. Apple App Store Badge Apple App Store Badge:

https://developer.android.com/distribute/marketing-tools/brand-guidelines.html

6.1.2. Apple App Store Product Name Ohio Department of Job Family Office of Child Support for iPhone and iPad.

App Store product name - lead with the company name followed by the app name and end with the appropriate Apple product names. For example, it is correct to say “Company name App name for iPhone, iPad, and iPod touch.”

Attachment 1


6.1.3. Apple App Store - URL address naming Acceptable: www.company.com/app/iphone or www.company.com/ipad

Android Mobile Application

6.2.1. Google Play Badge Google Play is a digital distribution service operated and developed by Google. It serves as the official app store for the Android operating system, allowing users to browse and download applications developed with the Android software development kit (SDK) and published through Google.

6.2.2. Google Play Product Name Ohio Department of Job Family Office of Child Support for Android.

6.2.3. Google Play - URL address naming com.companyname.applicationname

Mobile App Design

UX & UI Features

Actions Gestures Transitions Native Interactions

Pull to refresh Zoom In & Out Accordion Screen

Wallet

Parallax Support Swipe: Top, right, bottom, left

Dimming Health Kit

Scroll to anchor Pinch Concertina Fold

Touch ID

Scroll to widget Rotate Dynamic Maps

Drag & Drop Tab Swipe Blurring Contacts

Custom loading indicator

Widget/Object level transition

Calendar

Phone book index Social

Attachment 1


Actions Gestures Transitions Native Interactions

Messaging

© Copyright 4/20/17 Kony, Inc.

Native Device Functions Utilizing native device functions allows mobile applications to create stronger connection with users and continue to build on and leverage ongoing technical innovations..

Native Feature JFS - Use Cases

Minimize Forms & Click Through Optimization of forms and screens to provide easier access to frequent functions through floating menus, tabs, and dynamic panels

TouchID / Fingerprint Authentication Secure member accounts & data and open up access to other Native functions

Push Notification Send mobile text reminder notifications (e.g. appointments and payments due)

GPS Location services to find nearest offices and mapping

Upload Documents Submit relevant electronic profile documentation

Photo – OCR Library Upload Photo upload of DL or State ID, W2’s, Bills, etc., for verification of employment, income, and address

Native Functional Integrations Calendars, Contacts, Maps, Phone / FaceTime © Copyright 4/20/17 Kony, Inc.

pp flow

Attachment 1


FUNCTIONAL REQUIREMENTS

SOW Mobile Application Functional Requirements

Mobile App Platform 1. Develop a Child Support mobile app that customers can launch and view

on their smartphone and tablet. 2. The app must be accessible from the Apple App Store and the Android

Google Play Store. 3. The initial mobile app releases should be designed for the following

devices: a. iPhone iOS 7.0+ b. Android 5+

4. The app must meet the Apple and Google guidelines for publishing to the stores.

5. The app must be accessible 24/7 except when backend processes are running or not available.

6. The app must provide access metrics (e.g., number of hits, pages accessed, etc.).

7. The app must provide a 5 minute ‘Idle Timeout’ feature. Note: Within the Kony mobile application, the timeout defaults to 5 and the app itself logs out the user. But, if the native controls take the user outside of the application, like in the case of Android devices, the application cannot enforce a timeout.

8. The app must display a ‘processing/loading’ icon while information loads. 9. The app must display an ‘Unable to access information’ message when

app is unable to retrieve data or encounters an issue when retrieving data (e.g., database lock, etc.).

Branding 10. The color schema of fonts, shading and images must utilize the Pantone

colors specified by the ODJFS Branding Standards. 11. The app icon must contain the ODJFS logo and be provided by or

approved by the Office of Communications. 12. The Splash screen must contain the ODJFS logo and the Office of Child

Support banner. 13. The Splash screen must contain the same background as the Child

Support web portal login screens. 14. All images and icons included in the app must be provided by or approved

by the Office of Communications.

Attachment 1



User Experience/User Interface (UX/UI) 15. The mobile app must provide a user experience that provides accurate,

timely, and well organized information. 16. The information must be retrieved from the current SETS Child Support

data. 17. The Home screen must “welcome” the user to the app. 18. The most important data to the user (support order, last payment, and

balance information) must be presented on the Home screen. 19. The mobile app must ensure data is secured by logged in customer. 20. The information must be specific to logged in customer (by case and

participant type). a. Obligor data presentation will be different than Obligee data

presentation. 21.

User Profile/Demographics 22. The mobile app customers must be obligees or obligors as established by

Ohio’s child support cases/orders. 23. SETS participants registered in the Child Support Customer Web Portal

will login to the mobile application with the same User ID and password. 24. SETS participants not yet registered in the Child Support Customer Web

Portal may register in the mobile app. 25. SETS participants must enter valid credentials to create a user login:

a. E-mail address b. Social Security Number c. Case Number d. Participant Number e. Payment card number or bank account routing number (Obligees

only) 26. SETS participants must have at least one open case to register in the

SETS Child Support portal or via the mobile app. a. If the participant has no open cases at time of registration, the

following message is displayed: Closed cases cannot be used for authorization.

27. SETS participants, who have previously registered with at least one open case, must have at least one open case to view mobile app.

a. Message displayed after Login credentials verified and after case(s) are closed:

Attachment 1



All of your cases are closed. Please contact the Office of Child Support for any information.

Note: The User Profile/Demographics requirements and any related error messages will need to be reviewed and modified per the requirements defined in the new user authorization and authentication process.

App Icon 28. The App Icon (for the App Store and Google Play Store) must contain a

JFS standard background color with the ODJFS logo and Office of Child Support text.

29. The goal is to design an icon that can be replicated for other JFS offices (e.g., Child Care, Workforce Development, etc.).

30. When the user opens the app for the first time, the app will alert the user that “this app will access location/maps and camera on your device” and provide a feature to acknowledge the feature.

Menus 31. The app menu will display at the bottom of each screen providing quick

navigation to the following functions: a. Home b. Messages c. Payment History d. Upload Documents

32. The Hamburger menu will display the following functions: a. Enable Touch ID b. Change Password c. Change E-mail Address d. Notification Preferences e. County Agency Locations f. Logout

Splash Screen 33. The Splash screen will display the ODJFS logo. 34. The Splash screen will display the picture as designed by ODJFS. 35. The Splash screen will display while the app is loading.

a. The expected loading time is 1-5 seconds.

Login Screen 36. The Login screen will require user to enter User ID and Password or

Touch ID.

Attachment 1



a. User ID text box i. User ID placeholder text: Enter User ID

b. Password text box i. Password placeholder text: Enter Password

37. The Login screen will provide Forgot User ID and Forgot Password features. a. Forgot User ID text

i. Hyperlink text to navigate to the Forgot User ID screen b. Forgot Password text

i. Hyperlink text to navigate to the Forgot Password screen 38. The Login screen will display a Login button which will initiate process to

validate user credentials. (see User Login Validations below) 39. The Login screen will display a New User Registration button.

a. The New User Registration button will navigate the user to register a new user account within the mobile app and not be a link to the web portal for registration.

40. Login credentials (user ID and password) established upon mobile app new user registration will be the same for logging into the customer web portal. a. Once the statewide State ID process is implemented, the login

credentials may require the State ID and password. 41. A Need Help button or link will navigate the user to a Need Help screen

containing buttons or links to: a. Privacy Statement b. Frequently Asked Questions (FAQs)

Touch ID Screen 42. The Touch ID feature will utilize the phone’s native Touch ID

fingerprints. a. When user is attempting to login with Touch ID and the app does

not recognize the fingerprint, the app will display error messages (e.g., Touch ID invalid. Try different finger).

b. The user has 3 attempts at logging in with their Touch ID and if unsuccessful will then have 6 Login Screen User ID/Password entry attempts before account is Locked.

c. Touch ID error messages will be displayed to the user. d. The “Enable Touch ID” feature needs to display only upon the

user’s1st login. Then the user will need to go to the Hamburger screen to enable Touch ID.

Attachment 1



43. On Android devices, the Touch ID will display a Cancel option. On iOS devices, the Touch ID will display “Enter Password” and “Cancel” options.

44. A Touch ID icon will not be displayed on the Login screen. NOTE: The Touch ID feature must be native to the device/iOS and supported on Android 6 and above.

User Login Validations 45. If the customer enters an invalid User ID or password, the following

error message displays: Invalid User ID or Invalid Password.

46. If the customer does not enter the User ID but enters a password, the following error message displays: The User ID field is missing.

47. If the customer does enter the User ID but does not enter a password, the following error message displays: The Password field is missing.

48. If the customer enters an incorrect User ID (e.g., with special character) or password (e.g., less than 6 or more than 15 characters) 6 times in 15 minutes, the account is locked, the following error message displays: This account has been locked. An e-mail has been sent to the owner of this account with instructions on how to unlock it.

Note: Currently, a User ID can only be numbers and letters (no special characters). Passwords can be number, letters, and special characters. Each must be 6-15 characters.

Forgot User ID Screen 49. The Forgot User ID screen will display a text box with label and

placeholder text: Enter your E-mail address 50. The Forgot User ID screen will display the following text below the text

box: a. (Must have an @ symbol in the E-mail address)

51. The Forgot User ID screen will include a Submit and a Cancel button.

Attachment 1



Forgot Password Screen 52. The Forgot Password screen will display a text box with label and

placeholder text: Please provide your User ID 53. The Forgot User ID screen will display the following text below the text

box: a. (6-15 characters)

Note: This directive text may change with the requirements of the statewide State ID process.

54. The Forgot User ID screen will include a Submit and a Cancel button.

Registration 55. The Registration screen will allow child support participants who are not

yet registered in the Child Support Customer Web Portal or in the mobile app to create user credentials.

Need Help Screen 56. The Need Help screen will include information to assist the user.

Initially, this screen will include the following buttons which will launch app screens or JFS web pages (TBD) displaying the information. a. Privacy Statement b. Frequently Asked Questions.

Change Password 57. The Change Password screen will allow the user to change their Child

Support customer web portal and mobile app password. 58. The Change Password screen will include the following 3 data fields:

a. Enter Your Current Password b. New Password c. Re-enter New Password

59. The Change Password screen will include Submit and Cancel buttons. 60. On click of the Submit button:

a. The new password entry will be validated with the user’s password in the system.

b. The New Password entry and the Re-enter New Password entry must be the same.

61. On click of the Cancel button, the Home screen is displayed.

Change E-mail 62. The Change E-mail screen will allow the user to change their Child

Support customer web portal and mobile app e-mail address.

Attachment 1



63. The Change E-mail screen will display the following text: Note: E-mail address must be unique.

64. The Change E-mail screen will display the user’s current e-mail address.

65. The Change E-mail screen will include the following 2 data fields: a. New E-mail address b. Re-enter E-mail address.

66. The Change E-mail screen will include Submit and Cancel buttons. 67. On click of the Submit button, the two entered e-mail addresses will be

validated. a. The New E-mail address and the Re-enter E-mail address must be

the same. b. The New E-mail address and the Re-enter E-mail address must

contain an @ special character. 68. On click of the Cancel button, the Home screen is displayed. 69. An e-mail is system generated to both the previous and the new e-mail

addresses advising user of the e-mail address change.

Home Screen 70. A “Profile” image will display in the top right section of the title bar.

Upon tap, the Personal screen will display. 71. A banner will display County Bulletins and Customer Alerts options.

a. Indicators for the number of active county bulletins and customer alerts will display.

i. Only the county bulletin(s) posted by the county of jurisdiction for the user’s open case(s) will be included in the count.

b. The count indicators will be cleared once the user has viewed the County Bulletins or Customer Alerts screen.

i. These counts will remain cleared while the user is logged into the mobile app.

ii. These counts will not display upon a subsequent login if the user has already viewed these same county bulletins or customer alerts.

iii. If a county bulletin is updated and still active at the user’s next log in, that bulletin must be included in the count displayed in the Home screen banner.

iv. If a new county bulletin is posted or a new alert is determined by the SETS mainframe query since the last user log in, then that bulletin or alert must be included in the count.

Attachment 1



72. A “Welcome, <customer first name>” will display. 73. The OCS state Newsflash (that displays on the web portal Login screen)

will display on the Home screen. 74. A section for each of the user’s open cases will include:

a. Case Number b. Order Number c. Other Party d. Balance Due (i.e., Total Unpaid Balance)

i. If the case-order has a credit balance, the label will be Credit Balance.

e. Obligee: Last Payment Received (amount and date) OR Obligor: Last Payment Sent (amount and date)

75. When the user has more than one open case, the case sections will display in order by the date of the most recent payment amount.

76. Each case section will be animated to navigate to Support Order Detail screen.

Support Order Detail Screen 77. The Support Order Detail screen will provide a link to the CSEA

information by case/county. 78. The Support Order Detail screen will display:

a. Case and order information b. Case Number c. Order Number d. Other Party e. Health Insurance Obligor f. Order Date

79. The Support Order Detail screen will display a Total Monthly Support section to include a labels and amounts (when greater than $0.00) for each of the following components: a. Child Support b. Spousal Support c. Medical Support d. Interest e. Interstate Fees f. Administrative Fees g. Other Fees h. Total Monthly Support

80. The Support Order Detail screen will display a Total Unpaid Balance section to include labels and amounts (even if $0.00) for each of the following components:

Attachment 1



a. Current Month Unpaid Balance b. Past Due Unpaid Balance c. Total Credits d. Total Funds on Hold

81. The Support Order Detail screen will display a Recent Payments section to include labels, amounts (when greater than $0.00), and dates for each of the following components: a. Disbursed to Family b. Disbursed to Fees c. Disbursed to Others d. Amount Collected e. Applied to Current Support f. Applied to Arrears

County Agency Directory Screen 82. The County Agency Directory screen will list all 88 counties. 83. Each county name will be hyperlinked to display the County Agency

screen with the CSEA information.

County Agency Screen 84. The County Agency screen will be displayed upon tapping the county

name in the County Agency Directory screen or in the Support Order Detail screen.

85. The County Agency screen will include the CSEA information including: a. County name b. County agency contact’s name and title. c. Agency address d. Agency phone number e. Agency fax number f. Agency hours of operation.

86. The County Agency screen will include a feature to open the agency location in the device’s native maps app.

87. The County Agency screen will include a feature to send a message to the county displayed.

Personal Screen 88. The Personal screen will display when the user taps the Profile image in

the title bar of the mobile app. 89. The Personal screen will include images with text to navigate to the

personal screens: a. Contact Information

Attachment 1



b. Child Information c. Employer Information d. Health Insurance Information

Contact Information Screen 90. The Contact Information screen will display the participant’s personal

information, residential address and mailing address. a. Personal Information

i. Full Name ii. Date of Birth iii. Home Phone # iv. Cell Phone #

b. Residential Address i. Address ii. Apartment iii. City iv. State v. Country vi. Zip

c. Mailing Address i. Address ii. Apartment iii. City iv. State v. Country vi. Zip

91. The Contact Information screen will display the following text: Please use the Message Center to submit any Contact Information changes.

92. The “Message Center” text will be animated to navigate the user to the Contact Information screen with the message topic “Contact Information Change or Addition” pre-selected.

Child Information Screen 93. The Child Information screen will display the following information when

the participant is the obligor. a. Case/Order b. Full Name (of child) c. Expected Emancipation Date

Attachment 1



94. The Child Information screen will display the following information when the participant is the obligee. a. Case/Order

The following information repeats for each child on the selected case/order.

b. Full Name (of child) c. Date of Birth d. Expected Emancipation Date e. Residential Address

i. Address ii. Apartment iii. City iv. State v. Country vi. Zip

95. The Child Information screen will include a feature to select the case/order which will refresh the screen with the child information for the child(ren) in the selected case.

Employer Information Screen 96. The Employer Information screen will display each of the participant’s

active (i.e., non-end dated) employer information. The information will include: a. Employer Name b. Street Address c. Suite d. City e. State f. Zip Code

97. The Employer Information screen will display the following text at the top of the screen: a. Please use the Message Center to submit any Employer

Information changes. i. The Message Center text will be animated to navigate the

user to the New Message screen with the Employer Change or Addition message topic pre-selected.

98. The Employer Information screen will contain a feature to select an employer from a list of the participants’ active (i.e., non-end dated) employers in SETS. a. This selection feature may be a drop-down list or a rolling selection

widget dependent on the type of device (i.e., Android or iOS).

Attachment 1



Health Insurance Screen 99. The Health Insurance screen will display each of the participant’s active

(i.e., non-end dated) health insurance information for each open case in SETS for obligees and obligors. The information will include: a. Case/Order b. The following information repeats for each active health insurance

record in SETS for the participant. i. Provider Name ii. Policy # iii. Group # iv. Begin Date v. Covered Participants

1. The first and last name of the covered participants 100. The Health Insurance screen will display the following text at the top of

the screen: a. Please use the Message Center to submit any Insurance

Information changes. i. The Message Center text will be animated to navigate the

user to the New Message screen with the Health Insurance Change or Addition message topic pre-selected.

101. The Health Insurance screen will contain a feature to select a case from a list of the participants’ active (i.e., non-end dated) cases in SETS.

i. This selection feature may be a drop-down list or a rolling selection widget dependent on the type of device (i.e., Android or iOS).

Messaging 102. The Message Center screen will list all messages not deleted (archived)

by the customer. 103. Unopened incoming messages from the county will have a new

message indicator. 104. Each message will include:

a. Topic b. Case number c. Order number d. Last message thread date e. Last message thread sender

105. The Message Center screen will allow the user to select a message which will open a Message screen including all message threads within the selected message.

Attachment 1



a. The Message screen will list all message threads within a message in descending order by date.

b. The Message screen will include a feature to send a reply to the county.

106. The Message Center screen will include a feature to send new message to the county.

107. The New Message screen will include the following text: The message you send is secure and can only be viewed by Child Support Staff. No one else including the other party on the case can see your message.

108. The New Message screen will include an option to select message topic. The message topics will include:

a. Case Information b. Employer c. My Payments d. Other e. Support Enforcement f. Termination of Support g. Contact Information Change h. Employer Change or Addition i. Health Insurance Change or Addition j. Modify My Order

109. The New Message screen will include an option to select case-order. 110. The New Message screen will include a Continue button to navigate to

the Reply screen. 111. The Reply screen will display the selected message topic and case-

order. 112. The Reply screen will include a 2000-character text box with a counter

that displays the count of characters remaining as the user types in the message text box. a. Provide keyboard input functionality (e.g., type characters) b. Include a camera image with functionality to take and attach a

picture c. Provide text regarding the appropriateness of attachments.

County Bulletins 113. The Customer Bulletins screen will display the active county bulletins

that the county contact workers have recorded via the worker web portal screen.

Attachment 1



Customer Alerts 114. The Customer Alerts screen will display the alerts for Missing SETS

data: a. Missing Address b. Missing Employer c. Missing Health Insurance

Upload Documents 115. Selection of the Upload app menu will open the New Message screen. 116. The New Message screen will provide a camera feature that launches

the device’s native camera. a. The user can capture an image and attach it to the message. b. The message topic of “Other” will be pre-selected. c. The user will select a case/order and enter message text. d. On Submit, the message and image will be sent to the county with

the message displaying in the county web portal Work List 117. A running record comment is recorded in SETS.

Alerts and Notification Preferences 118. The mobile app must allow customers to opt into e-mail and/or push

notifications a. By default, customers will be opted out of receiving e-mail and push

notifications. 119. The mobile app will display push notifications the same as the

customer web portal alerts. including: a. Notifications for missing address, employer and/or health insurance

information. i. The alert for missing address information will display to both

obligors and obligees. ii. The alert for missing employer information will only display to

customers who are obligors on a case. iii. The alert for missing health insurance information will display

to the customer who is designated as the Health Insurance payor on the “Support Order Detail” screen.

b. Notification to an obligee when a payment was disbursed to the family.

i. A payment disbursed to the family shall match the payments displayed in the “Collections sent to family” column of the payment history.

Attachment 1



ii. If multiple payments are disbursed to the customer during the same day, only one payment e-mail notification will be generated.

Note: Refer to the web portal Customer Dashboard Screen Specifications document for further information on the alerts.

Mobile Application Performance Metrics a. Login process less than five (5) seconds. b. Initial splash and login screen to load immediately. c. Back ground load of supporting application data and or functions to

load within two (2) seconds. d. Screen transitions within one third (.33) seconds. e. Document upload process within two (2) seconds. f. Account inquiry data display less than two (2) seconds.

Prototypes and Use Cases Targeted for 1st Mobile Application Release The following screens are planned and have prototypes available. This list should not be considered as an inclusive list of screens for the Mobile Application

1. Splash 2. Login 3. Touch ID 4. Registration 5. Home 6. County Bulletins 7. Customer Alerts 8. Hamburger Menu 9. Change Password 10. Change E-mail Address 11. Message Center 12. Message 13. New Message 14. Reply 15. Support Order Detail 16. County Agency Directory 17. County Agency 18. Personal 19. Contact Information

Attachment 1


20. Health Insurance 21. Employer Information 22. Child Information

App Menu App Menu Overview

The app menu displays in a horizontal row at the bottom of every screen with icons and text to provide quick navigation to specific screens.

UI & Widget Overview The prototyped app menu includes the following icons and text. These images may be replaced during the app development cycle.

# Item Name Kony Widget Type Description

1

Image Tap to navigate to Home screen.

2

Image Tap to navigate to the Message Center screen.

4

Image Tap to navigate to the Payment History screen.

5

Image Tap to navigate to the New Message screen which allows the user to capture an image and attach the image to a message to the county.

Use Cases

UC10-01 – Navigate to Home screen

Pre-condition:

1. The user has launched the Child Support mobile app. 2. The Login screen is displayed. 3. The user enters credentials and taps Login.

Normal Flow:

1. The Home screen is displayed. 2. The user navigates to any other screen in the app. 3. The user taps Home image in the app menu.

Post-condition:

1. The Home screen is displayed.

Attachment 1


UC10-02 – Navigate to Message Center screen

Pre-condition:

1. The user has launched and logged into the Child Support mobile app. Normal Flow:

1. The user taps the Message image in the app menu. Post-condition:

1. The Message Center screen is displayed.

UC10-03 – Navigate to Payment History screen

Pre-condition:


1. The user taps the Payment History image in the app menu. Post-condition:

1. The Payment History screen is displayed.

UC10-04 – Navigate to New Message screen for Document Upload

Pre-condition:


1. The user taps the Upload image in the app menu. Post-condition:

1. The New Message screen is displayed with the Other message topic pre-selected.

Hamburger Menu Screen Overview

The side menu in the mobile application is referred to as the “hamburger menu”. This menu is displayed by clicking the in the top left corner of any screen. It contains menu items providing navigation to screens in the application. The user taps a menu item to navigate to the associated screen or taps in the space below the menu items or swipes to the left to return to the screen from where they accessed the hamburger menu.

Attachment 1


UI Overview # Item Name Kony Widget Type Description

2 Touch ID Switch Slide to toggle on and off.

3 Change Password Text Tap to navigate to the Change Password screen.

4 Change E-mail Address

Text Tap to navigate to the Change E-mail Address screen.

5 Notification Preferences

Text Tap to navigate to the Notification Preferences screen.

6 County Agency Locations

Text Tap to navigate to the County Agencies screen.

7 Logout Text Tap to log out of the mobile application.

Widget Behavior

# Item Name Validation Business Rules Interactions

1 X Image On Click, collapse hamburger menu and return to the screen last viewed by user.

2 TouchID Switch If first time toggle on, display the Touch ID screen on next login. If touch ID previously established by user, display the Touch ID pop-up on next login.

Slide to toggle on and off.

Splash Screen Specifications Screen Overview

The Splash screen displays quickly (1-5 seconds) upon launching the application displaying the ODJFS logo with no other widgets. There is no user action on this screen.

UI Overview


1 ODJFS Logo Image Displays the ODJFS Job and Family Services logo.

2 OCS Banner Text Displays the “Office of Child Support”

3 Background Image Displays the “Kids” picture.

Widget Behavior None

Attachment 1


Use Cases UC12-01: Child Support App Successfully Launches

Precondition:

1. User taps App icon. Normal Flow:

1. Child Support mobile application begins to launch. 2. The splash screen displays for 1-5 seconds while the application loads to mobile

device. Post- Condition:

1. The Login screen is displayed.

UC12-02 Child Support App Fails to Launch

Precondition:

1. User taps App icon. Normal Flow:

1. Child Support mobile application begins to launch. 2. The splash screen displays for 1-5 seconds while the application attempts to launch

to mobile device. Post- Condition:

1. An error message (e.g., Technical difficulties. Please try again later).is displayed.

Login Screen Specifications Screen Overview

The Login Screen displays immediately after the Splash screen

Functionality available on the screen is as follows:

- Touch ID (iOS devices only) - Login:

o Enter User ID o Enter Password o Login button

- Forgot User ID or Password? - New User Registration button - Need Help - Enable Touch ID (iOS Devices only)

Attachment 1


UI Overview


1 Login Button Tap to login to the app

2 User ID Text Box Enter User ID

3 Password Text Box Enter Password

4 Forgot User ID Link Tap to launch Forgot User ID screen

5 Forgot Password Link Tap to launch Forgot Password screen

6 Touch ID Button Tap to login using Touch ID

7 Enable Touch ID Button or Check Box

Swipe to enable touch ID

8 New User Registration

Button Tap to launch New User Registration screen

9 Help? Link Tap to link to OCS FAQ html

Widget Behavior


1 User ID Not blank Mandatory field 6-15 characters Not Case Sensitive

2 Password Not blank Mandatory field 6-15 characters Case Sensitive Should be masked

Attachment 1



3 Login Valid User ID and password

On Click: First Login: Show Push Notification pop-up asking the user whether he/she wants to receive push notifications from the Office of Child Support. If the user clicks an OK (or Allow) option, push notifications will be enabled. If the user clicks the negative option (e.g., No, Maybe Later, or Don’t Allow), push notifications will not be enabled. The user can change their selection by accessing the Notifications Preferences hamburger menu option. Consecutive logins on iOS (touch ID not enabled) and Android devices: Open Home in Current Window Consecutive logins on iOS with touch ID enabled: Show Touch ID

4 Forgot User ID N/A On Click: Open Forgot User ID screen in Current Window

5 Forgot Password

N/A On Click: Open Forgot Password screen in Current Window

6 Touch ID Only on iOS devices

User should have successfully logged in at least once and registered for Touch ID

On Touch: Open Home screen

7 Enable Touch ID

- Only on iOS devices - Switched off by default

If enabled at time of login, users will be able to login using touch ID.

On Touch, the Touch ID screen is displayed.

8 New User Registration

On Click: Open New User Registration screen

9 ? Need Help On Click: Open Need Help screen

Privacy Statement FAQ http://jfs.ohio.gov/ocs/OCSFAQs.stm

Attachment 1


Use Cases

UC13-01: Login

Precondition:

1. User is on Login screen

2. User is online

3. User has entered valid User ID (not case sensitive) and password (case sensitive)

4. User has enabled Touch ID (only on iOS devices)

Normal Flow:

1. User taps on Login button or presses Touch ID (only on iOS devices) to authenticate

Post-condition:

1. Home screen is displayed

UC13-02: First Login

Precondition:

1. If user has enabled Touch ID, first follow UC01 steps 1 to 4. 2. Push Notification Option pop-up is displayed on Login screen.

Normal Flow:

1. The user taps OK - Push Notifications are enabled. 2. The user taps the negative option (e.g., No, Don't Allow, or Maybe Later) - Push

Notifications are not enabled. Post-condition:


UC13-03: User is registering for Touch ID

Precondition:

1. The user is prompted to enter the User ID and Password. Normal Flow:

1. The user enters the User ID and Password and sets Enable Touch ID to ON. 2. The user presses Login button.

Post-condition:

1. System authenticates the credentials, and if successful: 2. System prompts to register the Touch ID.

Attachment 1


3. The user registers the Touch ID successfully. 4. System stores the User ID and Password in the device DB (encrypted). 5. System stores a flag to display Touch ID option from subsequent logins. 6. The user is navigated to Home screen.

UC13-04: User clicks on Cancel on the Touch ID pop-up:

Precondition:

1. The Touch ID pop-up is displayed. Normal Flow:

1. The user clicks on Cancel on the Touch ID pop-up. 2. System closes the pop-up. 3. The user enters User ID and Password manually. 4. The user clicks on ‘Login’ button.

Post-condition:

1. System authenticates the entered User ID and Password with backend. 2. If authentication is successful, system navigates the user to Home screen. 3. System updates the encrypted User ID and Password on device DB.

Exception Flow:

E01: User ID and/or Password incorrect

1.1 “Invalid User ID or Invalid Password” message is displayed in pop-up.

1.2 The user taps Close button.

1.3 Pop-up is closed; Login screen is displayed

E02: User ID missing

2.1 “The User ID field is missing” message is displayed in pop-up.


2.3 Pop-up is closed; Login screen is displayed.

E03: Password missing

3.1 “The Password field is missing” message is displayed in pop-up.


3.3 Pop-up is closed; Login screen is displayed.

Attachment 1


E04: User locks account

4.1 User enters an incorrect User ID or password 6 times in 15 minutes.

4.2 The account is locked

4.3 The following error message displays, ‘This account has been locked. An e-mail has been sent to the owner of this account with instructions on how to unlock it.’

E05: Touch ID authentication failed

5.1 If Touch ID authentication is unsuccessful in the first attempt.

Note: Number of failed attempts is 3 (reference section 14.1)

5.2 System displays <message TBD – maybe: "Sorry, unrecognized User ID or password" > message with ‘Close’ button.

5.3 The user taps ‘Close’ button.

5.4 Login screen is displayed.

E06: User tries to login using Touch ID without having a successful login with 'Enable Touch ID' set to ON

6.1 The user taps on Touch ID.

6.2 System displays <TBD – Error> message with ‘Close’ button

6.3 The user clicks on ‘Close’ button

6.4 Login screen is displayed

UC13-05: Forgot User ID

Precondition:

1. The user is on Login screen

2. The user is online

Normal Flow:

1. The user taps on Forgot User ID link. 2. The Forgot User ID screen is displayed. 3. The user enters e-mail address and tabs Submit button. 4. The user navigates to their e-mail to find their Child Support User ID. 5. The user clicks the hyperlink in the e-mail.

Post-condition:

1. The mobile app is launched and the Login screen is displayed.

Attachment 1


UC13-06: Forgot Password

Precondition:

1. The user is on Login screen.

2. The user is online.

Normal Flow:

1. The user taps on Forgot Password.

Post-condition:

1. The Forgot Password screen is displayed.

UC13-07: Touch ID

Precondition:

1. The user is on Login screen.

2. The user is online.

3. The user is using an iOS device.

Normal Flow:

1. The user taps on Touch ID

2. System prompts user with message to login using touch ID

3. The user uses device touch ID to login

Post-condition:

1. Home screen is displayed

Alternate Flow:

A13-08: User taps Cancel on Touch ID pop-up

1. Login Screen is displayed

Touch ID Screen Specifications Screen Overview

The Touch ID feature must be native to the device/iOS and supported on Android 6 and above. The Touch ID screen displays only upon the user’s initial login to the Child Support mobile app. If the user opts not to enable Touch ID at initial login, the user can enable touch ID via the switch on the hamburger menu.

Attachment 1


The user will have 3 attempts at Touch ID login and if unsuccessful will then have 6 Login Screen User ID/Password entry attempts before account is locked.


1 Screen Text: Touch ID

Text Displays “Would you like to enable touch ID?”

2 Touch ID Recorder image Image only.

3 Enable Touch ID Text On click, enable the mobile device’s touch ID for access to the Child Support mobile app.

4 Maybe Later Text On click, do not enable the mobile device’s touch ID for access to the Child Support mobile app.

Widget Behavior


Maybe Later

Does not enable the mobile device’s touch ID for access to the Child Support mobile app.

Use Cases - iOS Biometric Test Scenarios

UC14-01- Successful Touch ID Login 1. The user enables the Touch ID through pop-up alert

a. Take the User to the first Login screen b. Login with User ID & Password c. Access the app.

UC14-02 - Unsuccessful Touch ID Login 1. The user Login Fails because the user provides invalid credentials & User tries with

finger not registered in the device. UC14-03 - Unsuccessful Touch ID Login 1. The user Cancels the Touch ID popup alert > Take the user to the Login screen.

UC14-04 - Unsuccessful Touch ID Login 1. The user chooses the ‘Enter Password after scenario 2

a. Take the user to the Login screen.

UC14-05 - Disabled Touch ID Login

Attachment 1


1. Touch ID disabled by the user on the device. a. Take the user to the Login screen.

UC14-06 - Touch ID Not Available

1. Touch ID is not available on the User Device (Device Hardware disability) a. Take the user to Login screen.

UC14-07 - Touch ID Fails 1. Touch ID fails because the user has no enrolled fingers on the device.


UC14-08 - Touch ID Not Available 1. Touch ID not supported on the User Device (Software Disability)

a. Take the user to the Login.

UC14-09 - Touch ID Not Available 1. After 3 failed login attempts (Touch ID)

a. Redirect the user to the Login screen.

UC14-10 - Touch ID Not Available 1. The user registers Touch ID on the device with an account.

a. The user tries to Login with a different user ID and password which is not registered.

b. The user then presses device home button with fingerprint to login with Touch ID. c. Give access to the user & authenticate only with the registered finger.

UC14-11 - Touch ID Not Available 1. The user taps Enable Touch ID & kills the application

a. On Login still prompt Enable Touch ID settings.

Use Cases - Android (Samsung 5.0 & Marshmallow 6.0)

UC14-12 - Touch ID Not Available 1. The user enables the Touch ID through pop-up alert.

a. Take the user to the first Login screen. b. Login with User ID & Password. c. Access the App.

UC14-13 - Touch ID Fails

Attachment 1


1. The user Login Fails because the user provides invalid credentials & the user tries with finger not registered in the Device.

a. Invalid User ID & Password.

UC14-14 - Touch ID Cancelled 1. The user cancels the Touch ID pop-up alert.


UC14-15 - Touch ID Cancelled 1. The user chooses the Cancel button after failed login attempt.


UC14-16 - Touch ID Disabled 1. Touch ID disabled by the user on the device.


UC14-17 - Touch ID Not Available 1. Touch ID is not available on the user device (Device Hardware disability).

a. Take the user to Login.

UC14-18 - Touch ID Fails 1. Touch ID fails because the user has no enrolled fingers on the device.


UC14-19 - Touch ID Not Supported 1. Touch ID not supported on the user device (Software Disability).


UC14-20 - Touch ID Failed Login 1. After 3 failed login attempts (Touch ID)

a. Redirect the user to the Login screen. A. Max failed attempts for Samsung Galaxy devices running on Android version 5.0 > Reset from the settings with Backup Password. B. Max failed attempts for Marshmallow devices running on Android version 6.0 > Resets after 1 minute

UC14-21 – Different Account Login 1. The user registers Touch ID on the device with an account. The user tries to Login with

different account which is not registered. a. Give access to the user & authenticate only with the registered finger.

Attachment 1


UC14-22 – Different Account Login 1. The user taps Enable Touch ID & kills the application

a. On Login still prompt Enable Touch ID settings

Forgot User ID Screen Specifications Screen Overview

The Forgot User ID screen is displayed when the user taps the Forgot User ID text on the Login screen. The user enters their e-mail address and taps the Submit button which sends the user an e-mail.

No App menu displays on this screen.

UI Overview

# Item Name Kony

Widget Type

Description

1 Screen Title: Forgot User ID

Text Displays “Forgot User ID”

2 Enter E-mail Address Text Box

Placeholder Text: Enter E-mail Address

3 Instruction Text The following text is displayed: An e-mail will be sent to you providing your user ID.

4 Submit Button Validates the user entered e-mail address.

5 Cancel Button Returns the user to the Home screen.

Widget Behavior


1 E-mail Address Text Box

Text entry must contain the @ special character.

None

Attachment 1



2 Submit E-mail Invalid If entered e-mail does not does not contain “@.” Display: The e-mail address is not a valid format. If entered e-mail does not agree to SETS DB2 e-mail, display: Information entered does not match a registered user. Please try again.

On Click, verify entered e-mail address to the SETS DB2 for the participant.

3 Cancel On Click, the Login screen is displayed.

Use Cases UC15-01 – User enters registered e-mail address to retrieve User ID

Pre-condition:

1. The user has launched the Child Support mobile app. 2. The Login screen is displayed. 3. The user taps on Forgot User ID text.

Normal Flow:

1. The Forgot User ID screen is displayed. 2. The user enters a registered e-mail address. 3. The user taps Submit.

Post-condition:

1. The Login screen is displayed. 2. An e-mail is sent to the registered e-mail address.

a. The following is the format of the e-mail currently sent by the customer web portal:

In response to your request your authorized User ID is listed below. <User ID>

Please click the following link and then enter your User ID and password to log into your account. <link to mobile app>

Attachment 1


If you or someone authorized by you did not request this information, please contact your child support agency. Thank you,

OHIO DEPARTMENT OF JOB AND FAMILY SERVICES Do not reply to this message as the mail box is not monitored.

UC15-02 – User enters invalid e-mail address

Pre-condition:

1. The user has launched the Child Support mobile app. 2. The Login screen is displayed. 3. The user taps on Forgot User ID or Password text.

Normal Flow:

1. The Forgot User ID screen is displayed. 2. The user enters an invalid e-mail address (without “@.”). 3. The user taps Submit.

Post-condition 1:

1. The Forgot User ID screen remains displayed with the following message: The e-mail address is not a valid format.

UC15-03 – User enters e-mail address not registered in SETS

Pre-condition:

1. The user has launched the Child Support mobile app. 2. The Login screen is displayed. 3. The user taps on Forgot User ID text.

Normal Flow:

1. The Forgot User ID or Password screen is displayed. 2. The user enters an e-mail address not found in the SETS DB2. 3. The user taps Submit.

Attachment 1


Post-condition 1:

1. The Forgot User ID screen remains displayed with the following message: Information entered does not match a registered user. Please try again.

2. The e-mail address entered by the user continues to display so that the user can correct entry (e.g., correct a typo).

Forgot Password Screen Specifications

Screen Overview The Forgot Password screen is displayed when the user taps the Forgot Password text on the Login screen. The user enters their User ID and taps the Submit button which sends the user an e-mail.

No App menu displays on this screen.

UI Overview

# Item Name Kony

Widget Type

Description

1 Screen Title: Forgot Password

Text Displays “Forgot Password”

2 Instruction Text To retrieve your password, enter your User ID.

3 Enter User ID Text Box

Placeholder Text: Enter User ID

4 Submit Button Tap to submit User ID.

5 Instruction Text The following text is displayed: An e-mail will be sent to you providing instructions to reset your password. For password resets, you must click the link provided in the e-mail within 2 hours. If you do not click on the link within 2 hours, you must resubmit your request.

Widget Behavior


1 Enter User ID

Entered User ID must exist in DB2.

Alphanumeric with no spaces

User entry saved.

2 Submit User ID valid If entered User ID agrees to SETS DB2, send e-mail with text including hyperlink to reset password. Hyperlink returns user to the app.

On Click, verify entered User ID to the SETS DB2 for the participant.

Attachment 1



3 Cancel On Click, the Login screen is displayed.

Use Cases UC16-01 – User enters valid User ID

Pre-condition:

1. The user has launched the Child Support mobile app. 1. The Login screen is displayed. 2. The user taps on Forgot Password text.

Normal Flow:

1. The Forgot Password screen is displayed. 2. The user enters a valid user ID. 3. The user taps Submit.

Post-condition:

1. The Login screen is displayed. 2. An e-mail is sent to the participant.


Subject: Password Reset/Unlock Request from ODJFS

In response to your request, please click the following link below to reset your password within the next 2 hours. Please note, if you do not reset your password within 2 hours, your request will expire. <link to reset password> Thank you, OHIO DEPARTMENT OF JOB AND FAMILY SERVICES Do not reply to this message as the mail box is not monitored.

The system generates a second e-mail to the customer stating the password has been successfully changed.


Attachment 1


Subject: Account Password change confirmation from ODJFS

In response to your request, your password has been changed. If your account was previously locked, it has been unlocked. If you are currently a registered user for ODJFS online Cash, Food, or Medical benefits, please note that your password has changed for both programs. Thank you, OHIO DEPARTMENT OF JOB AND FAMILY SERVICES Do not reply to this message as the mailbox is not monitored.

UC16-02 – User enters an invalid User ID

Pre-condition:


Normal Flow:

1. The Forgot Password screen is displayed. 2. The user enters an invalid user ID (entry includes space(s) or special character(s)). 3. The user taps Submit.

Post-condition:

1. The Forgot Password screen remains displayed with the following message: The User ID should only contain numbers and letters.

UC16-03 – User enters User ID not registered in SETS

Pre-condition:


Normal Flow:

Attachment 1


1. The Forgot Password screen is displayed. 2. The user enters a user ID (6-15 characters with no spaces or special characters). 3. The user taps Submit.

Post-condition:

1. The Forgot Password screen remains displayed with the following message: Information entered does not match a registered user. Please try again.

Home Screen Specifications Screen Overview

Upon successful login, the mobile app retrieves county bulletin(s), customer alert(s) and financial information for the participant based on his/her open cases.

Below the “Home” header, a banner with County Bulletins and/or Customer Alerts is displayed. An indicator will display with the bulletin count and alert until read by user. The user will tap each of these to view the details on the County Bulletins screen and Customer Alerts screen.

The primary purpose of the Home screen is to display summary financial information by case-order. For participants with more than one open case the case-orders will display in descending order by the date of the most recent payment of each case.

The following information is displayed.

- Case# - Order# - Other Party - Balance Due - Monthly Support Obligations by case-order - For Obligees: Last Payment Received (amount and date) OR For Obligors: Last

Payment Sent (amount and date)

The user can tap anywhere in the case information section to navigate to the Support Order screen to view details.

UI Overview

# Item Name Kony Widget

Type Description

1 Screen Title: Home Text Displays “Home”

2 Hamburger Menu Image/text Tap to display hamburger menu

3 Profile Image/text Tap to display the Personal screen.

4 County Bulletins Link Tap to display County Bulletins screen

Attachment 1



5 Customer Alert Image/text Tap to display Customer Alerts screen

6 Welcome, <Participant > Text Displays “Welcome,” followed by the participant’s first name

7 State Bulletin Text Displays the Newsflash bulletin.

8 Case: <Case Number> Text Displays “Case:” followed by the SETS case number.

9 Order: <Order Number> Text Displays “Order:” followed by the SETS order number (associated with the above case).

10 Other Party: <Other Party> Text Displays “Other Party:” followed by the name of the other participant on the case.

11 Balance Due: <amount> Text Displays the Total Unpaid Balance amount.

12 Last Payment Received <amount> <date>

Text Obligee Only: Displays the last payment received.

13 Last Payment Sent <amount> <date>

Text Obligee Only: Displays the last payment sent.

Row items 8 - 13 repeat for each open case associated with the participant

Widget Behavior


1 Hamburger Menu

On Click, Hamburger menu displays.

Attachment 1



3 County Bulletins Does the participant have an open case in a county with a county bulletin? (could have open cases in different counties)

Displays a count only if the participant has a case in a county that has an active county bulletin posted AND the County Bulletins screen has not been read by the user. Once the user has viewed the County Bulletins screen, the count badge will disappear. Once the user logs out of the app and back into the app, the count badge will only display if a bulletin has been updated or a new bulletin has been created by a county for which the participant has a case in that county jurisdiction.

On Click, County Bulletins screen displays.

4 Customer Alerts Does the participant have a SETS system generated alert for missing information or for payment?

Displays a count only if the participant has at least one system generated missing data alert AND the Customer Alerts screen has not been read by the user. Once the user has viewed the Customer Alerts screen, the count badge will disappear. Once the user logs out of the app and back into the app, the count badge will only display if a new alert for that participant has been determined by the SETS query.

On Click, Customer Alerts displays.

5 State Bulletin Displays when a Newsflash is active.

On Click, expand section to view entire bulletin.

Attachment 1


Use Cases UC17-01: Display Home Screen

Precondition:

1. The user has at least one open case. 2. The user successfully logged in the mobile application. 3. The Home screen is displayed. 4. The case-order with the date of the most recent payment amount is displayed first.

Normal Flow without County Bulletins or Customer Alerts:

1. A banner with the text County Bulletins and Customer Alerts is displayed under the Home header. No count badges are displayed.

2. The Home screen includes “Welcome” followed by the participants first name. 3. The Case# <case number> is displayed. 4. The Other Party <other party’s first and last name> is displayed. 5. The Balance Due <Total Unpaid Balance amount> OR the Credit Due <Credit Due

amount>is displayed. This amount may be $0.00. 6. The Last Payment Received <amount and date> is displayed.

Normal Flow 1:

1. The user taps on a case/balance section.

Post-condition 1:

1. The Support Order Detail screen is displayed.

UC17-02: Normal Flow with at least one County Bulletin but without any Customer Alert

1. A banner with the text County Bulletins and Customer Alerts is displayed under the Home header. A count badge is displayed for the County Bulletins but no count badge is displayed for the Customer Alerts.

a. Once the user taps the County Bulletins banner on the Home screen and views the County Bulletins screen, the count badge no longer displays.

2. A “Welcome” followed by the participants first name is displayed below the banner. 3. The Case# <case number> is displayed. 4. The Other Party <other party’s first and last name> is displayed. 5. The Balance Due <Total Unpaid Balance amount> OR the Credit Due <Credit Due


Attachment 1


Alternate Flow:

1. The user taps on the County Bulletins banner. Post-condition:

1. The County Bulletins screen is displayed. 2. The user taps Home app menu item to return to the Home screen. The County Bulletins

count badge no longer displays during the user’s logged in session.

UC17-03: Normal Flow with at least one Customer Alert but without any County Bulletin

1. A banner with the text County Bulletins and County Alerts is displayed under the Home header. No count badge is displayed for the County Bulletins but a count badge is displayed for the Customer Alerts.

a. Once the user taps the Customer Alerts banner on the Home screen and views the Customer Alerts screen, the count badge no longer displays.

2. A “Welcome” followed by the participants first name is displayed below the banner. 3. The Case# <case number> is displayed. 4. The Other Party <other party’s first and last name> is displayed. 5. The Balance Due <Total Unpaid Balance amount> OR the Credit Due <Credit Due


Alternate Flow:

1. The user taps on the County Alerts banner. Post-condition:

1. The County Alerts screen is displayed. 2. The user taps Home app menu item to return to the Home screen. The Customer

Alerts count badge no longer displays.

Alternate Flow:

A17-01: Normal Flow with both County Bulletins and Customer Alerts

1. A banner with the text County Bulletins and Customer Alerts is displayed under the Home header. A count badge is displayed for the County Bulletins and another count badge is displayed for the Customer Alerts.

2. A “Welcome” followed by the participants first and last name is displayed below the banner.

3. The Case# <case number> is displayed. 4. The Other Party <other party’s first and last name> is displayed. 5. The Balance Due <Total Unpaid Balance amount> OR the Credit Due <Credit Due


Attachment 1


Alternate Flow a:

1. The user taps on the Customer Bulletins banner. Post-condition a:

1. The County Bulletins screen is displayed. 2. The user taps Home app menu item to return to the Home screen. The County

Bulletins count badge no longer displays but the Customer Alerts badge continues to display until the Customer Alerts screen is viewed.

Alternate Flow b:

1. The user taps on the County Alerts banner. Post-condition b:

1. The County Alerts screen is displayed. 2. The user taps the Home app menu item to return to the Home screen. The Customer

Alerts count badge no longer displays but the County Bulletins count badge continues to display until the County Bulletins screen is viewed.

County Bulletins Screen Specifications Screen Overview

The County Bulletins screen displays any active county bulletins associated with the county of jurisdiction for the customer cases. When a participant only has one case or when all of the participant’s cases are associated with one county of jurisdiction, only one bulletin will display if that county has an active bulleting. When a participant has at more than one case with cases in different counties of jurisdiction, the active bulletin of each county will display. These bulletins are displayed in descending order by date so the most recent bulletin is displayed first.

UI Overview If no county bulletins exist for the county’s associated with the user’s cases, then “No County Bulletins” display on the screen.

# Item Name Kony Widget

Type Description

1 Hamburger Menu Image/text Tap to display hamburger menu

2 Screen Title: County Bulletins

Text Displays “County Bulletins”

3 Message Text Displays “No County Bulletins”

OR Either the “No County Bulletins” message displays OR the county message lines 1-3 display.

Attachment 1



3 Message Line 1 Static Text Displays: ‘<date posted> - <county name>”

4 Message Line 2 Static Text Displays the county bulletin message text. This text area can contain up to 2,000 characters which could be multiple sentences and/or paragraphs of text as entered by the county contact.

5 Message Line 3 Static Text Displays the URL or e-mail address, if any, associated with the bulletin board message.

Widget Behavior


1 Hamburger Menu

On Click, Hamburger menu displays.

2 URL The county bulletin may have a URL.

On Click of the URL, the page is opened in a browser window.

Use Cases UC18-01 Display County Bulletins

Precondition:

1. The user has launched the Child Support mobile app. 2. The Login screen is displayed. 3. The user enters credentials and taps on Login. 4. The Home screen is displayed.

Normal Flow:

1. A banner with the text County Bulletins and Customer Alerts is displayed under the Home header.

2. A count badge is displayed for the County Bulletins. 3. The user taps on the Customer Bulletins banner.

Post-condition:

1. The County Bulletins screen is displayed. 2. The user taps the Home app menu item. 3. The count badge no longer displays.

Attachment 1


Customer Alerts Screen Specifications Screen Overview

The Customer Alerts screen displays SETS system generated alerts for missing contact, employer or health insurance information.

UI Overview If at least one alert has been system generated by SETS for the participant, the Customer Alerts screen will display information. Otherwise, a “No Alerts” message will display.


1 Screen Title: Customer Alerts

Text Displays “Customer Alerts”

2 Contact Information Alert Text Displays: We do not have a current address for you. Please submit your current address information.

3 Employer Alert Text Displays: We do not have a current employer for you. Please submit your current employer information.

4 Health Insurance Alert Text Displays:

We do not have current, private health insurance information for you and the child(ren) you are required to cover. Please submit your current health insurance information.

Please note, if the health insurance you are providing is Medicaid, there is no need to report this information as Medicaid shares that information with us. If you have been ordered to provide private health insurance but are receiving Medicaid coverage, the alert will continue to display as a reminder to report private health insurance information, including insurance purchased through the Ohio health insurance marketplace, if it becomes available to you. Case: <case#-order#> Child(ren): <child name> Case: <case#-order#> Child(ren): <child name>, <child name>

5 No Alerts Text Displays “No Alerts” when no alerts exist for the participant.

Widget Behavior


1 Contact Information Alert

If the participant does not have a valid address in SETS, display the Contact Information alert.

Tap the “Message” text to display the New Message screen with the Contact Change or Addition topic pre-selected.

Attachment 1


Use Cases UC19-01 Display Customer Alerts

Precondition:

1. The user has launched the Child Support mobile app. 2. The Login screen is displayed. 3. The user enters credentials and taps on Login. 4. The Home screen is displayed.

Normal Flow:

1. A banner with the text County Bulletins and Customer Alerts is displayed under the Home header.

2. A count badge is displayed for the Customer Alerts. 3. The user taps on the Customer Alerts banner.

Post-condition:

1. The Customer Alerts screen is displayed. 2. The user taps the Home app menu item. 3. The count badge no longer displays during the user’s logged in session

UC19-02 Navigate from Contact Information Alert to New Message

Precondition:

1. A contact information alert is displayed. Normal Flow:

1. The user taps on the word “Message” within the alert text. Post-condition:

1. The New Message screen is displayed with the message topic “Contact Information Change” pre-selected.

UC19-03 Navigate from Employer Information Alert to New Message

2 Employer Alert

If an obligor does not have an active employer in SETS, display the Employer alert.

Tap the “Message” text to display the New Message screen with the Employer Change or Addition topic pre-selected.

3 Health Insurance Alert

If a participant who is the health insurance obligor does not have active health insurance for the child required by the support order, display the Health Insurance alert.

Tap the “Message” text to display the New Message screen with the Health Insurance Change or Addition topic pre-selected.

Attachment 1


Precondition:

1. An employer information alert is displayed. Normal Flow:


1. The New Message screen is displayed with the message topic “Employer Change or Addition” pre-selected.

UC19-04 Navigate from Health Insurance Information Alert to New Message

Precondition:

1. A Health Insurance information alert is displayed. Normal Flow:


1. The New Message screen is displayed with the message topic “Health Insurance Change or Addition” pre-selected.

Support Order Detail Screen Specifications Screen Overview

The Support Order Detail screen will display when the user taps on any case/balance section on the Home screen. The Support Order Detail screen displays current, active SETS support order(s) and balance information and allows a user to view payment information for the current and prior 3 months. Closed orders are not viewable in the app (or in the customer web portal).

UI Overview


1 Hamburger Menu Image/text Tap to display hamburger menu.

2 Screen Title: Support Order Detail

Text Displays “Support Order Detail”.

3 Profile Image Tap to display the Personal screen.

5 Case / Order Label <Text>

Displays “Case / Order” text.

6 <Case Number / Order Number>

Label <Text>

Displays the case and order number.

7 Child Support Contact: <CSEA name>

Label <Text>

Displays the county of jurisdiction for the selected case.

Attachment 1



8 CASE / ORDER Label Tab label.

9 Case and Order Information

Label Section Header

10 (i) Image Tap to display the “Explanation of Terms” pop-up.

11 Health Insurance Obligor: <participant first and last name>

Label <Text>

Display label and participant name if open MS support order.

12 Order Date: <order date> Label <Text>

Display label and order issued date

13 Total Monthly Support Label Section Header


16 Current Child Support Label <Text>

Display label and amount, if > $0.00

17 Current Spousal Support Label <Text>


18 Current Medical Support Label <Text>


19 Past Due Support Payment

Label <Text>


20 Administrative Fees Label <Text>


21 Interstate Fees Label <Text>


22 Interest Label <Text>


15 Total Label <Text>

Amount; can be $0.00 Tab to expand and collapse section.

23 Total Unpaid Balance Label Section Header


26 Current Month Unpaid Balance

Label <Text>

Display label and amount (amount can be $0.00.

27 Past Due Unpaid Balance Label <Text>

Display label and amount (amount can be $0.00).

28 Total Credits Label <Text>


29 Total Funds On Hold Label <Text>


15 Total Label <Text>


Attachment 1



30 PAYMENTS Label Tab label.

31 Recent Transactions

32 Retrieved from SETS. Each payment description may be: 1. Sent to Family 2. Collection Amount 3. Applied to Current

Support 4. Sent to Fees 5. Sent to Other 6. Applied to Past Due

Support 7. Refunded

Text <Amount>

Display each label and amount, if > $0.00

Widget Behavior


1 Information Image Display for each section header Tap to display the Explanation of Terms pop-up.

2 Case-Order Selection

PickerView Display when participant has more than one open case-order

Roll to select a case-order.

Support Order Detail – Explanation of Terms When the user clicks on the (i) that displays to the right of the section headers, a pop-up displays containing the following text for the specific item.

During mobile app development phase, the options for the display of this text will be reviewed and a project decision made.

Explanation of Terms

Case Number: A unique 10-digit, system assigned number used to identify a Child Support Case Order Number: Court or administrative order number associated with the case number Total Unpaid Balance: Includes total arrearages plus any unpaid obligations for the current month on the As of Date. The entire amount may not be owed to the family. Support owed to the family, other entities and fee balances are all included in this amount. NOTE: This amount will be equal to the Current Month Unpaid Balance + Past Due Unpaid Balance minus any Past Due Support Payments displaying in the Monthly Support Obligations section of the My Support Order(s) and Balance Information screen.

Attachment 1


Current Month Unpaid Balance: Includes any support, payments ordered to reduce past due support (arrearages) and fee obligations due for the current month. The entire amount may not be owed to the family. Support owed to the family, other entities and fee obligations are all included in this amount Past Due Unpaid Balance: Includes prior period unpaid support (arrearages) and fees (not including any unpaid obligations for the current month) on the As of Date. The entire amount may not be owed to the family. Support owed to the family, other entities and fee balances are all included in this amount Total Credits: The total amount of excess funds remaining after all current monthly obligations have been met. These funds will be used to count as a payment toward next month's obligations Funds on Hold: Support collections that are temporarily held instead of being issued, usually because there is a court order for the child support enforcement agency to hold the payments, due to a bad address, etc. The amount of these funds may already be included in the reported collections and applied to the unpaid balance Monthly Support/Current Child Support: The amount designated for the current month's amount of money an obligor is required to pay to provide support for the child(ren) of the case/order Monthly Support/Current Spousal Support: The amount designated for the current month’s amount of support owed to a former spouse; also, called alimony. Monthly Support/Current Medical Support: The amount designated for the current month’s obligation for the child’s health care needs. Monthly Support/Past Due Support Payment: An additional monthly payment made towards past due support to reduce the unpaid balance on the order. The Past Due Support Payment amount includes the following obligations:

Ordered Payment Child Support Arrears Ordered Payment On Past Care Ordered Payment Spousal Support Arrears Ordered Medical Payment Finite Cost Ordered Payment Non-Medicaid Ongoing Support Ordered Medical Payment Birth Cost Ordered Medical Payment Other Costs Ordered Medical Payment Ongoing Support Support Assigned to Other State

Monthly Support/Interest Payment: Monthly payment made towards interest on arrears. The Interest Payment includes the following obligations:

Interest Payment on Unassigned Arrears Interest Payment on Assigned Arrears

Monthly Support/Administrative Fees: Monthly 2% administrative/processing fee as indicated in the order

Monthly Support/Other Fee Obligations: Monthly obligations that are owed to fees as indicated in the order. The Other Fee Obligations includes the following obligations:

Payment on Genetic Test Lab Fee

Attachment 1


Payment on Court Costs Payment on Filing Fees Payment on Attorney's Fees Payment on Other Fees

Monthly Support/Interstate Administrative Fees: The monthly charge paid to another state’s child support enforcement agency to cover the cost of processing the support payments. Monthly Support/Total: Total obligation charged for the current month.

Use Cases UC20-01: Display Support Order Detail Screen

Precondition:

1. The user is logged into the mobile app.


Normal Flow:

1. With the Home screen displayed, the user taps any case/balance section.

Post-condition:


UC20-02: Display Support Order Detail Screen

Precondition:

1. The user is logged into the mobile app. 2. Any screen, other than the Home screen, is displayed.

Normal Flow:

1. The user taps the Home menu option in the app menu. 2. With the Home screen displayed, the user taps any case/balance section.

Post-condition:


UC20-03: Display the County Agency Information

Precondition:

1. The user is logged into the mobile app. 2. The Support Order Detail screen is displayed.

Normal Flow:

1. The user taps the county name displayed to the right of the “Child Support Contact”.

Attachment 1


Post-condition:

1. The County Agency screen is displayed.

UC20-04: Display Explanation of Terms

Precondition:


Normal Flow:

1. The user taps the (i) to the right of the Case and Order Information section header. Post-condition:

1. The Explanation of Terms pop-up is displayed.


Precondition:


Normal Flow:

1. The user taps the (i) to the right of the Total Monthly Support section header. Post-condition:



Precondition:

1. User is logged into the mobile app. 2. The Support Order Detail screen is displayed.

Normal Flow:

1. The user taps the (i) to the right of the Total Unpaid Balance section header. Post-condition:


UC20-07: View Support Order Detail for a Different Case

Precondition:


Attachment 1


Normal Flow:

1. The user selects a different case-order from a drop-down Post-condition:

1. The Support Order Detail screen is displayed with information for the selected case.

Payment History Screen Specifications Screen Overview

The Payment History Report page provides information regarding financial transactions processed for the current month plus the past 23 months’ period.

The Payment History screen includes a Generate Payment History Report button. Tapping this button will call a web service to generate the Payment History Report as a PDF document with up to the 24 months of data in a recommended format. The way it is shown is dependent on the native behavior of the underlying device operating system. The iOS devices usually can show the pdf within the application in browser view. Conversely, in Android the pdf will have to be downloaded and the user will use their native PDF reader to open and view the file. The native behavior cannot be changed and the users on their devices are used to that experience. Once the user opens the PDF file, he/she can use native options to print, email, or share.

UI Overview


1 Screen Title: Payments Text Displays “Payments”

2 Case/Order Text Displays “Case/Order” followed by the SETS case / order. Number.

3 Explanation of Terms Label Section Header

4 (i) Image Tap to display the “Explanation of Terms” screen.

5 Retrieved from SETS. OBLIGOR: Each payment description may be: 1. Sent to Family 2. Collection Amount 3. Applied to Current

Support 4. Sent to Fees 5. Sent to Other 6. Applied to Past Due

Support 7. Refunded

Text <Amount>


Attachment 1



6 Retrieved from SETS. OBLIGEE: Each payment description may be: 1. Disbursed to Family 2. Collection Amount 3. Applied to Current

Support 4. Disbursed to Fees 5. Disbursed to Other 6. Applied to Past Due

Support 7. Refunded

Text <Amount>


7 Transaction Date Text Retrieved from SETS. The payment transaction date.

8 Payment Amount Text Retrieved from SETS. The payment amount.

Widget Behavior


1 Information Image Display for each section header Tap to display the Explanation of Terms

2 Case-Order Selection

PickerView Display when participant has more than one open case-order

Roll to select a case-order.

Personal Screen Specifications Screen Overview

The Personal screen displays images and text that allows the participant to select the type of information that they want to review. The user navigates to this screen from the Profile image displayed in the top right section of the header.


1 Contact Information Image/text Tap to display Contact Information screen

2 Insurance Information Image/text Tap to display Health Insurance Information screen

3 Employer Information Image/text Tap to display Employer Information screen

4 Child Information Image/text Tap to display Child Information screen

Attachment 1


Widget Behavior


1 Contact Information

Display in top left corner of quadrant

On Click, display Contact Information screen

2 Insurance Information

Display in top right corner of quadrant

On Click, display Health Insurance Information screen

3 Employer Information

Display in bottom left corner of quadrant

On Click, display Employer Information screen

4 Child Information Display in bottom right corner of quadrant

On Click, display Child Information screen

Use Cases UC22-01: Display Personal Screen

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed.

Normal Flow:

1. The user clicks the Profile in the upper right of the header. Post-condition:

1. The Personal screen is displayed.

UC22-02: Display Personal Screen

Precondition:

1. The user is logged into the mobile app. 2. Any screen, other than the Home screen, is displayed.

Normal Flow:

1. The user clicks the Profile in the upper right of the header. Post-condition:

1. The Personal screen is displayed.

Attachment 1


Contact Information Screen Specifications Screen Overview

The Contact Information screen displays customer’s current SETS demographic information including name, date of birth, phone numbers, residential address, and mailing address.


1 Please use the Message- Center to submit any contact information changes

Text/hyperlink Instruction to send contact information updates to the county. Includes a hyperlink to the Reply screen.

2 Full Name Text Retrieved from SETS. The customer’s first and last name.

3 Date of Birth Text Retrieved from SETS. The customer’s date of birth in MM/DD/CCYY format.

4 Home Phone # Text Retrieved from SETS. The customer’s home phone number in XXX-XXX-XXXX format.

5 Cell Phone # Text Retrieved from SETS. The customer’s cell phone number in XXX-XXX-XXXX format.

6 Residential Address Text Section Header

7 Address Line 1 Text Retrieved from SETS. The customer’s residential address line 1.

8 Address Line 2 Text Retrieved from SETS. The customer’s residential address line 2, if any.

9 Apt Text Retrieved from SETS. The customer’s residential apartment number, if any.

10 City Text Retrieved from SETS. The customer’s residential city.

11 State Text Retrieved from SETS. The customer’s residential state.

12 Zip Code Text Retrieved from SETS. The customer’s residential zip code.

13 Country Text Retrieved from SETS. The customer’s residential country.

14 Mailing Address Text Section Header

15 Address Line 1 Text Retrieved from SETS. The customer’s mailing address line 1.

16 Address Line 2 Text Retrieved from SETS. The customer’s mailing address line 2, if any.

17 Apt

Text Retrieved from SETS. The customer’s mailing apartment number, if any.

18 City

Text Retrieved from SETS. The customer’s mailing city.

19 State

Text Retrieved from SETS. The customer’s mailing state.

Attachment 1



20 Zip Code

Text Retrieved from SETS. The customer’s mailing zip code.

21 Country Text Retrieved from SETS. The customer’s mailing country.

Widget Behavior


1 Message hyperlink

On click, display Reply screen with message topic Contact Information Change and case/order pre-selected. The expanded message fields are displayed.

Use Cases UC23-01: Display Contact Information Screen

Precondition:


Normal Flow:

1. The user taps the Profile in the top right section of the title bar. 2. The Personal screen is displayed. 3. The user taps the Contact Information icon.

Post-condition:

1. The Contact Information screen is displayed.

UC23-02: Contact Information – Reply to County

Pre-condition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the Profile in the upper right of the header. 4. The Personal screen is displayed. 5. The user taps the Contact Information image. 6. The Contact Information screen is displayed.

Normal Flow:

1. The user taps the “Message Center” contained within the text at the top of the Contact Information screen.

Post-condition:

Attachment 1


1. The Reply screen is displayed. 2. The case-order is pre-selected based on the case-order displayed on the Contact

Information screen. 3. The message topic “Contact Information Change” is pre-selected. 4. The user enters text and clicks the Send button.

Health Insurance Screen Specifications Screen Overview

The Health Insurance screen displays each of the customer’s current SETS health insurance information associated with the case-order selected. The screen also includes a hyperlink that redirects the customer to the New Message screen with the message topic populated with Health Insurance Change or Addition.

UI Overview


1 Please use the Message Center to submit any insurance information changes

Text/hyperlink Instruction to send health insurance information updates to the county. Includes a hyperlink to the Reply screen.

2 No Data Available Text Text is displayed when no active insurance records in SETS.

3 Case-Order: Text Retrieved from SETS.

4 Provider Name Text Retrieved from SETS. The health insurance provider name.

5 Policy # Text Retrieved from SETS. The health insurance provider name.

6 Group # Text Retrieved from SETS. The health insurance group number.

7 Begin Date Text Retrieved from SETS. The health insurance begin date.

8 Covered Participants Text Retrieved from SETS. The case participant’s covered by the health insurance.

Widget Behavior


1 Message hyperlink

On click, display Reply screen with message topic Health Insurance Change or Addition and case/order pre-selected. The expanded message fields are displayed.

Attachment 1


Use Cases UC24-01: Display Health Insurance Screen

Precondition:


Normal Flow:

1. The user taps the Profile in the top right section of the title bar. 2. The user taps the Health Insurance icon.

Post-condition:

1. The Health Insurance screen is displayed.

UC24-02: Health Insurance – Reply to County

Pre-condition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the Profile in the upper right of the header. 4. The Personal screen is displayed. 5. The user taps the Health Insurance image. 6. The Health Insurance screen is displayed.

Normal Flow:

1. The user taps the “Message Center” contained within the text at the top of the Health Insurance screen.

Post-condition:

1. The Reply screen is displayed. 2. The case-order is pre-selected based on the case-order displayed on the Health

Insurance screen. 3. The message topic “Health Insurance Change or Addition” is pre-selected. 4. The expanded text fields are displayed. 5. The user enters text and clicks the Send button.

Employer Screen Specifications Screen Overview

The Employer screen displays each of the customer’s current SETS employers. If a customer has more than 10 open employment records in SETS, only 10 employers will display.

Attachment 1


UI Overview


1 Please use the Message Center to submit any employer information changes

Text/hyperlink Instruction to send employer information updates to the county. Includes a hyperlink to the Reply screen.

2 No Data Available Text Text is displayed when no active employer records in SETS.

3 Employer Name Text Retrieved from SETS. Displays the employer name.

4 Suite Text Retrieved from SETS. Displays the employer (work site) address suite.

5 City Text Retrieved from SETS. Displays the employer (work site) address city.

5 State Text Retrieved from SETS. Displays the employer (work site) address state.

6 Zip Code Text Retrieved from SETS. Displays the employer (work site) address zip code.

Widget Behavior


1 Message hyperlink

On click, display Reply screen with message topic Employer Change or Addition and case/order pre-selected. The expanded message fields are displayed.

Use Cases UC25-01: Display Employer Information Screen

Precondition:


Normal Flow:

1. The user taps the Profile in the top right section of the title bar. 2. The user taps the Employer Information icon.

Post-condition:

1. The Employer Information screen is displayed.

UC25-02: Employer – Reply to County

Attachment 1


Pre-condition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the Profile in the upper right of the header. 4. The Personal screen is displayed. 5. The user taps the Employer image. 6. The Employer Information screen is displayed.

Normal Flow:

1. The user taps the Message Center contained within the text at the top of the Employer screen.

Post-condition:

1. The Reply screen is displayed. 2. The message topic “Employer Change or Addition” is pre-selected. 3. The expanded text fields are displayed. 4. The user enters text and clicks the Send button.

Child Information Screen Specifications Screen Overview

The Child Information screen displays the current child information associated with each case. When the obligor is logged into the mobile app, only each child’s name and emancipation date is displayed. When the obligee is logged into the mobile app, each child’s name, date of birth, emancipation date, and residential address is displayed.

The Child Information screen shall be available for cases that are not spousal-support only. The user receives an error message on the Child Information screen - ‘Spousal Support only; No child information’ if the user tries to view a spousal-support only case (In SETS: CASE02-CDE-TYPE-CASE = NDSS).

UI Overview Obligor View of Child Information: # Item Name Kony Widget Type Description

1 Case / Order Text/hyperlink Case / Order selection.

2 Full Name Text Retrieved from SETS. The child’s first and last name.

4 Expected Emancipation Date

Text Retrieved from SETS. The child’s expected emancipation date.

Obligee View of Child Information:

Attachment 1



1 Case / Order Text/hyperlink Case / Order selection.

2 Full Name Text Retrieved from SETS. The child’s first and last name.

3 Date of Birth Text Retrieved from SETS. The child’s date of birth in MM/DD/CCYY format.

4 Expected Emancipation Date

Text Retrieved from SETS. The child’s expected emancipation date.

5 Residential Address Text Retrieved from SETS. The child’s residential address line 1.

6 Apartment Text Retrieved from SETS. The child’s residential apartment number, if any.

7 City Text Retrieved from SETS. The child’s residential address city.

8 State Text Retrieved from SETS. The child’s residential address state.

9 Country Retrieved from SETS. The child’s residential address country.

10 Zip Code Text Retrieved from SETS. The child’s residential address zip code.

Widget Behavior


1 Case / Order On tap, the picker view widget displays the participant’s opens case/orders.

Use Cases UC26-01: Display Child Information Screen

Precondition:


Normal Flow:

1. The user taps the Profile in the upper right of the header. 2. The Personal screen is displayed. 3. The user taps the Child Information icon.

Post-condition:

1. The Child Information screen is displayed.

UC26-02: Display Child Information for a Different Case

Attachment 1


Precondition:


Normal Flow:

4. The user taps the Profile in the upper right of the header. 5. The Personal screen is displayed. 6. The user taps the Child Information icon. 7. The user selects a Case / Order from the list.

Post-condition:

2. The Child Information screen is displayed for the selected case.

County Agency Directory Screen Specifications Screen Overview

The County Agencies screen displays a list of county agencies sorted alphabetically by county name. Clicking a name navigates the user to the County Agency screen with the Child Support Enforcement Agency information displayed.


1 Alphabetical Character

Text/hyperlink The first letter of the county name.

2 County Text County Name

These items repeat. The list starts with a row with an A followed by rows displaying all county names that begin with the letter A, then a row with a B displays followed by rows displaying all county names that begin with B, etc.

Widget Behavior


1 County Name hyperlink

On Click, display the County Agency screen with the information for the selected county.

Use Cases UC27-01: Display County Agency Directory Screen

Precondition:

1. The user is logged into the mobile app.

Attachment 1


2. The Home screen is displayed. 3. User taps the hamburger menu. 4. The Hamburger menu is displayed.

Normal Flow:

1. The user taps the County Agency Locations option. Post-condition:

1. The County Agencies screen is displayed.

UC27-02: Display Selected County Agency Screen

Precondition:

1. The Hamburger menu is displayed. Normal Flow:

1. The user taps the County Agency Locations option. 2. The County Agency Locations screen is displayed. 3. The user taps any county in the list.

Post-condition:

1. The County Agency screen is displayed with the selected county information.

County Agency Specifications Screen Overview

The County Agency screen displays the Child Support Enforcement Agency (CSEA) information.


1 County Text County Name

2 Header Text Child Support Enforcement Agency

3 Agency Contact Text Agency contact’s name and title.

4 Agency Address Text Agency address

5 Agency Phone Number Phone Agency phone number

6 Agency Fax Number Text Agency fax number

7 Agency Hours Text Agency hours of operation.

8 Get Directions Button Opens device’s native maps app.

9 Send Message Button Opens the New Message screen.

Attachment 1


Widget Behavior


1 Agency Phone Number

Displays the agency phone number.

On click, the native phone is launched with the selected phone number.

2 Get Directions Displays the county agency address location.

On click, the native maps app is launched with the county agency address location.

3 Send Message Link to New Message screen.

On click, the New Message screen is displayed.

Use Cases UC28-01: Display County Agency Screen

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the hamburger menu. 4. The Hamburger menu is displayed. 5. The user taps the County Agency Locations option.

Normal Flow:

1. The County Agency Locations screen is displayed. 2. The user taps a county agency name.

Post-condition:


UC28-02: Display Selected County Agency Screen

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the case/balance information. 4. The Support Order Detail screen is displayed.

Normal Flow:

1. The user taps the Child Support Contact: <agency name>

Post-condition:

Attachment 1



UC28-03: Launch Phone Call to County

Precondition:


Normal Flow:

1. The user taps the phone number.

Post-condition:

1. The native phone dialer launches and initiates a phone call to the selected number.

UC28-04: Launch Get Directions to County

Precondition:


Normal Flow:

1. The user taps the Get Directions button.

Post-condition:

1. The native maps app launches with the county address location displayed.

UC28-05: Launch Message to County

Precondition:


Normal Flow:

1. The user taps the Send Message button.

Post-condition:

1. The Reply screen is displayed with the county selected.

Attachment 1


Change Password Specifications Screen Overview

The Change Password screen allows the user to change their child support mobile app/web portal password.

Note: When a user changes their password in the customer web portal or mobile app, a password change confirmation page is displayed and an email is sent to the customer advising them that their password has been changed


1 Current Password Text Box Text box that allows 15 characters (no spaces) for user’s current password.

2 New Password Text Box Text box that allows 15 characters (no spaces) for user’s new password.

3 Confirm New Password

Text Box Text box that allows 15 characters (no spaces) to confirm user’s new password

4 Submit Button Submit new password.

Widget Behavior


1 Current Password

Validate entry to user’s password in DB2.

If current password is valid, continue validation of new password.

Tap to display the alphabetical keyboard.

2 New Password

Validate the entry is 6 to 15 characters with no spaces. Validate the entry matches the Confirm New Password entry.

If New Password matches the Confirm new Password, save new password.


Confirm New Password

Validate the entry is 6 to 15 characters with no spaces. Validate the entry matches the New Password entry.

If New Password matches the Confirm new Password, save new password.


Submit Current Password must match user password in DB2. New Password must be the same as the Confirm New Password.

On Submit, the entered password is validated to the user password in DB2, then the entered New Password is validated to the Confirm New Password.

Attachment 1


Use Cases UC29-01: Enter New Password

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the hamburger menu. 4. The Hamburger menu is displayed. 5. The user taps the Change Password option.

Normal Flow:

1. The Change Password screen is displayed. 2. The user enters their valid current password, a new password, and the same new

password in the Confirm New password field. 3. The user clicks the Submit button.

Post-condition:


UC29-02: Enter Invalid Current Password

Precondition:


Normal Flow:

1. The Change Password screen is displayed. 2. The user enters their invalid current password, a new password, and the same new

password in the Confirm New password field. 3. The user clicks the Submit button.

Post-condition:

1. A pop-up message displays advising user the current password entered is invalid. Note: The account will lock after 6 invalid current password entry attempts.

UC29-03: New Password and Confirm New Password Do Not Match

Precondition:

Attachment 1



Normal Flow:

1. The Change Password screen is displayed. 2. The user enters their valid current password, a new password, and different text in the

Confirm New Password. 3. The user clicks the Submit button.

Post-condition:

1. A pop-up message displays advising user the new password and the confirm new password do not match.

UC29-04: Invalid New Password and Confirm New Password

Precondition:


Normal Flow:

1. The Change Password screen is displayed. 2. The user enters their valid current password, an invalid new password and invalid

Confirm New Password. 3. The user clicks the Submit button.

Post-condition:

1. A pop-up message displays: ‘The new password you entered is not valid. Please try again’.

Change E-mail Address Specifications Screen Overview

The Change E-mail Address screen allows the user to change their child support mobile app/web portal e-mail address.

Attachment 1



1 Current E-mail Address

Text Displays the user’s current e-mail address.

2 New E-mail Address Text Box Text box that allows alphanumerical characters and the @ and period special characters (no spaces).

3 Confirm New E-mail Address

Text Box Text box that allows alphanumerical characters and the @ and period special characters (no spaces).

4 Submit Button Submit new e-mail address.

Widget Behavior


2 New E-mail Address

Validate the entry contains no spaces and contains an @ special character

E-mail address must not contain any spaces and must contain an @ special character.

Tap to display the keyboard with alphabetical characters and the @ special character.

Confirm New E-mail Address

Validate the entry contains no spaces and contains an @ special character

E-mail address must not contain any spaces and must contain an @ special character.

Tap to display the keyboard with alphabetical characters and the @ special character.

Submit Validate the New E-mail Address entry matches the Confirm New E-mail Address entry.

The New E-mail Address must match the Confirm New E-mail Address entry.

On Submit, the entered e-mail addresses are validated for an @ special character, then the New E-mail Address entry is validated with the Confirm New E-mail Address entry. The new e-mail address must be unique and not associated with any other participant’s e-mail address in SETS.

Use Cases UC30-01: Enter Matching E-mail Addresses

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The user taps the hamburger menu. 4. The Hamburger menu is displayed. 5. The user taps the Change E-mail Address option.

Normal Flow:

Attachment 1


1. The Change E-mail Address screen is displayed. 2. The user enters a new e-mail address password (with no spaces but with an @ sign)

then enters the same e-mail address in the Confirm New E-mail Address text box. 3. The user clicks the Submit button.

Post-condition:

1. The Home screen is displayed. 2. An e-mail is sent to both the prior and the new e-mail address advising user the e-mail

address has been changed.

UC30-02: Enter Invalid New E-mail Address

Precondition:


Normal Flow:

1. The Change E-mail Address screen is displayed. 2. The user enters the same e-mail address in the New E-mail Address text box and in the

Confirm New E-mail Address text box. The entries do not contain the @ special character.

3. The user clicks the Submit button.

Post-condition:

1. A pop-up message displays advising user that the e-mail address must contain the @ special character.

UC30-03: New E-mail Address and Confirm New E-mail Address Do Not Match

Precondition:


Normal Flow:

Attachment 1


1. The Change E-mail Address screen is displayed. 2. The user enters an e-mail address in the New E-mail Address text box but a different e-

mail address in the Confirm New E-mail Address text box. 3. The user clicks the Submit button.

Post-condition:

1. A pop-up message displays advising user the new e-mail address and the confirm new e-mail address do not match.

Need Help Screen Specifications Screen Overview

The Need Help screen displays links to important information. Currently, this screen contains buttons which navigate the user to the ODJFS Disclaimer Policy and to the Frequently Asked Questions.


1 Header Text Need Help

2 Disclaimer Policy Button Displays the ODJFS Disclaimer Policy

3 FAQ Button Displays the ODJFS Frequently Asked Questions

Widget Behavior


1 Disclaimer Policy

The text is provided by OCS Office of Communications for the disclaimer policy and must be the same as the web portal disclaimer policy. Currently, the disclaimer is available to the public at: http://jfs.ohio.gov/ocomm_root/privacy.stm

On Click, the disclaimer http://jfs.ohio.gov/ocomm_root/privacy.stm is opened in the native browser window (or in a mobile app screen containing the same information).

2 FAQ The FAQ is provided by OCS Policy Department. Currently, the FAQ is available to the public at: http://jfs.ohio.gov/ocs/OCSFAQs.stm#21 Note: this information refers to “Child Support Customer Service Portal - Registration and Login Questions and Answers” and may be updated by OCS.

On Click, the disclaimer http://jfs.ohio.gov/ocs/OCSFAQs.stm#21 is opened in the native browser window (or in a mobile app screen containing the same information).

Attachment 1


Use Cases 31-01: Display the Need Help Screen

Precondition:


Normal Flow:

1. The User taps Need Help.

Post-condition:

1. The Need Help screen is displayed.

UC31-02: Display the Disclaimer Information

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The User taps Need Help.

Normal Flow:

1. The user taps the Disclaimer button.

Post-condition:

1. The Disclaimer Information is displayed (TBD).

UC31-03: Display the FAQ Information

Precondition:

1. The user is logged into the mobile app. 2. The Home screen is displayed. 3. The User taps Need Help.

Normal Flow:

1. The user taps the FAQ button.

Post-condition:

1. The FAQ Information is displayed (TBD).

Attachment 1


Screen Layouts The following screens were prototyped in Kony Visualizer software and published to a Visualizer preview app for ODJFS review. These prototyped screens are to be used as functional prototypes only, not for design requirements.

Attachment 1


Figure 1 – Splash

Attachment 1


Figure 2 - Login

Attachment 1


Figure 3 – Touch ID

Attachment 1


Figure 4 - Registration This Registration screen was prototyped based on current customer web portal registration screen and accessible from the Login screen ‘New User Registration’ button.

Attachment 1


Figure 5 – Need Help

Attachment 1


Figure 6 - Home

Attachment 1


Figure 7 - County Bulletins

Attachment 1


Figure 8 - Customer Alerts

Attachment 1


Figure 9 - Support Order Detail – Case, Support & Balance Information

Attachment 1


Figure 10 - Support Order Detail – Payments

Attachment 1


Figure 11 – Payment History Tapping the button on this screen will call a web service to generate a Payment History Report with 24 months of data in PDF format. The way the PDF is shown is dependent on the native behavior of the underlying device operating system. The iOS devices usually can show the PDF within the application in browser view. Conversely, in Android the PDF will have to be downloaded and the user will use their native PDF reader to open and view the file. The native behavior cannot be changed and the users on those devices are used to that experience. Once the user opens the PDF file, he/she can use the native options to print, email, or share the PDF document.

Attachment 1


Figure 12 – Message Center

Attachment 1


Figure 13 – Message (threads)

Attachment 1


Figure 14 - New Message

Attachment 1


Attachment 1


Figure 15 - Reply

Attachment 1


Figure 16 - Hamburger Menu

Attachment 1


Figure 17 - Change Password

Attachment 1


Figure 18 - Change E-mail Address

Attachment 1


Figure 19 - County Agency Directory

Attachment 1


Figure 20 - County Agency

Attachment 1


Figure 21 - County Agency – Get Directions Permissions

Attachment 1


Figure 22 - County Agency – Get Directions Launch Native Map

Attachment 1


Figure 23 – Personal

Attachment 1


Figure 24 – Contact Information

Attachment 1


Attachment 1


Figure 25 - Health Insurance

Attachment 1


Figure 26 – Employer Information

Attachment 1


Attachment 1


Figure 27 – Child Information – Obligee

Attachment 1


Figure 28 – Child Information – Obligor

Attachment 1


References Kony

© Copyright 4/20/17 Kony, Inc.

Mobile Ideation Session April 20, 2017

Google

https://play.google.com/intl/en_us/badges/

https://developer.android.com/distribute/marketing-tools/brand-guidelines.html

Mobile Application Functional Specification Document...x Provide consistency in user experience for...

Documents

Transcript of Mobile Application Functional Specification Document...x Provide consistency in user experience for...