okay so let's start people will come and they'll join okay so let's start so everyone thank you for joining uh this is the third chapter of journey to star series so a bit about series uh i started this series i guess three weeks back so with an aim to bridge the gap between experts and folks like us so we should get an opportunity to learn directly from them even they want to share their knowledge so it's a that platform and the best part of this platform is uh every day the attendees decide the topic for the next session okay so i hope you all are safe then a bit about me i'm currently working as a servicenow consultant and i love to explore security ops maybe that passion for security ops has made me a google hall of famer but i feel that biggest achievement of mine in my short career is the support that i'm getting so we'll learn together and we'll grow together so let me introduce our guest for today hi sujeeth how are you your voice is breaking i mean it's kind of i'm not getting any voice uh there is some disturbance in the audio so uh one news initially we planned for uh integration number as well as vs code but at the very last moment uh the sugan was not suband is not able to join he is not feeling well so we have uh restricted it to vs code itself and what we will do uh will take on the questions if you have any in qa and a session and we'll answer them over email i will pass it on to sugan and we'll get a response from him and we'll definitely have a session on integration hub soon maybe as soon as he is well shujit are you back hello hello so let me call him and ask him what's the issue these technical glitches he rejoined yeshujit hello can you hear me now yup for fill it yeah hi everyone uh so my name is shujit mishra i'm working with servicenow since december 2017 as a principal product manager and overall i've got 12 years of experience and i have worked across product management and business analysis across ad tech mobile and front deck domains so that's about me uh that's great man so uh sujeet as i mentioned uh today we are just having vs code so there is no integration hub so i'll pass on the control to you just share your screen and enlighten us with your va sports stuffs just happy to do so so can i start heading you can share your screen icon okay hi everybody can you guys see my screen now yeah okay great just [Music] so uh so yeah thanks to for this and i'll start off with so we have launched this servicenow extension for vs code and this is the official version from servicenow and we launched it on november 8 2019 and as i'm talking we have got close to around 11 300 installs of this extension so primarily i will give you a background of why we did it so uh currently most of the developers who are working on servicenow application use our based id which is studio and there was feedbacks coming in because not very everyone was happy to use studio the reasons were like the performance issue you always need to be connected to the internet because it was a web-based in ide and if if someone has to compare the current studio with a id like vs code there were a lot of features which were missing so we thought of addressing those challenges and cater to the feedbacks which were coming in through this extension so the safe harbor notice so i will be covering all these uh overview why vs code extension for home via builders why the extension should be used and key tech takeaways so why vs code extension so as per stack overflow surveys which have been done in 2018-19 vs code is the most popular development tool which is used by the developer community and also market competitive needs because as i mentioned there were feedbacks coming from certain segments of developers who built servicenow application that they were not very happy with the existing web-based ide which was there the form of studio see in order to address these two uh points which is the tool of choice always as well as a market competitive needs we came up with the vs code extension so why vs code so i think these are the predominant reasons why we uh selected vs code it is uh developed by microsoft lightweight uh source code editor and we service now has a very strong partnership with with microsoft and we wanted to leverage that partnership it combines simplicity of source code editor with powerful debugger developer tooling you also have debugger which is pretty useful while someone is developing applications you have intellisense in the form of code completion which i think everyone will agree that it is very very useful when someone is doing application development key features like syntax highlighting code snippets it allows integration with source control highly customizable i think the last but not the least best option for working on web components so this is basically tied to a story so we we started with app extension where you will be able to build apps and slowly we are also looking at how the vs code extension can be used for component development also going forward and that was the predominant reason we shortlisted vs code so so on the left hand side we have the scripted data on the platform which i've spoken to but not everyone liked it so we came up with the script editor uh in the form of vs code extension so what it does it provides more options for scripting to our developer community and for uh whom we have built it this is for any application developer who wants to build service now application us using vs code so uh why we should be using it it is official extension from servicenow so we so we here we review all the feedbacks which are coming coming through community i personally reached out to many developers in form of linkedin and try to get their feedback of what is working what is not working if they are using servicenow vs code extension uh we have a dedicated team who basically works on this extension it helps in offline development so what it means it you don't have to be always connected to the instance you basically download your application and using into that extension you work offline and then once you think that you are done with all your changes you can sync it back to the instance it has got intelligence which helps in development you don't have to basically type everything it helps in the auto completion feature where it basically understands what exactly are the functions you are typing and accordingly it will prompt you for the uh uh related functions then it has got linting so intellisense and linting in the vs code extension is same as what is available on now platform so we have one team which basically works on the on on platform capabilities which is the script editor and there is another team which which i work with which owns the vs code extension so we know what exactly is there on the platform and what needs to be built on the off platform so that we with the the entire objective is going forward we want to have parity between the on platform and of platform capabilities uh the execution of background scripts so the extension also allows you to use background script and two-way thing so it doesn't matter whether you are working on the instance or the extension so we allow two-way things so basically whatever changes you are making you can sync it either ways so type of application supported so uh so when you basically set it this up and you click on create project you will get two options custom applications and store applications but i i know uh developers who also use packages and plugins which can be enabled through settings but the reason we did not provide it up front is because uh i mean i am talking i've spoken to multiple developers and also i i know how the workflows work so most of the developers from the external world will not be using packages and plugins much so so these are the two applications which basically the developers work on and this is what we are providing uh then you can work on multiple projects from multiple scopes so say if you are a developer who is working on two different applications which are present in two different instances so that is also supported you can basically authenticate yourself to two different instances and once you are there you can basically work on both the instances through the vs code extension as per your needs uh as i mentioned we have platform linking so we are using eslint as the default linting tool for the platform and same is available in the vs4 extension so we have intellisense uh intellisense is available for glide apis and jelly tags then we have background script which can be executed by selecting the desired text from js file uh then support for global i think this is a feedback which has been coming from multiple people whom i have spoken to so we do have support for global and i would like to take your feedback on this so so i will tell you how exactly this works now so uh so there has to be there's a precondition which is uh basically needs to be satisfied if you want to work on your global files so currently in the extension what a developer needs to have is at least a scoped application or a stored application or a package or plugin and that is how you start your create project flow the workflow in the extension and then if you have to specifically work on global files if we you have the file search functionality which is used for working on global files so what it does is you you basically configure which are the files you would like to work on um the global files and you do a search for them so when it is uh so when the search results come up they basically are down downloaded to so if you have seen on the left hand side we have two folders one is the uh src which is a source folder where the applications will go will be getting installed and there we have something called a scratch folder so scratch folders are where your global files will get downloaded and you can always work on them and uh so so this is what we had done for the version 1.0 and after that we have made four releases so uh so how it it happened was we are following a monthly cadence but again it all depends it is not a confirmed or a short thing that we will be releasing every month but if we see that there are a lot of features which we have planned which needs to be put out there so that the developer communicate community can use or if we see there are a lot of feedbacks which is coming and we need to work upon that so so that is where we go with our monthly releases so after november uh in march 2020 is when we launched version 1.1 so in this what happened was project type updates so as i mentioned initially we had everything like store application scope application packages and plugins but from the data which we gathered and on having spoken to developers we got a feedback that packages and plugins are something that not everyone uses so we thought that it is it would be confusing for our users to basically put it a friend so what we did was we basically uh as i had shown in the screenshots we only have the scoped application and stored application upfront but uh having said that it is not that you will not you cannot work on packages and plug-ins if that is what you use for your day-to-day work you can always go to the settings and configure it the packages and plugins will be enabled for you then files downloaded through file search can now be edited and sync and this is what i was talking about so all the global files uh i think there are a lot of developers who work only on global files this is for them so so what you do is basically you you download your file the file will get downloaded into your scratch folder and then you can then you will be able to work on the global files and you can edit them and you can sync them back to the instance then uh the documentation link was fixed so we had minor glitch around the documentation so we have fixed those in version 1.1 now version 1.2 was released in april 2020 so that was mostly uh the objective was to enable telemetry to get insights into how the users are using the extension but having said that if you are not very comfortable sharing your data or how you use the extension you can always uh decide to disable the telemetry but the major objective of having telemetry enabled for this extension was to get more insights so that we continue to know which particular areas are the ones which are mostly used by the developers and which are the uh less used so what we do is so this basically helps in prioritizing features uh around so uh around the ones which are more more widely used by the developers so this will also ensure that you get more and more features and more capability around those areas and it will go and we will continue to add value for our users now uh monthly release uh 1.3 which happened in may so uh we have started supporting short instance url so say you have like say for me like shujit mishra dot servicenow.com so you just need to type https shujit misha and it will just take the ser it will automatically append the servicenow.com part to the url and take you to the instance so you don't have to remember all the things it's just the basic uh or probably i can say the keyword or the unique part of the url which you remember and then uh rest of things we will be taking care of it then we have developed keyboard shortcuts so uh you have a lot of different commands which the developers will be using so we have developed the keyboard shortcuts for those also uh then we have provided real-time progress bar indicator we so so as a team we thought that there were certain functions like import application sync or file search which was taking time so right now we have so so right now what happens is we have a progress bar indicator which will tell you exactly say there are like uh you are doing a sync operation and it involves 100 files right so it will basically tell you how many files have been uh synced and how many are remaining like two of uh two or four hundred three or four hundred it will continuously keep telling you so these are the number of files which have already been synced in the sync operation uh we have also done new exchanges to the file search we are trying to make it as simple as possible for the users to use our file search functionality uh which i think is pretty key because most of the users as i mentioned work on the global files and this is where uh you will be able to basically leverage the extension to work on your global files then we have also made changes to the file type speaker your ux improvements uh so merge file group and file types hierarchy list are now merged into one flattened list so we are trying to make it as simple as possible for the users to use our extension so the priority file types will be displayed on the top for easy discoverability the list can be filtered either by the file group file type or the table name so these were the changes which we made in the month of may version 1.3 1.4 was a pretty big uh release with lot of features which which i think is pretty useful for everyone and i think andrew had written a blog which i had shared on linkedin also so what are the changes which have happened as a version part of version 1.4 so version 1.4 had addition of new utility commands where you can open a script file and platform you can preview files and instance copy society to clipboard revert file changes to instance version so these were the new utility commands which were added then we had background script on our announcement so this again is driven by user feedbacks which were coming through the community ability to choose a desired application scope when running scripts and background so now the user will be able to dis select the scope in which the user wants to run the background script the dedicated background scripts folder for creating and executing background scripts one click execution of scripts in background scripts folder using the toolbar icons we have removed the run background script global option so initially we had only global option which was not very pretty much used and there was feedbacks coming in that where the user wanted to basically select the scope in which they wanted to run the background scripts then update set for the scratch users can can now choose update set for files in scratch folder i think this is a one again uh pretty big change which we have done i would like to call out so previously for the scratch folder you are not able to select the update set in which you want it to work on right now so this was again i think the feedback coming from andrew that the user basically look for selecting or choosing the update set in which they want to work on so this this was done then we also have enabled sync to default update set in scratch is disallowed and then we have now jelly intelligence improvement with support for multiple tags in a single line and single tag spanned across multiple lines that we have made uh ux changes which is like improved dx of the file search results improved ux of conflicting files gui screen and then we have also made changes in the bulk sync support for scratch so these are the various uh changes or i can say additions which have been done to the extension post our going live in november 2019. so we right now have like five versions which are uh which we have basically worked on or the five releases which have happened post november 2019 uh so these are the uh so the next steps i would request if you are using the extension great uh we would love to hear your feedbacks around how the extension what what is exactly working for you what is not working for you how can we make it even better which will solve your problems so this is and for the people who have not used the extension in this call i would urge you to go to this extension and basically use the extension we also have a community page where which is dedicated to the vs code extension so you have any questions you have any feedback for us you can provide it in the link and this is a demo which i had created i think it's slightly old but still then it's very useful for people who have not used the vs code extension please you can go and uh see the demo where i've spoken about the various functionalities capabilities in the vs code extension and also to add to that in k20 we had these three sessions for or for the vs code extension so this was a theater session this was a creator called breakout session and i think this is one where you will find it most useful which was a workshop it was like typically 100 minutes workshop and we have tried to demonstrate each and every use case uh associated with the features or capabilities of the vs code extension so i think with that i would like to close and probably we can start uh the discussions uh thank you shujit so that was really nice actually we have one question from kumar you can just come up and put on your question yeah i want to know is there any cost involved to enable the vs code no there is a vs code kumar is absolutely free and the extension also is free i i mean i do not see any cost until unless there is a restriction in your organization to use vs code and that is one of the feedback which i have heard from people but uh but there is absolutely no cost involved for using vs code for a developer's point of view it is very great for us to use it right that's why so you are using it right now or you have not had no no no i am not using it but since you demonstrated all all these things i am planning to i will go okay what i would like you to do is after this call please go to the vs code extension um vs code marketplace and install this extension and start using this so can i enable it on my personal instance you you can there are a lot of developers who are actually using it on their personal instance also okay okay thank you okay so kumar i am using it so okay a few questions from my side so you said uh while working for global files we download those files okay right so how multiple people will work suppose uh me and you are working on that file i downloaded it but then other person updated it updates it then i'll be having the previous version so is there a way to manage it uh okay uh so let me tell you how how i see this so what you are the use case you mentioned through ic is more about team development or collaboration right and uh the charter which my team has is only around uh the the i would say code and design and debugging right so that particular area i think we will not be able to touch so what i have demonstrated is uh so basically uh at the same time if some if two developers are working it is difficult how i see uh the only way i i can envision this and the way i will try to solve this basically you have to interact offline okay and that linting feature is it similar to servicenow i mean what you get in the background scripts yes yes yes it's exactly the same and this one tool uh we all use as a ide that is explore right here that is in the system so right okay uh yeah yeah group please yeah so i just want to know what's the difference i mean what added advantage that vs code gives okay uh so i will tell you there so i will divide this reasons into two parts one is which i can share the second is which i cannot hear okay uh so yeah uh so so coming to the ones which i can share i think uh everyone would agree that vs code i think is the most popular tool right and uh among the developers uh who would like to build applications that was primary reason which we which you decided on vs code and uh the other reason is it gives you that and the full-fledged id like capability the explorer i think i saw i found few videos on that but i would not call it a full-fledged ide right yeah it's not full-fledged but right so so uh again there are a lot of things uh which we i cannot disclose so we are uh we are planning to build a few more additions which i am sure everyone in this call would love to but the unfortunate part is i cannot share it at this point of time okay uh and we have some big plans like uh so if you ask me uh i see it the vs core extension scaling up in a big way two years from now and i don't think the scalability feature uh or scalability capability will be there in explorer i think that is how i see is the biggest difference between the vs code extension which we are building and explorer which you mentioned about okay and any uh thoughts on i mean i was discussing this uh in november or january as well regarding vs code so i got some feedback regarding uh multi-factor authentication i mean it's currently not supported in vs code extension so any plans on that or is it something that we are missing up as developers hey dhruv thanks for bringing that up so i will tell you uh even the same thing i have been hearing from multiple developers i i love to interact with my users so uh so this is a feedback which i have received through my linkedin chats it has come to the service service now community uh page which we have for vs code extension and i would love to share that we prioritize this as a tough uh need of the extension and very shortly i will not disclose the date but you can make it out very shortly it will be available in vs code extension so what you have to do is uh so it will be in combination with the oauth so basically uh you in the in the oauth when you start right you have that client id and client secret you have to basically uh configure it and then uh once the mfa is enabled on your instances you can easily use it as like the way you are doing it so here at a question for the group now uh you guys uh use oauth in the extension currently i am not using it but it's like people are very various organization wants their developer environment to be you know that much compact or right but uh through what what i wanted to understand as a feedback from this group is if if anyone uh is using the mfa right at this point of time uh among the people who are already like present in the meeting can can uh can can anyone tell me uh like uh the the documentation which is available i would like to get a very honest feedback here is the uh documentation around how you can enable uh oauth for your uh for your extension vs code extension is it very useful it's not very clear i wanted a feedback around that anyone can help you with the feedback so rahul and uh istan has said no so basic is pretty clear right i mean it's very seamless yeah yeah yeah it is symbolized yeah okay so uh so what i have been trying to understand is so i got a feedback uh i think on linkedin saying that what uh the over the documentation which is currently there is not very clear for the users to understand and set this up so i actually wanted to get a pulse on that if everyone in this group feels the same uh or or it is easier uh so what i have been doing is i have like personally going and thinking that i don't know anything about what and just trying to go through the document and do it step by step uh okay honestly didn't know we had an option too okay it's not so if you go when you set this up right so first you have to set up your workspace and then you have to set up your project correct now add at that point of time uh when the authentication piece comes up right uh which kind of authentication you would like to use so along with basic you will also see the oauth yeah so i'm not sure uh when he said that maybe it is it isn't socializing uh yeah so okay i i mean by default it takes basic so i just hit enter and maybe that's why it is missed out so so that might that might be the reason because you might have used basic only right right but it gives you both the options if you want to try with some other way a fresh way of starting then i think both options will be available very correct now that it reminds me yeah yeah i do remember there was an option below that yeah cool so anyone anyone who is basically uh who has a mfa at their organization and they are not able to use the extension because of this gap uh i'm not sure with that who is using that but i had the question so i'll just have to yeah that's a good question even i wanted to talk about that through because very shortly you will have that support but what i am trying to understand is uh if if the as i mentioned the oauth documentation is it good enough or we need to improve on that so so i'm looking into it personally so uh so that is where i wanted to get some feedback which particular aspect of that documentation was not clear if if any uh no worries uh so other part i want to check was how many of you actually work only on the global files you don't have any scope application you don't have any store application you don't have packages or plugins only global files my case if you are doing source just put on the chat i mean yeah maybe maybe in the chat you can just type and then probably you can uh i i really want to talk about that so global files is something like if someone is working on itsm so he must be working on that global file right yeah good good people have started writing yeah please please whoever wants to add please go and add it so i i have got a response from edge john i've got a response from andrew i've got a response from anyone else hey guys please understand that we have to work together to improve our product right so so i would need a free candid feedback from you uh we have a response from aziz shubham has responded oh i see a lot of people now responding good hari shankar has responded okay let's start so so so when you start maybe maybe any one of you can maybe take me through that slow or just i'll try to understand more around that so when you work on global how do you work currently so i can start properly so uh i mean personally i i use the vs code editor for my personal instance i'm just playing around with it because it's very new to me but officially at my workplace i use the servicenow platform i mean i go into individual client scripts or business rules or anything that i want to manipulate i do it on the platform directly okay but uh to be honest with vs code from this meeting while we were explaining i realized that we could download global files current work on it so i just tested it and i think that works better for me so i'll probably start trying it out and then moving to my uh kind of socialize this with my fellow developers sure sure as well so that's something new to me as well so i i would like each one of you to be ambassador for me and go and talk to your fellow developers at as instant mention and talk to them about benefits of using this extension so uh just one thing over here uh should it uh and you're saying the approach that even i follow like create an update set to work on the requirement and then just migrate that update set sure uh so andrew i would like to understand from you so if if there is a case where you do not have uh so right now the the limitations or constraint i would say of the extension is you need to have a scope application store or a stored application or a packager plugin to work on the global files so without that it is difficult so so i mean if i have to if i ask you to break up your work how much of that is only around the global files hey um andrew here uh i probably do like maybe 50 or 60 of my work is global um the other problem that i have like i i certainly downloaded the vs code when it was announced back last year and i've tested it but i've never actually implemented it as a part of my work um because i find what i do is flow designer integrations and like things that are not just a business rule or a client script or like a single piece of code i will jump through the platform i'll be doing things here and there and there and there and the the workflow that i found in the vs code extension wasn't sort of conducive for doing a lot of little different things to get a job done like if you're creating a catalog item you start you have to make an item you make all the variables that's not something you can do from an ide yeah sure um okay uh then my next question would be probably uh what is not working well if someone using the vs code extension what changes uh the one point i have already mentioned is support for mfa apart from that what else do you guys think that should be there in extension which is not there which will help you to use the extension more in your day-to-day work i guess for me if i could create an update set in global scope and then download a particular say script include or file that i'm working on make the changes save it in that global update set and have it update back to um the platform and like i said i haven't tried that myself in the the application since it was released so it may have been one of the updates that i've missed like if i get someone that calls up and says oh this particular thing isn't working and i know that's part of a script include if i could fix that in vs code that would be good by creating the update setting global updating the script include publishing that back to the platform and testing it there so i know this is possible like again uh the precondition will be if you have a scope or a store application in vs4 extension this is very much possible right now okay cool so i'll have to give that a go please please do try and let me know if it works for you or not the only use case which i am like trying to discuss or i am i am trying to get a feedback is where users do not have any scoped application or a stored application then the vs code extension usability becomes a challenge so i am looking for that kind of user who only works on the global files i mean global files uh if you see it as this thing right so it's now it's a no code or local code platform so we have to get into the platform it's like we on vs code we can work on those files that we know that this particular business rule is working for this then we can update that right but since we have to go in the platform and search then it's like and as an additional step if i'm going on vs code right okay so what i was thinking through is if someone is like uh has a use case where we don't have any scope or a stored application right you only work on a on say the global files as we are discussing yesterday about the itsm and the discovery apps right so in that case of scenario i was just thinking how we can basically enable the vs code extension for that kind of use cases also so you don't have to basically go and create project but you can directly go into the file search and then use to search for the specific files you want to work on make those changes and then sync it back to the platform using update sets in that case uh is it possible i'm not sure whether it's possible or not yeah that is what we are evaluating right now so i was looking for like uh tell me so i'll tell you how i go in the platform suppose if i'm working on change management okay so there is any action getting performed and i see that you know this is possible through br only or through client script only okay so i go on that thing suppose i go on the business rule i will first filter based on the table down on condition or based on script so is it possible if uh to search brs or script include client script based on the table not the script includes but the business rule that on which table they are running or conditions if i can search when searching the global files based on the table name not on the br name or based on the condition not on the br name okay i think that would be a good thing to have because we wouldn't really remember the names of the stuff that we've written so we used to do i also usually use the tables and then filter out what i need to see got it so you are looking for searching business tool and script include based on the table right not the script includes but business rules client script because crypt includes are not based on the table right okay client scripts okay i will take this as a feedback uh and then see what best can be done okay it can be like uh the way we do like suppose uh incident we want to search for anything so we will go for incident dot config okay so it will give us a list of everything whether it's a flow business rule anything so if that functionality we can have like we select a table we'll see all the configuration files for that table uh we are also and from there we can select boss this things like i need to work on this i will download it and work on it okay okay sure taking this feedback and and we will evaluate what best can be done here uh any any more feedback uh which you want that extension should have which is right now not there and will help you in your day-to-day work yes i have one query yeah yeah is it possible that multiple developers can update the one script include in the different functions uh multiple developers updating script include this again i think that is where the challenge is like uh like on the platform also you are talking about debit scale or collaboration which is owned by another team so so our charter basically uh doesn't include that and that is what i was telling through also so uh the way i see it is basically you have to talk to the other developers offline and then then sync your work yeah so in that case you get the one feedback you can take like in the spn or the tfs we have a feature like the uh checked in or checked out so that picture will help uh rather to connect to offline or the developer will know that uh this file has been checked in uh we need to that's that can be included yeah got it sure so it is kind of a version control i see right yeah virgin control yeah sure so in other platforms it's like uh if i am working on a file so it is locked for me as long as i am not updating it other person won't be able to download it right right right right that's kind of thing yeah i got it uh yeah the thing is that in the platform itself it will show that uh like group is updating so right right right very difficult in the vs code right right say that the group is updating something in the script yeah we we have plans around version control on the platform let's see how we can like marry both these things together okay great so anything else any feedback for the ps4 extension so i just want to know about a bit more about that short instance thing short instance you are right right so i haven't checked it what's what's in the last so it's basically so uh so through uh this is like how it will work you don't have to type the full url you just start with the say the the servicenow.com part doesn't need to be typed in by the user it will be automatically picked up by the extension okay and is it like if sometimes i type it and sometimes i don't type it it will automatically detect or is it like a kind of a restriction that i just need to type on the instance name no no it is entirely up to you if if you type the the specific part it will automatically take the rest the servicenow.com part or if you want you can type the full one also it is like making the life of your users easy that you don't have to remember all the urls of your instances okay okay okay is there more not any more questions around the vs code extension i would like to use the rest nine minutes for any feedback if okay first of all i i also own the script editor and the debugger script debugger on the platform so any specific feedbacks around that also i would love to hear from you guys i guess we should plan another session okay i i would love to have a session on debugger also okay yeah so in the last meetup we have discussed a few points in the description right right so so let me tell you there is a very good thing which we are planning uh in the debugger so so i will not talk more uh but that's a very exciting thing i think every one of you will love that so so i think that is what i was looking for some the feedbacks actually help us build better products right so that is what i wanted to understand if there are any specific feedbacks around the debuggers editor i would surely look into those um i've got something about the the script debugger in the paris release there's the um the console correct um when i heard about that i was excited um and then i upgraded my pdi recently and i was testing it and i noticed it doesn't actually start the console until you are into an active debug session i was really hoping that opening the debugger even if you're not in an active session would give you an interactive console sort of like your chrome console so you could essentially get not get rid of but use it instead of the explore dialogue to test your scripts in a background script sort of situation without needing to run a script to get at it okay uh okay i think uh yeah as you mentioned you need a active debugging session andrew the reason uh we have developed in that that fashion is because uh background scripts are not supported in this console this only purely for the server side scripts which you basically run in through your debugger right and that is the way it is intended to be but when you said that you i mean when you say that without a debugging session you want the console what specific use case would be only for the background scripts right essentially i guess yeah like testing server-side code on the fly okay uh i i think i'll take this as a feedback and let's see what or how we can do it uh so background scripts i think internally is owned by some other team i have to find that but yeah i will take this feedback yeah i guess if you're using the vs code extension you can do those background scripts on the fly a bit easier um but yeah like i'd really hoped that you could have a console and you could declare variables and then call those variables similar to the chrome developer console yeah sure um the other thing i had if nobody else does i've used some virtual agent and flow designer and noticed that the script editors in those different applications have different features to the script editors for background scripts and client scripts and other platform things is there going to be an upgrade to bring everything to parity uh just a minute i'm just taking a note on you sure so what's the difference in that i mean i might have missed that um so i found out sort of by mistake that in flow designer script editor you can actually hold down i think command on mac and add cursors to basically you know click on three or four lines and then type the same thing in four four different places um but you can't do that in platform script editor so that uh oh that multiple update multiple replays kind of thing that we use in other editors call it uh so uh andrew the feedback was that the behavior of various script editors are different on the platform right you give example for the flow designer you give an example from virtual reason uh editor and the editor on the platform right uh yeah i think that's a very valid point uh yeah that multiple update feature if we get that on extension that would be i guess it would be there right that is a yeah that's their app okay the multiple selection thing right yeah okay got it yeah i think i've also noticed that um the intellisense kind of auto complete works better in yeah flow designer and virtual agent script blocks than it does in the platform once okay sure if that's the case i mean that features are different i mean it might be a possibility that those scripted editors are different is it possible or is it like the same script field it looks the same and as far as i'm concerned as a developer like i would expect that if it's a script editor in platform it behaves the same no matter where you are yeah thanks and i think these are some very good feedbacks no worries do we have any more questions over here anyone if that's the case then so after the call i'll trigger one email that will have all the links as well as this presentation that uh shujit has given and i'll upload the recording of this session so i'll upload provide that link as well so in case you have missed or if any of your friends have missed that and you can share and i was to share that 25 voucher with the person who refers the most part i guess that won't work because the person who were there they even they haven't joined so i give you this opportunity so you feel that who has given the best feedback or this question that will you can give it to him that's a difficult role to play every day i'm saving my side man yeah i'm putting me in trouble i i think uh with the kind of feedbacks coming in from andrew i think i out pick andrew find them and you have won a voucher or 25 dollars awesome thank you yeah one more thing is uh for the for the users on in this call who are already there and using vs code extension please do write a review on on the vs code marketplace based on your experience what are your liking what you are not liking uh we would love to hear from you guys yeah man share that link i'll just put on those links as well in the email itself so that they have a direct link okay okay all these three links right uh let me just uh okay let me do one thing through uh let me put this in the chat it will it be helpful yeah that's fine i'll copy it from here or you can just what's up that to me we'll just have a look yeah sure i think i will whatsapp you okay okay fine thank you guys thank you everyone for the feedbacks loved uh doing this session maybe maybe next time group we can have a session for our debugging editor yeah man but next time we are planning with no no no no maybe some time in 2020 okay so uh i'll tell you delhi meetup is coming most probably next week or next to next week okay so we can it's also going to be virtual so we can take that up there as well i'll send the link for delhi meetups yeah okay it doesn't matter whether i am presenting or not but i will be joining that for sure okay you have to present man i i'm i'll talk with god of that you know giving that catch you later you