We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

laurenmcman
Administrator

You Showed Up. Now Claim Your Badge.

 

Developer Passport week is officially underway, and if you're planning on tuning in, watching the streams, and leveling up on everything Australia has to offer, you've earned something for it.

 

 

Community Badge - Community - Dev Passport Australia Release Preview - Regular@3x.png

 

 

Using the comments section, answer the two questions below, and you'll receive a limited-edition Developer Passport Community badge on your profile. It's exclusive, it's time-limited, and once it's gone, it's gone for good.

 

Here's all you have to do:

 

Question 1:

 

How helpful was the Developer Passport in understanding what's coming for builders and developers in the Australia release, and how to use said enhancements? Please share any additional feedback you have about this new format for release content (i.e. product-specific livestreams with members from the team that helped create them). 

 

Question 2:

 

Which developer products would you most like to see additional content about in the weeks following the Developer Passport? Do you prefer any specific medium (e.g. blogs, videos, PDFs, etc.)?

 

 

That's it.

 

Drop your answers in the comments below and we'll take care of the rest. Your badge will show up on your Community profile within a few weeks of the deadline.

 

Speaking of the deadline, you have until March 27 to claim it. Don't leave it on the table!

139 Comments
SohamTipnis
Mega Sage

@laurenmcman,

 

Answer 1:

The Developer Passport was quite helpful in understanding what’s coming for builders and developers in the Australia release. It provided a clearer overview of the new features and enhancements, especially from a developer’s perspective. The way the information was organized made it easier to connect the updates with real use cases and think about how they could be applied in actual implementations.

The product-specific livestreams were also a nice addition. Hearing directly from the people who worked on building the features made the explanations more practical and insightful. It felt less like a generic release summary and more like a guided walkthrough of what developers should focus on.😀

 

 

Answer 2:

I would like to see additional content around Flow Designer, IntegrationHub, Virtual Agent, and ServiceNow APIs, as these are areas developers work with frequently while building and integrating solutions on the platform. More practical guidance on topics like advanced flow design, custom integrations, API usage, and extending Virtual Agent capabilities would be especially useful for developers who are trying to implement real-world use cases.

In terms of format, a combination of short technical blogs and demo-based videos would work best. Blogs are great for quick reference, step-by-step explanations, and code snippets, while videos help in visually understanding how a feature works in the platform. Occasionally, downloadable guides or PDFs that summarize key features and best practices could also be helpful as quick reference material.😊

 

sanjay02
Kilo Sage
Hey @laurenmcman really enjoyed the Developer Passport sessions—great initiative and very helpful for understanding the upcoming Australia release!

Question 1:
How well did Developer Passport help you understand what's coming in the Australia release and how to use it? Which product are you focusing on most?
 
The Developer Passport was very helpful in understanding what’s coming in the Australia release, especially from a developer’s perspective. The product-specific livestream format made it easier to connect features with real use cases rather than just reading static documentation.
Hearing directly from the teams who built the features added a lot of clarity and context, particularly around how and why certain enhancements were introduced. It also helped in identifying practical ways to apply these updates in real-world implementations.
 
One suggestion would be to provide a clear mapping between new features and existing capabilities, so developers can easily understand what has changed and how it impacts their current implementations.
 
Question 2:
How do you prefer to learn and get help when building in ServiceNow, and how can the Community better support you?
 
I would be particularly interested in seeing more content around:
 
  • Now Assist (GenAI capabilities in Virtual Agent and workflows)
  • IntegrationHub and API-based integrations
  • Flow Designer advanced use cases
  • UI Builder and Workspace customization
In terms of format, I prefer a mix of short videos and detailed blogs. Videos are great for quick understanding and demos, while blogs help with deeper learning and referencing during implementation. Step-by-step guides or real-world use case examples would be especially valuable.
 
 
 
KrishnaMohan
Tera Sage

Question 1: 

Effectiveness in Understanding Enhancements

The format is particularly helpful because it addresses the "how-to" rather than just the "what."

  • Detailed Activation: Instead of broad summaries, each session (Playbooks, Flows, Experiences, ReleaseOps, Studio & Build Agent) provides a focused environment to see the new Australia features in a live, functional setting.

  • Contextual Learning: By breaking the content into specific product days, developers can prioritize the sessions most relevant to their current stack, making the vast release notes much more digestible.

Feedback on the New Format

The shift to product-specific livestreams featuring the actual engineers and Product Managers (PMs) behind the features has several key benefits:

  • Direct Access to Expertise: Having PMs like Jason Lefever (Playbooks) or Robert Feduruk (ReleaseOps) lead the demos adds a layer of "source truth" that is often missing from standard documentation. They can explain the intent behind a feature, not just its function.

  • Real-Time Troubleshooting: The live Q&A allows for immediate clarification on edge cases or upgrade concerns, which is invaluable during the Early Availability (EA) phase.

  • Centralized Hub: Consolidating streams, blogs, and technical demos into a single "Passport Hub" on the Community site reduces the "tab fatigue" usually associated with tracking release updates across different portals.

  • Incentivized Engagement: The addition of a limited-edition Community badge for participation is a small but effective way to drive consistent attendance throughout the week.

 

Question 2 : 

1. High-Priority Developer Products for Follow-up

  • ReleaseOps & Runbook Tasks: Since ReleaseOps is the structured alternative to Update Sets, deeper content on Runbook Tasks would be helpful. Specifically, how to handle complex merges or data-driven configurations that usually fall outside the scope of a standard deployment.

  • Build Agent & Studio "Next Gen": The Passport teased that "ServiceNow Studio has entered the chat." Post-Passport content should dive into the expanded metadata type support—showing exactly which previously "un-trackable" elements can now be managed via Source Control.

  • Flow Designer (Flow Context Summary): This is a massive quality-of-life update. A technical deep dive or "Troubleshooting Workshop" focused on using these summaries to debug mid-flow failures in real-time would be a top request.

  • Now Assist & Agentic AI: As "Agentic AI" and the AI Control Tower are major pillars of the Australia release, developers need more than a demo; they need a "Build an Agent" guide that shows how to connect custom tools to the new hyperscaler integrations (AWS, Azure, GCP).

2. Preferred Mediums for Post-Passport Content

To keep the momentum going after the live streams, a mix of "reference" and "execution" formats works best:

  • "Delta" Blogs (The "What's Changed" Guide): While the release notes are thorough, short-form blogs that highlight specific deprecated methods (like the new strict read only restrictions for setValue) help prevent breaking changes during upgrades.

  • Interactive Code Snippets/GitHub Repos: For features like the new Scoped GlideDate/GlideTime methods (getDisplayValueEx), having a repository of "Copy-Pasteable" examples saves hours of trial and error.

  • Micro-Videos (The 2-Minute Drill): Instead of 60-minute streams, 2-minute "how-to" clips focused on a single UI Builder component enhancement (like the new Predicate Builder filtering) are easier to consume during a busy sprint.

  • PDF Implementation Checklists: A "Release Readiness Checklist" in a downloadable PDF remains a staple for leads who need to coordinate with their QA and Platform teams.

Bhavya11
Kilo Patron
  1. How helpful was the Developer Passport in understanding what's coming for builders and developers in the Australia release, and how to use said enhancements? Please share any additional feedback you have about this new format for release content.

     I really appreciate how you've broken the Developer Passport down into specific products. The platform is huge now, so focusing on smaller chunks makes the Australia release much easier to warp my head around. right now, i am putting almost all my energy into playbooks and flows


  2. Which developer products would you most like to see additional content about in the weeks following the Developer Passport? Do you prefer any specific medium (e.g. blogs, videos, PDFs, etc.)?

    i am big fan of learning by doing. i usually look for short 'how to' videos  and step by step guides to get moving. if i hit a wall, i head straight to the forums to see how other devs solved it.It would be great if it the community had more 'plug and play' code samples and faster turnaround  on common troubleshooting threads 

 

KasiRamanathan
Tera Contributor

Question 1:
I found the Developer Passport to be really helpful in understanding what’s coming for builders and developers in the Australia release. The format made it easier to see the practical impact of the new features instead of just reading about them in release notes. Having product-specific livestreams with members of the teams who actually built the features was especially valuable, because they were able to explain the reasoning behind the changes and show how the enhancements can be used in real scenarios.

