https://platform-docs.slingr.io/dev-reference/flows/steps/Recent content in Steps onHugo -- gohugo.ioenMon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/categories/Mon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/categories/Definition # Steps are predefined components that serve specific functionalities. They are used in a flow to create code in a more graphical way, eliminating the need to learn any specific coding language. Instead, you simply need to drag and drop steps from the steps palette onto the canvas area and then connect them by dragging a connector from a source step to a target step. Steps are categorized, and documentation for each step can be found on the following pages.https://platform-docs.slingr.io/dev-reference/flows/steps/system-steps/Mon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/system-steps/Start step # General Info # Category Description Rules System Initiates the flow. - A single start step is mandatory. Inputs # No configuration required. Outputs # No configuration required. Sample # The flow begins with the logger step, which logs a message, and concludes with the end step. End step # General Info # Category Description Rules System Marks the end of the flow. Optional, and can return a result.https://platform-docs.slingr.io/dev-reference/flows/steps/control-steps/Mon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/control-steps/List iterator # General info # Category Description Control The List Iterator is a control flow statement designed for iterating through items within a collection, such as result sets or multiple fields. This step facilitates the inclusion of other steps within it. The behavior of this step encapsulates the behavior of the nested steps, enabling structured traversal of the collection. Inputs # Label Type Required Visibility Description Iterable list resultSet / field(many) yes Always The list of elements to be traversed.https://platform-docs.slingr.io/dev-reference/flows/steps/data-steps/Mon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/data-steps/Create record # General info # Category Description Data This step generates a new record instance within the database. Inputs # Label Type Required Visibility Description Entity entity yes Always Entity to create a new record instance. Data dataBody yes Always Data to be used to create record. Outputs # Name Type Description createRecord record Create record instance. Sample # The flow begins, and the "create record" step generates a new record.https://platform-docs.slingr.io/dev-reference/flows/steps/ui-steps/Mon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/ui-steps/Download file # General info # Category Description UI Performs a download of the specified file. Inputs # Label Type Required Visibility Description File ID text yes Always The ID of the file to download. Outputs # No configuration required. Sample # The flow begins, and the "download file" step downloads the specified file. If an error occurs during the file download, the error will be logged, and the execution will be terminated.https://platform-docs.slingr.io/dev-reference/flows/steps/library-steps/Mon, 16 Nov 2020 13:59:39 +0100https://platform-docs.slingr.io/dev-reference/flows/steps/library-steps/Definition categories # Description # Flow Steps Libraries empower you to define your custom steps and seamlessly integrate them into your workflows. It’s imperative to specify inputs, outputs, and the script that a step will execute. Once defined, this library becomes a reusable asset accessible across various parts of your application. Category # In contrast to predefined steps, you have the flexibility to configure the category of your step library.