Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. 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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.


Status Not under consideration
Created by Guest
Created on Jan 29, 2013

File name defaults for Fragments

Problem description
* Defaults for fragmenting the model are not smart, and may hang the
tool when cleaning up model.
** Would be nice if when creating a fragment, the file name defaulted
to the name of the Class/Package that the operation is being performed
on.
** Works better/faster all of the model files are loaded before the
operation is performed.

From IBM:
The reason we don't name new fragments according to the name of the
root element is to avoid having to rename the fragment file when
refactoring the name of the root element. Many CM tools have problems
with renaming files (will loose revision history etc). But I suppose we
could add a preference for this behavior if you like.

Idea priority Low
RFE ID 30693
RFE URL
RFE Product Rational Software Architect Real Time Edition
  • Admin
    Osman Burucu
    Reply
    |
    Jan 19, 2024

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion.

    This idea is either outdated or has been implemented in one of the versions. Please check with latest version (V 12.0 at the time of writing)

    The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Reply
    |
    Sep 24, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - Software Architect Real Time Edition

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Software Architect Real Time Edition

  • Guest
    Reply
    |
    May 15, 2013

    IBM development clarified that this is still under investigaiton, no ETA.

  • Guest
    Reply
    |
    May 14, 2013

    Status from Jim Burke indicates this will be part of 8.5.1 CP2.