Empower Your Business with Cloud Based Contact Management Software in Onboarding forms

How to create outlook signature

[Music] we are actually going to be configuring a workflow this is the user experience the user has while onboarding their device so you see we've already logged into cloud path here as we saw we demoed earlier in an earlier module or earlier lab and now we're going to go into the configuration portion so you're going to click on the configuration and then we're going to go to workflows workflows is the workhorse of cloud path in this case you can see we have no workflows configured yet so we're going to configure one for the first time so we're going to click on create workflow and at that point it's gonna ask you to name that workflow in this case I'm just going to call it james workflow now this is a naming or a display name of it but down at the bottom is actually the URL name so this needs to be a URL sensitive or URL proven a name that we can create here and this is going to be the actual URL that all the workflow that I'm configuring now is going to be placed under meaning that once I have published this or once this has gone out any any devices that need to be onboard or going to actually use this URL name and we'll see see the more details later about that but do know in this case I'm just gonna put simple James - workflow once I've done that and I push save now you can make sure that I have include demo data unchecked unless you want to have that and if you're practicing or if you want to get some experience you can click on that and it'll automatically populate we'll see in a minute that will actually use that for or actually later on we'll actually see where we use that and you can see what all populates there it's just simply a way for it to automatically kind of create a basic workflow for you for you to be able to examine or be able to manipulate if you so choose then click Save here and at that point you can now see we have a workflow listed here it is of course unpublished because we've just created it and then here is the URL for that particular workflow James - workflow you can see here we'll see how that works a little bit more detail now there are a couple of different tabs the properties tab is actually the tab that is what we were just in you can see that it kind of gives us the ability to change the display name change the URL here if I do change this after I've published this then I would have to republish this workflow so it's it's kind of important for us to stick to that the same URL that we created in the beginning if you have to change it you can but it's not recommended to do so simply just create the workflow or create the the URL name that you want to represent this workflow the enrollment process tab is actually where we'll actually start creating the workflow will visibly have a representation of what we're configuring and how we want that user to flow through their user experience look and feel of course is a tab that we can change the colors change that layout a change kind of how it looks and how we represent that to that to that end user and we'll talk about that in more detail we have a lab that shows that and then the snapshots where we actually publish it this goes this gives us not only a history of what we've published from this specific workflow but also allows us to publish for the first time this workflow once we've created it and then we have an Advanced tab and that's where we'll actually see the full URL that we actually send users to so this is a this is if we have a device that needs to be on boarded we would put this URL in a controller to redirect users anytime they come into an open SSID or that they've logged in for the first time and they need to go through an onboarding experience or an onboarding process this would be the URL that they would be directed to once we published this workflow a couple of things I like to point out as well is if I were to create this workflow and I want to remove it completely we can of course do the clean up option here and you see that we can click on this it would delete the workflow and related data it's important to understand that this does not remove the information or the the servers or any other device configuration that we've configured along the way of creating this workflow but it just simply deletes the workflow itself so in this case we've now created the URL and now we're going to go in and actually start the workflow so we're going to click on the enrollment process we're going to click on get started and it's going to give us some options here these are all our plugins that we talked about earlier these are all different options that I can plug into the workflow for that user to experience in this particular case we're going to start off with an acceptable use policy and so it's the first option here and then we're going to actually push Next here once we do that access it asks us to either create a new acceptable use policy from a standard template or we can have some options here do understand that if we did have multiple workflows or if we have different areas within that workflow that we would want to present a acceptable use policy again we can reuse that it is independent and so therefore we can either choose to to use that one again or we could create a unique one for every time we want to do an acceptable use policy that's totally up to you we're going to use the new or the the new and standard at this point and there were our display name we're just going to put in here the James AUP also you can see that there's display information there's different options that we can choose even from the standpoint of colors this is the customization side look and feel as we call it and then of course here's where we can actually put in different messages okay so you can configure this or customize this I'm going to use a standard template to keep it simple and that will give us the ability just to have something representing and acceptable use policy I can always go back in this and change this customize it later as well so from that standpoint we're gonna save that and now you can see we have a first step here of an acceptable use policy like I said if I wanted to go in and change this I could simply click on this display and of course that would draw me back into that configuration and I can of course adjust that as I see fit or as needed and cancel that and so we first have our first step within the enrollment process which is the acceptable use policy all right now we're not going to stop there what we're going to do is now we're actually going to create a split so we talked about the split plugin before and I'm going to actually apply that to this workflow so I'm gonna click in between step one and the results and click on that and then I'm gonna go down and look at the options I have again these are plugins I can use any one of these or the only ones that I want in this case I'm going to select the split users in two different branches and so that's going to create the first branch or the first split within our workflow I'm going to push next it's going to be a new split and again each one of these splits can be independent I could recreate or I could use an existing one because this is a new new cloud path deployment there aren't going to be really any other options in there these are just some pre presets in there but I want to use my own and create a custom split and so I'm going to use a new split here going to push next I'm going to name that split and we're going to do this as Corp UI OD - and then we're going to also have a guest user and this is just naming that split itself okay so we can identify that so at that point I'm going to push save and now you see we have our two options here these are the two that I've that I can create I can also create additional options here and so I've if I want to do that I could click on additional option here but what I want to do at this point is just name these or customize these so I'm gonna click on this one and click on the little pencil here and it's option one and of course this option I'm gonna call corporate BYOD you can have other customized you can do filtering we'll talk about that later again it's enabled we can create display text you can see there's a bunch of other different configurations this will actually modify what would be displayed here so this would you know we can go customize that later but right now I'm going to just leave it the way it as a default so now we see that one has been changed to corporate BYOD I'm going to go click on my second tab here it's important to understand and note that when I click on a tab it basically covers up the others and of course now it's displaying this second option each one of these because these are branches might have different representations meaning that I'll have additional steps underneath this tab opposed to the different different additional steps I'll have in this different tab so it's important to click on the tab that you're wanting to configure it adjust to make sure that you're adding steps or your you're creating a a workflow based on underneath that particular tab or that particular branch within your workflow so I'm going to click on edit on this and this is going to be guest user I'm gonna push save to that and now we see we have two different tabs these are two different results that I now have at my my workflow users whenever they start onboarding they're gonna go first gonna see the acceptable use policy then they're going to be presented with two different options that they can go which is going to be corporate BYOD or guest user okay now that I've completed that I want to start developing these branches so in this case we're going to go under the corporate BYOD tab as you can see here and I'm gonna click on the insert step here now what I want happen is as soon as that person selects that option I want them to validate or verify that they are a corporate BYOD or corporate user in that case we're going to try to insert an authentication process and so what I'm gonna do is select this second option here I'll indicate to a traditional authentication server I'm gonna push next ok and so now once I've selected that you can see I have a different a couple of different options here I can connect to LDAP radius the onboard database a couple of different options there so what I'm going to do is collect the Active Directory and I'm going to configure that for this example so my ad the domain name we're gonna just put in Rukus training so we're gonna put that in there again these are just your your configurations based on your settings and what I mean your settings I mean your your LDAP servers that you have configured so you'll need to go in there and this needs to be applied based on those configurations and how it's going to be connecting to it in this case you see I've got the LDAP you might use LDAP s or secure in your environment and this just lab over just using straight LDAP and then the ad DN name we're gonna be adding it in there and then ultimately we need to select in this case an ad username attribute and we can choose the attribute and we're going to use the user principal name in this particular case again though you know different servers each one of these will have custom configurations based on your environment and how you want to configure it and of course how it's going to match into your existing setup that you have and that's where cloud path shines because it allows us to adapt and to be able to incorporate in many different environments that you already have set up we're simply trying to automate the process that you possibly are doing manually in your environment when it comes to onboarding devices so once we've configured that we're going to go ahead and push next and we can look through the different options here one thing we can pay attention to is to see that you can use CAPTCHA if you want to do that so in that case we can select this option and it will verify and add additional parameters or additional features on verifying that particular user and then we are going to go ahead and select that for this this example you can see there's some other configurations that we can do again we're just trying to keep this simple as a demonstration definitely when you get into yours you can look at these different options and be able to explain these or customize it to your environment more specifically this is just the demo of creating a basic workflow you do also notice that once we went to the next page here the demo or the display name already was populated we're going to just keep that simple we can customize this making it more personal or more specific more descriptive for what we're trying to do but again we're just creating the the authentication method so I'm going to go ahead and click Save here and we can see now we have an additional step here step 3 underneath corporate BYOD and that is to prompt the user for credentials and we're going to be using it against the authentication to the Rukus training ad server now because the authentication when a user or a device is trying to authenticate is based on certificates we want to be able to manage those certificates right so if it is a case that this user is onboarding a new device replacing an old one we would definitely want to have them review certificates that might be associated or assigned to them allowing them to delete or deactivate those other certificates that are no longer active simply because we're replacing it so we're going to add a prompt for that particular feature or that particular option it's going to ask for concurrent certificates so as that person authenticates and they move on through that workflow this is going to cause it to pop up and say these are the certificates we show issue to you or they still act / still need if there aren't any that need to be deactivated that's fine but also it would give an opportunity for the user say oh yeah there's one that no longer had that device or it's not issued to me anymore and allows them to delete those certificates this is important from certificate management if we have those deactivated then that licensing of that particular certificate can then be reused so it's a case that this is an important process when it comes to managing these certificates and again allowing it to be self-managed from that particular user that user knows better than anybody else what devices these he's currently using what's active and of course what he can deactivate that he might not be using any longer so we're gonna push next there and we're going to be using a new prompt so this is uh again everything's modular so in this case you're going to select a new one because this is a new calcloud path deployment we don't have any existing so we're going to click that and push next and then we're going to be asking to name that now this is lab 6a so I'll just put in lab 6a when it comes to the concurrent certificates we can also see there's different parameters here when it comes to the certificate templates the display threshold how many we want to display a maximum allowed certificate so many a lot of certificates are allowed to a user all this can be adjusted again we're gonna set these or leave these at the default but do know these are customizable options that you can choose when it comes to configuring this workflow so once we've done that we're going to push save nope sorry has to be unique apparently I've got something in there older so I'm gonna put this as new save so now we can see that we have a new prompt after they've they've authenticated they move on through this workflow in step four is going to give them an option to say I'm going to remove any existing certificates issued and see if there's any that they want to deactivate at that point then what now that we've gone through this process we've authenticated the user we verify there's any certificates what we want to do is this device their onboarding we now want to assign them a device configuration and we want to assign them a certificate and that's the the end result it is for either each branch one thing I do like to point out is by default any time option is selected from a split user or the end of each branch there is this automatic result because that's really what we want as a result from this workflow right so if I click on guest user you'll even see there's a result here that was already configured now that that needs to be configured but it's in that workflow alright so at that point we can go in and edit this and tell it exactly what kind of device configuration as well as certificate we want to issue to the device of anything that runs through or goes through this particular branch of this workflow so we're going to finish our corporate BYOD up so we're going to click on that scroll down we're gonna go into the result and we're going to configure it okay now that we're doing that you're gonna see we're gonna assign this so the way I'm going to configure this result is I'm going to go over here to the pencil on the far right we're gonna click on that and it's going to give me the option to choose so in this case it says none do thing of course we don't want to do that we want to actually create a new device configuration so we're going to select this option we're going to push next and this is allow us is going to be able to configure a device configuration what is the device configuration well this is identifying the SS IDs that we want this particular device do it to connect to and authenticate from so when they connect to that we'll be able to say this is the settings that we want configured on that particular device again all of this is modular so it can't be a case that I could configure this here and then reuse it any different branch now depending on those branch results or depending on what you're wanting to accomplish within those branches of the workflow will cause you to either configure multiple device configuration options or possibly reuse them again it really has to do with what type of device we're onboarding naturally we wouldn't probably want to use the same device configuration for a BYOD corporate device then we would say a guest user so those would be two different configurations why would we have two different ones well the BYOD device we might want it to be able to configure to a secure network that's separate from what we might want guests connect to and so therefore we'd have two different device configurations the guests might go to a VLAN only internet connection and so forth and so each one of these are customizable and can be applied at the results of each one of these branches ultimately giving us a unique configuration depending on the device that's being on-boarded so here we're going to just do a new device configuration we're going to do this as corp BYOD and then in the wireless connections here we're going to configure this now it's very important to understand the SSID that I put in here needs to be the same as this ID of the the the wireless connections that we have can on our controllers or on our wireless networks okay because this is literally going to be a configuration that's going to be downloaded on the device this information needs to be accurate or matching that exactly so we're going to configure the wireless connection in this case I'm just going to say my name James secure and this way I'm going to have an SSID that's called James secure so when this device gets on boarded it goes through this word of this onboarding process and it gets its configuration downloaded it's going to know that it needs to go to and can be connected to the SSI they James - secure and of course then this certificate will be used that we're going to be showing and configuring in a minute is going to be used for authentication for that particular user so I'm going to push next here we also have the conflicting SS IDs now conflicting SSID is going to be the onboarding SSID that this person might be connected to right now performing his onboarding duties or his on porting process so in this case we're going to be and again this is an existing SSID that they actually connect it to and so I want to identify this so when this device now is on board and it gets its certificate I don't want it to be going back to that onboarding open SSID I want it to go to the secure SSID and so when we say it's conflicting we're going to basically a verify and say we do not want you to go back to this and so we're going to identify it here and then part of that configuration will cause it to want to go to the secure instead of the existing Zess ID they're connecting to while onboarding these are different options when it comes to the OSS we can specify these when it comes to you know the the the type of device and quad operating system it's running in this case we're going to keep these as default but again you can see this is part of the the MDM and of course nak features that we have that we'll be explaining in more detail later we're going to keep those as default for now and you see here we have a couple of options when it comes to the the authentication so once that certificate is issued what device do we want it to authenticate to in this case we're going to be using the onboard radius server that cloud path already has up and running on this particular instance it always does so when you cloud path radius server is a feature that is active ready to go and gives us the ability to use that so we're going to be using this in an example so we're going to keep it at the default of authenticate to the on board radius server we have additional options again more details when it comes to all the devices onboarding we will verify information there and again that's reason why we say an AK MDM light because it will go and verify this information while that device is being configured for the the access from from cloud path so we're just going to leave that again a default we're going to push next and then we're going to issue a certificate again this is the certificate that is actually going to be used for authentication so once that device migrates to the secure Network that we just identified in in previous steps this is actually going to cause it to use the certificate for authentication so we're gonna create a new certificate template and we're going to be using the onboard certificate authority again this is just an example you can see there's many other options we can we we can provide within cloud path allowing us to use either items or certificate authorities you already have in your existing environment or allow you to simply use the one that's onboard it already active and running within path and that's what we're going to do we're going to be using the intermediate CA there I'm going to push next and then we're going to select a username now you can see that there's many there's already presets here of course you can set your custom one and this is just the authentication name or the setup or the format in which we're going to be having that user authenticate some of the benefits to this is is as we identify these or if we specifically identify these based on the workflow that these are being completed hence in this case it's the BYOD corporate whenever we look at the logs within cloud path it makes it very handy for us to be able to look at this and identify how that device or what type of certificate or what type of username so it gives us ideas of what what template that this particular user might be using to authenticate that device and again it's just more of that log and be able to readily identify these and be able to look through that quickly and see what gasps possibly faculty whatever it might be that they're authenticating to and those logs are just much clearer and gives us a better picture of what's going on of course at that point we can also select different time zones for time link the period that the certificate is going to be active in this case because it is a corporate video IOD we're gonna probably keep it at a year here but we could shorten this especially if it's a guest coming in and we're going to be issuing a certificate they're only gonna use that for a couple of days we could shorten that time period to where that that certificate would expire causing that device to have to either re on board or they're on their merry way they're not going to be coming back and that ever allows us to free up a certificate that can be issued to future guests that are on boarding at later dates so we're going to keep that one at one year when you log in yours you can see that there's different many different options again when it comes to do to how you want to set this certificate template up but we're going to lead this at default and of course the granite for one year okay we see now we have a complete result when it comes to our corporate BYOD we have a step three and step four we've created and then the result of them completing those steps within their onboarding process is that they are going to be issued the configuration of corporate BYOD and then they're going to be issued a certificate that is going to be used to authenticate that has the username at BYOD rocket starting that workers wireless dotnet that you see there again all these are customizable you can change these up but in this case this person completing this workflow this is their experience a couple of things you can see they're handy is you can hover over these particular items and they give you more details of exactly how this is configured and if I need to change it I can simply click on these these URLs and they will give me the ability to go customize or change these parameters so now I'm going to go in and complete the guest user branch so I'm going to click on the guest user here as you can see that has a different different branch or different steps here we haven't created any so we need to go in and create these steps so what we're going to do is we're going to go into the guest user and we're going to click in between here and start step here and in this example we're going to simply use a voucher system for this particular user now we haven't talked about that completely yet but just know that this is a way in which we can have a value given to that user and then that user can use that to onboard their device and so we're going to click on authenticate using a voucher from a sponsor and we'll talk about vouchers in more detail later but this is just setting up that branch flow for the guest users we're going to push next we're going to label this so we're going to label this as guest users and then you can see we can go in there and change the formats of that particular value or that that number numeric value or that value that we're giving them you can specify the length alphanumeric we're gonna go ahead and make this just numeric you can see we have options there the validity period length of course we can adjust and we can also adapt it in the sense of how many times that particular value could be used in this case we have it set as once time a one-time use but we could put in there multiple depending on your environment again depending on how you want this configured if you I want more control over it you can set that up as a one x there for each time a user wanted to onboard a new device they would have to get a new voucher we're gonna set everything else keep everything else at the defaults however we're going to scroll down to the sponsorship area and we're going to set up the LDAP username so this is just going to be able to identify uniquely how we want those usernames to be so it could be a case that we have and this is a pattern right that we're setting up so if you have somebody that's like John Doe at ruckus wireless net then that would be a John Doe so we can go in there and have the asterisk which means all of them or we could be more specific and just say that is going to be a certain pattern that we want here so in this case we're going to put in John Doe and then that way we can verify that that is the pattern matching when it comes to the LDAP username we're going to keep all the other configurations as default we're going to push next and yet you can see once we push next it does come up and to create about your prompt this is a display name again these are the display common names you see within the workflow I'm going to go ahead and keep this one at default there are other options you see you see that we can choose here again we want to keep it simple just for demonstration purposes so we'll keep these default values and then we're gonna go ahead and push Save as we see in the guest user we now have a new step here corporate BOE the BYOD has its own steps in this case we have unique steps when it comes to the guest user option if somebody so chooses this within the workflow so to keep it simple we're just going to have an axe ask for a voucher so in that case the voucher is completed if they have if they have a voucher number they put it in and then the result is we want to do just like we did with BYOD is we want to give them a custom configuration as well as a certificate and issue that certificate for any future logins towards that that SSID that we assigned them to in the device configuration portion giving them the the authentication okay the authentication method when it comes to that connection now because we are going in and it is a guest user we can now create a custom device configuration for guest user specifically meaning that we're going to have them going to a different SSID we're going to issue them a certificate with a less time or a shorter time than we did with the corporate BYOD and so forth so we're going to go ahead and adjust this and we're going to click on the little pencil here and we're going to use a new device configuration do note that we do have the existing configuration if we so choose but because this is a guest user we want to create unique values and so therefore we're going to create yet another device configuration for the guest users we're gonna go ahead and push next there we're just gonna give it a simple name here so it's going to guest users I'm gonna push next their wireless configuration so this is going to be the SSID that we want these users to migrate to so in this case this one's going to be James - guest again this will be an SSID that has to be configured on controller and needs to be existing for it to function correctly or again going to be using a certificate to authenticate the user we're going to push next here we are not going to configure a conflicting SSID because we might be the case that we could have these users actually use that open SSID and we could have them authenticate to that but again as you know we can configure something and not have them go back to any SS IDs or keep them to have any kind of configuration towards existing SSID as they might be connected to and as a result we're just going to go ahead and push next there I can identify them at this point we could go back at a later time as usual this should be familiar you can see that this is what we had from BYOD earlier we're gonna go ahead and keep these as defaults as well we're going to push Next and then we're going to authenticate the user to the onboard ready server again so we're gonna push next they're additional options again these are part of the the customizable features when it comes to enacting the M we're gonna leave those as default right now and then we're going to issue them a certificate now this is the one that we used earlier that we configured for the BYOD but we want to configure a new one for these guest users and we want to shorten the time in which that certificate would be valid so we're going to create a custom certificate template for our guest users we're gonna select that and push next we are going to be using the onboard certificate authority which is the same that we had for BYOD but again we're going to be able to customize these certificates we're gonna push Next here and this time we're going to select the guest right so we're going to have it authenticate with a different type of user name as you see here giving us the ability to readily identify this user at inter logs as the users are onboarding and using this certificate we're also going to go in and grant the access and we're going to shorten that so in this case instead of having it as a one year we're gonna set it up as three days so in this case three days here so the certificate will be good after that p.r time period that particular user or that particular device would have to onboard again the way we've got this configured uh configured is when they have to onboard again and they would need a new voucher right because that's what gives us the ability to move forward within that workflow in this particular case you can configure it in any way you want and customize it to your needs within your environment once we've done that we're going to push next takes a little bit to configure this alright once that's done you can now see that we have a different steps when it comes to the guest user we click on corporate BYOD again we have those flows so depending on as the user on boards with depending on which option they choose within that that onboarding experience they're going to have a different user experience or different requirements this case they're going to be having the the authentication based on their credentials whereas the guest user is going to require a voucher now once we've got this complete it's important to understand that this has not gone into effect simply because we're still in an unpublished state all right anytime I've already go in here and unchanged things those changes are not immediately taking effect it's a case that I have to go in and actually publish that workflow it's once those changes are made for it to become active what does a publishing process do well publishing process actually creates what I have created from a workflow here and it's created and represented all of this workflow pattern within a URL we can see the URL for this particular workflow that's that's going to be to be where is all this configuration is going to be placed all right so now we need to publish with this workflow for it to become active the two ways you can do that when it comes to a brand-new workflow we can either click on snapshots and we can see where we can actually push the publish button or if it's an existing workflow that we're actually upgrading or updating we'll need to go and click on this little publish button over to the left of it because once we've published it for the first time there will no longer be this option within the snapshot tab so therefore you will exclusively use just this publish option on any future now because it's a snapshot tab meaning though that will have multiple snapshots and possibly changes that we would have within a workflow available to us to either rollback towards or to be able to use it's important to understand too though that if you go back to a previous snapshot although that is what's active and that's the experience the users will have based on that one moment that snapshot was taken but it doesn't mean that it's going to revert you work flow back to its original form based on that snapshot so if you were wanting to match that snapshot you would need to go back and change your workflow to match what that snapshot was and and be able to be able to republish that if you wanted to make some changes so it's really important to understand that in this case we're gonna go ahead and push publish in this case so at that point we're gonna see this going through a process of being able to compile this workflow and then ultimately put it underneath that URL right now it's still working you can see that we have the little star or the little active icon here once that goes green then that means that workflow can now be used and devices can migrate to that and go through that workflow experience we see that it's now gone green and so now we know that that snapshot is is ready to go or that workflow is ready to go where do we go to see that workflow we can go into the Advanced tab here and now this URL is the representation of that users workflow so we're gonna go and click on this so let's go through what the user experiences here so now we see that we have the acceptable use policy here that we have set up as the first step I'm gonna push start we're going to choose BYOD first or corporate BYOD first here and we're going to put in a username and password this username and password I've set up on our ad server so let's put that in along with our password and the CAPTCHA we can see they were authenticated and now they are accessed to download a configuration file this is Express connect it allows them to launch this it will not only configure their device for the appropriate SSID Zitz to connect to it will also download the certificate and the certificate in this device allowing it to authenticate using that certificate moving forward as it migrates to the secure SSID now that we've seen the BYOD side of this workflow let's go to the guest side so I started it over here and now we're gonna go next to the guest user portion we're gonna put in a voucher number code that I already have let's continue and we can see also they receive a download to prompt for them to click on this and it's going to provide configuration for them as well it's important to understand that each one of these have a different experience right not only is the experience from the flow but also the configuration that they're going to be receiving along with the certificate the corporate side we remember we set up a certificate that has a validity date of a year whereas the guess is only for three days not only that we've also told each one of them to be configured to connect to a different SSID this one being a guess where as the corporate was the secure James secures what we set it up for so either one of them can go through this brew this this branch or this workflow pick their specific branch and as a result have their unique configuration set up on their device and authenticated through a certificate that has a validity date different than the other branches if you so choose so this completes the lab 6a hope you enjoyed this and we're looking forward to showing you some other labs thank you you [Music]