for creating the new alias, your host is your pdi instance and your username & pass are admin & password. It doesn't seem to work. Am I missing anything? It's not working for me
Hi! I'm developing a custom component using UI framework. I tried to use more OOTB Now component, after I downloaded via npm and imported in my project all of them ran to error(now-button, now-dropdown, now-tab) and my project crashed. The now-button used to work a month ago, but now it doesn't. Is it possible there is some problem with all now components or npm? (I upgraded my dev instance to washington 2 weeks ago from vancouver). Thanks for reply:)
The changes he showed in the video aren't captured in the update set but you can see all incoming changes in 'Versions' related list pointed to sys_upgrade_history (that means each new update is treated as upgrade in the system). For source control and deployment of changes from one instance to another, he has done that using github in the part-2.
![[NOW-SDK walkthrough pt. 2] Linking the ServiceNow SDK to a source control like GitHub](http://i.ytimg.com/vi/PUcDQU-rsng/mqdefault.jpg)
![[NOW-SDK walkthrough pt. 2] Linking the ServiceNow SDK to a source control like GitHub](/img/tr.png)
for creating the new alias, your host is your pdi instance and your username & pass are admin & password. It doesn't seem to work. Am I missing anything? It's not working for me
Hi! I'm developing a custom component using UI framework. I tried to use more OOTB Now component, after I downloaded via npm and imported in my project all of them ran to error(now-button, now-dropdown, now-tab) and my project crashed. The now-button used to work a month ago, but now it doesn't. Is it possible there is some problem with all now components or npm? (I upgraded my dev instance to washington 2 weeks ago from vancouver). Thanks for reply:)
I'm curious how this works with update sets. Seems useful.
The changes he showed in the video aren't captured in the update set but you can see all incoming changes in 'Versions' related list pointed to sys_upgrade_history (that means each new update is treated as upgrade in the system). For source control and deployment of changes from one instance to another, he has done that using github in the part-2.
Nice to know but it's a little painful to create an app by this way. 😅