Framework
If you are building Now Experience UI Framework Components, you will probably need your components to interact with the ServiceNow database. To do that from a component, you’ll need to use the Http Effect API. This post will walk through using the Http effect to consume the REST Table API to display the number and short description from the latest incident in a ServiceNow PDI. It may not be the most practical use case, but the goal is to show an easy way to interact with ServiceNow data from a component.
We have spent some time recently, through both blogs and Live Coding Happy Hour, diving into the Now Experience UI Framework launched in the Orlando release. Since we may not be coming back to that subject on the show for a little while I’m going to do a quick recap on what we’ve learned so far through the three episodes we’ve done on Now Experience Components and share some helpful resources.
If you are trying to build your first component on a personal developer instance(PDI), you will run into some issues. ServiceNow is aware of the problems, and we will have them fixed up for you. In the meantime, here are the workarounds.
Component Building for PDIs The company code for PDIs are numbered, and web components can’t start with numbers. The now-cli automatically inserts your scope name into the component name, thus causing the issue.
It has been a pleasure writing blogs on the platform features we believe developers want to know about and their changes during the Early Access period of the Orlando Release. I hope you have found them to be useful and relevant to you as a developer. The Developer Blog will continue to seek out topics for technical deep dives as we exit the release season.
One more thing! Wait, we can’t go just yet, you say?
