Awesome content, thanks so much! It makes so much more sense from a dev point of view how to work with SNOW. One little suggestion: please turn the background music a bit down or even consider removing it altogether. What you say doesn't need any background noise, since it's awesome in its own right.
I've been dying for some info on this that's easy for a smooth-brain like me to understand. THANK YOU Can you do this for non-scoped app stuff as well?
Hi Robert, thank you for watching and for the feedback! I'm only aware of this working at the scoped application level. And that's the part that took me a while to wrap my head around as I wasn't accustomed to thinking "let me create an application for this thing I want to do in ServiceNow." There are cases like I ran into yesterday where I was making a change to the Microsoft SharePoint Spoke application (connection aliases are within that application scope). If I was to move that between instances I would have no choice (that I'm aware of) but to use an update set or export/import XML records. But my flow that uses the SharePoint Spoke could be in its own application scope and therefore could be managed with source control.
Thanks for this video. Instead of merging the new idea branch back into the master branch, could you pull the new idea branch down to the "production" instance?
Hi qwertymontreal and thank you for the question! Unfortunately you can't do what I showed here in production and I neglected to highlight that in my video. So what you see here with source control is for non-production instances. In that use case, YES you can pull the new branch down - absolutely! For production, you would need to "publish" the app in order to use it. Here's a link to documentation on things you can/should do in production: docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/concept/tips-production-deployment.html Hope this is helpful and thank you for watching!
Hi Justin, As always thanks for another great video. Quick question - do you know if this works for the day to day work that we do on the Global apps or is it only for Scoped apps?
hi thanks for the great video. You explained how you can capture 'flow designer' . and commit it to github . How would i go about . just backing up the PDI with just mid server on it. and also i have the header color ? non of that you can see on studio
Hey Alex! Thanks for watching and leaving this comment! It just so happens that I released another video touching on this subject this past Monday. Here's a link: th-cam.com/video/-cbu20wWEFk/w-d-xo.html Also, in that video I reference a ServiceNow dev article about backing up your PDI. Here's that link: th-cam.com/video/-cbu20wWEFk/w-d-xo.html That last link is pretty thorough with options on how to backup like you're asking. And my video shows how you can leverage that MID server to do some backup automation so you're not having to fuss with commits or downloading update sets all the time. I hope this is helpful!
Hi Zaturn - thank you for watching and leaving this question! As far as I know there's not way to do this for ServiceNow applications or Global. Those are still managed using update sets like they always have been. I guess in theory you could export those to source control but there's nothing integrated like you see in this video. I do think there are changes coming in future releases, however, so stay tuned to ServiceNow and this channel as I will certainly be posting here when there are enhancements to these capabilities!
This is great. Just one doubt, let's say I have a system property whose value depends on different instances. Now if I use SCM, it will copy the same value when remote changes are applied in other instances. Is there a way we can manage/manipulate the values of such records based on instance? In Update Set, i would usually edit it in XML and then retrieve it.
Hi Sushant - thank you for watching! That's an interesting and thought-provoking question. I've done the edit XML in Notepad++ workaround myself but I can't think of a parallel for your repo pulls. My brain is working on it! This system property, even though it's different for each instance, does it stay the same in the instance?
@@JustinMeadows yeah... I mean let's say the property is similar to glide.servlet.url which is simply your specific instance URL... Or it could be domain of your third party app API whose values will be dev url for dev instance/ stage for stage instance... The values stays constant in respective instance...!
Hi Stephen - thank you for watching! So long as you have permission to open and edit the existing application in Studio or App Engine Studio, you should be able to link it to source control like I show in this video. When you do that initial "link/connect" to source control, it uploads everything in the app. What I think is happening behind the scenes is that the contents of your update sets related to that application are getting synced/copied but I haven't tested to verify my suspicion.
If I don’t use the branch and let’s suppose I want to do any new thing in my master branch only. So after doing that and committing the change , so in the GitHub do I get a notification like we had saying a branch has Been added like we have updates for the master branch and then we pull it and see it on our other instance?? Like how does it happen then if we don’t create a separate branch?
Hi Rohit - thanks for watching! You would see it in the other instance and you have a choice whether or not to pull down/sync the changes. So if you were just staying in master/main and didn't want the updates in a particular instance, you would just never sync them (they won't update/sync automatically).
Hi David - thank you for watching! Unfortunately no this won't work for changes made in global scope. The repo integration is at the application level currently.
Hey there! Thanks for leaving a comment! That's the beauty of using source control in this way... It is the precaution that will preserve your custom applications outside the instance. My PDI, for example, could be reset completely but my app will stay safe and can be added to my new PDI.
Awesome content, thanks so much! It makes so much more sense from a dev point of view how to work with SNOW. One little suggestion: please turn the background music a bit down or even consider removing it altogether. What you say doesn't need any background noise, since it's awesome in its own right.
Thank you so much for the feedback! I'm doing lots of experimenting so this is great; I will definitely play around with both those ideas!
Great work!!! I wanted to start using it, now I know how!!!
I've been dying for some info on this that's easy for a smooth-brain like me to understand. THANK YOU
Can you do this for non-scoped app stuff as well?
Hi Robert, thank you for watching and for the feedback! I'm only aware of this working at the scoped application level. And that's the part that took me a while to wrap my head around as I wasn't accustomed to thinking "let me create an application for this thing I want to do in ServiceNow." There are cases like I ran into yesterday where I was making a change to the Microsoft SharePoint Spoke application (connection aliases are within that application scope). If I was to move that between instances I would have no choice (that I'm aware of) but to use an update set or export/import XML records. But my flow that uses the SharePoint Spoke could be in its own application scope and therefore could be managed with source control.
Thanks for this video. Instead of merging the new idea branch back into the master branch, could you pull the new idea branch down to the "production" instance?
Hi qwertymontreal and thank you for the question! Unfortunately you can't do what I showed here in production and I neglected to highlight that in my video. So what you see here with source control is for non-production instances. In that use case, YES you can pull the new branch down - absolutely! For production, you would need to "publish" the app in order to use it. Here's a link to documentation on things you can/should do in production: docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/concept/tips-production-deployment.html Hope this is helpful and thank you for watching!
Hi Justin, As always thanks for another great video. Quick question - do you know if this works for the day to day work that we do on the Global apps or is it only for Scoped apps?
hi thanks for the great video. You explained how you can capture 'flow designer' . and commit it to github . How would i go about . just backing up the PDI with just mid server on it. and also i have the header color ?
non of that you can see on studio
Hey Alex! Thanks for watching and leaving this comment! It just so happens that I released another video touching on this subject this past Monday. Here's a link: th-cam.com/video/-cbu20wWEFk/w-d-xo.html
Also, in that video I reference a ServiceNow dev article about backing up your PDI. Here's that link: th-cam.com/video/-cbu20wWEFk/w-d-xo.html
That last link is pretty thorough with options on how to backup like you're asking. And my video shows how you can leverage that MID server to do some backup automation so you're not having to fuss with commits or downloading update sets all the time.
I hope this is helpful!
@@JustinMeadows great thank you for getting back to. Will have a look this video and the article
Thank you!
Thank you for watching Don!
Thanks 🙏
You’re welcome 😊
How to do this for non custom applications like Customer Service or Global applications?
Hi Zaturn - thank you for watching and leaving this question! As far as I know there's not way to do this for ServiceNow applications or Global. Those are still managed using update sets like they always have been. I guess in theory you could export those to source control but there's nothing integrated like you see in this video. I do think there are changes coming in future releases, however, so stay tuned to ServiceNow and this channel as I will certainly be posting here when there are enhancements to these capabilities!
@@JustinMeadows Very much thanks for taking time to answer my question!
This is great. Just one doubt, let's say I have a system property whose value depends on different instances. Now if I use SCM, it will copy the same value when remote changes are applied in other instances. Is there a way we can manage/manipulate the values of such records based on instance?
In Update Set, i would usually edit it in XML and then retrieve it.
Hi Sushant - thank you for watching! That's an interesting and thought-provoking question. I've done the edit XML in Notepad++ workaround myself but I can't think of a parallel for your repo pulls. My brain is working on it! This system property, even though it's different for each instance, does it stay the same in the instance?
@@JustinMeadows yeah... I mean let's say the property is similar to glide.servlet.url which is simply your specific instance URL... Or it could be domain of your third party app API whose values will be dev url for dev instance/ stage for stage instance... The values stays constant in respective instance...!
What role do you need to import into the instance? Do you need admin? Or is there a role within the app that will allow an app admin to import?
How would I push all the code from an existing application in Studio up to Github to start migrating to repository as a source control?
Hi Stephen - thank you for watching! So long as you have permission to open and edit the existing application in Studio or App Engine Studio, you should be able to link it to source control like I show in this video. When you do that initial "link/connect" to source control, it uploads everything in the app. What I think is happening behind the scenes is that the contents of your update sets related to that application are getting synced/copied but I haven't tested to verify my suspicion.
If I don’t use the branch and let’s suppose I want to do any new thing in my master branch only. So after doing that and committing the change , so in the GitHub do I get a notification like we had saying a branch has Been added like we have updates for the master branch and then we pull it and see it on our other instance?? Like how does it happen then if we don’t create a separate branch?
Hi Rohit - thanks for watching! You would see it in the other instance and you have a choice whether or not to pull down/sync the changes. So if you were just staying in master/main and didn't want the updates in a particular instance, you would just never sync them (they won't update/sync automatically).
Will this work for non-scoped apps? For example will it work with non-scoped apps at the Global level?
Hi David - thank you for watching! Unfortunately no this won't work for changes made in global scope. The repo integration is at the application level currently.
What will happen to our custom applications developed ,while instance upgrade ,what precautions to be taken for it.
Hey there! Thanks for leaving a comment! That's the beauty of using source control in this way... It is the precaution that will preserve your custom applications outside the instance. My PDI, for example, could be reset completely but my app will stay safe and can be added to my new PDI.
So it won't work for global. Interesting.
There are rumors that that might change. But for now, you're correct.
Thank you 👍
Thank you for watching aesean!