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 Mar 27, 2018

RELATED IDEAS

Improve Attachment Process

The NC FAST application uses the OOTB Curam Attachment functionality which transmit files via CMIS protocol to FileNet. The method of delivery in this transaction is not using a stream/buffer to submit the file. As a result memory from our application servers are allocated to this process for attachment uploads and downloads. We have seen servers crash due to out of memory errors. The results of our root case analysis leads us to belive this heap of memory usage by the attachment process is overwhelming the app server when a file is “large”. We have files in our system that exceed 500MB. We have update our max limit of files that can be uploaded to 100MB to help avoid OOM errors, however this is not the permanent solution because of future business requirements surrounding child welfare activities.

We are now requesting an RFE to investigate the overall attachment process in Curam so that the memory heap from the app servers is not unduly burdened. The streaming/buffering of files is one option we would like explored to see if it improves the problems we are currently facing. Any architectural solution that can be provided to eliminate OOM errors due to large files being consumed, would be welcomed.

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
  • Guest
    Reply
    |     May 8, 2018

    Hi Michael,

    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.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     Apr 5, 2018

    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,
    Eloise O'Riordan, Cúram SPM Offering Management team