Manage component

Design a component

Components are developed in the Designer in the same way as applications. A component must have an end step.

Define component input

Input to the component is defined in the start step of the component by specifying parameters with FlowScript, a name and data type.

Define component output

Output from a component is defined in the end step by selecting from a list of available variables.

Commit a component

A component needs to be committed before it can be used in an application. Click on the Commit button in the top right corner and enter a commit message.

Use a component in an application

Components are displayed at the bottom of the Steps panel in the Designer interface. To incorporate a component into your application, simply drag and drop it from the panel onto the application canvas. Once placed, establish connections between the component and other steps within the application using sequence arrows, following the same procedure as with other steps.

Configure the component by assigning a target variable, which will store the output generated by the component. If the component requires input variables, these are specified using FlowScript.

In this example, the Get User Defaults component requires AppOwner and RunAs, for which we assign values to variables with the same name within our application.

Component dependencies

When a component (or other asset) is used in an application it will always use the latest committed version of the component when it's running in Development environment.

When the application is committed, the version of the component will be fixed, ensuring it remains unaffected by subsequent changes to later versions of the component.

When deploying an application version, it will include the precise component version that was in use at the time of the commit.