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 Future consideration
Categories Social Program Management Platform
Created by Guest
Created on May 31, 2019

RELATED IDEAS

Enhanced Troubleshooting capability for Client Navigation Errors

We have experienced situations whereby the SPM client infrastructure randomly failed to read the values of User Interface navigation and UIM elements. This caused the UI to show labels like "Tab.name", "Person.Title" and so on. We were unable to debug/investigate these situations further because these element values are stored in the ApplicationResourceCache but this does not use the Curam Cache approach that would allow monitoring via JMX. The cache can only be monitored by enabling sql tracing which is not a viable approach for Production environments.

We are requesting that the ApplicationResourceCache be redesigned to provide a monitoring capability that can be used in a Production environment. This might be via JMX or via some other mechanism, although JMX is preferred since it would be consistent with how caches are monitored by customers today.

NB: Other caches which do not confirm to the standard Curam Cache/JMX approach should also be considered for redesign.

For reference, the originating PMR for this was TS001786734.

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
  • Guest
    Reply
    |     Jun 7, 2019

    Hi Clay,

    We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.

    IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

    IBM will update this request in the future.

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

  • Guest
    Reply
    |     Jun 4, 2019

    Hi Clay,

    Thank you for your enhancement request.
    We require some further analysis to determine whether or not this enhancement can be considered in a future release.
    I will provide another response when our investigation is complete.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team