1

OASISEnterpriseMobileSupportHelpDocument

Version-1.1

Date-March1,2018

2

Contents1. LoginScreen.........................................................................................................................................3

2. HomeScreen........................................................................................................................................4

3.FSODetailScreen.....................................................................................................................................8

4.ArrivalScreen...........................................................................................................................................9

5.SafetyScreen.........................................................................................................................................12

6. PhotoScreen......................................................................................................................................18

7. BOMScreen.......................................................................................................................................22

8. ZTPScreen..........................................................................................................................................25

9. OVTScreen.........................................................................................................................................27

10. AuditScreen...................................................................................................................................29

11. S2Screen........................................................................................................................................32

12. DepartureScreen...........................................................................................................................35

13. Timer(Disabledcurrently).............................................................................................................39

14. Autoupload...................................................................................................................................40

15. RecordScreen................................................................................................................................41

15.AllRecordScreen.................................................................................................................................43

3

1. LoginScreen1.1 Introduction-

§ LogincredentialsaresameasInstallerPortalcredentialsforloggingintotheapplication.§ OnlyforInstallers.

4

1.2Features-

1.2.1Loginscreen–

• UsercanclickontheForgotPassword?Linktoresetpasswordontheportal.

• Online/OfflinestatusontheLoginScreensuggeststhatapplicationisconnectedto

internetoritsoffline.

2. HomeScreen1.2 Introduction

§ Firstscreenafterusersuccessfullogin.

5

2.2Features-

2.2.1Jobschedules–

• PreviousJobSchedulescontainsthosejobswhichpassesthecurrentdate.• CurrentJobschedulescontainJobswhicharescheduledforcurrentdateorinfuture

2.2.2 WorkorderView–LocationLevel

• UnlikepreviousOASISapps,allworkordersscheduledundersamelocationaregroupedtogethertopresentlocationlevelview.AlsocalledasParentview.

• Helpsindoingbulkoperations,avoidsre-do&duplicationsoneachFSOs.• Usercanclickonthe+icontoexpandallthejobsforthatlocation.• Clickonlocationviewtostartlocation/parentflow

6

• ThestatusatthelocationLevelgetchangebasedonthestatusofthechildFSOs

• UsercanclickontheMapicontoseethelocationoftheJob.• UsercanclickonthephoneIcontocallthedealer.

Location/ParentView

7

• IconsforscheduledSitescanbeseenatthelocationLeveltheseiconsareliketheIPforthoseservices.

• UsercanseebriefdetailsoftheFSOscheduledlikeOrderedSiteType,scheduleddate,San,FSO#,OrderedTypeandSubOrderType.

2.2.3Calendarschedules–

• UsercancheckthecurrentandfuturejobsschedulesbyswitchingtoCalendarviewontheHomeScreen

• ScheduledjobswillbeshownonCalendarscreenasbelow

• Usercannavigatetothesejobsfromcalendarviewalso.• ThegroupedjobswilldisplayLocationFSOnumberasintheIP.• ThedesignandrepresentationissimilartoIP.• ByclickingontheLocationFSOusercangototheFSODetailsscreen.

8

2.2.3Bottomnavigationbar–

• Syncbuttoncanbeusedtosyncdatafromservermanuallyanytime.• AllRecordsbuttontakestheusertoAllRecordsScreenwhereusercanseetheFSOthat

hehascollecteddatasofar.Usethesamescreentodobulkuploadorbulkdelete/housecleaning.

• LoginbuttontakestheUsertoLoginScreen.• Configbuttontakestheusertotheappconfigurationscreenwhereusercanchange

someconfigurationsrelatedtotheapplication.

3.FSODetailScreen3.1 Introduction-ThisscreenhelpusertoaccessdetailregardingeachFSO.AfterpressingFSO,usercanaccessFSOdataindetail.

3.2 Features-

3.2.1 Phoneoption-

9

• Afterclickingabovelink,usercandirectlycommunicatetothecustomer.

3.2.2 Emailoption-

• Afterclickingabovelink,usercandirectlysendemailtothecustomer.

3.2.3 Mapdisplayoption-

• Afterclicking,usercandirectlyseethelocationofthecustomer.

3.2.4 Otherfeatures-• Afterselectinglocation/parentFSOfromhomescreen,userwillswitchtoFSOdetail

