good morning everyone and welcome to mobile app academy this is our live building series where we show you how to build and configure mobile apps on the now platform my name is david haw and i'm an outbound product manager here at servicenow and i'll be your host for today's session but i also have hannah bassana in kinnear uh david merch charity cats we all represent the mobile team here at servers now we all want to give you a warm welcome for joining us live here today um but if you are joining us for the first time welcome to the session you know we have our product experts here to help provide guidance best practices and try to answer any of your questions that come up and we typically host these mobile app academies every two weeks at 10 a.m pacific time and if you're curious our recordings are also posted to youtube on the servicenow now community channel just want to point out a few resources that we do have available before we get started if you are new to mobile we highly recommend that you check out some of our self-annulment resources such as our mobile guide books and white papers which you can all find on the mobile community site but we also have a plethora of other resources such as labs mobile trainings on the now learning sites as well as our playlist to all the previous app academies which you can find sessions like you know how to get started with mobile agent uh as well as now mobile as well as 30 other 30 other app academy sessions um and if you do like these sessions our servicenow team we also do host academies for hr service delivery as well as platform foundation platform analytics virtual agent and many others but you can find these series in their respective community forums just by navigating to the forum tab on now community but with all of that said um let's actually get started with today's topic mobile publishing version 3.1 we have hannah bisana from our product team today to take us through everything that you need to know around mobile publishing oh um i just realized we have the wrong title slide here but today's topic is mobile publishing um and hannah's gonna walk us through you know what it is why it's important some of the updates for version 3.1 and how to get started and we'll also give you a walkthrough as well um and just to speak through to some of the things that we're going to show you today this will be a one-hour session we'll start off with with a quick 10-minute overview on what mole publishing is and why it's important but then we're going to jump into about a 40-minute reported walk-through there's some sensitive data that we had to blur out as we go through this mold publishing process and so hannah has prepared this video for you but we will open up to some q a afterwards so just hang on tight but with all that out of the way let me go ahead and pass it over to hannah who will take us through mobile publishing hi good morning good afternoon and good evening i'm going to go ahead and share my screen and i'm going to make sure to share my audio so the video works excellent so hello all um i'm gonna stay out of presentation mode because i have a very big very big monitor but hi all so glad that you could join um as david mentioned this is our mobile publishing overview and config so mobile publishing has gotten a lot of attention recently and some people the first question that comes to people's minds is what is mobile publishing and how does it differ from mobile branding or mobile white labeling and our honest answer to you guys is those three words are totally synonymous um we call it mobile publishing some of you who might have been familiar with our process a year plus ago might know it as mobile branding and then generically it's called white labeling so i'm going to go into a little bit of our overview uh what does mobile publishing provide so you can create your own corporate mobile branded app this will enable you guys to have your corporate identity and promote adoption as well as secure company data and specifically mobile publishing provides automatic automatic branding process to incorporate your corporate identity including a custom app name icon colors and splash screens for all of your apps obviously you're welcome to use and most of our customers do find that all they need is our servicenow ga apps um the general the general family releases that we have our most recent being san diego but should you guys want to edit a little bit more this is where mobile publishing comes in we also have additional mobile security including data protection service access and policy reinforcements as well as manage device mobile device management through microsoft intune and blackberry we also have a few different distribution methods now and this is new as a version 3.1 i'll get into that a little bit but customers can avoid listing their app on public channels such as the app store google play store by leveraging some of our private distribution methods or they can opt to put it on the more public stores and then we also have ongoing app management once we create this app you're not on your own to figure out how to continue to use it and optimize it for your team so you'll automatically get security and ios updates and patches for these mobile apps i do want to emphasize i do want to emphasize that mobile branding mobile publishing is not the only way that our customers can get what they need out of our apps so our mobile clients do take less time to deploy it is immediate um and you can also internally brand and customize your app's theme just in the servicenow ga apps if you just want to have after you click into the servicenow app have the layout and format look in the same colors as your company logo you can do that through theming but for external branding that is where we enable the customer a bit more and use mobile publishing as well as the opportunity for private distribution so as mentioned some companies might find that they do not want their internal app to be published on the public store for anybody to download obviously there are still login still login security constraints but still that might make some customers uncomfortable so we allow for private distribution methods and this can be anything through working through your mdm provider it could be sending posting a link to the app on your internal portal or literally sending out a package file to each of your employees we also have as mentioned the emm capabilities for mobile publishing it's important to know that we only support blackberry and intune so if you have your managed devices or a managed app and you would like to do that through other vendors mobile publishing might not be the best solution for you but we find that this is the use case for many of our customers that blackberry and intune is typically what they were using anyway and works for most now just to go into a little bit further for mobile publishing customers can request to implement their company's visual identity and again the customizations that are supported are the app name itself the app icon the splash screen that loads while the contents of the app is loading you can have private distribution methods our new and improved public distribution methods and editing those themes now i do want to say that this is a paid plugin this is not something that you would immediately get um through servicenow it's mobile publishing is included in pro enterpriser app engine skus uh or a la carte and this is what i'm going to be going into in a lot of detail here for our demo but the customer build process at a high level is here the customers submit a build specify what device type typically ios and android the icons themes splash screens etc servicenow will build that app and typically either test it for you or allow you to introduce your own testers and then you will approve those releases and then you can deploy it to your employees so i'll go into this process a bit more because it does differ by what type of operating system you want and what type of distribution method now this is a big slide but i promise that i break it down um in the subsequent slides and the demo so the as mentioned the process is different by operating system and distribution type ios you can see just generally that there is an extra step involved and typically that means that the ios builds can take as long as four weeks apple's a little bit more particular about what apps they allow in their app store generally to be created and so they have a approval process that takes a bit longer than android and android is a little more short a little more sweet and it takes one to two weeks to complete so i'm going to break down each of these individually in the live demo to come but one thing i really want to emphasize is it is not enough to simply ask your account exec to enable the paid plugin or buy mobile publishing a la carte you're not finished there are a few prerequisites that you need to have in order to complete just the first step of the process and that's requesting the public app or private app and in both cases you'll need a file a google firebase account and this it this will generate a few things for us on the form you'll see coming up uh but also allow us to set up push notifications on android for private distribution there is another account you need to have prior to even requesting and that's apple business manager now a lot of our customers who choose to go with public distribution tend to have a little bit more experience with creating apps and deploying it to their employees so they will likely already have an apple business manager account but we do specify that it is required specifically for private distribution and that's because it generates a few things we need for the form as well as use for the distribution of that app and then we'll also need the names and emails of your ios app testers and you'll see exactly why in a minute there are a few other accounts that we that we say that you need it's requisite to complete the process but not for the initial form completion and that's things like apple test flight accounts the apple connect account a developer account and then of course a manage google play account to actually post this app to the google play store now before i go into the config and that's my face on on that man um before i go into the actual configuration of mobile publishing i wanted to pause here and give you guys an opportunity to ask questions about what mobile publishing is or isn't and if you have questions about the steps rest assured that i'll i'll address those shortly david do we uh take questions in chat do we let people unmute how does how does the question part work uh we usually let uh folks answer questions in the chat and we'll bring them up um but it doesn't look like we have any questions so far um so maybe we wrap it so bad fantastic okay um one more thing i want to show y'all just for familiarity before we go through the live config are these slides so i broke it up per distribution process typically when you request a published branded app you'll want both ios and android so let's just focus on private versus public so again here the prerequisites and other requisites for a private app and then here is the process both android and apple both yep android and apple start with the submission of a request servicenow will build the app and then the middle part is testing the latter part is deployment and i'll go through the specifics but i wanted to familiarize you guys with this slide as well as the public app process you'll see public here public here and public here as we go through the live demo you'll want to know which we're looking at and last thing to say before i move on to this video is i will be going through almost all of these steps in their entirety the first couple steps are ones that servicenow owns so i can speak with complete breadth knowledge and accuracy on those steps but as we move into the more apple or google specific processes we do have internal documentation that'll walk each of your admins or ios developers through exactly what they need to do but these processes are owned by external companies and are subject to change so if you're watching this recording or youtube video a few months from march 2022 things might change but we do also link out to those external documents so that you might be able to cross check and make sure you know exactly what you're doing but i do my best to demo everything in this video and i'm going to go ahead and hit play now the first thing customers needs to know is that there are prerequisites to mobile publishing first off it's a paid plugin that's included in pro enterprise or app engine skus or it could be bought a la carte and in order to distribute your app publicly or privately there are a few prereqs and other accounts that need to be created such as the google firebase account for either distribution we'll generate a few different pieces of information we need to complete the form as well as how to set up push notifications for android in the private distribution there's another account the apple business manager that we will absolutely need as well as names and emails for ios app testers to complete the form you'll see a few other accounts that are necessary indicated by an asterisk that are requisite to complete the process but not for initial form completion like a test flight account apple connect apple developer and manage google play account to eventually push the public app to your users now as mentioned this is a paid plugin so step zero for a customer is to work with their account exec to enable the mobile publishing plugin the customers would go to the servicenow store so store.servicenow.com you can type in mobile publishing in the search bar and you'll see our app and solution listed here if your account exec has enabled mobile publishing on your instance this button will highlight and say get so you can click this and either automatically or manually upload this plugin to your instance a good way to know whether or not it works is the next step in the process you go to your customer instance and we're going to type in mobile branding one thing to note this does still say mobile branding and mobile branding mobile publishing and mobile white label are all synonymous the formal process is called mobile publishing inside of servicenow but this is some older older terminology so if you see branding comes up it just means the same thing the request branded app will be the area where you spend the most time a few things while it loads you can see that loading square sometimes it'll take a little bit longer to populate every area in this form please just wait until you can see these buttons so that you know that everything is loaded correctly now you'll notice there are three different large headings here these are the three different types of apps that you can brand within servicenow first our fulfiller app our requester app and then our soon to be deprecated onboarding app and you can request one of each and each time each time servicenow publishes a new family version or general release every six months you'll need to come back in here and click update custom branding request to uptick some of the new features servicenow has put out but you shouldn't have to do that any more than every six months or at max once a year if you want to leverage the features that we come out with on the mobile team so i'm going to show you guys how to create a custom branding request we'll do a fulfiller app and first we'll do private since that has a few more pieces to the puzzle here so first you'll notice that there's a drop down this is new for our customers who have used mobile publishing prior to november 2021 you can pick private or public we'll do private first and you can pick to deploy ios or android one thing that you should note is that this form is dynamic so the ios branding setup and android branding setup will appear or disappear depending on which so you know all information that show that is shown is required so first let's put the request your contact information last name first name email and this is going to be your point of contact for each step in the process for this app creation so this really needs to be the person that you want to be in the loop every step of the way and you'll notice there's this add testers section if i toggle off ios that add testers section goes away so this is an apple specific requirement where you need to as a customer identify who your testers are going to be for your ios app before you ever request it you cannot add testers later it's a bit more of a manual process so be sure to add your testers and another thing to note is your testers do need to have an email linked to an apple id and this is a apple requirement not a servicenow one but please ensure that their email is linked to an apple id and lucky enough for us johnny tester's account is associated with apple id so i can add him right away now our form does not have validation by the way so it'll let you add it one way or another you need to verify with your tester we'll go into the generic section of brand your app long name this is a private app so let's go private app long name i'll go three to make sure it's unique private app short name three private app three and man so this mam support is to if you would like to have a managed mobile device and you want it to have application management this is where you would select your vendor either intune or blackberry is what's supported right now by servicenow if you would like your whole device to be managed instead of just this custom app you would hit none and work with your mdm provider so we'll keep none for now native client and client theme you can these are pre-populated you can ignore but the universal links host this is pre-populated and it matches your instance id this can be edited in the previous page but servicenow does not suggest you do so because it could break some of our connections what this is used for is for deep linking and customers who need to use it will likely know what that is this eula and privacy policy is a new section for us we have now enabled customers to not only use the default service now end user license agreement and privacy policy or they can upload their own eula urls and privacy policy urls right here we'll stick with servicenow default and move into the ios branding setup so the ios branding setup that apple dep id org id or name these are the two fields that necessitated some of our prereqs for the private process i'm going to pull this up one more time just so everybody is very familiar for ios private you need to have an apple business manager account because it generates both the apple ped org id and org name and is used for distribution so the way you find this is you'll have either your ios developer on site or your mobile team or you yourself create an apple business manager account when you have this account you would go into your settings and go into your enrollment information under org settings what you'll see here is your organization id as well as your org name and these are the exact fields that our form requests so i'm going to copy this org id please make sure you put this in exactly as it is written in your apple business manager especially this organization name directly above your org id if i leave out the dot if i don't capitalize it this has to be exactly the same or else the connection between our systems and apple business manager will not work so i'll put in the org name servicenow comma inc period there's no space before no space after excellent and then i move on to the more fun part for mobile branding you could always use the default service now branding icon splash page in colors but half the fun of this is using the custom branding icons and you can see here we have app icon splash screen and splash screen color now each of these fields does have a few few criteria you have to follow specifically the size and the shape so please make sure for app icons they all follow a 1024x1024 for the ios splash screen that loads while the content that appears on your app while the content of your app is loading it must be 2048 by 2048 square icon with company logo and name and the splash screen background color should the image i selected not fill up the entire user's device i can pick a nice purple to match and that concludes the ios branding setup i'm just going to collapse this header and we'll move into android branding setup now oops you'll notice we have a few fields here firebase app id firebase ip api key excuse me and firebase project id these are why we required a google firebase account and i'm going to flip on over to our firebase account now most companies will have a prod and sub prod as we do if you just create it you may only have one project that's perfectly fine let's click into the project to create an app now our subpro does have a few apps already there because this is our mobile publishing pipeline but what the next step is to create an app for this project you do this with the plus button you can create several different types of apps but ours will be android and we have a few fields to fill out this android package name is extremely important this is how we link our system to google and it's right here on the form your android package name this package name is pre-populated by combining our standard dot com service now b2b your app long name as well as a dot plus the type of servicenow app you just requested in our case it was a fulfiller app so i'm going to copy that whole string put it here no space before no space after this one will be what do we say private app three was that what i called it it doesn't have to be the same but it sure does help we'll register the app you can ignore the signing certificate it's optional and as well as these config files and sdks we've simplified our process to where you no longer have to do anything with this and you can just continue to your console now you'll notice the number of apps here has increased i can click and we are going to look at our private app three right here so first i'll just you know enable it on the dashboard sounds great but let's click the settings and in these settings is where we will find some of the important information we need first field was the firebase app id and i'll just move this over so we can see what we're looking at the firebase app id is scrolling down here this is our app id let's make sure we're on the correct app you can see how you can toggle and the app id will change so ensure you're on the correct app and pull the app id here which will always have colon android colon somewhere inside of it so you know you pulled the right thing colon android colon fantastic a firebase api key scroll back up here is our api key given to us by firebase make sure to get every character and finally our firebase project id now you'll notice there's a project number and project id please make sure you grab the actual project id not the number itself excellent and that should wrap us up on firebase for now i'm going to move this out and we can continue on the android branding setup this trusted certificate authorities is a special use case where the servicenow ga apps specifically for android can allow two different types of certificate authorities one is the proper certificate of authority created by a government or a business another is a user added certificate authority and this just allows a lot of flexibility and customizations known that android's known for and sometimes that can give security issues for some customers where they do not want to click opt-in to trust but in more cases than not we're fine with as much flexibility as possible here we see the theming options again i'm gonna use custom of course and android has a few additional pictures you need to add including a foreground launcher icon versus a background launcher icon the all this means is when you're when you're moving your apps around on your android phone the foreground launcher icon will wiggle and follow your finger and the background launcher icon will stay in its location on your device page just so you can see it typically and i don't see why you would have them different but sometimes you can add some extra flair there an android notification icon will be the photo to the left of any text you have for a banner notification and then the android splash screen again used whenever the content of the app is loading and then we'll add splash frame background color a nice kind of blue purple maybe just plain purple great and scroll up you can see we have completed all of the necessary fields and we're good to go so we're going to hit submit and we're reminded that this process can take two to four weeks now as this is submitting it will say an email notification will be sent if there are any changes in the build status and i'd like to show you this is why it's important to have the correct person in the requester's contact info because we will send automatic email saying thank you submitting your mobile branding request you submitted it here this is the platform the app name and how long you can expect to hear back as well as some helpful resources and here we see our build is in progress usually takes two to four weeks and we'll send you an email and this is our app private app long name three and we see the build is in progress now i'm going to show i'm not going to walk you through the whole process again to request a public app but i will show you what the differences are and the first of which being the requisites are a little bit different you no longer need an apple business manager account you do still need an apple connect apple developer and a managed google play account but these are other requisites for later in the process and you just need a google firebase account in order to fill out the form and again the first step is the same submit a ios branded app request submit android brand app request we do that on the portal and for a public app we will build the app and provide you an x archive link or a aab file and i'll show y'all what that looks like shortly so you'll notice i cannot request another fulfiller app because we can only request one of each type so i'll go down to the requestor app and show y'all how public might differ first and foremost there are additional terms to agree to for public publishing and that's because we are publishing to the apple app store and the google play store so there are a few things you have to agree to here this is the same but you'll notice under the point of contact here there's no longer add testers for ios or otherwise it doesn't change and that's because for a publicly branded for a publicly distributed branded app the customer themselves will actually own their app store connect account it's no longer servicenows that we we work on behind the scenes for you guys you will actually own your app store connect account and you can manually add your testers at any point in the process so that's why we no longer ask for it here we also no longer ask for a long name that's actually more of a android background piece of information so you just need to have your short name and then subsequently the ios branding setup you'll notice there are a few fewer fields a few fewer fields yeah to fill out here and that's again because we don't require an apple business manager account beforehand you'll be hooking all that up on the back end and the android branding setup is all the same so when you submit here really it's only the back end of the process that changes for a public build i'm going to go ahead and cancel this build so i can talk y'all through some of the statuses you'll be seeing and again this is just the same page that we went to request branded app but now as we already have some apps requested you'll notice you can no longer click new custom branding when a build is in progress and so this is the private app we just created and if you have previous builds you can see under here and build history you'll notice request your app doesn't have any build history i haven't requested any requester apps before but for a fulfiller app you'll be able to see if you ever wondered why i put this as number three it's because private app long name two and private.long name one have a few different statuses here you'll be able to see build cancelled build failed and when the time comes as this one continues to go through the process i'll scroll down and eventually it'll say ready for testing and you can also see my build history here now i'm going to pop over to a different thunderdome simply to show you guys a few more statuses so we're still in branding request branded app and this is still the mobile branding setup so if you see here on the fulfiller app i'm going to open up this build history because we still have a build in progress and you can see my super duper app the branding update is complete this is a public app and we can see we have a file to download and nothing else to do here i'll kind of come down here and we'll hopefully yep this is an android you'll see that there's a file to download i'll talk you through that but nothing else to do once build is complete something else i want to call out is once a build has completed you'll be able to see this new button update custom branding and this is what i spoke to before on anytime servicenow has new mobile features and a family release tokyo rome san diego utah vancouver etc you'll need to come here and hit update custom branding you can choose any of the builds you already have i'll just choose this one and it'll pre-populate a lot of the form for you theoretically there we go it'll pre-populate a lot of the form for you so you don't have to remember some of these more challenging keys now i'm going to back out of this and go back to our customer instance where we created our public or private app long name three and i'm actually going to start focusing now on this public hb app you'll notice it's already ready for testing public apps are made ready for testing much faster just because they don't have to go through as much of an approval process with apple so from now on we'll be really focusing on this public hb app and i'm going to start talking about the public distribution process for both android and ios i'll go ahead and pull up this slide again because i think it's very helpful so we have already gone through submitting the branded app request for android and ios next thing you'll see is we build the app and we'll provide you with that x archive download file and a aab for ios and android respectively what you're going to do is you're going to download those files and it'll in this at this point you as the customer will start testing your app now these latter parts these ladder steps step three four and five and then step three and four for android are processes that are owned by apple and google respectively i am not going to walk you through the exact steps because these steps are not our process to own and could change at any point but i do want to since the public app process is a little more challenging than private walk you guys through and show you where some of the documentation is so we have our and actually i'm going to keep our little process steps down here so we can all see for an ios public we'll have an x archive download file and we'll see here we have an x archive file here now what we'll do is we'll just click and download it and this is the part of the process where we'll start relying on our servicenow documentation this is i want to call your attention to this now support doc support.servicenow.com i'm logged in internally but this is also an external facing portal and we have a document that walks you through as best we understand how to update x archive and create the ipa for public distribution unfortunately that's not bigger that is a different file type for apple specifically but it'll walk you through starting from creating your app id in the developer account because if you'll remember that apple developer account is a requisite to create to finish this process it'll walk you through how to create your app id getting your distribution certificate creating your provisioning profile going to app store connect and creating your app there and again the app store connect account was used to set to test your ios app how to update your x archive file go through a few system properties and then ultimately resigning the x archive uploading to app store connect and once you've done that you'll need to approve the build and deploy to the app store so we have probably two more steps to go so first off on your app and again we created this one but we're using this one representatively you'll see the approve build button now you will do this in order to deploy your app to the app store before hitting approve build go ahead and make sure you read this this is a public build to complete deployment please follow these instructions what this will do is shoot you out to our docs.servicenow.com documentation page you can see request a branded android app for public request a branded ios app for public if you click in it it'll recap the steps i just mentioned in this video but also what to do next is downloading the x archive file signing it and creating the ipa file and again here's where the documentation is linked that i referenced earlier and lastly if you scroll all the way up you'll notice this green button universal links file is ready to download once an ios build is complete you can download the universal links file and upload it to your host aka this instance we have our configuration instructions here so you know exactly how to configure your aasa file but please note you have to log in as an admin on your own customer instance in order to do this now that you've configured your universal links and your push notification files you'll be able to approve the build within app store connect itself which will deploy the app to app store now i'm going to stop just short of approving the build because you'll notice that customer approves the build as the last step in both these processes and i'm going to go through the android steps so we've definitely gone through step one submitting the mobile branding request servicenow has built the app and provided an aab file to download and i'll show you how to download the aab file for testing and then uploading to the google play console for said testing so first we'll go to our portal here you'll see we have download aab file now this takes a little bit of time so i went ahead and did it ahead of time you can see here we have our public aab file right here and as mentioned we'll need to test this file and let me show y'all the best way to do that this is where the requisite managed google play account comes in and so what we're going to do is go to our google play store play.google.com and i'm on just the all apps generic console and the this google play store will either already have your app on here but just in case you could go to create app if you don't see your new one we'll give it a name what was this one public hb yep public hb it's an app it's free i confirm and yes i'm cool with those i will create this app and it says start testing now so let's go ahead and go into the testing module and we can create either open or closed testing to be honest with you i'm not sure the difference but hopefully this is where your native team will help you out but either way you're going to need this is where you'll download your app bundles and the closed testing looks very similar or upload your app bundles rather so i'll take my aab file drop it here and it's going to generate my signing key and as mentioned this is a bundle so it's going to take a second to upload now while this is uploading some of you familiar with our mobile publishing process might say hold on i'm familiar with an apk file but not an aab and what the notable difference is is for the public android process you'll receive an aab file and for your private process private you'll notice it says apk now not to get into the weeds of it but let me pull in this nice picture that explains it all an aab file is a packaged uh a packaged android file which has a few other important files on there your google play store will parse these out and push your very well known tried and true apk file out to your users to download the app to either test or to just have as an end user so i think i spotted the aab being finished yep here we go it has come up with a release name based on some other things i can edit i'm going to go ahead and hit save and now i have a release i'll go back to my apps check out my public hb app and i can do start testing now a few of my new tasks are selecting our testers creating a new release and going forward i'm not going to go through but you do need to create a new email list this is why we didn't ask for your testers in android but once you're finished testing your app you can go to the same dashboard after clicking your app scroll down and release it so before releasing you'll definitely need to approve this app on your instance but let me show you what but this is where you'll eventually release it you'll need to complete some initial setup tasks first listed here and you can release through this little portal now the last step in our process is to approve the build in both cases and deploy to either store so let's go ahead and approve the build and see what happens it says our app is almost ready so now that the build has been approved it's going to refresh the page and you'll notice there you'll notice there's nothing else to do here and this is because it is now up to the customer to deploy their app on either store and this is kind of the more manual process in addition to uploading the files themselves but it can be a bit more manual of a process and that's why we suggest the customers with a little less technical acumen on deploying these apps might want to go private so let's talk about the private steps so now we're in private and you'll notice the android steps are largely the same servicenow has built the app and provides the apk file and again the apk file is just something you can hand directly to a user for them to download a android app that customer can test the app directly on their device you'd approve build and then deploy with your preferred method and what that means for android is either deploying your apk via your mdm provider putting that apk on a intranet portal or emailing directly out to your employees you no longer need this google play console for private this is only for public but for apple you will notice that you deploy their app with mdm or apple business manager redemption codes now come back up here the prerequisites and you can see that your apple business manager account was necessary not only for the inputs on the form but also to use for distribution for your private os apps so let's go into our apple business manager and see what that looks like i'll go into business.apple.com and go to your custom apps which is a setting you had enabled previously and we can see all of our custom apps that we have i'll click on red soda can as an example because i know that this happens to be a test app but eventually after you have approved your build then we will publish to your apple business manager account for you so we go into the red soda can app and you can see you can buy licensees and this is where you can have the managed distribution method via mdm or through redemption codes now redemption codes are free and you can let's just say i want five redemption codes i only have five employees to whom i'd like to deploy this red soda can you'll hit purchasing get and i'll have an order number when i purchased it and soon i'll also have a file hopefully that'll there we go i hit download and we'll be able to see all of the redemption codes that you can make available to your employees right here in order to deploy your app privately now one last thing i'd like to mention is i showed you how to redeem this via your redemption codes but if you click managed what that means is it's deployed through your mana mobile device management provider and again servicenow supports intune and blackberry and the steps to actually deploy a managed app are here i'll show you guys one last place for documentation this is our community.servicenow.com or communities portal just go into forums i go to mobile apps and platform and deployment considerations and here we go sync your branded mobile ios app to microsoft in tune and we have introduction to man we have a few really good documents here but this is how you can distribute your app using emm or your intune you can hit find out more in either of these and it'll give you all the information you need additionally these are your mdm providers so they should be able to help you with deploying your app in any way you would like to okay one last thing i want to say is now that we've already approved our build you can see the build is approved the very last thing you'll need to do is enable push notifications for your new android and ios app and the documentation to do so is in our very handy docs.servicenow.com portal you can search the documents for mobile push there we go mobile push notifications look for the most recent release san diego and here you'll find a document on how to configure push applications for ios branded apps android branded apps and your standard servicenow ga apps and then one note on the ios branded apps is this document is pretty thorough on step eight it will ask you to upload your p12 certificate file and where you find that is going back to extend this going back to your mobile app branding setup page looking down at your approved build and you'll see this column push certificate ios only so you'll have a file either right here or as a part of the bundle that you download just depending and that's it are there any questions from anybody great i see there are still a few participants on so guys thank you for dealing with the potentially blurry video for you i suppose it's a zoom issue but we will upload this to youtube as well and i can publish the full 50 gb video to make sure it's nice and crisp for y'all um david ha is there anything else i'm seeing one question from ken um he says it's unrelated but how do you set up a client string field on a form based on the combination of two different fields um ken we might need you to clarify on what you're trying to do here so i'm going to unmute your micro fest i'm going to allow to talk and then and feel free to mute yourself yeah um i have an input form and i want to uh select information uh say it's dependent like on a client and a uh a category and i want to populate a string field based on what the user selects for the client and the category and i'm not sure how to do that if you can do it uh ian would you happen to know off the top of your head on this one yeah so um we can auto-populate a string field when that input form screen loads but unfortunately to have a separate string field based on after the form is loaded and based on the selection of you know values on the input form screen at that point is not currently supported but that's definitely something i would recommend to put on up on our idea portal as a requested feature okay perfect uh we have another question from uh mercia how do you update add features to the published app do you go through the same process each time uh good question for hannah actually yeah actually this is something that we've enhanced our form uh with and you no longer initially you had to go through the entire uh form again and request the same your same branded app and make sure that you put in a lot of the same fields but now we have an updated button on the form itself that will simply say request updated mobile branding and it'll pre-populate with some of the fields you've already with the fields that set up your old app so that you won't have to do it yourself awesome hope this uh answer your question marcia um any other questions before we wrap up today and if mercia wants to hang on for one minute i can show my screen or it is uh as it is a part of the video as well honey you probably share your screen for you know a quick minute and then we'll wrap up from there yep shouldn't take a second you got mercia so we are on my instance i typed in mobile branding to request the branded app and you'll notice that this is the private app long name we were creating in the in the demo the build is still in progress excuse me unblock my calendar and down here on latest builds once the branding is complete you'll have the new custom branding button but also the update custom branding and when you click this you can pick which build you'd like to duplicate in the form and it'll pre-populate a lot of this stuff for you so it sh and so that should be a lot faster in the requisition process and also because apple has already approved this app once and it's simply an update to that app the approval process through apple will be expedited as well awesome thanks for taking us through that anna uh looks like we have another hand raised from ken so i'm gonna meet you again feel free to so uh where do i uh go to put that idea uh in about um dependent client uh the idea of portal um i don't have the you you're talking about where where is the idea portal yeah yeah um david do you have the uh url off yep uh let me pull up the uh screenshot real fast i got it david perfect allow me in my so i'm on the docs.servicenow.com and all i did was search for idea portal and it'll talk you through what it is how to submit an idea sort through a few and do a few more uh management thereof and then do you want to go ahead and community uh where you can submit the idea as well yes of course so there's that and then this is communityservicenow.com [Music] you go into i believe it to be forums right david yep there's also a tab right on there too perfect oh yeah there it is you're right ideas portal so community.servicenow you'll click ideas for it and i'll have you sign in so that you can post it but again the tab is right here all right thank you no problem sweet uh looks like there's no other questions so we'll go and wrap up uh thank you everyone for for joining us today again sorry for the blurriness but just know that we will improve the resolution when we do the upload um and also there's gonna be a quick survey that will ask you know if these sessions are relevant to you we want to make sure that we are hosting the right sessions and the right topics for everyone so definitely let us know in our post session survey what topics you want to see in the future okay but with all that said thank you all for joining us again we'll host another live session in two weeks and we hope to see you there thanks everyone