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 Feb 11, 2025

RELATED IDEAS

Improve performance by allowing harding of user locale

We’ve identified some SQL that’s running millions of times a day, whilst it is not a major overhead we wondered if something could be done. The SQL is


SELECT DEFAULTLOCALE FROM USERS WHERE USERNAME=? WITH CS


I traced this to curam.util.internal.security.base.Users.readLocale. Now, in some countries with multiple language support this might be required, however where we are all of our users are locale en_GB (we’ve even enabled exit points to set the locale to en_GB).


So, can we request a PRM for this so that there’s a property for the only locale, to be set project specific and returned without a DB read, if set, otherwise read the DB for the user locale?


In the meantime, can we create our own factory+implementation to do this? I’ve done this locally and it works, on a fag packet calculation this would lower the load on the DB by around 0.01% of the total. Which is not huge in the grand scale of things but this is sometimes running over 400 times a second.


This would be safe for us, we’ve enabled an exit point on the insert+modify to ensure that user’s locale can only ever be en_GB

Customer Name Scottish Government
Type of Request RFP
Market Opportunity

All
  • Attach files
      Drop here to upload
    • Admin
      ANGELA BRADY
      Reply
      |       Feb 28, 2025

      Hi Andrew,


      We have reviewed your enhancement suggestion.   

       

      Based on the information provided, our understanding of your request is as follows: 

      • Improve performance by allowing for where only one locale is in operation, to remove the need to read the DB to determine locale



      The theme is aligned with our current multi-year strategy for our product, and we have accepted your suggestion as a consideration for a future release. Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement. 

       

      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. 


      Regards, 

      Angela Brady, Cúram Product Management Team 


    • Guest
      Reply
      |       Feb 13, 2025

      On occasional we hit this table around 400 times a second and it always returns en_GB, so would be a help.

    • Admin
      Graham McCrindle
      Reply
      |       Feb 12, 2025

      Hi Andrew,

      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 to complete our evaluation, we will send you a request for more information.

      Thank you,

      Graham McCrindle, CURAM Product Management Team