Bulk Draft Digital Sign with airSlate SignNow

Bulk draft digital sign

good day everyone welcome to the ask the expert session on employee document management where we'll be talking about the employee document management bulk upload just give an introduction I'm a Michael Sheridan I'm from the HR business unit here at service now typically interfacing with with HR service delivery deployments and I'm joined by my esteemed colleague upon 'if you could give a quick introduction of honey thanks Mike hi everyone my name is a Pawnee Bucks I'm part of the HR product management team alongside Michael I primarily focus on our UK and European region working with our customers around product adoption and capturing feedback and insights to drive back into our business unit and continually enhance that product so it's just a quick note on the agenda will be plan on covering today is an introduction to employee document management so for those who are new to the product we want to give insight on what the product is for what it does etc um will then talk about some of the key concept of employee document management which are important to know for that bulk import because we're going to leverage those key concepts and then last but certainly certainly not least the the bulk of the conversation is going to be around that bulk import what that bulk import looks like how do we configure it what are the some of the configurations and how it's used so we're gonna start with just you know setting a baseline around employee document management recognizing that some of you guys on the phone may not be as familiar with this newer element to our overall HR offering in service snails eyes we see employee document management as a way to provide storage space system lack of a better word a way in which we can centralize documents that relate to an employee against their HR profile within ServiceNow and this ultimately provides easy access and retrieval of those documents when required both the HR and for the employee at times and it allows us also to define who can actually access and view these often sensitive documents and set rules around this for when you need to purge those documents and the data that you may have retained around that next time and you can provide service now for EDM it's it's interesting and we'll talk a lot about EDM that's just the acronym that we use internally but access now we saw this really is a natural component or enhancement to our overall HR service delivery offering it's interesting in many respects we were led to this through many requests and and a lot of interest from our existing customer base if you consider you know employees service delivery as a whole we're providing a means for employees to interact with HR and centralize the way in which they find information view knowledge articles interact in the race cases when they need to that is routed to the relevant HR teams and individuals they're also guided through these key moments that matter and through many of these interactions were capturing documents that pertain to that lifecycle event that key moment or that request made on behalf of that employee and through with that we saw an opportunity to centralize how we could capture those documents when they are created manage and maintain that information effectively and as I mentioned earlier purging that at the appropriate period this overall supports our proposition around HR service delivery and allows our customers to have one place to you know not only provide service to free to their employees but also manage these documents surrounding this so we're going to cover a number of key concepts that relate to our version and our vision of employee document management keeping in mind as well as something that you know is probably just good to to set context around upfront we talk about employee document management and it really is with that idea around employing and the center of managing these documents and and the whole purpose of this product so with that one of the things that we heard was you know 4-h arts and onerous task at times to access the documents that they've retained in their own you know additional tools whether that's a third-party cloud system whether that's literally a paper document and for being able to centralize that within the service now and simply identify which documents employees should be able to access on their own behalf was a great way to minimize the you know double handling of those documents and streamline employee access and we've done that through the employee service center so allowing HR to simply take and identify against certain documents or document types what should be accessible via that employees service center another key element when we talk about employee document management especially when you're looking at setting this up is around the security policies that underpin each of these different documents that you might be retaining what we've done is to give you a really simple way to configure the readwrite and authorization of purging of these documents so you're able to set specific security policies that pertain to specific documents identifying who can access what who can read what and ultimately who can you know authorize it being deleted forever in addition so we've talked about security but the other element around this is as you retain these documents how you're effectively aligning with say corporate policy or even a local or you know federal legislation that might define how long you actually have to retain these documents and so what we heard was that depending on certain jurisdictions and you know countries that a country may operate in will define different types or lengths of retention periods and so what service now did was to allow you to apply multiple retention policies per document depending on certain criteria based on different elements and you can see a great example here and Mike's going to walk through a demo of this later as well once that retention policy has come to its end you also have the ability to then how to service now automatically purge those documents so we're really taking the burden of HR we're taking the burden off them to maintain and to continue to you know be aware of what might be coming up to that end of retention period and now we can proactively notify HR if a document is or should be purged in the upcoming weeks we can provide notifications and we can also request authorization just to ensure that there is that human element in between what other key area which was you know really a request that came from our customer base was around certain circumstances of situations where when managing documents you may need to retain or apply what we term a legal hold based on you know certain litigation or legal action that maybe occurring at that particular point in time as such you may want to ensure that those documents are not necessarily purged despite the the purging rule until that legal action or case has been complete has been closed what you can see here is the ability not only to apply legal hold on an employee's profile which will then apply a halt to all documents in relation to that employee or are alternatively for example if it was an audit of the organization and you were required to legally hold all documents of a certain type you could do that as well and that will apply them across all employee profiles that have a certain type of document retained against it it's a really good feature that can help to mitigate any risk of you know losing critical documents that are required as part of an ongoing action so we've talked about a number of things that ultimately make up employee document management in our eyes and help to support the security of those documents one other element that we haven't yet talked about is metadata and that's more so around allowing our HR agents and our HR teams to find documents quickly and easily we're talking about potentially you know tens to hundreds of documents across an employee's lifetime at an organization and when looking for certain types of documents based on a request or a particular case that is raised metadata can help you to easily access and search for that in a far more simplistic manner well thank you for that information upon a great information so for the audience the item we're going to get into next is the employee document management bulk import so our goal is a centralized document so as many of you know in London we introduced the the concept of employee document management which including the features of manually moving these documents from cases or tasks to an employee repository so outside of automation there's a certain circumstance where I wanted to move a document from a employee relations case to their repository I can manually move that the other feature that London introduced was to automatically move documents um from cases so depending on the HR service we can choose to select what kind of document type we wanted to append to that document and then when the case was closed automatically move that into the employee repository so if you know as of Madrid we introduced the bulk upload functionality which is the ability for a use case like to upload scanned documents so as it currently exists we don't have a way to scan right into ServiceNow so the typical use case is to have those scanned documents exist in a repository that repository could be either a third party cloud that that repository could be a local drive you know on our mid server for example and then from there we can bulk import those files into employee document management so those are the current use cases as a Madrid how we can move those documents bulk import manually and automatically on the closure of a case before I get into more the detail since we're kind of transitioning from the the the key elements of EDM are there any questions on Lisa that have come up in the chat or on the on the Google hangout up to this point yeah so we had someone say it would be great to know if there's a bulk export feature the HR department would sometimes like to provide an employee folder upon request um and we do have the ability to extract files from those those document repositories um so that is a feature that you could leverage so it's a separate from the bulk import but by all means we could we could export those documents for you know for the was those legal reasons if need be okay any other questions what else comes up awesome okay so what are these features that we're introducing with bulk import party cloud-based storage or local network directly to employee document management and as we go on to the next slides I'll give some some pros and cons for each depending on your use case um employee documents located within HR service delivery makes administration a little bit easier so you know in the past when we had to investigate an employee or investigate a certain scenario that involved an employee and maybe some corrective actions that were taken we have to traverse through cases and tasks and you know it may be even outside of the application but we're traversing through service now to try to gather all of that information we're now employee document management centralizes that to where I have all of those documents in one place and you know to a ponies' point earlier about that legal hold is and now if there is a circumstance where we have to hold documents because of some litigation or an investigation or something of that nature we can hold those documents um they're all in one place we're not traversing so it really makes that administration or even that investigation that much simpler and then we can consolidate all those documents and maintain over the duration of the employees over their employment so again based on those purging rules or those retention policies um we could hold them for you know legally what we're bound to hold those for again outside of these circumstances where we're we're we're using legal holds um one thing I want to mention as well is that we leverage orchestration and an integration hub has used have you seen in the employee document management documentation on the doc site you are entitled to orchestration by way of employee document management so not that it requires a separate subscription but by virtue of EDM you can leverage orchestration for the purposes of employee document management on bulk imports so the current document repository so that's how are you holding your documents today so currently we're seeing two different variations we're seeing a third-party cloud so in my example today in my demonstration you'll see where I'm using box in order to retrieve some files but another customer may have a use case to where they're using onedrive or another third-party cloud to get those documents the other use case is the local files storage so typically we're seeing customers importing those files by way of their mid server so hopefully there's a question that comes up to say well why should I use one or the other and there are some pros and cons for each with a third-party Cloud Drive we can drill directly into the directory so meaning that if we had a directory that was called users and within that users directory it had subfolders of you know my Chariton you know and all the rest of the employees by way of the URL connection or the third party cloud we can drill into that that that root directory so it's not going to traverse through all of the users in those sub directories so it's if I connect to the user directory it's not going to automatically drill into Mike's Aponte's or anybody else's directory so that's one of the the differences between the local file storage with the local file storage so when we're bringing them in by way of mid tier we can traverse those sub directories so if it's a matter of we have a directory of users within that users directory there's a sub directory of Mike a sub directory of a Pawnee we can traverse those through the application in order to get those additional documents so the the the bulk of it is is that with the third party cloud I'm going straight to the directory if all of the company's employee files are in that one directory that's beautiful it doesn't cause us any grief um if there are sub directories that we may look into that local file storage and this is what we're seeing more customers do that they're storing their scanned documents they're storing their documents from other applications into that local file storage and then using the bulk import to go from that local file storage into the employee document management repository so hopefully I'll address some questions is how does this feature work so again first introduced in Madrid it works from those local file systems or from that third party cloud application once we install the employee document management or once we activate it um we have to say what kind of import it's going to be is it going to be a local or cloud because then we're gonna have additional configurations that we're going to have to do if it's if it's from the local we're gonna have to specify the mid server the SSH or any other protocol that we're going to use the transfer files in that specific configuration where we wouldn't see the same for a cloud URL we're then going to document our import map so we're gonna want to map um attributes from that file to what we expect in ServiceNow so we made map any file name that has NDA to a nondisclosure agreement document type so that's part of our our configuration which I'll go through as we go through the demonstration and then I'll specify my import sources so we use verify files we use a a process to create those staging records based on those files and then lastly we'll do a capture the capture is what actually grabs the file from the external source and then brings it into the employee document management repository and you know last I mentioned about the UI actions and those are the UI actions I'll show during the demonstration where we're going to verify the directory structure we're going to stage the files and then ultimately we're going to capture the files our eat that I'll pause at this point are there any questions that that have been raised Lisa no questions yet okay with not that cost of the link that if any users have questions later the link that was provided is for on the community specifically for this event and the Thani and Michael will always be able to answer them at any time after this broadcast absolutely thank you Lisa so again just to give a high-level employee document management import process so again from the local file storage from the third party cloud our first step is to prepare the files an import source so if we have files that really have no naming convention have special characters in the file name we're gonna want to do some some pre-work in order to make the import of the employee documents a little bit simpler so prepare files that's part of that if we already have a a structure that we're following um it makes that Alba much it makes that much easier for the import process when we're talking about mapping files and matching attributes of those files our next step is to then create a bulk import configuration so I'm going to create my source I'm gonna creep my verify I'm gonna create my stage Jing if if need be um typically we're going to copy that from the the examples that have been given but that would be our next step is to create that bulk import configuration next we're gonna add the import source records which is is you know it whether that be my way of that local file storage or that third party cloud and then last before we start the import is add those import mapping records so we're bringing over those attributes we're gonna want to you know traverse from um an NDA into a non-disclosure agreement so we're gonna want to work out all of those details so the document types that we want to pull in are going into the into the correct document type with employee document management Michael can an HR admin carry out this import process by way of the employee document management role so there are separate roles specific for employee document management where you're going to want to append those individuals who you want with those duties with those employee document management roles the great question though okay so going along with our steps and again I'll walk through these to show you what these look like within the application so we're gonna prepare our files and import source so I'm gonna configure the access to the source repository so for URL based files it's typical that we're using OAuth things of that nature we can grab the token to access those files and these are all pieces of information that we're going to include within our employee document management um source configuration the cloud files can use on the mid server and typically leverage those SSH configuration to access files so again part of our preparation for our document import and then we could tag our name files that we want to import and this is part of that that file pre-work that we're going to do if there is not a naming convention if there's no way to identify the individuals by way of the file name or identify what document type it is so these are some of the pre-work that some of the tests that we're going to do is free work for the for the bulk import um some of the tag or file names that you'll want to import include things like on the employee so um you know the ServiceNow ID you know which is you know a Michael dot Sheridan for example um the document type is something we're going to want to make sure that we're mapping so we so it's importing into the correct document type with an EDM um the file name so it could be visible as a ServiceNow attachment um again some things to think about as we're talking about attachments is if if your organization has any limitations on attachment types so you know we have a system property from a platform perspective so if you're seeing that you're wanting to import files that have um I would say non-standard file extensions and they're not coming in or you're seeing issues um this could be something to check from a platform perspective are you not allowing those type of documents and then the the file it can contain information in different ways so we can have attributes or tags on those files that we can grab in order to identify what kind of file it is me or what kind of document type it is um and then we could we could use a directory path as well so using some of the features and some of the configurations of the import such as as regex and things of that nature we can we can grab more information based on any of those attributes or or meta tags so our next step would be then to create that bulk import configuration so what we're doing is filling in fields like host name and the source directory for import again this is something I'll walk through and and show you in the demonstration and then the credential for access so are we using OAuth are we using basic authentication are we using um SSH or some other method which depending on the type of import we're using local or or third-party cloud would dictate what protocol we're going to use or what credentials we're going to use and then we have this concept of staging record just off status so when we stage the records do we want them as ready do we want them as draft so again another simple configuration that we'll go through as I as I traverse through the through the demonstration so our next step would be the add import source record so we have several integration points that we're using in my example I'm leveraging the UM the flow designer in order to have actions to validate have actions to look up the file and have actions to capture and I will get into the fine um ones and zeroes of the scripting of those but I'll show an example on maybe of the catcher the capture action um in the flow designer so you can see how that works so essentially those are the mechanisms that are actually reaching out to see what's in the directory are reaching out to look at the file and ultimately to capture that information and the file and bring it over into ServiceNow so one thing to note is that the import source code can be written and deployed as a flow action a flow sub action we can use work flow and we could use a ServiceNow script or JavaScript so just so you're aware of the methods that we can use where what you're what you see in the demonstration is just using that's uh using the flow so our next step is then to add import mapping records so this is the import process that's going to convert and parses that information that we've configured so it's going to use reg X to get the first name dot last name as the file name or it's going to use our configuration to say well when it's got NDA within the file name we know that that's going to translate to non-disclosure agreement document type in ServiceNow so again we're translating those values and when I say translating it's not you know by the way of language it's by translating um you know um Sheridan is gonna translate to michael dot Sheridan as an example and one thing that we have one functionality additional functionality we have on that import mapping is the source value can be filtered so if we want to filter it just by a file type so we only want to pull in PDFs you know and that may be your use case we can use that import configuration to filter by the by the source so if there are no questions I'd like to show you what this looks like in the live and in the application where I'm going to perform an import not seeing any questions yet okay let me expand this a little bit so where I'm at now is the bulk import configuration for employee document management and I've created my own example black or box cloud import configuration and I'm just gonna Traverse here to my bauxite so you can see where I have this Michael shared and verification document and a Michael shared an NDA document that I want to use bulk import to connect to this third-party a cloud application in order to pull in the documents so just that you understand that tie I don't have these records staged and I'm 100 transparency I'm going to open my profile so you can see that I have no employee document management or no employee document management files appended to my to my HR profile so I'm just going to pull up my HR profile and here I have visibility into any employee document management files that are are specific to my HR profile so as you could see there are none so I'm going to go back to my bulk import and we'll take a look at my configuration so my configuration ID my URL to my box 8 I have the source type of what am I going to use am I using a local um Drive to import these files or am I using a URL in my case I'm using mocks on using the URL I could additionally log any of the mappings of my of my import mappings to help troubleshoot so document types aren't coming over as they are expected when I log the mapping then I could have visibility into seeing what's going you know from a log perspective um I have the ability to to configure how I want the staging record um to to be created when it's uh when I run the staging so do I want and then drafter I do I want it as ready in order to run the start capture job it has to be at the ready so you know given your use case if you want to you know have it as draft review it then move your your stage documents to ready but be that as it may it's a configuration that you could use to make that a little bit simpler for my particular mapping I'm using a credential alias and I just named it this is my box example a credential I'm not going to pull up those credentials and due to a sensitivity but I'll show how I configure those to see so you can see what it looks like so what I'm going to do is just jump back here so you could see a example credential so I've created this different sample credential and what I want to show here the purpose is so you can see how I can select what protocol I'm going to use so with this new sample credential I want to create a credential for this alias and then these are my choices so again typically SSH we see with the local um method of bulk import we're seeing ooofff basic auth credentials for um connecting to a third party cloud just to give you you know some insight of the different protocols that we're using for authentication or credentials as part of the employee document management um configuration so going back to my my cloud box import these are the UI actions I referred to earlier to where we can start that verify configuration job we can run a staging job in order to to get the information of those files and to stage them and then ultimately for our capture job or actually pulling that those files over again these are our from our UI actions that are going to invoke the jobs and those jobs that we're invoking are what you'll see here below so I have an example file look up for my staging part of the employee document management I have an example directory look up for the verify portion of my employee document management import and then ultimately I have a capture job and it's the example file capture that I'm using in order to bring the file over all of these are actions within my my flow designer configuration based on what I'm trying to do I'm trying to verify I'm trying to stage the file and ultimately I'm capturing the file my next part of the configuration are those elements to where I'm mapping over so just as an example and I'm not using David Liu in any of my demonstration data but here's where we want to UM you know where the source element had David l we want to replace it with david dot liu so here's some of the flexibility we have as part of that import map so if there's part of the file name that I want to use regex in order to do some conversions I could use reg X as part of a filename mapped element um my doctype so I could use meta tags in order to determine what my doctype is so within my meta tags of my document some of those attributes may point to it's a non-disclosure agreement or it's a transcript that it mentions something about school um that's just another example where I statically map a school with transcripts and then we have some other configuration so for my map that woman of item the source is an ID for for my employee I'm using the meta owner and then I'm using some variables in order to set those values so this is kind of showing some of the use cases where it's more simpler where I have that that formatted file structure that file naming to where I may not have to lean on regex or or some of those other tactics in order to you know ultimately get the file name that I desire with a first not last so again an important part of our employee document management um based on you know what we're trying to bring over or what information we want to traverse from the source element to the map element or my next step is I want to show you a little bit what what this looks like in the flow designer before I actually go through the exit go through the import hey Michael yes yeah two more if this runs service now cloud to box cloud does this mean I can also accomplish this from a phone as long as I can drop Docs into box from my phone I could then bulk import them from my phone as well that would not be possible from your phone so anything that that runs on employee document management is really running from the server not from any any local node meaning you know my workstation and certainly not the not the phone okay one more question was there anything special to be done on the Box site to get a auth or was it just the Box login credentials its it could be just the Box login credentials but every use case could be different a mind was a little bit simpler it was a personal box site that I use in order to grab those credentials but that's not that wouldn't be the same for everybody so um ooofff is what's typical I see others using basic auth um you know your case may you know warrant one or the other or something different so it really depends on your use case but more of a common for boxes is the OAuth and the the OAuth configuration specifically is something that's detailed in the in the employee document management documentation as well thank you so what I'm going to do is is pull up my my my actions and they're all prefixed with example but these are the actions that are being called to by the employee document management so you saw where I had the example directory look up I had the example file capture and I had the example file look up and I can open you know just the example file capture just to show you what that looks like so I have my input variables so the requests that I have a string and then we have some script steps what's the end point what's the file name what's the what's the the record reference and then if I go down further I have things like items affected so this is how we know how many documents we have so as part of the the bulk import these are all things that we may want to tailor to our configuration depending on what we're trying to bring over but just an example in the file capture step we have the inputs we have a script step we have a rest step at Step three another script step and then ultimately we have the outputs of the the flow design or action so this is really the the moving parts if you will the engine of employee document management which is really making that effort to go out there to look at the directory structure as going out there to look at the files and ultimately going out to your repository whether that be local or third-party cloud to pull the files in I didn't get into much of the code so hopefully I didn't scare anybody away but I just wanted to give you some insight so you understand the working mechanism at least in this example for employee document management so does that raise any questions um from anybody in the group and you know I encourage any questions that's what we're here for so um by no means uh I'll hold back so I don't be shy whatsoever okay my next step is now I want to walk through how this looks in action so I want to be able to verify I want to be able to stage and I want to be able to capture those files so the first thing I'm gonna do is I want to verify the configuration so I'm gonna go ahead and click on that UI action and if I looked at my jobs I could see it skewed if I go ahead and refresh here I could see all my tests is in progress and it was validated so this has been a lucky demo for me so it all happened fast so it validated so I connected successfully and it found files so I know that my next step would be I want to start staging those files so I'm gonna click on my start staging job and we're gonna see the same to where that staging job is queued I'm gonna go ahead and refresh so it's starting to import those into my staging so it's it processed those files so what I'm gonna do here is refresh my entire record and we should see the employee document staging well now I see those two documents that I showed earlier in my box site which was Michael Sheridan NDA and a Michael Sheridan verification and as you could see based on my configuration they're both at the ready state instead of draft just by virtue of how I had those configured in my in my staging record state field above so now it would be more of a verification yes this is the document type that I want yes this is the file type that I want so my next step could be to start the capture job and this is what's actually going to bring the file over so if I start to capture job and I go to refresh my record so it still so it might capture job the stage complete the last run finished the files were processed so if I go back to my staging you could see now they just went from ready to complete and just for verification I could go to my HR profile and I could open my Michael Sheridan HR profile and as you could see in my employee documents I now have two documents and if I open the document I could see the audit trail so I could see that this what document was uploaded by HR admin on this date so another item you know as part of our audit that we're doing on employee documents we want to know where the document came from so that's really concludes the demonstration of how this employee document management import works some of the moving parts of the employee document management and in terms of the configuration so the things to consider are do I want to import from a URL do I want to import from a local drive what are the benefits of each when you're going to make those decisions in how you're going to bring those files over I'm gonna jump back to the PowerPoint but if any questions are have have come up from this point I'll certainly I'll certainly entertain them as I'm going back to the to the PowerPoint I'm not seeing any questions coming through yet but I'll keep you apprised all right and the last thing I want to talk about before I turn it back over to a Pawnee is some of the tips so what are we seeing with employee document management bulk imports that we can pass out on to the community so um first is that the it's the the bulk import was initially structured for a UNIX flavor mid server so you know customers are going to have to use the PowerShell if they're using um windows mid servers so that's something that some that we're updating our documentation on but something to know that if you're on the Madrid build and you have a Windows mid server those those actions are going to come from by way of PowerShell and instead of a a UNIX shell in Korn bashing cetera a big one and I think the simple one is ensure ports are open for communication so we're seeing customers that I think more when we're using a local drive that we have SSH open that we have all the ports needed in order to communicate even with the file transfer and we have some other customers that are using SCP and things of that nature we just have to make sure that those ports are open did have one more question sure would you please show we're a filter or for file type example PDF files only can be configured during import yes and once I get past these import tips I'll jump back to the to the application and show where you can that's that filter thank you so I'll show that before I pass it on back to atrani um a important item to note is that when you're using the mid server make sure that the account for the mid server has the employee document management writer role so we're saying that customers are getting pretty far in their configurations and not having the role is not allowing the the mid server to pass those files during that capture phase so I'll make sure that that mid server account has that document writer role um when create when connecting to a local document repository we're seeing that most if not all customers are having the grant admin rights on that local on that local machine and specific to Windows mid servers that we're saying and then last but not least is really just more preparation and kind of making things easier for you is is to have your employee documents in a central repository so have all the documents a simple directory structure so again if you're traversing um you know 50 directories deep it's going to make things difficult and then have a consistent file naming convention so if some files you're bringing over is NDA some files you're bringing over as non-disclosed some non-disclosure now you have a disconnect in in or you're having to create additional mappings for the same document type so it's just gonna make things simpler for you on the front so all of your configurations could fall in line you can minimize the configurations you'll need because you're following you know that naming convention for example so before I pass it to a Pawnee let me jump back to I'm show where we can filter so I'll go to my import source mapping and I'm trying to see which one would have B so here's the the filter reg ax so if I wanted to filter by certain document types I would do it in my import map so if you're looking to configure and and looking to filter out certain document types um this is how you would do it through your import map through the filter field and the filter regex well I'm going to now pass it back over to a Pawnee awesome demo and you know really insightful so far I think the last thing that we wanted to call everyone's attention to before we wrap this ask the expert session up is just around some of the other training and assets that we have available so you can see here a number of links mostly we suggest stay in touch with the community we have a huge customer global customer base that you can interact with connect with peers and similar organizations in your industry within our community site and we also have so many different resources that pertain to not only employee document management but other areas of our overall HR service delivery offerings so have a look stay in touch in addition we're also focused on providing additional assets that focus on employee document management specifically deployment models and best practice and recommended guidance so stay tuned we're in the midst of putting this together but this will be available shortly so please do ask your account managers or reach out to us at a time and we will be sure to share that with you I think lastly and then more than anything else we really appreciate you joining this call especially at the time for us if you can provide any feedback or additional topic areas that you want to learn more about or have another ask the expert session on then please post that we want to make this as valuable for everyone here and to answer those burning topics that you want to learn more about so thank you and just before we close I just want to encourage the community to present your questions we could all learn from each other we're noticing that the more and more interactions we're getting on these topics within the community the more and more customers the more and more partners the more and more um colleagues are able to learn about the application or learn about certain functionality and certainly learn about how different use cases are using the application or using the application making the import in a different way but still meeting their use case so I know we have some common use cases there are some unique use cases but by presenting your questions you know subscribing to the community we're always you know in a constant cycle where we're always learning more and more about all the applications based on the feedback and the interaction from the community so so I appreciate it I I i challenge you to present your questions ongoing so we can all learn from each other