More and more development tasks require work across application scopes. Scoped flows leveraging global subfows and global scripted APIs called from scoped scripts are just two of the most common examples. There are many valid architectural reasons for splitting concerns across multiple scopes, it's just that flicking between files to make changes concurrently is a PITA.
ServiceNow Studio has banished scope switching! When files are opened in a ServiceNow Studio tab, they can be edited regardless of the current session scope.
Developers using ServiceNow studio will never see this banner again!
There's not much more to add. The file scope will be displayed in the bottom right corner of the screen, next to the current update set. When the current tab is changed, the scope automatically updates to indicate the scope of the file, nice!
File Scope and Update Set are displayed in the bottom right corner of the screenNext up in Day 9, we look at the Generative AI features embedded in ServiceNow Studio.
1 Comment
