all righty let's go ahead and get started here good morning good afternoon good evening everyone whether you're joining us live or on demand we want to welcome you to uh our mobile app academy once again where we show you how to build and configure mobile apps live on the now platform my name is always is charlie steiner and i work in product marketing here at servicenow today we'll be going through uh getting started with customizing the field service mobile app a new topic for us and something we're very excited to share with you if you're just joining us live for the first time this is a live building series that focuses on managing and building out mobile apps in real time we'll have product experts on hand to provide guidance best practices and answer any of your questions posted in the q a window we host these sessions every two weeks here on zoom at 10 a.m pacific and our recordings are posted on youtube shortly after so those links to the community and her youtube page will be posted in the chat shortly for your reference either right now or after this session we encourage you to check both of those out but what's really important to us here at mobile app accounting is when we get insight from you so again please post any of your questions your takeaways which you've been working on the chat or in the community we love getting in touch with you guys learning what's new learning what's going on in your world as well because we really base our session topics around what we hear from you and what you want to learn more about and today i'd love to introduce uh special guests who will be taking us through customizing the field service mobile app ian kinnear is a principal technical consultant on the customer outcomes team here at servicenow um and as always we have fujo and david ha who'll be moderating the chat and answering all of your questions so let me go ahead and pass it over to ian and you can just introduce himself and get us started with face topping yeah all right can you hear me okay yep we hear you great okay just a couple slides to start us off um so hey hey everyone my name is ian kanier i'm a technical consultant based out of ottawa ontario canada i've been with servicenow for almost seven years now and what i would like to show you today are some just some simple tips and tricks to maintain the user experience while configuring the mobile app what i found in my role implementing requirements for various organizations is that it's kind of easy to fall into a trap where even you know where you might have the best intentions um you know that you might implement some changes that could lead to usability issues so that's what i want to cover today some tips and tricks for maintaining a great user experience in the mobile app so just real quick my agenda really simple high level we're going to implement a requirement to ensure time is recorded prior to closing a task we're going to review the impact to the user experience having done that and we are going to review and implement tips and tricks to keep that user experience level high so that's it for the slides let's move this out of the way so what i'd like to do first is just give a brief tour of the field service management application within mobile agent it's not going to be you know terribly in depth just real quick just to give us a flavor so if you look at my screen am i still sharing yep we can see your screen just perfect all right you can see the mobile app on the left-hand side and the uh my browser on the right yep yep okay great um so you'll what you'll see is so the app is split into sections using a launcher so looking at the bottom of the of the mobile screen here you can see my work with your inventory articles in the knowledge base notifications and more looking at my work this is where you're going to see you know your open tasks assigned to you and so i can swipe through see what tasks are assigned to me i can see all you still hear me okay yep we can hear you okay just making sure because my audio just tuned down massively all right so i've got my list of tasks here i can tap into a task to view it i can take actions regarding that task i can look at information so these are the fields that are available on that task form in the details tab i can look at my activity from here i can see my journal basically take a look at what's happened within the the activity stream what's happened within that task if i need to i can even you know maybe take a photo or a video attach that to the task and it's going to show up in the journal and just tapping back through so in addition to my own tasks i can look at my group tasks i can see my schedule on a calendar tap through my task that way or if i want to i can look at a task map see what my tasks are in the context of the location i can tap on say you know a task icon here swipe through see what tasks are there i can also slide through at the bottom so i can swipe up here and swipe over to another task see where that task is located as well so continuing on looking at at my inventory at the bottom of the screen so from here i can look at you know any part requirements that i might have created my inventory available parts and so on i can also look up an asset by scanning so here's a qr code scanning an asset tag i'm going to search for that find that asset you know maybe i need to create a work order from here or perhaps see a list of tasks in the work orders that have completed regarding that particular asset or maybe that are upcoming from the articles so here's where i get to look into my knowledge base i can also do that contextually from within a task passing in the short description or i can tap and search for a particular article i can access my articles by category by popularity by use notifications here is where i'm going to see any push notifications that i might have received i don't have any right at the moment and then more will allow me to access additional you know settings and as well as my team so i can see that i'm signed in here as a technician in norcal technicians group i can see my manager tap into that team see who my manager is hopefully i know see my team members maybe tap into one maybe i need to call that person or give them or send them a message i can do that out right out of here or see where they are right now i can also from within the settings application if i tap back i can access my offline mode so if i find myself in an area with no coverage maybe and i need to obviously continue my work i can access functionality within the mobile app using my downloaded cache and to do that i'm just going to toggle on offline mode right here so i'll update my cache and go offline so i can see my download is complete i'm now in offline mode and you know maybe within a task i might want to let's take a test that's in progress here maybe i want to remove a part swipe over remove that part and i can see that this particular action is queued up to be committed later on and in order to do that once i'm finished with my offline activity maybe i'm back in cell phone coverage i can toggle that off and resync so that's just a real quick overview tour of the mobile app um what i want to do is get into my use case here so basically what we're going to do is we're going to look at a a scenario where you know perhaps you're you need to have your technicians record their time before they're going to close a task so in order to do that let's take a look first let's open up a task here so i can see right now i haven't made any changes i can tap close complete i could close out that task right now but what if i wanted to ask the user to tap up to my overflow and record their time always before they complete that task and i want to prevent them from closing that task until this action is taken so that's what we're going to walk through so thinking about this the first thing we're going to need to do is build something that in the back end can tell us if the user has recorded time or not so let's look at in studio so i'm looking at my browser on the right hand side of the screen here and what we can do first is look for our close complete function and we can see that that close complete function uses an action item in the back end to process that button press that close complete button press and that's called wot close complete so let's look for that as well and get it open here it is up here so let's take a look at this script here what it's doing so what it's going to do is as soon as i tap that close complete it's going to do a lookup and get the particular task that we're wanting to close and then it's going to do a basic check here it's going to say i want to make sure it's open and i want to make sure it's valid to close this and i'm also going to take a look so sorry here live issue i can see in this version i've already made the change so let's pretend that we'll go ahead and pretend that i haven't done that so what all it's going to do here is ask us so to provide details for that closure note if you haven't if you tried to submit it without having any information so that's just going back to the mobile app over here you can see that we've got a mandatory closure note you can also see that i've added a couple questions basically just simulating that you know what's likely to happen when you're when you're configuring is you're going to have to ask your users probably something else other than the note so just to simulate that i want to fill out this and that and ask the customer this and maybe do have to fill out a whole bunch of information before i close that all right so what we're going to we're going to want to do next is we're going to want to create something that's going to help us to determine if that time card has been submitted or not so for that what we're going to do is we're going to hop back out of studio for a second and whenever we do this kind of functionality it's always a good idea to build it out into a reusable function and a script include so let's do that so i'm going to access my script includes over here and you can see that i've already created here a script include called mobile util so let's open it up and take a look at the code here this is just made very simply we got a function called check record time and it's going to check to see if a time card is associated to a task and how it's going to do that it's just going to look up that it's going to take in a task by cis id it's going to look that task up check for a record in the time work table and if it finds one it's going to return true and if it doesn't find one it's going to return false so now that we've got this what we're going to do is we're going to go back and we're going to access in studio and we're going to add in that additional check right here so in order to to access our script include it would just basically be you know creating a variable and you know we will invoke this particular script include and then once we we've done that all we need to do is add an if statement and we can call this particular function that we've created called check record time and we're going to pass in the task so it's going to be check record time and then we're going to bring in that sys id and then if we have if we get if we do not get true in other words we haven't gotten a time record back in that we're going to add in a message so let me just we'll add in a quick message here so all we're going to say is we're going to have an error message and we're going to say just please record your time before closing this task so let's go ahead and save that and now let's take a look at how that looks within the mobile app so just in case i am going to close and reopen here and access the same task and i can double check just to make sure over here in my related list i don't have any time worked on this task but let's look at what's going to happen to the user if this is implemented so i'm going to close complete maybe i'm going to fill out this information and fill out that information and here's a bunch of information i just asked the customer and here's all the steps i took to resolve this so you can see what i'm getting at here as a technician i've now filled out a whole bunch of information and i got now go to submit it and unfortunately i sorry this one thing here so you can see right here what i missed um i want to return and not continue on and close the task so i posted my message and i let the task get closed that's okay that's why it's live so let's do it again with another task so here's another task i can accept and start work and again close complete this time i won't be so creative with my questions with my answers rather if i submit this i get a message please record your time before closing a task so this is what i wanted to cover in this webinar is that's not the greatest work experience i've you know experienced from a user perspective because now what do i have to do i have to cancel out after i've already recorded all this information then i have to go back then i have to record my time and put in my time worked any comments and submit that and now i can do this so not a great work a user experience we've created so far we maybe had the best intention we want to make sure that people record their time so what can we do to maybe improve that a little bit so the first technique that i want to show is to hide so basically control the visibility of let's tap start work again so i can show you so what i'm talking about here is let's look at controlling the visibility of this close complete button and not allow them to even see that until they've recorded time so let's look at let's go back to mobile studio on the right hand side of the screen and we're going to look at our close complete action again and if i scroll down here you can see that there's a condition built here so that condition is looking at you know is it open are we the current user and so on and so forth so why not since we already have built a function within a script include to be able to do that to be able to check whether or not that time has been recorded or not how about we take that same logic right that we implemented sorry back over here and right here right so new script include and call that check record time function so how that would look if i write it out let's tap click back over here to my action so what i pasted in right here is just the exact same thing just written out so new script include check record time passing in the ssid and whatever else was there before so let's save that and let's look to see if we have a better user experience or not so looking back at the mobile app just because i've made a change to a function i'm going to restart that and i'm going to open up my task and you can see that maybe we've improved it a little but it's still not perfect and the reason why it's still not perfect is so right away you can see we don't have any more close complete here and we don't have it using our overflow menu here at the top we do have our record time but i might not necessarily know as a technician that i've that that's what i need to do but let's pretend that i did in this task and so i'll put in the work date i'll put in my time worked and submit and now you can see magically my close complete button is back so as i was saying that's a little better but it's still not perfect because the user doesn't necessarily know that they need to do that close complete function if the button is missing they could be spending their time trying to find the button why can't i close complete so this is where i get to kind of the trick part of what i wanted to show so what we can do is let's create another close complete button but this close complete button instead of showing out all these questions and leading the technician down a path to fill that out and then be annoyed let's just give them a message immediately that they haven't recorded their time yet so let's look at how to do that so what we're going to do is create a new mobile function to do that and what i'd like to do is create the action item first so that's what's going to process my button so what i'll do is i'll just create new and why don't we call this close complete record time reminder and of course you'll put a good description there and then this is going to be on the our work order task table and we're going to use the current record as a condition but let's change this to a script like our other close complete uses and what we can do here is again just it could be as simple as just saying gs.add error message and then something like unable to close task please record your time first that's all it's going to do so let's submit that and then we're going to create the button next over here i'm going to click on create new and let's call this close complete record time reminder so we know what it is and the action item it's going to use big surprise is going to be the action item that we just created and what we're going to want to do is okay we're going to give it a table it's going to appear on and a condition so let's use a script for our condition and then again rather than typing well i can show you an easy way to get what our condition should be so that would be to look at our other close complete grab this paste this in here however we are going to add in here a not so if we have not recorded time and all the rest of those conditions are true then we're going to show our new close complete record time reminder button so let's submit this and now cross our fingers close the app and reopen it just to make sure we have all the latest and i will take a task here accept that task and start work and we do not yet have our button as we were expecting so that's interesting so let's see what we've done wrong here so we've got oh okay so so david and foo are probably laughing at me here um so in order for a button to appear on a screen we need to add an instance of that button to the screen so it doesn't matter that i've created it's not going to appear until i open up my screen which is in this case my tas so here's where we're going to configure our screen in the mobile app so basically what we're seeing over here we've got our list set up and our form set up and we want this button to appear in the form so i'm going to click there we want that button also to appear in the body so i'm going to click on body and i'm going to head down to the footer where use part is appearing here and you can see that there's our existing close complete function footer function here so what we're going to want to do so um if you run into this maximum of three footer functions are supported that that's fine um what it's trying to prevent here is um you can only there's only space for three buttons however if you're using conditions like we are to show or hide those we can potentially have the need to add more as long as we make sure that only three ever appear here that's fine so what we're going to do is head over to our function sorry we're going to head over to the screen um which is my tasks and we're going to have a so we're going to find our close complete function this is i've clicked into the list view so let's here so actually easier way to do it would be to find the function instance so what we can do is we can open this and i'll open this in another window to get the function instances and then i'm going to open close complete all right so here's my close complete function instance that's going to appear on the close comp sorry it's going to appear on the task screen actually on the details tab of it right here and it's going to be a primary color and it's going to appear on the footer so all i'm going to do is i'm going to do a insert and stay so this is going to be if my chord time not completed and our function is going to be close complete record time reminder and the label can be closed complete that's fine and i'll just give it an order and insert and stay and then just to confirm that that shows up in studio let's open studio back up select our field service mobile scope and then we're going to go back into my tasks the form body scroll down to the footer now we can see we've got two closed completes we've got our original one and our new one that we created all right so now let's go back to the app and see if things have approved so here's our task and now thankfully we've got our close complete button here so if you recall on this particular task we haven't entered any time worked yet so our technician might think okay i've done my work i need to go ahead and close my task so i better close complete so if i tap that i see this message now appearing telling me to close a task so just a little bit of a better user experience than having them enter in a whole bunch of information and not be able to move any further so if i was to then tap up and record my time i'll enter the date and the time that i worked and submit this from the user perspective they still see close complete everything is fine however if i tap it now now i see my close complete that i want them to see when it's actually time to close that task so i'm going to take a pause here and just uh reach out to you uh david fu and charlie see if there's any questions yeah we had a couple questions earlier and i love how you uh made a couple mistakes earlier and you know there's no laughing outside at all again i think the best part of mobile app academy is where you know we figure out where our mistakes are and kind of teach everyone and kind of share those learnings on how we troubleshoot so that's the the greatest part of our mobile app academies um but we did have a couple questions earlier one asked uh and i'm assuming that they're a bit more immuno mobile and uh you know they asked uh when you pulled up your function how do i change like fields that the end user could change or edit so it would be like a very simple declarative action and you know you change the parameters around so yeah sure so so let's look at that uh close complete function that where we added in um that fill out this and that and so on so i'll scroll down to my functions and find close complete here and if i scroll down to the bottom and look at the related list here i can see that there are four ui parameters ui parameters are the fields that are if i just tap close complete again that are going to show up and the user is going to have to fill in these can be either you know mandatory or not you know or different types of fields it might be a choice list or it might be a string uh it might be a a true false slider or a number just based on what i need and so here you can see that out of the box there's a closure note that was there and i just went ahead and added really quick you know three additional questions here now once you add a ui parameter it's not just going to show up right away so what we need to do is figure out what we want to do with that so at this point we're just sort of collecting information so probably we want to um you know store this information somewhere because we're asking them to fill it out so that's where we're going to go back and and look up again on our action item that's supporting this function and um open that up and so here's where um you know we could we could use those so um you know if i look at the here this example so if i take the input.wb wat close complete what i've done here is is tied to that action item there are item parameters so this is we need to make a connection from the form that appears to the actual functionality on the back end that's going to take that and and do something with it write it to the task table for example so what i would do is i could i would create that item parameter and then within my um within my action item i can then use that like it could be just as simple as if if this was an update um you know i could i won't save this but it could be as simple as taking a value like the closed note and then pulling in that value so here's a way to do it without scripting um we just had a script because where we've implemented some you know some additional funky logic here with error messages and so on but um that's basically what you would do you would have your ui parameter you would have your item parameter on the action item and then the last thing you would need to do is if you notice this action parameters mapping screen this is where you would map that ui parameter that was submitted to the item parameter in the back end so once you you do those three things you can add additional fields to this form great i think that answered the customer's question uh quite clearly we have another question um and it's someone who's not familiar with how you're able to put more than three footers uh on your device so on studio it shows you know seven footers uh although you are maxed out to three so you can use platform ui to do that so how did you set the conditions so that only three would show up and how do you how do you make those show up not the other four well so so each of these functions has a condition built on to it so in this case this was the original close complete where we added an additional condition in here to only show it if the user has actually completed their time so so basically you you're going to be looking and building these conditions so that you know you can show or hide those buttons as you need to and the biggest you know value you know the the most frequent use field for doing that is obviously going to be the state right so on our if i if i look back at the mobile screen here and tap to my work so you can see that for a work order task that's just assigned here it's not yet work in progress i've got it my accept and reject here these this is the same task screen and you can see i've got accept and reject over here so it's all in the conditions and you know by extension the data on the task namely the state in this case to make sure that i'm showing that button um you know in the right time for the user depending on that state and i'm limiting myself here to three what i recommend is for these functions that are going to appear in the main task try to keep those to any action that will basically drive the state flow for this particular task so you know what's the next thing i need to do to do to work this task well i need to decide if i'm going to accept or reject it and then once i do that i need to either start my travel or if i'm already there i can just start work right away i wouldn't want to you know ask the user to close complete at this point when they haven't even started work yet on it it's still in a state of accepted so that's where um you're going to go on to kind of drive that through the conditions hopefully that makes sense right that's a really good point um and to kind of add to that verage you asked you know uh if i had more than three functions you know uh can i increase the count on my footer and just as ian was saying you only want to put the buttons that would make most sense to kind of drive that workflow right um if you have further actions that you want to do on this record i would suggest putting them in the top menu which uh is going on now where you can see all these other actions that uh that the end user can do but it might not be relevant at this stage or at this current um yeah yeah and if i head back to uh my task in progress here you can see i've got additional uh functions i can do from the overflow menu these are things that i aren't necessarily linked to the state you know like maybe editing changing a couple fields on this particular task removing i might not need to remove a part so that's why i prefer to have that up here in the overflow menu as opposed to down here in the main part of the form uh we have another question from swapnil and uh this person is asking do ui actions work on the mobile apps as they work on the snow platform uh i'm not sure why actions are referencing the classic app or old legacy app or if it's just actions on the platform in general so any actions that you want for your end users to have access to uh you do have to configure it um you know whether specifically for mobile right um so any actions that you might already have on the platform needs to be also done again uh either using mobile studio or using the platform ui to build it for mobile so really you know all your end users they don't have access to any actions uh until you build it for them um and associate to your mobile client and i will send a link to a training course that will that's an introduction to the mobile apps and how you can get started using mobile studio i think that would be very helpful to really understand how to get started with your remote and the good news there too is you do get you know all this functionality coming out of the base system so you know a lot of thought obviously went into you know getting creating all of the functions that you need as a technician from within the mobile app mimicking or you know in some cases enhancing what you can do in the platform ui as well so you know what we've looked at today are just some examples where i might need to go in and add something else so yeah short answer is yes but you need to build it just build it in a different way using functions within the mobile app right right um so we're gonna leave spend the next five ten minutes to answer any other questions that come in uh feel free to continue asking us questions and uh we will uh if we need further um uh clarification we'll also unmute your mic as well so we have another question from swapnil do the platformer's ui policies also work on the mobile apps uh so if you have any existing ui policies that currently uh that you have on the platform uh mobile uses its own ui policy table so again if you scroll down a little bit more there is a table for ui styles and this is where you would create ui style or ui policy sorry um and you know your platform's ui policies won't automatically migrate to mobile you'll have to actually create them again and this will allow you to create you know uh read write or making um fields mandatory uh whether the fields are visible or whether it's mandatory uh you can configure it here mostly um and i can send a product doc link for more information about it too any other questions the other thing david if if there's nothing else that i could potentially show is is this um yes communication to an external widget let's actually show that so we have an extra 10 minutes let's actually uh build one additional um flow while we still have time yeah i mean maybe i can just like take take us through it step by step because i've already got a case uh you know an example of it built but it's it's easy enough to to replicate just where this use case is coming in is if i wanted to jump out and show something outside of the mobile framework but i want to pass some information in there so the example that i had was you know maybe i've got some special instructions that are tied to a particular company so it you know it's going to be dynamic depending on whatever company is tied to this work order task and i want to have that those instructions um be you know a little more uh descriptive and friendly like um you know maybe have some images and or additional information that i would want to use html for to display that and um so what i've done to handle this situation in the past is actually just create a portal widget and navigate create a navigation from within the mobile studio to link the pass in what i need to pass so that i can display the appropriate data so in this case the special instructions that correspond to this company so just looking at that a little more in a little more detail let's say i had a field on the company table where i was going to have some notes stored that should pertain to this particular customer and i want it only to appear for the user when the company is cyberdyne obviously it's tied to this particular company so if i tap in the mobile app you can see i've created a field navigation here where it's i'm still you know from the user's perspective i'm within the mobile app but actually we're breaking out to an html page that's being rendered from the portal so that's how it looks in the mobile app and then if i show you over here so if i look at the widget that i created if you're familiar with portal widgets this is going to be really real simple for you to understand but essentially here so let's open it in our editor widget editor so now i'm not i'm not in mobile i'm not doing anything from a mobile framework perspective at all i'm in i'm in a portal page so i created a portal to support these widgets that i've i've set up here and i've created a new widget called special instructions and you can see that in my server script all i've done is i've pulled in a parameter from that uri from the the url with the uri that we've navigated to and so i'm looking for that to be passed in for the company society to be passed in using that mechanism and if it is then i'm just going to do a glide record on the core company pull that up and then store in the variable what those notes are and then my html side of my widget all i'm going to do is just display them pretty simple using a buy in html so the portal code is pretty straightforward and then in studio this is actually going to be a specific kind of function we would use called a smart button so you can see i've created one here called view special instructions and it's going to be of type url and then i just give it a name a label rather and then i pass in this uri and the secret sauce to this is just to leverage data that's on our table the task table in this case and pass in that cis id using the uri and it's really as simple as that other than let's not make the same mistake i made earlier on the task table or sorry in the task applet you can see that again just scrolling to the top for a second we got our list in form and then on the body we have our field functions so these are functions that are going to appear like this location you know where i can open up google maps or apple maps whichever from there well we're going to use that same field function but on so identify that on the special instructions field we're going to tie in our view special instructions smart button that we just created so once we've done that this special instructions field will show up as a link and i can tap into it now you might be asking well what is this field how did you make this view special instructions text is it a field what is it so this is just kind of another trick that i've used a few times in the past i could easily have may use the company field here and put it on the our our field function on the company and then if you tap it it would open the special instructions but if i wanted to show the user a more helpful message like view special instructions this is gonna possibly not blow you away but all i did here is i created a new field which i called special instructions let's look at our dictionary and i created a new field on the task record which is called special instructions and it has a default value of view special instructions and it's read only so it's basically just kind of a little trick to you know have a field here available that i can display on my task form and then apply the function to any questions about any of that no question so far on that but that's a really cool trick um i'm definitely gonna showcase that a bit more even i wasn't aware so really great demo um i'm actually going to unmute uh varaj uh he had a question earlier about footer functions that maybe can help clarify for us and we'll just have a chat so i'm trying to unmute you now a lot of talk okay uh viraj if you unmute your mic you should be able to ask us the question directly now okay uh can you hear me yes okay thank you thank you again thank you david so here on my task applets you can see there is a footer functions and where you added a clothes complete uh footer function newly so you added it from not from studio you added from the platform view because the plus sign on your right hand side on the top where it's label function function type but an emphasis that is not enabled so can we enable it is there some kind of property that we can increase the count in the system so that it can be we can use it directly from here instead of going to the platform view i see so uh i think uh what happened here was i think that this plus button that you're seeing this grayed out plus one it's actually hard-coded for it to stop working after you have three functions so if ian were to delete uh you know um if he only had two actions for accept and reject you would actually see that plus button show up again but because he maxed out his uh this on studio studio only allows you to add a maximum of three so that's why he has to go into platform ui to add additional footer functions and then that's where you apply your conditional access where right if you have more than three the only ones that will show up will be based on the ones that um fulfill those conditions so what you can do really easy is if you if you tap er so if you click over to your functions and then um it doesn't even really matter which one you open um it and then what i do sometimes is i will um sorry this it does matter which one you open sorry if i i'm on the wrong page i want to go to my applets take that back and under mobile and then find the um my tasks like i did before and then so i can just right click here on this related list and open new window and then open it up and then that way i can see the table that it's located in and if you don't know you can just grab this table you'll need to do this once so i can bring up the list of function instances in my platform ui and then i can just drag it over so i have my function instances here you can see with my poor memory i had already actually done that but i forgot so here's my button instances and then you know if i wanted to i could even edit this to make it more user-friendly sorry it's this one um but you get the idea yeah yeah yeah got it thanks thank you i also wanted to say that and i would recommend to ask this question as well in community because i have recently been on a paris instance for a customer and i am almost certain i just don't want to say it for official that it actually was changed so you can add more i'm not sure but it's possible yeah yeah that's good to know though so i guess in paris uh it's no longer hard-coded to only have three so i believe so but you know we can double check that um and you know maybe ask the question on community somebody on a paris instance can easily tell you or like i said having even without that it's pretty easy to just find that list then you know navigate to your your list and then you can always you know copy and insert and stay on a new one right and with you know every release we are trying to make the developing experience much easier so uh you know in paris we try to make uh some of the things that you can only configure and platform ui will you'll find sometimes being migrated back into mobile studio so things get better over time and slowly if there are any things that you know that's preventing you from having a good experience or you have any suggestions please open up idea ideas on our idea portal which you can find on our mobile community site as well uh that's uh so anything that you open up as an idea it goes straight to our internal product teams backlog and we have kind of a further discussion on it and helps us prioritize so it's very helpful for us to share feedback there uh and with that i think we are at the top of our hour let me see if there's any last minute questions that we can answer looks like we were answering the majority of them uh we do have a question from tony uh about this mobile app academy and how frequently uh we have them so this is a bi-weekly um live session that we have every tuesday morning at 10 a.m pacific time so we will have another mobile academy two weeks from day so feel free to keep checking out the mobile community site to get the latest updates hopefully david and team will have me back because it was fun so some other time maybe you'll hear from me again and ian you're amazing so really appreciate this session and uh hopefully everyone else found it very helpful too um okay with that uh everyone thank you for joining us today i hope you've all found this session informative and helpful if you have any further questions feel free to keep posting on our community site where we can explore further configurations on our future sessions make sure to keep following us on our mobile community site and i hope to see you at our next mobile academy thank you everyone