screen.• IfuserselectstheindividualFSOeitherfromhomeorcalendarscreen,detailsfor

thatparticularFSOwillbeexpanded.

4.ArrivalScreen4.1Introduction-

• Arrivalscreenisworkingastheentrypointforthisapplication.AfterpressingnextonFSOdetailsscreen,userwillgettotheArrivalScreen.

• OASISsupportsbulkArrival–TechisallowedtoreportbulkArrivalIVRonmultipleFSOsscheduledundersamelocation.

• Usethecheckbox’sonlefttoselect/unselecttheFSO’storequestbulkIVR.

4.2Features-

4.2.1Introduction-

10

• Atthispoint,usercanselectfuture/currentFSOsviacheckboxselection.• Aftersuccessfularrival,usercannotreselectarrivedFSOs.

4.2.2.1Userisinofflinemode-

4.2.2.1.1Ifdistanceisequalorlessthanlimit-

• AfterpressingNEXT>>button,VerifyArrivalpopupwillopenwithYSE&NOoptionoverthescreen.UseYestocontinuetosafetystep.

4.2.2.1.2Ifdistanceismorethanlimit-

11

• AfterpressingNEXT>>button,VerifyArrivalpopupwillopenwithProceed&Abortoptionoverthescreen.

• Atextbox/areatoenterthereasonforbeingfarawaywilldisplayinsidethepopup.

• Techissupposedtoenterreasonforbeingfarawayfromorderedlocationinordertoproceed.

• AfterpressingAbort,userwillberedirectedtohomescreen.

4.2.2.2IVR-(Successresponse)-

• AfterpressingNEXT>>button,VerifyArrivalpopupwillopenwithYSE&NOoptionoverthescreen.

• AfterpressingYES,ifserverreturnssuccessasresponsethenuserwillbenavigatedtosafetyscreenwithoutanymanualeffort.

4.2.2.3IVR-(Failureresponse)-

• AfterpressingNEXT>>button,VerifyArrivalpopupwillopenwithYSE&NOoptionoverthescreen.

• AfterpressingYES,ifserverreturnsfailureasresponsethenIVRSubmissionpopupwillopenwithacknowledgmentcheckbox.

• TechissupposedtoreportIVRmanuallyeitherthroughcallorIPIVRformandthenhavetoacknowledgeinOASISthatIVRhasbeensubmittedofflineinordertoproceedtonextsteps.

• Afterselectingcheckbox,usercanmovetosafetyscreen.

4.2.3CaptureGPS-

12

• BeforecapturingGPSlocation,usermustenablethelocationserviceoverthedevice.• Afterpressing"CaptureGPS"button,GPSautocollecteddatawillfilltotherespective

boxes.• UsercanalsomanuallyenterGPSlocation.

5.SafetyScreen5.1FEATURES-

5.2.1SafetySplashScreen-

• Afterperformingarrival,userwillbelandedonSafetySplashscreen.• ThisscreencontainsTerms&Conditionsrequiredforlegalpurposes.• ThescreenwillhaveacheckboxandaCancelbutton.UsermayclickonCancelbutton

toskipthesafetyscreenormaycheckthecheckboxtolandonSafetyScreen.

13

5.2.2SafetyScreen-

• AllrequiredsafetyquestionsandsignaturesaremandatorybeforeDeparture.

14

• Alltherequiredquestionswillbehighlighted.Onceansweredhighlightwillberemoved.

• Alsoatthetopofthescreen,userwillhaveaquestion“Willyouberequiredtoworkatheights”selected“No”bydefault.Once“Yes”isselected,all“Permittoworkatheights”andsomeotherimportantquestionswillbecomemandatoryandwillbegethighlighted.

15

5.2.2.2ScreenLayout&Functionality-

5.2.2.2.1SafetyLinking-

o SafetypagewillhaveadropdowntoselectFSOs.

o **Onceallsafetyrequiredquestionshavebeenanswered,userwillbeprovidedwithoptionto“SaveandLink”.Userhastousethatbuttontosavethesafetyformandtolinkthesametoallotheravailable/arrivedFSO’sundersamelocation.

o Note:Safetywon’tlinktoothersarrivedFSO’sundersamelocationifthisisnotmanuallyclickedbyuser.

16

