Visual Workflow Builder

overview visual workflow builder is used to create automation workflows through a visual interface without manually writing domain specific language (dsl) code add triggers and activities to the workflow canvas, configure their properties, review the generated dsl, and publish the workflow as a reusable catalog item benefits the visual workflow builder helps you create workflows without extensive dsl knowledge add and configure workflow steps through a visual interface generate dsl automatically from the workflow configuration review the generated dsl before publishing publish workflows as reusable catalog items for tenant users prerequisites before you create a workflow, make sure that you have access to bridge automation service you have the required permissions to create and publish workflows the required provider connection is available for the activities that you want to use you have the parameter values required by the selected activities access the visual workflow builder from the main menu , go to services → platform services → bridge automation → orchestration administration → visual workflow builder the workflow builder page opens visual workflow builder interface the workflow builder provides a workflow canvas and a library of available workflow components the following table describes the main interface elements interface element description workflow name displays the name of the workflow a new workflow can initially appear as untitled workflow step library contains the available triggers, control flow elements, catalogs, and activities search helps you find an item in the step library filter filters the items displayed in the step library workflow canvas provides the workspace where you add and connect workflow components publish publishes the configured workflow as a catalog item save for later saves the workflow as a draft so that you can continue editing it later the availability of library items can depend on the configured providers and connections workflow components a workflow consists of a trigger followed by one or more activities you can also add control flow elements to define conditional processing triggers a trigger defines how a workflow starts a trigger can represent a human action an event a schedule the completion of another workflow when you add a trigger, configure the applicable properties, such as name label description input parameters default values required connections add a trigger before adding an activity activities remain unavailable until the workflow contains a trigger this requirement prevents the creation of an activity that does not have a valid starting point control flow control flow elements define how a workflow proceeds based on configured conditions use these elements to add conditional routing or branching to a workflow catalogs the catalog section provides reusable catalog components when applicable catalog items are available activities an activity performs an automation operation the available activities are organized by supported channels or providers, which can include aws azure github terraform drag an activity from the step library to the workflow canvas, and then configure its required parameters create a workflow create a workflow by adding a trigger to the canvas, configuring the trigger, and then adding the required activities add and configure a trigger open workflow builder create a new workflow in the step library, expand triggers drag the required trigger to the workflow canvas enter the trigger name, label, and description configure the required input parameters and default values select the required connection, if applicable save the trigger configuration after you configure the trigger, the applicable activities become available in the step library add an activity in the step library, locate the required activity drag the activity to the workflow canvas place the activity after the trigger or the preceding workflow step configure the required activity properties select the connection that the activity uses configure the failure behavior save the activity configuration repeat these steps to add other activities or control flow elements to the workflow use meaningful names and descriptions for the workflow and its components clear names help other users understand the purpose of each step example create an aws s3 bucket workflow this example uses a human trigger and an aws activity to create an amazon s3 bucket add a human trigger in the step library, expand triggers drag the human trigger to the workflow canvas configure the trigger name, label, description, and required inputs save the trigger configuration add the aws s3 bucket activity locate the aws s3 bucket creation activity in the step library drag the activity to the workflow canvas add the activity after the human trigger configure the activity properties the following table describes the demonstrated properties property description bucket name specifies the name of the s3 bucket to create aws region specifies the aws region in which to create the bucket activity id identifies the activity within the workflow failure behavior defines the workflow behavior if the activity fails connection specifies the account in which the activity runs the selected connection determines the target account the selected aws region determines where the s3 bucket is created verify the connection and region before you publish or run the workflow an incorrect connection or region can direct the operation to an unintended account or location review the generated dsl the visual workflow builder automatically translates the visual workflow configuration into dsl use the code view to verify that the generated definition contains the expected values to review the generated dsl complete the trigger and activity configuration open the code view review the generated dsl verify that values such as the s3 bucket name and aws region match the visual configuration return to the visual view to correct any configuration, if required note you do not need to write the dsl manually when creating the workflow visually save a workflow as a draft use save for later when the workflow is not ready to publish configure the available workflow components select save for later the workflow remains in draft status so that you can continue editing it publish a workflow publish a completed workflow to make it available as a catalog item complete the workflow configuration review the generated dsl select publish enter the catalog name enter the version select a catalog type provisioning operations select an existing category enter a description complete the publish action after publishing, the workflow appears in orchestration administration with information such as catalog item type access scope category default version onboarding date publication status a successfully published workflow displays the published status and becomes available for use by other authorized users in the tenant edit a published workflow open a published catalog item to update its workflow configuration open orchestration administration locate the published catalog item open the item for editing update the workflow parameters or related configuration update the version, if required save and publish the updated item confirm the versioning requirements before updating a published workflow the meeting notes indicate that users can change versions, but they do not define the required versioning convention