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 Andrew Wylie
Created on Apr 28, 2021

RELATED IDEAS

Enhance DbDiff in Upgrade Helper to handle Batch job record changes

The DbDiff tool in the Curam Upgrade Helper doesn't handle BatchProcDesc and BatchParamDesc record sync'ing when there have been changes to Batch job records.

Those 2 tables are populated by execution of script /EJBServer/components/core/data/initial/handcraftedscripts/BatchDesc.sql

Since DbDiff will not parse INSERT INTO...SELECT type statements, it will not be able to generate statements in its output to bring those table sup to date.

Either we need to think of a better way to populate these 2 tables differently, ie. INSERT statements, from generated model files or DMXs, or the dbdiff process needs to be aware of these types of scripts and handle them by instruction of something like, truncate the 2 tables then rerun batchdesc.sql again. However, it needs to be done in a way that means human manual intervention is not needed, ie automated.

(note similar issue exists for security and file Supergroup.sql in /EJBServer/components/core/data/initial/handcraftedscripts/Supergroup.sql...customers have to run SQL to detect NOT IN records and execute manually to make the missing FIDs/SIDs get populated correctly form release to release)

Customer Name ESDC, District of Columbia - Washington
  • Attach files
  • Benoit Tremblay
    Reply
    |     Sep 28, 2023

    CoE has not heard much on this issue and we’re not really making use of this. Low priority

  • Guest
    Reply
    |     Apr 29, 2021

    Hi Andrew,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
    * Simplify the upgrade helper process by reducing or simplifying steps in the upgrade helper process such as enhancing DbDiff to handle Batch job record changes.
    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,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Reply
    |     Apr 28, 2021

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

    Thank you,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.