<?xml version="1.0" encoding="UTF-8"?><!--
- Licensed Materials - Property of IBM Corp.
- IBM UrbanCode Build
- IBM UrbanCode Deploy
- IBM UrbanCode Release
- IBM AnthillPro
- (c) Copyright IBM Corporation 2002, 2016. All Rights Reserved.
-
- U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by
- GSA ADP Schedule Contract with IBM Corp.
--><pluginInfo>
  <!--

  **author name IS required**

  The Author Section is used to give credit to the author of the plugin.
  Name is the only required element/attribute, but feel free to also include your email,
  website  or bio to allow users of your plugin to praise your work, ask questions
  or share their use case to help grow your plugin's functionality.
  -->

  <author name="UrbanCode">
    <organization>UrbanCode</organization>
    <email>info@urbancode.com</email>
    <website>http://urbancode.com</website>
    <bio/>
  </author>

  <!--

  **intergration type IS Required**

  The integration type section identifies where the plugin fits into the process
  excepted types are SCM, Build, Artifact, Automation, Deploy

  For example:

  The plugin pulls Artifacts from an artifact repository during deployment
  the Type would be "Artifact"
  or
  The plugin deploys to a middleware server
  the Type would be "Deploy"
  -->

  <integration type="automation"/>

  <!--
  **source is NOT required**

  The source section identifies the location of the plugin source code
  For example
  https://github.com/...
  -->
  <!--
  <source url=""/>
  -->
  <!--
  **license type is NOT required**

  If your plugin uses any licensed software please acknowledge it by
  listing the license type below
  -->
  <!--
  <licenses>
    <license type=""/>
  </licenses>
  -->
  <!--
  **tool-description IS required**

  The tool-description section is used to summarize the software
  the plugin was created to integrate with.

  For example:
  Apache Ant is a software tool to automate software processes during the build or
  deployment of an application. Ant uses an propitiatory XML file to define build
  and/or deployment steps(referred to as targets by ant) . The Ant executable is
  called to execute the targets in the build.xml.
  -->

  <tool-description>ServiceNow integrates ITIL v3 processes, social collaboration for IT departments, software-as-a-service delivery, and modern Web functionality to deliver a flexible, easy-to-use and self-managing application.</tool-description>

  <!--
  **related-info is NOT required**

  The releated-info section is used to define links which may be useful to users of the plugin
  but don't fall into the release-notes or tool-description section.

  For example: releated-info can be links to pdf documentation, help videos related to plugin setup or the product's
  website.

  excepted values for type include: PDF, WEBSITE, VIDEO
  -->

  <related-info>
    <link description="For more information on ServiceNow" title="ServiceNow Community homepage " type="WEBSITE" url="http://community.service-now.com/"/>
  </related-info>

  <!--
  **meta-html in NOT required**

  The meta-html section is used define the meta description and the meta keywords of the plugin page.The meta
  description tag allows you to influence the description of your page in the web crawlers that support the
  tag The meta keywords tag allows   you to provide additional text for crawler-based search engines to index
  along with your body copy.

  If multiple keywords are used they must be comma(,) delimited
  -->

  <meta-html>
    <meta content="" name="description"/>
    <meta content="" name="keywords"/>
  </meta-html>

  <!-- Do not change the release-version, the build process injects it. -->
  <release-version>18.902605</release-version>

  <release-notes>
    <!--
      **release-note IS required**

      The plugin-version name must match the plugin version found in the plugin.xml file

      The release-note should document the changes, improvements, or bug fixes introduced
      with the new plugin version

      The release-note may contain text or reference a file in the plugin zip package

      For example your release note could be:
      Support for was added for version 10.0 for software X
      or
      releaseNotes/release1.html (where release1.html contains html formatted version information)
      -->
    <release-note plugin-version="7">
      Add proxy server configuration, CMDB steps.
    </release-note>
    <release-note plugin-version="8">
      Converted plugin to use ServiceNow REST API
    </release-note>
    <release-note plugin-version="9">
      Added support for ServiceNow REST API in versions Eureka and Fuji
    </release-note>
    <release-note plugin-version="10">
      Added more support for ServiceNow REST API in versions Eureka and Fuji
      Removed newAPI button. Automatically determines API version.
    </release-note>
    <release-note plugin-version="11">
      Fixed functionality bug for delete and insert steps.
      Removed automatically  API selection.
      Fixed potential bug when interacting with Eureka instances.
    </release-note>
    <release-note plugin-version="12">
      Updated libraries.
    </release-note>
    <release-note plugin-version="13">
          Plug-in now supports full record CRUD and Query operations.
            New Steps:
              - Update Records
              - Check Records
              - Update Records
              - Query Records
            Updated Steps:
              - Delete Records
              - Create Records
    </release-note>
    <release-note plugin-version="14">
      Rename steps.
    </release-note>
    <release-note plugin-version="15">
Support property file encryption.
    </release-note>
    <release-note plugin-version="16">
Improved error logging and various bug fixes.
    </release-note>
    <release-note plugin-version="17">
Fixed bug when checking for fields and value equality in Check Records step.
    </release-note>
    <release-note plugin-version="18">
Added Check Change Request Fields step.
    </release-note>
  </release-notes>

</pluginInfo>