<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Keywords on Step Documentation</title>
    <link>https://step.dev/knowledgebase/31/userdocs/keywords/</link>
    <description>Recent content in Keywords on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 28 Feb 2019 14:08:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/31/userdocs/keywords/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deployment of Keywords</title>
      <link>https://step.dev/knowledgebase/31/userdocs/keywords/keywords-deployment/</link>
      <pubDate>Mon, 19 Jun 2023 00:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/keywords/keywords-deployment/</guid>
      <description>You can add and manage Keywords by manual registration or automatically using Automation Packages.
Adding a new Keyword by manual registration In order to use your Keywords with Step, you need to register them. This can be done through the web interface or the Java API.
Generic fields From the Keyword collection window, use the + button to open the following New keyword dialog. The dialog is a visial editor that lets you fill in generic and type specific information for your Keyword.</description>
    </item>
    
    <item>
      <title>Keyword Configuration</title>
      <link>https://step.dev/knowledgebase/31/userdocs/keywords/configuring-keywords/</link>
      <pubDate>Sun, 18 Jun 2023 00:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/keywords/configuring-keywords/</guid>
      <description>Step offers holistic business use cases that lets business and technical users reuse different automation components. To enhance interaction quality and prevent input mismatches, users can specify mandatory information required to execute a specific Keyword.
Schema Optional and mandatory input keys can be specified in the form of a JSON schema tied to the Keyword. Schema can be provided manually as part of the Keyword&amp;rsquo;s generic fields or automatically populated based on the &amp;ldquo;schema&amp;rdquo; attribute of the Keyword annotation in Java and .</description>
    </item>
    
    <item>
      <title>Prebuilt Keyword Libraries</title>
      <link>https://step.dev/knowledgebase/31/userdocs/keywords/prebuilt-keyword-libraries/</link>
      <pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/keywords/prebuilt-keyword-libraries/</guid>
      <description>Step ships a small set of officially-maintained, ready-to-use keyword libraries. This page lists them, and explains where they come from and how to use them. For where these libraries fit among the other Keyword types, see the Keywords overview.
Where they are published The official prebuilt libraries are published as Maven artifacts under the group ch.exense.step.library on mvnrepository.com/artifact/ch.exense.step.library.
All libraries are released together and share the same version number.
Library Use it for Key Keywords Artifact ID system Running OS commands, scripts, or existing external tools/projects from a Plan — the general-purpose escape hatch when no dedicated plugin exists (see Generic command execution).</description>
    </item>
    
  </channel>
</rss>
