Skip to main content

Upgrade Application by Importing


Feature Overview

It means that after the configuration of the source application is modified, you can upgrade the target application to the latest configuration or feature by importing the application.

Use Case: For large customers, multiple organizations are usually deployed to simulate multiple environments in the R&D process. In this case, application upgrades can be achieved by importing applications that are running stably in the test environment into the production environment. There is no need to modify the configuration of the application in the production environment.

This feature is only available in Enterprise and Ultimate Editions.

How to upgrade applications

Export the modified source application

After the source application (or called test application) is modified and tested, export the application. Applications can be upgraded by importing as long as they are of the same source.

What are the applications of the same source:

For example, new application A is created, A is exported and imported to generate application A1, and A1 is exported and imported to generate A2. A, A1, and A2 are all same-source applications. Same-source applications can be upgraded by importing, which means that after modifying any one of them, you can import it to the other two for upgrading.

Import to target application for upgrading

1. Entrance to application upgrades

Application Admin goes to [App Management] > [Single App Upgrade].

2. Upload the upgrade file

Select and upload the exported mdy file, when uploading, it will check the password, file format, etc.

3. Check the upgrade scope

Once the file is uploaded, it will read the upgrades and list the upgrade details. Click the [Details] button on the right to view the specific adjustments. Click the [Import] button to start the upgrade.

  • New: It indicates the items that are available in the source application but not in the target application, which are added when importing.

  • Update: Items that are present in both the source and target applications are shown as update, but it does not mean that there are modifications made.

  • Match users/departments/positions when importing

    • Checked

      • When it is in the source application and not in the target application - add it to the target application if it can be matched in the organization

      • When it is not in the source application but in the target application - retain the users that are already in the target application.

      • When it is in both the source and the target application - update the member's permission configuration

    • Unchecked

      • When it is in the source application but not in the target application - these data are cleared out

      • When it is not in the source application but in the target application - retain the members that are already in the target application.

      • When it is in both the source and the target application - not update the member's permission configuration

  • Backup the current version when upgrading

    • If checked, the application configuration before import will be backed up.

After the import is complete, the upgrade history is displayed on the management page.

Rules for Application Updates

Update Scope

What data needs to be retained? What data needs to be updated? What data remains unchanged?

  • Overwrite and update: If there is correspondence, overwrite and update.

  • Add and update: if it is in the source application, but not in the target application, add and update.

  • Keep unchanged: if it is not in the source application, but in the target application, keep it unchanged.

Exceptions:

  • If the data that needs to be updated is logically deleted ( such as a workflow in a recycle bin), it needs to be restored and updated.

  • If the data to be updated is moved to another application, add and update it.

tip
  • No deletion when upgrading.

    For example, if you add a new worksheet, modify a workflow, or delete a role in an application in the test environment, when you import and upgrade the application in the production environment, it will only synchronize the newly added worksheet and the modified workflow, but the deleted roles will not be synchronized, and you need to operate manually.

  • Update only the application configuration, not the record information.

Rules for Updating

⚠️ - Add and update: Modules that contain list data are to be added and updated, such as options sets, business rules, and public statistics. Data with correspondences that can be found is updated; if not, it is added.

❌ - Keep unchanged: No processing required.

✅ - Overwrite and update: Update to the source application's configuration.

ModuleOperationDescription
ApplicationIcon and Name❌ - Keep unchanged
Navigation Settings (on PC and mobile, including grouping of application items)✅ -Overwrite and update
App Description✅ -Overwrite and update
Usage Analysis❌ - Keep unchangedRetain the usage analysis in the target application.
Option Set⚠️ - Add and update
Recycle Bin for Application Items❌ - Keep unchanged
Backup Files/Backup Operation Logs❌ - Keep unchanged
Chart-Public✅ -Overwrite and update
Chart-Personal❌ - Keep unchanged
Publish Settings/App Maintenance Status✅ -Overwrite and update
Application API Documentation❌ - Keep unchanged
Global Variable⚠️ Add and update
WorksheetIcon and Name✅ -Overwrite and update
Grouping of Application Items⚠️ - Add and update
Hidden Status of Worksheet✅ -Overwrite and update
Submit Form-Configuration✅ -Overwrite and update
Data Name✅ -Overwrite and update
Function Switch✅ -Overwrite and update
Business Rule⚠️ - Add and update
Custom Action⚠️ - Add and update
Printing Template⚠️ - Add and update
Index❌ - Keep unchanged
Controls and Configuration✅ -Overwrite and update
Form Style✅ -Overwrite and update
Recycle Bin for Fields❌ - Keep unchanged
Public Release-Configuration✅ -Overwrite and update
View Configuration✅ -Overwrite and update
Discussion and Log❌ - Keep unchanged
Draft❌ - Keep unchanged
Record Data❌ - Keep unchanged
Custom PageIcon and Name✅ -Overwrite and update
Component Configuration✅ -Overwrite and update
Component Name & Layout⚠️ - Add and update
WorkflowType/Name/Status/Last update time/Creator✅ -Overwrite and updateAfter updating the workflow configuration, re-publish it. If the publishing fails due to non-existence of fields or other reasons, it will be in the pending update status.
Nodes Configuration✅ -Overwrite and update
Basic Configuration/Manual Node Settings/Process Parameters✅ -Overwrite and update
Execution History❌ - Keep unchanged
History Version❌ - Keep unchanged
UserRoles and PermissionsNote: To generate an latest permissions configuration based on the final upgraded application structure.
Member Data✅ -Overwrite and update
Send Notification/Allow Viewing-Configuration✅ -Overwrite and update
User Extended Information✅ -Overwrite and update
External PortalExternal Portal✅ -Overwrite and updateOnly update target apps that have enabled the external portal, if the target app has not ever enabled the external portal, no update.
Roles and PermissionsNote: To generate an latest permissions configuration based on the final upgraded application structure.
Statistics❌ - Keep unchanged
Portal Settings-Basic Settings❌ - Keep unchanged
Portal Settings - Information Collection✅ -Overwrite and update
Portal Settings - Custom Login Page❌ - Keep unchanged
Portal Settings - Message Settings (SMS/Email)❌ - Keep unchanged

Have questions about this article? Send us feedback