How to properly use keywords from within a plan. Read More »

Keywords are the fundamental building blocks of Plans. This section groups the documentation related to the declaration and use of Keywords Read More »

Be notified when various events occur. Read More »

Start building your automation blocks. Read More »

Controls help you design and structure your execution plans. Read More »

Define custom rules for alerting, notifications, and integrations with external systems Read More »

Executions reporting Read More »

Execution reporting (legacy) Read More »

Schedule executions reporting Read More »

Start building your automation blocks. Read More »

Variables are used throughout plans to pass information from one node to another, or to store the result of a dynamic computation. Variable types Similar to any programming language, Step supports the use of variables in Plans. The variables declared and used in a Plan are called Plan variables. A Plan variable is a container that stores a data value under a specific name. Like in classical programming languages, Step supports the following types of variables: Read More »

Subscribe to various execution events. Read More »

How to build modular plans. Read More »

Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types. Read More »

Executions housekeeping and advanced options Read More »

Executions descriptions Read More »

Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types. Read More »

Step includes a flexible mechanism for sending notifications in tandem with the definition of Alerting Rules, allowing to define exactly which events and conditions will result in which notification being sent, with what data. Read More »

Define custom rules for alerting, notifications, and integrations with external systems Read More »

Advanced execution options Read More »

View and analyse created incidents based on your alerting rules Read More »

Plan objects are containers for your automation logic. They’re implemented as a tree of nodes which can be of different types. Read More »

. Read More »

Sshedules view description Read More »

Performance dashboard for visual analytics Read More »

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 view description Read More »

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 »

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 Preferences description Read More »

Restore previous versions of entities Read More »

Create bookmarks to easily reach frequently used pages Read More »

Contains documentation for Step libraries. Read More »