This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
@Bhawana Gupta, thank you for updating the status to "Future consideration".
I think you have dismissed this suggestion too lightly and I would like you to reconsider. To claim that the "functionality already exists" is like telling me I have no need for a car because the "functionality already exists" to walk.
At the moment, every user in our organisation will hit the same issue, that they can't connect to multiple MEC/EWM workspaces in a chosen folder as they would expect to with other Eclipse installations. This will cause them wasted time while they search for a solution, and me wasted time trying to propagate the workarounds to the user community.
Further, creating shortcuts is not something all users are familiar with; it's just a real clumsy workaround. Do we need to create a separate shortcut for each Word document we edit? No. Do we need a separate shortcut for each Visual Studio project, Rhapsody model, or RTC project area? No. I cannot think of any other application which requires the user to create a separate shortcut for each project they want to open.
So I think there is a genuine need to enhance MEC so that it fully supports multiple workspaces in the same way that other Eclipse distributions do, and so that the capability is obvious in the user interface without searching support documents.
Further, because MEC has already been enhanced to be able to switch workspaces after initial launch, it appears that the fundamentals may be already in place.
The RFE review board has evaluated this request. This request, while valid, is being rejected as it is possible to do this using existing options.
Create a separate MEC shortcut for each workspace that the user wants to open when the application launches. Refer to Using multiple Engineering Method Composer workspaces .