Compared to traditional documentation alone, this format felt more engaging and easier to follow. It helped me quickly grasp what’s new and where those updates might fit into my development workflow. One suggestion would be to include a bit more hands-on demonstration or walkthroughs of real use cases during the sessions, as that would make it even easier for developers to adopt the features.


Question 2:
I’m particularly interested in seeing additional content around Release Ops, ServiceNow Studio, and the Build Agent. These areas are very relevant for managing development workflows and CI/CD processes effectively.

In terms of format, I would really prefer demo-based video content along with hands-on scenarios. It would be great to see some real-time or slightly challenging scenarios where problems occur and are then troubleshooted step-by-step. That kind of practical walkthrough helps developers not only understand the tools better but also learn how to handle issues that might come up in real projects.

Along with videos, short supporting guides or blog posts explaining the scenario and setup would also be helpful for reference while practicing.

Jyothi_VR_2026
Tera Explorer

Answer 1:

At the moment, I am focusing mostly on AI Agents and Agent Studio, Workflow Data Fabric with Zero-Copy Data Integration, and AI Control Tower governance capabilities.

 

Answer 2:

I prefer hands-on labs, real implementation examples, and short technical walkthroughs. The Community can further help by sharing architecture patterns, practical use cases, and quick demos of new features. Peer discussions and solution threads from experienced practitioners are especially valuable when solving real-world platform challenges.

ChristianDE
Tera Contributor

Question 1:

 

Well done Advocates. I really like the passport format. Being able to get bite sized feature reviews with access to the product expert is great. Having access to the release documents and PDI upgrades early is all good, but getting to see the key features explained by experts and then try them yourself in your PDI really helps too. Also having the option to then reply them while you test them is a plus.

 

 

Question 2:

 

With a lot of talks about AI, AI Agents and Agentic workflow, I think there is should be bit more focus on those items as well. A lot of the features are around how and where AI Agents can now be embedded with some details on how to configure them to e.g. work in playbooks, but I would like to see more about AIAS enhancements and standard shipped AI agents / NowAssist skills as I know that lists grows with every release as well.

 

In terms or format, I think the passport format would be great for that with maybe some hands-on exercises to be supplied after that can be used in PDI's or other instances, as PDI's don't usually have all the AI features enabled.

Abhishek_Pandey
Mega Sage

Question 1:

How helpful was the Developer Passport in understanding what's coming for builders and developers in the Australia release, and how to use said enhancements? Please share any additional feedback you have about this new format for release content (i.e. product-specific livestreams with members from the team that helped create them). 

 

: The new initiative is very helpful & provide better insight into new and  updated features. Like the approach and agenda with direct updated from product managers. 

Question 2:

Which developer products would you most like to see additional content about in the weeks following the Developer Passport? Do you prefer any specific medium (e.g. blogs, videos, PDFs, etc.)?
: All are amazing and following up on update though particularly interested in &  looking forward to follow up on following product updates and walkthrough

  • Flow
  • ReleaseOps

 

kmbeck2
Tera Contributor

Q1

Answer: 

What I liked most about the format was that it felt more engaging and easier to follow than traditional release content. The product-specific livestreams helped break things down into more focused areas, which made it easier to identify what might actually apply to day-to-day work. I also appreciated when the presenters explained not just what is new, but why it matters and where it could be used in real environments, even when my developer journey began within the last year.

 

Q2

Answer:

My preferred format would be a mix of short videos and written blogs. Videos help see the configuration step by step, especially for developer tools and platform features. Blogs or written follow-up guides are also important because they are easier to reference later when working through a build or troubleshooting an issue. A combination of livestreams or short how-to videos would definitely come in handy. 

 

Shivalika
Mega Sage

Answer 1:

 

𝗧𝗵𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗣𝗮𝘀𝘀𝗽𝗼𝗿𝘁 𝘀𝗲𝘀𝘀𝗶𝗼𝗻𝘀 𝘄𝗲𝗿𝗲 𝗲𝘅𝘁𝗿𝗲𝗺𝗲𝗹𝘆 𝗵𝗲𝗹𝗽𝗳𝘂𝗹 𝗮𝗻𝗱 𝗲𝗻𝗴𝗮𝗴𝗶𝗻𝗴. Some of the key aspects I appreciated are:

 

  • 𝗗𝗶𝗿𝗲𝗰𝘁 𝗶𝗻𝘀𝗶𝗴𝗵𝘁 𝗳𝗿𝗼𝗺 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘁𝗲𝗮𝗺𝘀

