Keywords
Keywords objects are containers for your automation logic. They’re implemented as a tree of nodes which can be different types.
Read More »
Keywords calls
How to properly use keywords from within a plan.
Read More »
Deployment
Start building your automation blocks.
Read More »
Controls
Controls help you design and structure your execution plans.
Read More »
Reporting
Executions reporting
Read More »
Configuration
Start building your automation blocks.
Read More »
Plan modularity
How to build modular plans.
Read More »
Plans
Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types.
Read More »
Archiving
Executions housekeeping and advanced options
Read More »
Executions
Executions descriptions
Read More »
Visual Plan editor
Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types.
Read More »
Advanced executions
Advanced execution options
Read More »
Alerting rules
Define custom rules for alerting, notifications, and integrations with external systems
Read More »
Incidents
View and analyse created incidents based on your alerting rules
Read More »
Notifications
Be notified as soon as an execution fails or completes.
Read More »
Plain text plans
Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types.
Read More »
Analytics (beta)
Performance dashboard for visual analytics (beta)
Read More »
Schedules
Sshedules view description
Read More »
Analytics
Performance dashboard for visual analytics
Read More »
Java Plan API
Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types.
Read More »
Monitoring
Monitoring view description
Read More »
Automation Packages
An Automation Package (formally called Executable Bundle) is a self-contained set of Plans and their related entities (Keywords, Parameters and Resources) that can be executed on a Step controller.
Supported formats: Automation Packages currently support Java as software platform. The format of an Automation Package for Java is a compiled jar containing Plans and their related entities as Java classes or resources. Additional software platforms like .NET might be supported in future releases.
Read More »
Event Broker Monitor
If you’ve purchased the Async package or are running the Premium Enterprise version of Step, you’ll be able to monitor in real time what’s happening in the EventBroker by navigating to the EventBrokerMonitor view:
The Stats tab provides global statistics on the broker, such as the current amount of messages present in it and the high mark (or water mark), oldest & youngest events, etc.
The next two tabs provide users with the ability to browse and search for events, and organizes the query results either by Id or Group.
Read More »
Import/Export entities
You may export the following entities:
Plans Keywords Parameters The functionalities are similar for all supported types of entities.
Export Export a single entity Export can be performed from the related table views using the actions buttons. For plans, single entity can also be exported from the Plan editor, click on the export button as shown in the following screenshot:
Export all entities of one type Step also lets you export all entities of one type.
Read More »
User account
User Preferences description
Read More »
Versioning
Restore previous versions of entities
Read More »
Libraries
Contains documentation for Step libraries.
Read More »