Importing Flows
In the following scenarios, importing flows is more convenient, efficient, and secure than manually adding flows:
Business scenario 1: Import historical data. When the company introduces a new system, the retained data of previous years needs to be imported into the system.
Business scenario 2: Import summary data. Due to permission issues, not everyone can use the system. Therefore, data needs to be summarized level by level and imported into the system by a specific person.
Procedure
- Choose .
- Choose and click Import Flow. The Import Flow dialog box is displayed.
Figure 1 Import Flow
- Click Select File, select the file to be imported, click Upload, and click Confirm.
- In the ZIP package, each file must be in JSON format, and its size cannot exceed 4 MB. Otherwise, the import fails.
- The size of the ZIP package must be less than 20 MB. Otherwise, the import fails.
- In a JSON file, the request URL of the business interface and the database URL in the stored procedure must be added to the trustlist. Otherwise, the import fails. Contact the administrator to configure the trustlist.
- Duplicate multimedia resource names and access code names cannot be overwritten.
- After a multimedia resource is imported, the multimedia library is updated synchronously, but the value of Resource Status is Ineffective. You need to choose , click the Edit button in the Operation column of the corresponding data record, and upload the multimedia resource again.
- After the flow is imported to another environment, if the robot reply diagram element contains an email, you need to manually set the email template, email resources, and email variables.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot