Skip to Content (Press Enter)
Back to Ideas
16
Like
Follow Idea
When publishing a cloned module ask for the application (instead of publishing directly to Independent Modules)
353Views
5Comments
New
1CP

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

25 May 2020
Copy link to comment
Merged this idea with 'Choose destination when cloning a module' (created on 13 Jan 2021 14:59:33 by Alexandre de Ribeiro)
15 Jan 2021
Copy link to comment

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.




This comment was:
- originally posted on idea 'Choose destination when cloning a module' (created on 13 Jan 2021 by Alexandre de Ribeiro)
- merged to idea 'When publishing a cloned module ask for the application (instead of publishing directly to Independent Modules)' on 15 Jan 2021 22:21:06 by Justin James
13 Jan 2021
Copy link to comment

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?



This comment was:
- originally posted on idea 'Choose destination when cloning a module' (created on 13 Jan 2021 by Alexandre de Ribeiro)
- merged to idea 'When publishing a cloned module ask for the application (instead of publishing directly to Independent Modules)' on 15 Jan 2021 22:21:06 by Justin James
13 Jan 2021
Copy link to comment

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



This comment was:
- originally posted on idea 'Choose destination when cloning a module' (created on 13 Jan 2021 by Alexandre de Ribeiro)
- merged to idea 'When publishing a cloned module ask for the application (instead of publishing directly to Independent Modules)' on 15 Jan 2021 22:21:06 by Justin James
15 Jan 2021
Copy link to comment

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


--Tiago Bernardo



This comment was:
- originally posted on idea 'Choose destination when cloning a module' (created on 13 Jan 2021 by Alexandre de Ribeiro)
- merged to idea 'When publishing a cloned module ask for the application (instead of publishing directly to Independent Modules)' on 15 Jan 2021 22:21:06 by Justin James
15 Jan 2021
Copy link to comment
Changed the category to
1CP
17 Jun 2021
Copy link to comment