What’s a keyword?
Conceptually speaking, Keywords can be seen as the reflection of a piece of business logic which a human (or a process) would otherwise perform. At the technical level, a Keyword is represented by a code package (or script), which performs a specific action on a target system. Upon execution, information can be passed to the Keyword dynamically as an input, as well as extracted from the subject of the automation and returned as an output.
When using and leveraging the Keyword API at industrial scale, many benefits arise, such as out-of-the-box scalability via the distribution of Keyword executions, execution traceability, reporting and a strong basis to base and organize automation code upon.
First, click the Keywords tab in step’s web application, and then click the New Keyword button
A template is provided at creation time, which we’ll use as a basis for our new keyword.
Let’s just add the following line of code to our template and modify the output in order to return the value of a date dynamically:
Your script should look something like this:
What’s a plan?
Plans are the implementation of an automation scenario, described in the form of a tree. They can represent any sort of automation asset, ranging from a test case, to load scenario, an RPA routine, or even a monitoring probe. They usually combine the execution of Keywords with various control structures. Once a Plan has started, execution ensues and keywords are distributed on the available agents.
Let’s now click the Plans tab and create a new plan by clicking on the New plan button.
Let’s name our plan and click the Save and edit button, which will take us to the plan editor.
We’ll search for our newly created keyword in the keyword library on the right side of the screen and add it to our plan.
An instance of the keyword’s call should now appear in your plan’s tree.
Let’s now execute our plan by clicking the play icon twice.
As you can see, the corresponding script was executed and the current date is provided as an output.
We now encourage you now to move on to a more complex scenario such as Selenium-based browser automation and also to take a look at our plan library and the rest of our documentation pages to get a better sense of all the possibilities offered by keywords and plans.