Imported Workflows have a new ID

[Banalian]

Describe the bug When either importing a workflow or restoring a backup, created workflow will have a new id instead of using the one saved in the .JSON file.

To Reproduce Steps to reproduce the behavior:

1. export either a specific workflow or create a backup
2. On another computer, either import the workflow or restore the backup
3. Observe that the workflow Id changed compared to the one on the original computer

Expected behavior Since the ID is saved in the JSON file, I expected it to be the same when importing it.

Desktop (please complete the following information):

• OS: Windows
• Browser: Google Chrome
• Extension Version: 1.28.27

Additional context Same as #1776, was trying a workaround by sharing a backup, but the Autohotkey script would then not work because the workflow Id changed, and I can't just modify the script each time with the new id since I give the computer a packaged Autohotkey script which can't be modified

[ffzhen]

I meet the same problem

[jingbof]

It always generates a new ID when importing packages (see importPackage and insert).

One workaround is to change packageStore.insert(pkgJson); to packageStore.insert(pkgJson, false); in Packages.vue, and then re-build and load it as an unpacked extension. (A better option would be to add a checkbox to retain the ID when uploading to import, though)