When publishing new eSpace's between environments via oml there could be an option to choose in which application the module should be stored into instead of having to go to Independent Modules and move the module to the intended application.
I totally agree!
Rita Tomé,
I would say that this ideia should be set as category of Service Studio rather than Service Center, don't you think?
Great Idea!
When cloning a module you need to publish the cloned module for the first time.
Currently it's always publishing to independent modules, where you 99% of the time will move it to the desired application.
Since, if applicable, you already geta pop-up to what catalog it goes, it should be also possible to choose to what application it belongs to.
This will save some clicks and even prevents "forgetting" it to move it to the right application
When viewing the Modules inside the "Independent Modules" you have to do it one by one. It would be great if there are two additional features available here:
1. Creating an Application directly within the move action. Because now if the module should be in a new Application, you first have to create it, then go back and perform the move operation
2. Select multiple modules to be moved to a desired Application, now you have to do it one by one.
This is two ideas, next time, please create two ideas. Because right now, this is the same as two other ideas, both of which were made before yours, and I can't properly merge anything because you put both ideas into one.
J.Ja