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 Not under consideration
Categories Social Program Management Platform
Created by Garry Heap
Created on Oct 14, 2020

RELATED IDEAS

Ability for DataExtractor to extract APPCASEELIGIBILITYRESULTDATA.CREOLERULESDATA

Customer Data team needs to extract data from APPCASEELIGIBILITYRESULTDATA.CREOLERULESDATA.
Currently the DataExtractor only extracts CREOLECASEDETERMINATIONDATA.CREOLESNAPSHOTDATA. Request is to duplicate that kind of thing to extract from the APPCASE... table.

Customer Name Scottish Government
  • Attach files
  • Guest
    Reply
    |     Dec 7, 2020

    Hi Garry,

    Thanks for your feedback that our suggested OOTB method can be used to meet your requirement here.

    We acknowledge the benefit of your enhancement request however other features are taking a priority in our planning at this time. Although we will not be addressing this item in the near term, your suggestion will be available for future consideration. This request will be closed and we will not be taking any further action.

    Thank you for taking the time to share your ideas with us. Although we cannot pursue all of the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.

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

  • Garry Heap
    Reply
    |     Dec 5, 2020

    Have reviewed this and i see you are correct in the suggestion of OOTB method to use. It does need additional development effort on the project to eg use XPath to parse the xml but that should be workable. Happy to close, thanks

  • Garry Heap
    Reply
    |     Dec 3, 2020

    sorry have been dealing with a number of things. will respond within next 7 days if you dont mind keeping open for a week longer, many thanks

  • Guest
    Reply
    |     Nov 3, 2020

    Hi Garry,

    We have reviewed your enhancement suggestion and require more information to properly understand the issue and the business scenario you are trying to support.

    We would like to better understand the following statement in the business justification section: 'Compliant way of doing this is needed, currently it doesn't exist, meaning that we have data in the database that is not accessible by DBAs.'

    Currently, there is a compliant API for just getting the XML as string data from CADG, e.g.
    http://cadg-demo.rtp.raleigh.ibm.com:9080/curamanalysisdocumentation/javadoc/curam/commonintake/facade/intf/ApplicationCaseCheckEligibility.html#viewCheckEligibilityDisplayRules-curam.commonintake.entity.struct.AppCaseEligibilityResultKey-
    Note that one call to this API retrieves the display rule data for just one of these determinations.
    Being a façade, it was written with the front-end use case in mind i.e. Get a specific determination from a given application case.
    So to extract this data from 100Ks of determinations (or possibly more, depending on your customers database), you would have to use this API in conjunction with others.
    You could use these APIs to pull the data from the SPM database, but then you would have to invest in development effort to enable your analysts/report engineers to get a breakdown of this data by dimension/segment, across all the extracted determinations.
    You would need to create your own data warehouse tables along with the data mapping of the extracted data to the data warehouse tables.

    Let us know if this method was considered as a compliant way of extracting the data.

    Please provide the requested information within 30 days so we may proceed with our evaluation. If we do not hear from you within that timeframe we will have to close the request due to insufficient information.

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

  • Guest
    Reply
    |     Oct 15, 2020

    Hi Garry,

    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.