Chorus - Subprocess version upon import process

[arisa1]

Current subprocess upon import to Chorus where there is an existing subprocess with a different version, a new version number will be added on the destination environment.

Scenario1:
For example, exporting from Dev1 with subprocess A version3.
Imported to Dev2 that already has subprocess A version3 (however, it’s different design details than version3 from Dev1)

A new version of subprocess A version 4 will be added. This may cause issues with the client as they are not sure which one is the correct version unless they manually check it one by one from their imported process flow.
-It may be useful to have a notification upon import that there is already an existing subprocess with the same name and version and that a new version number XX will be created. 
Or
Scenario2:
For example, exporting from Dev1 with subprocess A version6.
Imported to Dev2 that already has subprocess A but only version1-2.
After imported, subprocess A version6 will became subprocess A version3 (v3) on Dev2 (destination environment).
The user will need to reselect the subprocess version with a prefix ‘v’ and the latest version.

-It may be useful to have a notification upon import to a user that this workflow contains subprocesses with the same name/ version on this environment, please recheck/reselect the version before deployment.