<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>Application Scripting on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/application-scripting/</link>
    <description>Recent content in Application Scripting on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Jan 2019 08:17:19 -0500</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/application-scripting/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Updating Applications with Fix Scripts</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/training-fixscripts/</link>
      <pubDate>Tue, 29 Jan 2019 08:17:19 -0500</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/training-fixscripts/</guid>
      <description>We are experimenting with new training content delivery methods. This tutorial blog post is one of those experiments. We are very interested in your feedback. Please let us know what you think about this format and the content in the comments below.
 Introduction Fix Scripts, like any other script type on the Now Platform, have a purpose to serve. Fix scripts run server-side JavaScript to make changes required by an application that cannot be captured as an application file.</description>
    </item>
    
  </channel>
</rss>