Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform App Engine
Table of Contents
Choose your release version
    Home London Application Development Now Platform App Engine Application tools Automated Test Framework Automated Test Framework reference Administration Step configurations Step execution scripts

    Step execution scripts

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Step execution scripts

    In a step configuration record, the step execution script field determines what a step with this configuration does when it runs.

    Step inputs

    The input variables to a step are determined by the inputs related list in the step configuration record. The inputs parameter to executeScript() gives the script access to these variables. For example, if the inputs related list contains two records, var1 and var2, the script can reference var1 with the expression inputs.var1 and can reference var2 with inputs.var2.

    Step outputs

    The output variables to a step are determined by the outputs related list in the step configuration record. The outputs parameter to executeScript() gives the script access to these variables. For example, if the outputs related list contains two records, out1 and out2, the script can reference out1 with the expression outputs.out1 and can reference out2 with outputs.out2.

    Step result

    The stepResult parameter provides access to an API that controls whether the step passes or fails. It also determines the message the step writes to the log.

    The method stepResult.setSuccess() causes the step to succeed. The method stepResult.setFailed() causes the step to fail.

    The method stepResult.setOutputMessage() sets the message to write to the log when the step succeeds or fails. It takes one parameter: the string to write to the log. If the script calls stepResult.setOutputMessage() more than once, the most recent value set overwrites any previous value.

    Example: Record Query step execution script

        (function executeStep(inputs, outputs, stepResult) {
             if (gs.nil(inputs.table)) {
                stepResult.setOutputMessage(gs.getMessage("The '{0}' input variable was not specified",
                   'table'));
             stepResult.setFailed();
              return;
        }
        var query = new GlideRecord(inputs.table);
        query.addEncodedQuery(inputs.field_values);
        query.query();
        if (!query.next()) {
             stepResult.setOutputMessage(gs.getMessage("No records matching query:\n{0}",
                 inputs.field_values));
              stepResult.setFailed();
        } else {
             stepResult.setSuccess();
             outputs.table = inputs.table;
             outputs.first_record = query.getUniqueValue();
             stepResult.setOutputMessage(gs.getMessage("Found {0} {1} records matching query:\n{2}",
                                                      [query.getRowCount(),
                                                       inputs.table,
                                                       inputs.field_values]));
        }
        }(inputs, outputs, stepResult));
        
       

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Step execution scripts

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Step execution scripts

      In a step configuration record, the step execution script field determines what a step with this configuration does when it runs.

      Step inputs

      The input variables to a step are determined by the inputs related list in the step configuration record. The inputs parameter to executeScript() gives the script access to these variables. For example, if the inputs related list contains two records, var1 and var2, the script can reference var1 with the expression inputs.var1 and can reference var2 with inputs.var2.

      Step outputs

      The output variables to a step are determined by the outputs related list in the step configuration record. The outputs parameter to executeScript() gives the script access to these variables. For example, if the outputs related list contains two records, out1 and out2, the script can reference out1 with the expression outputs.out1 and can reference out2 with outputs.out2.

      Step result

      The stepResult parameter provides access to an API that controls whether the step passes or fails. It also determines the message the step writes to the log.

      The method stepResult.setSuccess() causes the step to succeed. The method stepResult.setFailed() causes the step to fail.

      The method stepResult.setOutputMessage() sets the message to write to the log when the step succeeds or fails. It takes one parameter: the string to write to the log. If the script calls stepResult.setOutputMessage() more than once, the most recent value set overwrites any previous value.

      Example: Record Query step execution script

          (function executeStep(inputs, outputs, stepResult) {
               if (gs.nil(inputs.table)) {
                  stepResult.setOutputMessage(gs.getMessage("The '{0}' input variable was not specified",
                     'table'));
               stepResult.setFailed();
                return;
          }
          var query = new GlideRecord(inputs.table);
          query.addEncodedQuery(inputs.field_values);
          query.query();
          if (!query.next()) {
               stepResult.setOutputMessage(gs.getMessage("No records matching query:\n{0}",
                   inputs.field_values));
                stepResult.setFailed();
          } else {
               stepResult.setSuccess();
               outputs.table = inputs.table;
               outputs.first_record = query.getUniqueValue();
               stepResult.setOutputMessage(gs.getMessage("Found {0} {1} records matching query:\n{2}",
                                                        [query.getRowCount(),
                                                         inputs.table,
                                                         inputs.field_values]));
          }
          }(inputs, outputs, stepResult));
          
         

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login