Skip to Main Content
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

Status Future consideration
Created by Rahul Bhardwaj
Created on Nov 1, 2021

Implement self-initialization/automatic warmup when Curam Case worker portal jvms are restarted

Our case worker application is very heavy (including rules) compared to Curam's OOTB. Curam Case worker portal takes up to 2 minutes for the first user on each jvm. With several JVM (36), it results in bad experience for many users. Automatic warmup will improve end user experience.
Customer Name Ontario - Ministry of Community and Social Services
  • Attach files
  • Rahul Bhardwaj
    Reply
    |
    Jan 25, 2022

    Please note that the same warmup need is also applicable for REST/SOAP websphere clusters. They have the same slowness symptoms and often result in timeouts (30s+) when the first call comes in after a restart.

  • Guest
    Reply
    |
    Dec 8, 2021

    Hi Rahul,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
    The start up, or warmup times for SPM is too long. We need to improve the start up time (or the warmup time) for SPM.

    This theme is aligned with our current strategy to investigate improvements that will help optimize the SPM response time on start up, and we have accepted your suggestion as a consideration for a future release.

    Not all items under consideration will make it into a release and we may address the problem in a different way although we will consider your suggestion to enhance the start up times for SPM.

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    Thank you,
    Ranjana Ghosh, SPM Product Management team

    Note: We have improved the RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.

  • Guest
    Reply
    |
    Nov 2, 2021

    Hi Rahul,

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required in order to complete our evaluation, we will send you a request for more information.

    Thank you,
    Shane McFadden, SPM Offering Management team