Test & Publish Workflows

Nected allows you to test workflows in a staging environment before deploying them to production. This helps to ensure that your rules are working as expected. To test a rule, click the Test in Staging button.

Testing a Workflow

Testing a workflow is pretty straightforward, just click on the Test in Staging button and it will take you to the test result tab. However, before testing a workflow, make sure that:

1. You've given proper input data to all added Nodes.

2. All added Nodes are tested.

In the "Test Result" tab, you'll get to see something like this:

1. Steps: This column is for showing the particular node. You can check if the node has been correctly executed from the ✅ mark at the right side of the node name.

2. Input: In the input column all the input attributes for that particular node are given.

3. Result: The result tab is the same as shown in the rule result window. Here is the execution result along with its Output(in JSON format) and Action name and status(if all conditions are met).

Always test every node and the overall workflow, before Publishing your workflow.

Publish a Workflow

The publishing flow for workflows involves a structured process to ensure changes are properly documented, reviewed, and versioned. Here are the detailed steps:

The workflow starts in a draft state. You can make any necessary edits to ensure it meets your requirements. Once you've done with the editing, you now can do two things:

1. Submit it for Review: If you're working in a team, and there is a reviewer, then you can assign the reviewer and submit the workflow in review. Then it will go into the review flow, which you can read from Approval Flow.
2. Publish your workflow: If you don't want to review your workflow by an approver, then you can also directly publish your workflow in production. Here is how you can do that:

   

   • When you are ready to publish, click the "Publish" button.

   • Title and Description: A prompt will appear asking for a title and description of the changes. This information helps maintain a clear version history.

   • Confirm Publishing: After providing the title and description, click the publish button to move the workflow to production. The workflow is now published and it will create a new published version that you can access from the Publish tab of the Version Control section. This version is live in the production environment.

How to roll back to a previous version?

Now, let's say you've 2 Published versions and while working on the 3rd version i.e. editing the 2nd version, if you get anything and you want to revert to the previous version, then you need to roll back to the previous version. You can see all the past published versions from the Published tab of the Version Control section. If you need to revert to a previous version after making some edits:

• Navigate to Version Control: Go to the Version Control section in the workflow editor.

• Select Published Tab: Click on the Published tab to view all published versions.

• Preview Previous Version: Identify the previous version (e.g., Version 1) and click the Preview button to review its contents.

• Rollback Action: Click the Rollback button. This action replaces the current draft with the content from Version 1, making it the new draft version ready for further edits or publishing.

For more details about Rolling back to a previous version, read the Version Control doc.

By following these detailed steps, users can effectively manage the publishing and rollback processes for their rules and workflows, ensuring high-quality and reliable outputs.

To make a Workflow in Production, You must test all the nodes separately or run "Test in Staging", otherwise the Workflow won't be published.