Curam by Merative Ideas Portal
Hide about this portal

Shape the future of Curam!

We invite you to shape the future of Curam, 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 Curam team to refine your idea

Help Curam prioritize your ideas and requests

The Curam 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 Jul 21, 2016

RELATED IDEAS

Require compression to LOB data fields on Attachment & ConcernRoleCommunication entities

Following analysis on SPMP-14118, the following two fields should be compressed prior to db write:

1. Attachment.AttachmentContents
-> inserted in curam.attachment.impl.AttachmentImpl.insert()
2. ConcernRoleCommunication.CommunicationText
-> inserted in curam.core.sl.impl.Communication.insertCommDetails()
The associated access methods should then be updated to decompress data. Possibly add a new column to the two tables, with a flag to indicate 'compressed'.

These should be compressed using gZip, java.util.zip.GZIPOutputStream, as is currently used for CreoleCaseDeterminationData.creoleSnapshotData.

Note:
1. This would require an upgrade helper as customers will have existing data on the database that is not currently compressed.
2. Impact to customers: any customised reads on the data would have to be updated to decompress where data is compressed.

These fields have been identified by the customer on PMR 75893,499,000 as requiring compression.

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
      Drop here to upload
    • Guest
      Reply
      |       Aug 5, 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

    • Guest
      Reply
      |       Aug 3, 2016

      Hi Kevin,

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

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