https://step.dev/knowledgebase/31/categories/data-management/ Recent content in Data Management on Step Documentation Hugo -- gohugo.io en Wed, 25 Sep 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/setup/configuration/timeseries-settings/ Wed, 25 Sep 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/setup/configuration/timeseries-settings/ How Time Series Works Step has its own implementation of time series, designed to efficiently manage and visualize large datasets over extended periods. This feature powers data visualization in the Performance tab of the execution view and the Analytics view. By grouping data into collections with different resolutions, the system optimizes both storage and retrieval for short-term and long-term analysis, ensuring high performance and resource efficiency. By default, Step uses several collections with varying resolutions to store data: https://step.dev/knowledgebase/31/setup/installation/binaries/dbinstall/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/setup/installation/binaries/dbinstall/ MongoDB This page contains information on installing and configuring MongoDB to be used with Step. Supported version We do support MongoDB version starting from 4.0.x up to 5.0.x. Installation Follow instructions at : MongoDB documentation Configuration If you want to tune your MongoDB instance, you will find all necessary information on the official website at : MongoDB configuration and maintenance. Activate authentication (optional) For activating the authentication between the controller and the MongoDB server, the following actions have to be taken: https://step.dev/knowledgebase/31/userdocs/plans/plans-variables/ Thu, 23 May 2019 07:00:01 +0100 https://step.dev/knowledgebase/31/userdocs/plans/plans-variables/ 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: https://step.dev/knowledgebase/31/userdocs/executions/execution-housekeeping/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/execution-housekeeping/ If Automatic housekeeping is ON, you may want to flag the executions to be retained by the housekeeping job. To do that, toggle the Retain this execution and provide the information about your execution in the Description textbox - for example, information about a referenced execution that’s part of an overall test release. On the other hand, if you don’t want to retain this specific execution, you may directly delete it within the same pane: https://step.dev/knowledgebase/31/admindocs/maintenance/backup/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/admindocs/maintenance/backup/ Data Model Step data are organized as collections into MongoDB. Each collection contains a specific type of data, which are explained below. Collections marked (EE) only exist in the Enterprise Edition, and a collection may only be created once the corresponding feature is used for the first time. Automation plans : the Plan definitions functions : the Keyword definitions parameters : the Parameters plansversions, functionsversions, parametersversions (EE) : the version history of Plans, Keywords and Parameters automationPackages : the deployed Automation Packages resources : the files uploaded or deployed in Step (Automation Package archives, libraries, datasets, attachments etc…) resourceRevisions : the revisions of these files tasks : the Scheduler tasks Executions and reporting https://step.dev/knowledgebase/31/admindocs/maintenance/housekeeping/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/admindocs/maintenance/housekeeping/ Automatic housekeeping Automatic housekeeping is provided as part of a standard Enterprise package only. As a Community user, please refer to the manual purge guide. Main concept Automatic Housekeeping allows the controller to automatically delete executions based on a configurable Time To Live (TTL) value, which defines the maximum retention period. This reduces manual maintenance, ensures consistent cleanup of related data, and prevents the accumulation of orphaned entities in the system. https://step.dev/knowledgebase/31/userdocs/parameters/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/parameters/ Parameters are centrally defined variables that can be accessed by both Keywords and Plans in Step. They offer several key capabilities: Scope Assignment: Parameters can be assigned to specific scopes, restricting their visibility and access to certain applications or keywords. Protection of Sensitive Parameters: Sensitive parameters can be protected to hide their values from users, ensuring secure handling of critical data. Activation Expressions: Parameters can be dynamically assigned or mapped to specific environments, users, or other conditions using activation expressions. https://step.dev/knowledgebase/31/userdocs/import-export-entities/ Fri, 02 Oct 2020 08:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/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. https://step.dev/knowledgebase/31/admindocs/projectmanagement/ Thu, 05 Dec 2019 14:25:01 +0100 https://step.dev/knowledgebase/31/admindocs/projectmanagement/ Multitenancy and project management helps isolating and managing assets (such as Plans, Keywords, Executions, etc) throughout the application. The main benefits of working with projects is the ability to serve multiple tenants and/or group of users with a single instance of Step facilitating the organization of your work and improving security. Except for administrators, user must be assigned to at least one project to be able to work with step. https://step.dev/knowledgebase/31/userdocs/versioning/ Sun, 29 Nov 2020 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/versioning/ Versioning is a feature to restore a previous version of an entity in Step Enterprise. This can be helpful to undo unintended changes or to revert a breaking change. How versioning works in Step Versioning is currently supported for the following entities: Plan Parameter Step automatically saves changes to these entities, aggregated to 1-minute intervals. This aggregation ensures, that a lot of small changes within a minute will only show as one change in the version history.