• Documentation
  • Tutorials
  • Blogs
  • Product

What's on this Page

  • Java Keyword API
    • Major release 1.3.0 since Step 27.0
    • Minor release 1.2.8 since Step 26.0
    • Minor release 1.2.7 since Step 25.3
    • Minor release 1.2.6 since Step 25.2
    • Minor release 1.2.5 since Step 25.0
    • Major release 1.2.0 since Step 22.0
  • DotNet Keyword API
    • Minor release 1.2.4 since Step 24.1
  • Step
  • Whats new
  • Release notes of the Step keyword API
Categories: RELEASE
This article references one of our previous releases, click here to go to our latest version instead.

Release notes of the Step keyword API

The Keyword API is maintained and versioned independently from the Step platform. This page outlines the release history of the Keyword API. Each entry specifies the corresponding Step version in which the respective Keyword API version was introduced. Unless stated otherwise, the API is designed to be backward compatible, allowing older API versions to function seamlessly with newer Step versions.

Java Keyword API

Major release 1.3.0 since Step 27.0

New features

  • New Keyword proxy to invoke keywords within Keywords. This enables creating complex plan directly in Java
  • New helper methods to easily retrieved variable from either inputs and properties

Minor release 1.2.8 since Step 26.0

This is a technical release with no functional changes

Minor release 1.2.7 since Step 25.3

New features

  • Support collections in keyword inputs

Minor release 1.2.6 since Step 25.2

New features

  • Support maps in keyword inputs

Minor release 1.2.5 since Step 25.0

Bug fixing

  • An exception is thrown when using an optional default input value
  • Session should support AutoCloseable objects in addition to Closeable ones

Major release 1.2.0 since Step 22.0

New features

  • New ‘Input’ annotation available to specify the keyword inputs and the related schema as Java function parameters
    • Enabling the support for arrays and nested objects containing simple types (number, string, boolean)
    • You can pass such values from the plan editor with JSON syntax, i.e. for arrays [ 1, 2, 3] and for object {“prop1”: “value1”}
  • Enable the definition of composite keywords as code
  • Support composite keyword in keyword packages

DotNet Keyword API

Minor release 1.2.4 since Step 24.1

New features

  • Support DotNet 8

See Also

  • Step Automation Package UI
  • Agent provisioning
  • Automation as Code
  • Step CLI
  • Bookmarks
  • Home
  • Whats new?
    • Release notes
    • Roadmap
    • Release notes Helm Chart
    • Release notes Step keyword API
    • News
  • Set up
  • Administration
  • SaaS guide
  • User guide
  • Developer guide
  • DevOps
  • Plugins
  • Libraries
Step Logo
    • Documentation
    • Tutorials
    • Blogs
    • Product
    • Home
    • Whats new?
      • Release notes
      • Roadmap
      • Release notes Helm Chart
      • Release notes Step keyword API
      • News
    • Set up
    • Administration
    • SaaS guide
    • User guide
    • Developer guide
    • DevOps
    • Plugins
    • Libraries