Test & Publish Rules
Nected allows you to test rules 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 button.
Testing scenarios
Nected supports a variety of testing scenarios, including:
Testing with different values for the input parameters.
Testing with null values for the input parameters.
Testing with optional input parameters.
Now, If a rule has nullable input parameters, you can test the rule with null values for those parameters. If a rule has optional input parameters, you can test the rule with and without those parameters.
Testing example
To test a rule with different values for the input parameters:
Click the Test in Staging button.
In the Test Rule dialog box, enter different values for the input parameters.
Click the Test Now button.
After the test is completed, it generates a JSON code as the output.
If you see the success message (which you've given while adding data) in the code, that means your rule is ready to publish. If you see the failure message, that means your rule is not ready to publish.
Significance of testing
Testing is important to ensure that your rules are working as expected. By testing your rules in a staging environment before deploying them to production, you can prevent errors and ensure that your rules are not causing any unintended consequences.
Testing is mandatory to do on each edit before publishing to make sure that rule is behaving as expected and without errors.
Final Step: Publish the Rule
Once you are confident in the rule's functionality, publish it. This action makes the rule available for use within your Nected environment.
Last updated
