Thanks a lot for this awesome demonstration of so many principles in just one show. I had to atop and rewind the video at certain stages again and again to catch all the details shown here. That is very helpful stuff. Well done!!!
Very interesting lesson, its really hard to understand this new concept for those people who just was working with servicenow and ES5. Appreciated, want more videos about nXu
I love this as a person who works with React. The syntax seems very similar and it looks like they used some techniques from Redux as well, think this will have a very promising future.
I wish I stayed on my Angular 2+ training course now all those years ago instead of learning just AngularJS 🙂 This reminds me of that a lot what with the CLI, I did find it exciting but much steeper learning curve. Definitely the right way forward for ServiceNow though.
thanks for mentioning my channel! head on over to barely functional dev for resources to help learn many of the basic programming fundamentals you will need to understand when writing your component code
Great episode! The debounce call on the actionHandler for user input was pretty awesome to showcase (~40:45), I didn't know about it before this demo, would have to write timeout and cancel logic otherwise.
Plugins refer to ServiceNow developed functionality that is added on to the base platform (like Multi Provider Single Sign on.) Some plugins are activated automatically when the instance is provisioned, some at upgrade, and some require licenses. Components refers to the OOB and third party UI pieces to build in the Now Experience framework.
At this point the components are available for Workspace. More will be available in future releases (post-Paris). Information on getting started can be found on the developer site. developer.servicenow.com/dev.do#!/reference/now-experience/orlando/cli/getting-started Thanks.
I reckon phase 1 is Agent Workspace only and then eventually portal in a few years, then the portal will still be there for a while after. That's my take on it anyway otherwise it is a HUGE change for their customers
Short answer - no. Service Portal is not going away. Just like legacy workflow, it will still be in the platform for maintenance purposes. We suggest a migration strategy so customers are using the supported method going forward. In this case, components.
Thanks a lot for this awesome demonstration of so many principles in just one show.
I had to atop and rewind the video at certain stages again and again to catch all the details shown here.
That is very helpful stuff.
Well done!!!
You're welcome. Thanks for watching.
Very interesting lesson, its really hard to understand this new concept for those people who just was working with servicenow and ES5. Appreciated, want more videos about nXu
I love this as a person who works with React. The syntax seems very similar and it looks like they used some techniques from Redux as well, think this will have a very promising future.
I wish I stayed on my Angular 2+ training course now all those years ago instead of learning just AngularJS 🙂 This reminds me of that a lot what with the CLI, I did find it exciting but much steeper learning curve. Definitely the right way forward for ServiceNow though.
thanks for mentioning my channel! head on over to barely functional dev for resources to help learn many of the basic programming fundamentals you will need to understand when writing your component code
Great episode! The debounce call on the actionHandler for user input was pretty awesome to showcase (~40:45), I didn't know about it before this demo, would have to write timeout and cancel logic otherwise.
is there a code repo anywhere for this? would be useful to have it for some of the styles
Can't we just use React in a NOW UI component? :) Would be cool if the NOW ClI could bundle the React code too.
What is the JS framework used for Web Component building in this video? I mean which programming language was used like React JS or some other one?
I believe that is explained in the video. It is our own framework based on web components. We specifically did NOT tie it to reduce technical debt.
What is the different between component and plugins ? Can custom plugins be developed?
Plugins refer to ServiceNow developed functionality that is added on to the base platform (like Multi Provider Single Sign on.) Some plugins are activated automatically when the instance is provisioned, some at upgrade, and some require licenses. Components refers to the OOB and third party UI pieces to build in the Now Experience framework.
2 years later and still no proper documentation on the ui framework...
Hi Guys, can this be deployed in portal and other places in the platform. And is there any docs on cli installation please. Thanks
At this point the components are available for Workspace. More will be available in future releases (post-Paris). Information on getting started can be found on the developer site. developer.servicenow.com/dev.do#!/reference/now-experience/orlando/cli/getting-started Thanks.
Crazy Stuff
how to create a project sir
So Service Portal is going away?
I reckon phase 1 is Agent Workspace only and then eventually portal in a few years, then the portal will still be there for a while after. That's my take on it anyway otherwise it is a HUGE change for their customers
Short answer - no. Service Portal is not going away. Just like legacy workflow, it will still be in the platform for maintenance purposes. We suggest a migration strategy so customers are using the supported method going forward. In this case, components.
Was there an answer to the question regarding doing React within a component. ~41:57
I'm still waiting on an answer. I pinged Wolf on it yesterday. I'll post something when he gets back to me (if he doesn't post directly.)
I don't think SN wants devs to use React. They could have used React instead of building a new UI Framework that's similar to React.