Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Not under consideration
Categories Social Program Management Platform
Created by Guest
Created on Jul 21, 2016

RELATED IDEAS

Require the documentation about component folders and interdependencies at build time to be enhanced

Ensure that the purpose and use of the component folders in the EJBServer/component and Webclient/component are clearly described in customer documentation.

https:w3-01.sso.ibm.com/software/servdb/PMR/PmrRecord?&pmrno=59756&bno=499&cno=000&cdate=O13/10/03

Cover any identified use cases:
The teams might help with the following questions:
1. As you know, there is no particular standard for the creation of component folders, and teams can create a new component folder as required for their projects, so the current organization of the component folders could be a bit add-hoc. It could be useful I suppose to know which component folders are associated with particular components, but if the users don't need to actually use this information (if it is information-only), it doesn't advance them much. Besides an overview for information-only, do we have any clear use cases that might require users to know what is in any particular folder?

2. We don't understand this business impact, except as an indication that the components folders are misunderstood. In general, as I understand it, you install what you need, and then build everything you have. Are there specific exceptions to this rule that you know of?

Business impact:
It can be difficult to identify precisely which components are required for a particular deployment.

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
  • Guest
    Reply
    |     Apr 2, 2020

    Hi,

    We have reevaluated your request and have determined that it cannot be implemented at this time.

    Your request may be resubmitted for consideration after 12 months from the date of decline.

    Thank you for your interest in the Cúram SPM product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |     Aug 6, 2016

    Hi,

    We acknowledge that this is a valid enhancement request. It will be considered for inclusion in a future release of the product. Thank you for your interest in the Cúram product.

    Thanks,
    Eloise O'Riordan, Cúram SPM Offering Management team