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 Future consideration
Categories Asset Manager
Created by Guest
Created on May 13, 2015

Create persistent, "latest" featured content

Our team (in fact, our enterprise) commonly uses RAM to publish documentation for consumption by disparate teams who have various levels of familiarity with RAM.

In many cases, we would like to publish a single URL that the users can bookmark as a reference. We don't want to change this URL every time the asset content changes.

When our featured content is essentially static (think: index.html), we have no concerns about the featured content changing from release to release.

We would like RAM to provide an alias URL for featured content that will link always to the LATEST VERSION of the artifact.

Idea priority Medium
RFE ID 71074
RFE URL
RFE Product Rational Asset Manager
  • Guest
    Reply
    |
    Oct 23, 2015

    The process for submitting new documents would not change, they would always be submitted as an update or as a new version. Accessing documents wouldn't change, for example, these would still work

    http://ramurl/uuid/v1.0/index.html
    http://ramurl/uuid/v1.1/index.html
    http://ramurl/uuid/v1.2/index.html

    The RFE asks that a virtual URL be accessible as well:

    http://ramurl/uuid/latest/index.html

    This would always point to the latest version of the asset. So in the case of this example, these links would take you to the same document:
    http://ramurl/uuid/v1.2/index.html
    http://ramurl/uuid/latest/index.html

  • 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 - Asset Manager

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Portfolio, product & project management
    Product - Asset Manager

  • Guest
    Reply
    |
    Jul 16, 2015

    The typical use case for this would be, for example, featuring "index.html". The document name would never change but you would want to be able to offer a "latest version" URL to that document. It would be some type of alias. For example, this URL takes you to a specific version:

    https://rational.kp.org/ram/artifact/3B099539-9230-DBE0-CD72-2A33E33D663A/1.5/mydoc/index.html

    If that's the latest version, then this would take you to the same place:

    https://rational.kp.org/ram/artifact/3B099539-9230-DBE0-CD72-2A33E33D663A/latest/mydoc/index.html

    This would let you give a single URL to a document that is constantly changing.

  • Guest
    Reply
    |
    Jun 12, 2015

    This request lacks sufficient information for us to evaluate it. It might not be considered further until it has been revised and clarified.
    How could you create the new document? Rename the doc name just like "xxxxxxxxxxxx_v1.0" to "xxxxxxxxxx_v1.1" and upload it into the same asset?
    Or create a new version of the asset and set it to 1.1, then upload the new doc with the same name?
    Thanks a lot.