I attended the Australia Playbooks and Flows Developer Passport sessions and found them extremely engaging. Hearing directly from the product developers and team members who actually built these features gave valuable insight.

 

  • 𝗖𝗹𝗮𝗿𝗶𝘁𝘆 𝗼𝗻 𝗻𝗲𝘄 𝗲𝗻𝗵𝗮𝗻𝗰𝗲𝗺𝗲𝗻𝘁𝘀

The sessions helped clearly explain what’s changing in the Australia release and how builders and developers can practically leverage these improvements in their implementations.

 

  • 𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝘃𝗲 𝗮𝗻𝗱 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝘃𝗲 session

I appreciated the interactive nature of the livestreams. I asked a few questions during the sessions, and it was great to see the Developer Passport team actively responding to queries from participants in real time. That level of engagement made the experience much more valuable.

 

  • 𝗩𝗶𝘀𝘂𝗮𝗹 𝗱𝗲𝗺𝗼𝗻𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻𝘀

The screenshots and walkthroughs of specific platform changes were very helpful. Seeing the UI updates and feature changes visually made it much easier to understand how those enhancements will impact day-to-day development work.

 

  • 𝗠𝘂𝗰𝗵 𝗯𝗲𝘁𝘁𝗲𝗿 𝗳𝗼𝗿𝗺𝗮𝘁 𝘁𝗵𝗮𝗻 𝗽𝗿𝗲𝘃𝗶𝗼𝘂𝘀 𝗿𝗲𝗹𝗲𝗮𝘀𝗲 𝘀𝘂𝗺𝗺𝗮𝗿𝗶𝗲𝘀

Personally, I found this format significantly more useful than the traditional two-day Rapid Wrap-Up. The product-specific livestreams allow developers to dive deeper into the areas most relevant to them.

𝗛𝗼𝗽𝗲 𝘁𝗵𝗶𝘀 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲𝘀 𝘄𝗶𝘁𝗵 𝗳𝘂𝘁𝘂𝗿𝗲 𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝘀

Overall, I thoroughly enjoyed the Developer Passport experience and would love to see this format continue with every release going forward. It provides a much richer and more practical learning experience for the developer community.

 

Answer 2:

 

𝗜𝗻 𝘁𝗵𝗲 𝘄𝗲𝗲𝗸𝘀 𝗳𝗼𝗹𝗹𝗼𝘄𝗶𝗻𝗴 𝘁𝗵𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗣𝗮𝘀𝘀𝗽𝗼𝗿𝘁, 𝘁𝗵𝗲𝗿𝗲 𝗮𝗿𝗲 𝗮 𝗳𝗲𝘄 𝘁𝗼𝗽𝗶𝗰𝘀 𝗜 𝘄𝗼𝘂𝗹𝗱 𝗹𝗼𝘃𝗲 𝘁𝗼 𝘀𝗲𝗲 𝗺𝗼𝗿𝗲 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗯𝗼𝘂𝘁:

 

𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲𝘀 𝗳𝗼𝗿 𝗔𝗜 𝗔𝗴𝗲𝗻𝘁𝘀

It would be great to see more follow-up videos or demos showing enterprise-level use cases for AI Agents across different processes. For example, practical scenarios involving ITSM , CSM processes, or HRSD process would help developers better understand how these capabilities can be applied in real implementations.

 

𝗠𝗼𝗿𝗲 𝘃𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗼𝗻 𝗜𝗧𝗢𝗠

If possible, I would truly appreciate more technical content or sessions focused on ITOM. Since ITOM plays a significant role in many enterprise environments, additional walkthroughs, architecture discussions, or real-world use cases would be extremely valuable for developers looking to deepen their knowledge in this area. (By ITOM I mean proper probes, sensors, patterns, service mapping)

 

𝗣𝗿𝗲𝗳𝗲𝗿𝗿𝗲𝗱 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗳𝗼𝗿𝗺𝗮𝘁

Demo videos and walkthrough sessions are particularly helpful for understanding new features. Pairing those with supporting blogs or documentation that summarize key points and implementation tips would make the experience even more effective.

 

@laurenmcman