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 Guest
Created on Oct 3, 2017

Support configuration based creation and population of staging tables with Dynamic Evidence data

The product should provide a facility to configure Dynamic Evidence Types of interest to turn on extraction of Evidence data (stored in DynamicEvidenceDataAttribute table) to corresponding staging tables. Based on metadata associated with a Dynamic Evidence Type, DDLs for the corresponding "staging" tables should be generated at build time. The “staging” table should be a relational representation of a logical Dynamic Evidence record. This means that the staging table would contain a column for each attribute of the Evidence Type. The data in these "staging" tables are meant to be truncated on a regular (daily / weekly /etc.,) as part of ETLs as they have been explicitly designated for reporting purpose. The product should provide batch / online processes to extract information from active Dynamic Evidence records to these staging tables. NC FAST would need control over usage of batch VS online mode for information extraction. Online mode might be used to avoid burdening an already packed batch window.

Customer Name North Carolina - Dept of Health and Human Services, New Zealand MSD, Minnesota
  • Attach files
  • Guest
    Reply
    |
    Mar 28, 2023

    Can Product development provide hook points in Dynamic evidence infrastructure to create individual evidence tables? These tables can be used by reporting team for their reports.

    Santosh

  • Sigitas Jakucionis
    Reply
    |
    Feb 5, 2023

    is it part of PD 3-year plan? Please inform MN project team. Thank you. Sigitas Jakucionis.

  • Guest
    Reply
    |
    Apr 26, 2018

    Hi Clay,

    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
    |
    Oct 5, 2017

    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