We are past the half-way point on Hacktoberfest and wanted to highlight the amazing progress so far! If you haven’t participated yet, you still have time! Check out our Hacktoberfest 2021 post to get started. Remember to claim your prize! If you already have participated and have made your four qualifying pull requests, don’t forget to go to DigitalOcean to claim your rewards! HAHAHUGOSHORTCODE-0xc00144b400-1-HBHB HAHAHUGOSHORTCODE-0xc00144b400-2-HBHB Pull Requests Hacktoberfest completion is measured in “Pull requests” approved and merged so let’s take a look at that first:
Have you built something really cool on ServiceNow? Solved an interesting problem? Have a great story to share with your peers? We want you to come speak at CreatorCon 2022, the conference for architects and developers of all skill levels! CreatorCon Call for Content We welcome submissions from everyone in the community, regardless of how long you’ve been in the ecosystem or whether you’ve spoken at a conference before. Developers want to learn from other developers, so this is your chance to give back to the community by sharing your experience.
It’s that time of year again! Every year we encourage ServiceNow Developers to participate in DigitalOcean’s Hacktoberfest event by contributing to a ServiceNow project or repository. Why participate? The more the community is equipped, the more that community can contribute. The more you get used to source-controlled projects, the more you can contribute to any number of open-source projects. You get a free t-shirt (the t-shirt also comes with bragging rights)!
In this post, we will provide a walk through on how to create your first and basic playbook in ServiceNow. If you saw Live Coding Happy Hour on August 19, 2021 (part 1) or September 2, 2021 (part 2), this post will go through the same material. Playbooks provide step-by-step guidance for resolving processes and enable agents to easily manage the lifecycle of cases by guiding them through sequences of tasks.
Let’s keep the Rome Release feature highlights going! Instance Scan, introduced in Quebec, was a great addition to the platform that allowed us to check our instances for issues or deviations from best practices. It is a great tool to use to maintain a high level of standard while doing development, performing releases, and during upgrades. Before Rome Instance Scanning was either manual (you executed a scan suite yourself) or scheduled.
Hey everyone! Here is a quick post about a new feature coming in Rome that will help everyone avoid licensing issues in Flow Designer. Before Rome, users working in Flow Designer may create an entire flow with custom actions and realize later that they were not licensed for some of the actions used. Starting in Rome, while in Flow Designer, if an action or subflow in your flow of if a step in your action utilizes functionality that your instance is not licensed for, a polite warning message will appear:
Rome is upon us! Today we are going to look at what is changing in Flow Designer. Be sure to check out the Rome Release Resources post to see what else is coming in Rome and how to upgrade your PDI. Check out the release notes for Flow Designer here and all of Rome’s release notes here. Performance Especially on large flows (as in, flows that have more than 100 actions), you will see loading times in Rome that are four times faster than in Quebec!
Earl Joins the Developer Advocate Team!!! About me I am Earl Duque and I am incredibly excited to be the newest Developer Advocate to join ServiceNow’s Developer Program I have a slightly different background than the Developer Advocates before me in that I have only been in the ServiceNow space since 2017. My career first started within Student Affairs and Contract Management before I jumped over to IT and started in a university service/help desk.