o Usercanremove/re-linkthesafetyform/data.o Ifneeded,Usercansave/collectsafetyinformationperFSO.

§ Oncelinkhasbeensaved,userwillbeprovidedwithanoptiontoedit/modifytheFSOdata.Onceselected,itwillbreakalltheexistinglinkstotheselectedFSO.

17

o IncaseanFSOislinkedtootherFSO,itwillprovidetheoptiontobreakthelink.o IncaseanyFSOisemptyandanoldparentFSOexists,userwillbeprovidedwith

optiontolinkwiththeexistingParentFSOs.

5.2.2.2.2StatusdisplayandIndentation-

• StatusofallthearrivedFSOswillbedisplayedatthetopofsafetypage.• OnceanFSOwillbelinkedtootherFSO,itwillbedisplayedwithanindentation.• Frombelowscreenshot,SafetydatahasbeensavedunderFSO#6538679andlinked

to6538689.

18

5.2.3HighlightRequiredFields-

• Onceuserwilllandonsafetyscreen,alltheincompleterequiredfieldswillbehighlighted.• Thefieldswillbedisplayedwitharedborder.Ifuserwilltrytomovetothenextpage,a

warningpopupwillwarntheuserregardingnon-completionofmandatoryfields.

6. PhotoScreen6.1 Introduction-Photoscreenisusedtocapturephotosinrespectofdifferentquestions.Itshowsallrequired/notrequiredquestionsinverticalscrollbarforarrivedFSOs.Alltherequiredquestionsborderedwithredcolor.Usercancapturemultiplephotosinrespecttoeachquestion.Usercanfurtherviewallthecapturephotosingallery.Usercanprocessgalleryphotosvialeft&rightarrows.Usercantakemaximum75photosinrespectofeacharrivedFSO.Usercancapture/importphotofromcamera/galleryrespectively.6.2 Features-

6.2.1 Carouselview-

• AllarrivedFSOmustvisibleasnodeinthisview.• Eachnodeshouldbeclickable.• Afterclicking,pagescrolltorespectiveFSO&expandthecontent.• Left&rightarrowcanbeusedtoprocessviewinleft&rightdirectionrespectively.

19

6.2.2 Camera/Importtoggleoption-

• Usercancaptureimagebyusingcamerafeatureofdevice.• Usercanimportimagefromdevicegallery.

6.2.3 Requiredquestion-• Allrequiredquestionsshouldhighlightviaredcolorborder.

• Aftertakingphoto,redbordershouldreplacebygreenborder.

6.2.4 Multiplephotoscollection-

• Usercancapture/importmultiplephotosinrespectofeachquestion.

20

• Aftertakingmultiplephotosleft/rightarrowshouldvisibletoprocessinleft/rightdirection.

6.2.5 Imagedeletion-

• Afterpressingcrossicon,usercandeletecapture/importphoto.

6.2.6 Othersection-

• Usercancapture/importphotosinothersectionavailableineachFSO.• Beforecapturingphoto,userfirstentersthedescription.• Ifuserdoesnotenterthedescriptionthenanerrorpopupwillgenerateoverthe

screen.

6.2.7 Nextbutton-

21

• Afterpressingnextbutton,usercanmarkphotoscreenphasecomplete.• Ifalltherequireddatahastakensuccessfullythenthisphasewillbemarkas

completed.• Ifanyrequireddataismissing,thenanerrorpopupisthrownasbelow.

Forbeforephotoscreen-

Forafterphotoscreen-

6.2.8 ToastNotification-

• Aftercapturingallrequiredphotos,abovetoastnotificationwillbedisplayedtothe

user

6.2.9 Blocking‘Afterphoto’screen-

22

• Note:Allrequired‘BeforePhotos’havetobetakenpriorcapturing‘AfterPhotos’.

Aboveerrormessageisdisplayedin‘AfterPhotos’screenperFSOblockifbeforephotosaremissing.

7. BOMScreen7.1 Features-

7.1.1 Carouselview-

• AllarrivedFSOmustvisibleasnodeinthisview.• Eachnodeshouldbeclickable.• Afterclicking,pagescrolltorespectiveFSO&expandthecontent.• Left&rightarrowcanbeusedtoprocessviewinleft&rightdirectionrespectively.

7.1.2 Scanbutton-

