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?
Orlando IntegrationHub Changes The Orlando release has been in Early Availability for weeks and GA is right around the corner. I previously covered the Flow Designer changes in Orlando and in this post I will do the same for IntegrationHub. Dynamic Outputs New York introduced Dynamic Inputs and now with Orlando we have Dynamic Outputs. These allow developers to define the data structure of a complex object programmatically and then use that as the output of an action.
It is ServiceNow’s new release season! With the Orlando release in Early Access, we will show some enhancements targeted around being more effective and efficient as a developer. These tools are specifically for developers and scripting on the Now Platform. Script Include Dependency A new contextual menu has appeared for your script includes. You might already be familiar with the open definition when using the contextual menu on a script include.
Orlando Flow Designer Changes The Orlando release, as with every release since the original introduction, features a number of new features and improvements in Flow Designer and IntegrationHub. In this post I will look at Flow Designer specifically with a future post covering InterationHub. Create a flow with an SLA Task trigger In Orlando there is a new trigger type SLA Task and new actions that work with SLAs. This allows for SLA based logic to be written and maintaqined in flows.
The first part of the platform I will be highlighting for the Orlando release is the Automated Test Framework(ATF). The reason I choose ATF first is the relationship between upgrading and testing. Automated testing helps accelerate validation after deployments and upgrades to the instance. Check out the overview page for ATF changes for Orlando. Testing Agent Workspace Forms With the addition of the Now Experience and Agent Workspace, which is the first part of the platform leveraging the Now Experience, automated testing was not initially available.
Orlando is Released!! It is that time of the year, new release Early Availability(EA) time. Each EA period is a flurry of activity in the Developer Program. Blogs, Videos, Demos, Slide decks Oh MY! I am always delighted to share and highlight what is new for developers. Below you will find some of those highlights for developers in Orlando. Over the next month or so, you can expect a steady release of deeper dives into the details.