Clone/Duplicate Applications

By Gonçalo Martins on 5 Jul

It would be nice to have an option to clone/duplicate an application in Service Studio in the application detail view like we have the option to edit and remove.

And also it would be nice to have the option to do the same to the modules inside but as an option.

It ever so often happens I need to clone an application. Currently, the basic procedure to clone an entire application is:
- Open each application module in Service Studio, clone it and publish.
- Go through each application module's clone and manage dependencies so they reference the other cloned modules instead of the original application's ones.
- Create new application and move cloned modules to new application.

The suggestion is: Provide some UI, either in Service Studio or Service Center, that automates this process for us. The developer would only need to press a button "Clone Application", and a new CloneOfApplication application would be generated.



Merged from 'Provide UI to clone Applications' (idea created on 2017-07-10 17:00:07 by Jorge Martins), on 2017-07-11 08:26:33 by Carlos Alfaro
Miguel Vicente24 Sep 2014
Ability to copy an application rather than module by module.

Merged from 'Ability to copy an application' (idea created on 2014-09-24 12:22:16 by Miguel Vicente), on 2017-07-12 06:04:43 by J.
Curt Raddatz30 Sep 2014
I think this already exists by creating an OSP file using the instructions here - http://www.outsystems.com/forge/ProjectUpload.aspx?ProjectId=0 - click on How do I export an Outsystems Application Package.

Merged from 'Ability to copy an application' (idea created on 2014-09-24 12:22:16 by Miguel Vicente), on 2017-07-12 06:04:43 by J.

Exporting an OAP allows you to share your application with others, so they can install it in other environments (IPP may apply), but it maintains application/module Ids. If you export a new version of the OAP (where some modules have been updated) and install it in an environment where you installed a previous version of the OAP, its modules will be overwritten.

This is the correct behaviour for Application Packages, but not good for the described use case, where we want to generate completely distinct applications/modules (different Ids) that happen to have the exact same content and relationships between themselves.