• UsercanscaneitherPartnumberorSerialnumber.• Ifpartnumberhasbeendetected,thenappwillsearchforP/Nandwillselecttheradio

fromthatgroup.OtherwisewillpopulateinSerialfield.

7.1.3 +/-iconineachgroup-

23

• Iconusedtocollapse/expandthegroupentriestomakescreenlessscrollable.7.1.4 Warningpopupasbelowwouldbethrowntouserifanyrequiredserialsare

missing.Nextbutton-

• Ifuserdoesn’tfilltheentirerequiredfield,thenafterpressingnextbuttonabove

errorpopupwilldisplayoverthescreen.7.1.5 Othersection-

Image2 Image1

• Usercanaddotherdataafterpressing+icon.• Ifpartnumberhasbeendetected,thenOASISfillsintothepartnumberfield

otherwisefillsintotheserialnumberfield.• Ifpartnumberalreadybeencollected,thendisplay(Image1)aserrorpopup.• Ifpartnumberdoesn’texist,thenappwilldisplay(Image2)aserrorpopup.

7.1.6 P/Ngroupwithredborder-

• Requiredpartnumberblocksaresurroundedbyredborders.

24

7.1.7 P/Ngroupwithgreenborder-

• Ifuserfilltherequiredentry,thenredturnstogreen.

7.1.8 ToastNotification-

• Afterfillingallrequiredbarcodedata,abovetoastnotificationshoulddisplayover

thescreen.7.1.9 Resetbutton-

• Resetalltheentries.• Done&refreshiconreplacedviaediticon.

• Collapsethecomment&Serialboxes&"PartNumber*Description"columnentries.

7.1.10 ZTPenabledpartnumbers-

• TheZeroTouchEnabledpartswillhaveadditionalparameterfromIPtoinform

OASISthatthispartshouldhaveZeroTouchIconasshowninaboveUI.

25

• Ifrequiredfieldhasscandataforselectedpartnumber,thendisplayzerotouchiconwithgreenborder.

• Ifrequiredfieldisemptyforselectedpartnumber,thendisplayzerotouchiconwith

redborder.

7.1.11 BlockingoverBOMscreen-

• Note:Allrequired‘BeforePhotos’havetobetakenpriorworkingonBOM.Above

errormessageisdisplayedin‘BOM’screenperFSOblockifanybeforephotosaremissing.

8. ZTPScreen8.1Introduction-

1. ZTPbydefaultisdisabledfornow–tillitpassesalltestphases.2. Priortolaunchztp,EnableZTPstepinHomeà“UserConfig”.

PollingintervalcanbesettomanagethetimeafterwhichtheZTPactionsshouldberepolledtofetchlatestdatafromIP.

3. TheZTPenabledpartsselectedbyInstalleronBOMScreenwillappearontheZTP

screen.

26

4. Thereareindividualoperationsonthisscreenforthepartslike“CHECKSTATUS”,”ASSOCIATION”,DISASSOCIATION”indicatedbyIcons.

5. AsectionwillshowstatusofAssociation/DissociationbasedontheresponsefromtheAPIasbelow-- UsercanselectSite-Typefromthedropdown.- Usercanalsoselectdevicetypefromthedropdownbasedonvaluecomingfrom

Server.

27

6. ZTPscreensupport“ALL(bulkoperation)”featuretoperformCHECKSTATUS,ASSOCIATIONandDISASSOCIATION.

7. ZTPscreensupportpollingrequestprocessingcounterandusercanstopthiscounterafterpressingprocessingcounteroptionasdisplaybelow-

8. ZTPscreenhas“Stop”buttontostopcurrent“ALL”featurerequest.

9. ZTPscreenhasoptiontoexpand&collapse“note”windowtoreadlongnotesclearly.

10. InstallerscouldchangetodifferentSANundersamelocation,usingdropdownshownbelow

9. OVTScreen9.1 INTRODUCTION-

28

OVTscreensareusedforsiteverification.

FEATURES-

UIDesignandLayout:

1. RetrieveOVTSignoffbuttonattop2. EachFSOswillbedisplayedinatabularformatwithfields:SignOff#textbox,Type

textbox,Datetextbox&‘LaunchOVT’button.

Functionalities:

LaunchOVT:UsercanlaunchOVTtoolinmobilebrowser.

29

