Hi everyone!
We use cloning modules for developing features that after get merged into the original module.
When publishing a cloned module, Service Studio publishes it to the application "Independent Modules". We then need to go there and move it to the correct application.
It would be helpful that when publishing a cloned module, Service Studio would ask in which application the cloned module should be placed.
--Tiago Bernardo
In the same way that it is possible to move a module to another application, it would be interesting to clone a module for the desired application and not just for the independent modules.
As a suggestion, there would be a button next to the move module with clone functionality that would similarly open the target application.
Hi,
your idea is very good, but what do you think of this one too?
https://www.outsystems.com/ideas/9761/clone-module-keep-in-application
It's similar to yours, right?
Hi Eduardo,
It is also a good way to solve the same problem.
The big problem is that for companies with a large number of developers and systems, leaving independent modules open is not a good option .Cloning modules is very trivial.Regards
I consider this idea a duplicate of this one:
"When publishing a cloned module ask for the application (instead of publishing directly to Independent Modules)"
Link: https://www.outsystems.com/ideas/9031/when-publishing-a-cloned-module-ask-for-the-application-instead-of-publishing-di