Very Helpful. My issue is in preview it's not displaying the image copied in any subfolder, my .md file in the root, I have tried dot double-dot slash combinations but no use. However it displays the images copied to the root. Where as this works when you drag drop from the subfolder into .md file holding shift (in Mac).
@Allenovation5 ай бұрын
Great information! Short and sweet! Thank you!
@servicenowcm57407 ай бұрын
Great Demo of App Generator
@Allenovation7 ай бұрын
Great video! I really like all the supporting content that really helped drive this message home!
@starlordnow7 ай бұрын
Thank you!
@LindaKirkpatrick8 ай бұрын
STARLORD, the hat...priceless. This is great content! Thanks for the overview.
@shaoservicenow8 ай бұрын
This is so awesome let’s go STARLORD!!!
@robertfulton15768 ай бұрын
So excited for GenAI App Creation on the ServiceNow platform. Thanks Starlord for making this easy!
@vivekoo70010 ай бұрын
This is excellent work and demonstration
@mkselders11 ай бұрын
Forgot how amazing you are at explaining ServiceNow concepts; amazing video!
@starlordnow9 ай бұрын
Wow, thanks!
@Plainjanejj11 ай бұрын
Awesome video!
@kenbridgeman8590 Жыл бұрын
Awesome video man. Love your energy.
@starlordnow11 ай бұрын
Awesome! Thank you!
@vickyyilmaz3396 Жыл бұрын
Very useful! Thank you Dale
@arumugamofcl Жыл бұрын
Hi Dale, I have one follow-up question, please advise If we move the OOTB to a global app and make the customization to it, How to use the actual OOTB for other departments without any changes? I got the below from your ServiceNow article. How to do this? ONE MORE THING: This is my personal implementation preference so take it with a grain of salt -> If you are deploying a Global app for the first time (Ex. Incident Management), consider creating a new scope for all of your changes to the app instead of making all changes in the Global scope. Consider calling the new scope something like "My Company's Incident Management". This will allow you to utilize Source Control and App Repo right out of the gate and pretty much avoid the need to promote Update Sets all together. This will also keep your Incident Management (or other) app basically untouched out of box. This makes your upgrades easier. You then have have an untouched app that you can use to extend for other departments all over again if needed. Or you can extend your new "My Company's Incident Management" app into new apps so they get your customizations. The sky is the limit!
@starlordnow11 ай бұрын
I agree with putting everything in a scope if starting new. Excellent idea! The goal here was for instances where the admins have been doing everything in Global, but want to start leveraging Source Control and/or App Repo. The files are still accessible from any scope as they are technically still in Global.
@pradhnyajangam3522 Жыл бұрын
Does selecting subscription while installing app via app repo makes any licence issue?
@starlordnow11 ай бұрын
Not really. Subscription Management is a tool for you to keep track of your license usage. It is similar to using a spreadsheet, but much better. You can be out of compliance by not keeping track of it in Subscription Management or by not configuring Subscription Management correctly. You can also use Subscription Management correctly and still be out of compliance. It is just for your own internal tracking.
@roshimahanta Жыл бұрын
Thanks for explaining the Stashing concept so nicely. It indeed helps!
@mayankbhatkar44872 жыл бұрын
How can we create Survey in app repository? I don't see the survey option there
@earlymaine2 жыл бұрын
Great video. I've been struggling with how to get away from Update Sets for a while and this was a great explanation and demo of this concept. Totally unrelated question, though... What are you using to include the environment name and color difference your browser tabs? I'm using a Chrome extension (can't remember the name off the top of my head) but it puts a banner across a corner of the page and can be intrusive. I really like the look of yours and would love to know how it's done :)
@AS-dj7vx2 жыл бұрын
that looks like a tab-group feature in Microsoft-Edge browser (also Chromium-based, so easy to switch to it)
@earlymaine2 жыл бұрын
@@AS-dj7vx Thanks. I wasn't aware of this feature.
@Plainjanejj2 жыл бұрын
Love the regular uploads! It’s cool to see a consistent channel that focuses on Servicenow!
@digdrewzter2 жыл бұрын
Is this showing that Tokyo now has the App Engine Studio and Studio merged, or are they still separate, and Source Control/Stashing etc can only happen in Studio?
@starlordnow2 жыл бұрын
They are two separate IDEs for editing Scoped Apps. If you set up Source Control for your app in one, it should be reflected in the other. I prefer to do most of my work in AES these days and fall back to Studio only when I need to implement something that is not available in AES. This video is focused on using Studio and App Repo which are Platform features available to anyone with a ServiceNow instance. AES is a premium product only available with an App Engine subscription which I cover in other videos.
@digdrewzter2 жыл бұрын
does this mean that "Deployment Requests" are a thing of the past?
@starlordnow2 жыл бұрын
Deployment Requests were introduced with App Engine Management Center in San Diego and are not going anywhere anytime soon. I would *highly* recommend using AEMC as the method for promoting apps rather than using App Repo directly. However, not everyone is licensed for App Engine. For those customers, using App Repo is 100% fine as it is a Platform feature everyone has access to. App Repo is also the underlying mechanism that AEMC uses to promote apps. See "Managing deployments using AEMC" -> docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/task/manage-deployments.html
@Plainjanejj2 жыл бұрын
Love the enthusiasm in your voice about Servicenow! These videos are edited really well too.
@starlordnow2 жыл бұрын
Thanks!
@Motorcyclemelee2 жыл бұрын
Thanks for producing this lighthearted, but informative video! What happens when Sydney finishes her next sprint and has some updates that are ready promotion to test but some updates that need to stay in dev? Is there a way to ensure only those updates that are ready for promotion get to test, UAT and production, while those she still needs to work on before they are promoted don't get promoted? If she publishes the app to the repo, won't all updates made to the scoped app get installed / updated?
@starlordnow2 жыл бұрын
This is where utilizing Source Control becomes very helpful. Here's some (very) high-level steps for that scenario: - Sydney's app is Linked to Source Control - She creates a BR called "Not ready yet" and another BR called "Ready to deploy". - When she commits her changes to Source Control, she unchecks the box for the BR "Not ready yet". This will commit only the BR "Ready to deploy" to Source Control. - Next, she goes to "Source Control" -> "Stash Local Changes" and stashes the BR "Not ready yet". Stashing changes is sort of like "cutting" them from the app and putting them in a temporary location to re-apply later. - Now she can Publish her app to the App Repo without the BR "Not ready yet". - After Publishing to App Repo, she goes to "Manage Stashes" and re-applies the Stash that has her BR "Not ready to deploy" in it so that she can continue working on it.
@Plainjanejj2 жыл бұрын
The best ServiceNow youtube channel around!
@starlordnow2 жыл бұрын
Thanks!!
@robertthedukefedoruk56072 жыл бұрын
Was so happy to see more of your work show up in my timeline.