RetrieveOVTSignoff:ThisbuttonwillretrieveSignoffnumber,SignoffBy,SignoffDateandTypefromserverandwillfilltheminrespectivefields.

• UserwillalsobeindicatedwiththenumberofSignoffsreceived.

10. AuditScreen10.1 INTRODUCTION–TechissupposedtoansweralltherequiredAuditquestionsperFSO.Allthemandatoryquestionsarestar(asterisk)marked.

30

• Visitquestionsforthelocationwillbeshownunder“PerVisit”sectionandatthealsoattheFSOLevel.

• Oncequestionforthelocationwillbeshownunder“Once”sectionandatthealsoattheFSOLevel.

• Answersfrom“PerVisit”&“Once”willbeupdatedtothesamequestionsunderFSO.

• IfthedataischangedatFSOlevelforVISITquestionitwillbechangedeverywherefortheFSO’shavingthatquestion.

31

• AuditquestionsaremandatorytoperformDepartureComplete.OnceAudit

questionsaredone,usercannavigatetoS2Screenusingnextbutton.• ErrorpresentedasbelowonpressofNEXTbuttonifanyrequiredAudit

questionsaremissing

32

• Oncemandatoryauditquestionsarecompleted,atoastmessagewillinformuserthatallmandatoryauditquestionshavebeencompleted.

•

11. S2Screen11.1 Introduction-

S2screenhaveslavelinkingtablethatshowsarrivedFSOsinformationwithchecked/uncheckedboxeswithgreen/redborder.3

• Greenborderindicatethatallthepreviousscreendatahasfilledsuccessfully.

• Redborderindicatestowardstheincompletionofdata.

33

11.2 Features-11.2.1 Checkbox’sandlinking-

• Checkbox–Enabled/Checked-SignatureislinkedandappliedtothatFSO• Checkbox–Unchecked–Signaturedoesn’tapply/linktotheFSOwhichisunchecked.

11.2.2 S2screenimplementationkeypoints-

• Re-linkingisnotallowedoncesignaturehasbeentaken.• Techisallowedtoremovethesignature(usingredcross)andthenre-link.

11.2.3 S2screenupdatescenarios-

11.2.3.1 IfselectedFSOhascollectedcurrentdatesignature-

• Aftertakingsignature,usercannotlink/unlinktheavailableFSOs.Thiswouldrequirenewsignatureagainbydeletingtheoldone.

34

11.2.3.2 LinkedFSO-

• UserisallowedtotakesignatureforinduvialFSO.• GotolinkedFSOusingtopdowntown,andselectedoption“Yes’fromthe

questionabove.ThiswouldremovetheexistinglinkandthenwouldrequirenewsignatureagainforthisFSO.

11.2.4 FSOBordercolor-11.2.4.1 GreenColor–Ifallrequiredinformationcollectedinallphases.

11.2.4.2 RedColor-Ifsomerequiredinformationismissing.

35

11.2.4.3 YellowColor-Eventhoughsomerequiredinformationismissing,ifOVThasbeencompletedthenitshowsasyellow.

12. DepartureScreen12.1 INTRODUCTION-

**Allthemandatoryscreens(Safety,BeforePhotos,AfterPhotos,Auditquestions,S2signature)shouldbecompletedbeforeDepartureComplete,notrequiredifdoingIncomplete.

12.2 FUNCTIONALITY-12.2.1 AutoSelectionforDepartureComplete/Incomplete-

• DepartureComplete/Incompleteoptionsareauto/pre-filledbyOASISbasedonthestatusesofindividualstepscollectedsofar.

• UserisprovidedwithfunctionalitytoenterDepartureNotes,ReasonCodesforeachFSOincaseofDepartureIncompleteetc.Hecandobulkselectionifsamenotes/reasoncodewouldapplyforall.

36

• ForDepartureIncompleteifreasoncodeisnotselectedthenafterpressing“Submit”button.Wewillshowbelowerrormessageandhighlighttheunansweredreasoncodeswithredborder.

37

12.2.2 WarningIcondisplaywithIncompleteFunctionalities-

**AllthemissingstepsarenotifiedinplaceofDepartureCompletecheckbox.

