Import/Export
The Import/Export feature in Nected enables users to streamline their workflow and rule management by allowing them to import and export configurations as JSON files. This functionality supports efficient rule and workflow management, backup, and transfer between environments. In this documentation we’ll cover how to access and use this feature, detailing the steps and underlying processes involved.
You can use this feature for both rules and workflow:
For rules: From the main menu, select "Rules". And then on the rule listing page, you can access the Import and Export options. Also, if you open any rule then inside the rule editor, you can again access these features.
For workflows: From the main menu, select "Workflows". And then on the workflow listing page and inside the workflow editor, you can access these features.
Exporting Rules and Workflows
To export a rule or workflow from Nected, follow these detailed steps:
Navigate to the "Rules" or "Workflows" section from the main menu.
Identify the specific rule or workflow configurations you wish to export.
Click the "Export" button. This action will open an export options popup.
Then from the popup, click on the "Export" button again, and it will simply download the rule/workflow in JSON format.
Importing Rules and Workflows
To import a rule or workflow in Nected, follow these detailed steps:
Initiate Import:
Navigate to the "Rules" or "Workflows" section from the main menu.
You can also initiate the import from inside their respective editors.
Click the "Import" button. This action will open a file selection popup.
Select JSON File:
In the file selection popup, click "Browse" to open the file explorer on your local device.
Select the JSON file that contains the rule or workflow you want to import.
Click "Open" to upload the file to the Nected platform.
Validation Process:
A validation pop-up window will appear, showing the progress of the file validation.
Nected will validate the JSON file to ensure it conforms to the required schema and integrity checks.
If the file is valid, you can simply click on "Next" to continue to the next step i.e. handling the dependencies.
If there are errors, an error message will detail the issues encountered during the validation process. These might include schema mismatches, missing required fields, or other structural issues in the JSON file.
Dependency Handling:
After the file has been imported successfully, a pop-up window will appear detailing these dependencies. According to the presence of the dependencies that the rule/workflow is using it will show you some options.
You will be prompted to handle each dependency with the following options:
Replace: This option will overwrite the existing dependency with the new one from the import file.
Use Existing: This option will retain the existing dependency and use it instead of importing a new one.
Create: This option will create a new instance of the dependency if it does not already exist.
Make your selections for each dependency. For instance:
For an existing decision table, you might choose to "Replace" or "Use Existing".
For a database connection, you might decide to "Use Existing" or "Create" a new one.
After making your selections, click "Continue" to proceed.
Completion:
Upon successful validation, the rules or workflows will be imported into the Nected platform.
The imported rules or workflows will become visible in their respective sections.
A final confirmation pop-up will display, confirming the successful import. This ensures that the imported elements are now part of your Nected environment and ready for use. Click on "Continue" again and it will redirect to the newly imported rule/workflow editor page.
These steps ensure that users can effectively import and export rules and workflows in Nected, handling dependencies and validations smoothly, and maintaining a robust configuration management process.
While importing or exporting a rule or workflow, keep in mind that you can import or export the dependencies (connectors, datasets, and APIs) seamlessly, but without the credentials. We don't share the credentials. This is to maintain security and data integrity.
Conclusion
The Import/Export feature in Nected streamlines the management of rules and workflows, making it easier for users to handle complex configurations efficiently. By following this detailed guide, users can leverage the full potential of the Import/Export functionality, ensuring smooth operation and consistent management of their rules and workflows. This feature not only enhances productivity but also ensures that configurations are easily transferable and backed up, contributing to a robust and flexible development environment.
Last updated
