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.

Absolutly agree!!  ++1

Any New Updated for that subject

Any update on this ?

Hey Badr and Rajashekar,

Unfortunately we don't have plans to tackle this in the near future.

Nevertheless, we will keep this under our radar.

Cheers

Still a very wanted function to have.

It would be a very nice feature indeed, since the "clone-each-module-and-change-references" method is far from being flawless...

it's a great idea and it is less error prone.

Would be nice to have. 

My Vote for you :) +1

Just to add we'd like the option too

Yes, we definitely need this - would have saved a lot of time in multiple instances.

With workflow builder as a start point, this becomes more interesting to get on the radar.

Cloning the whole app will help when you are creating a POC or Test application and you need to setup a POC for a distinct scenario just by making some changes in the original POC.

Besides cloning the app in service studio, having the option of cloning using CLI (command line interface) would be valuable in automation scenarios.

Seriously, five years already!

Nothing on it yet?

I guess not or else it would be posted here, wouldn't you think?

I would love to have this ability.  It would be so useful for testing behaviour against an earlier version.  If you are working in a team it is not feasible to use a solution to switch current running versions.

Awaiting for this feature, about to get this done manually for second project.

I consider this also a very nice addtion to the platform..

Agree! clone application is very useful for POC / testing with application with many modules.

Agree to all above! Cole/Duplicate application can save a lot of time for developers for one application where old and new version have to run in parallel.

Agree clone application will be fine for testing and PoC

Agree to all above! 

Much needed please,  !

Cloning apps is also useful is scenarios were we have a common base, a set of entities , logic and screens that can be reused to build other applications based on the fundamental artifacts

However, we do not provide the capability of turning one or more applications into a template - Think of this as an accelerator:

A customer builds a couple of apps , containing several modules - they hold the generic entities, screens and logic - This is the accelerator

Them they would use this accelerator app as the template to create other apps , like we have currently on service studio 011 , but AFAIK , customer cannot create this kind of templates - They are limited to the usage of clones (which requires a lot of work to the development team).  Can we have this as an improvement to the platform ?

Notice that Outsystems O11 already provides a similiar feature - start from app , which basically is a set of templates (apps) to bootstrap/accelerare the creation of apps ... so the ideia of to provide the customer the ability to create their own template/acelerator apps and have a way to easily a quickly bootstrap new applications based on that template