12.2.3 Expand/CollapseReasonNote&Notes-Userwillbeprovidedwitha“+”/”-”icontoexpandandcollapseeachrowforFSOs.TheexpandedrowwillhaveatextfieldtoenterNotesandReasonCode(IncaseDepartureIncompletecheckboxselected).Also,userwillbeprovidedwithbulkexpandandcollapseiconattopheadertoexpand/collapseeachrowalltogether.

38

12.2.4 Bulkselection-Notes/ReasonCode–UserwillbeprovidedwithcommonNotes/Reasoncodefieldsvisibleafterexpandingtopheader.AnyentryinthesefieldswillbereflectedintherespectivefieldsofeachindividualFSO.

12.2.5 DepartureIVRWhilecompletingDeparturefunctionality,userwillgetIVRstatusfromPortal.IncaseofIVRsuccessuserwillbenavigatedtoRecordsscreen.IfIVRstatusisfailure,userwillbeprovidedwithapopup,whichwillshowfunctionalitytocall.UsermayselectcheckboxtomoveaheadtotheRecordsscreen.

12.2.5.1.1 IVRstatusDisplayUserwillbeabletoseeIVRstatusforeachFSObelowFSOdetailsonceIVRstatusisreceived.

39

13. Timer(Disabledcurrently)13.1 Introduction-

ThisfeatureisimplementedtorecordtimespendbyuserforeachFSO.AtimerpopupwillautoopenfirsttimeonBarcodeandautostoponOVTscreens.Usercanopenthetimerfrombottomshortcuts.13.2 Features-13.2.1 Icon-

40

13.2.2 Start/Stopbutton-

• Usercanstart/stopthetimerusingSTART&STOPbuttonsrespectively.

14. Autoupload14.1 Introduction-

• OASISwouldautouploadthework(onlytextdata)toIPonintervalbasis.• Defaulttimeintervalissetto30min• UsercantheintervalfromUserconfigscreen.

41

15. RecordScreen15.1 Introduction-

• ThisscreenhelpusertodisplaysummaryforarrivedFSOs.• ThisscreenalsocontainsQRS(QuickRequirementSummary),ArrivalonSite,

Safety,BarcodeScan,SitePhotos,InstallVerification,S2Signature,DepartureData,Attachments,DeviceInfo&UploadInfosections.

• Bydefault,QRS&UploadInfosectionswouldbeinexpandmode.15.2 Features-

15.2.1 Collapse/ExpandInternaldata-

• Iconusedtocollapse/expandtheinternaldatatomakepagemorereadable.• ‘+’iconisusedtoexpanddata.• ‘-’iconisusedtocollapsedata.

15.2.2 Phasecompletionstatus-

• Phasecompletionstatusmayhaveanyvaluedefinedinaboveattachedphoto.

42

• Afterpressing“NEXT>>”buttonovereachscreenusercanmarkphaseascompleted.

15.2.3 Uploadstatus-

• Uploadstatusmayhaveanyvaluedefinedinaboveattachedphoto.• Uploadedmeansdatahasuploadedsuccessfullytoserver.• Modifiedmeansafteruploading,datahaschanged.• NotUploadedmeansdatastoreatlocalside.

15.2.4 Uploaddata-

• ItwilluploadtheselectedFSOsdataandupdatetheuploadstatus.15.2.5 Deletedata-

• ItwilldeletetheselectedFSOsdata.15.2.6 Clearuploadstatus-

• Afterpressingit,usercanclearuploadstatusofallselectedFSOs.

15.2.7 ExportAttachments-

• Usercanexportcapturedattachmentstogallery.• Afterclosingapplication,usershouldbeabletoaccesscaptureddataintogallery.• AllexporteddatamustbelongtorespectedFSO.

15.2.8 FSOselection-o Usercanselect/deselectFSOsundersamelocationviaabovecheckboxoptions.

43

o Usercanperformthebulkoperations(submit,delete,export,clearstatus)onlyforthoseselectedFSOs.

15.AllRecordScreen15.1Introduction-

§ Allrecordsareusedtodisplayalltheworkorderscollectedsofarwithattachments&textdata.

§ Itpresentsyoutheworkorderinahierarchyi.e.LocationlevelàIndividualChildlevel§ BulkoperationscanbeperformedusingAllRecords.§ Bulksubmit,delete&clearstatusondifferentlocationswithmultipleFSO’scanbe

handledeasily.

15.2Features-