Test & Publish Workflows
Last updated
Last updated
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 is pretty straightforward, just click on the Test in Staging button and it will take you to the test workflow tab. However, before testing a workflow, make sure that:
You've provided proper input data to all added nodes.
All added Nodes are tested.
In the "Test Workflow" tab after you click the "Test Now" button, you'll see something like this:
As a result of testing the workflow, you can see three columns there in the screen.
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.
Input: In the input column all the input attributes for that particular node are given.
Result: The result tab is the same as in the rule result window. Here is the execution result along with its Output and Action name and status(if all conditions are met). Inside the output tab you'll get two options: Raw and Pretty. These two are the low code and no code mode to check your output values respectively.
Always test every node and the overall workflow, before Publishing your 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:
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.
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.
For more details about version control, and 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.
Every publish creates a new version of the workflow and you can always view the last published version along with the current draft. You can now control the version of a workflow, and rollback to its previous version using our Version Control& rollback feature. You can read more about it in versioning & rollback.
