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 Vinod Musunuri
Created on Jun 29, 2021

Optimize reassessment processing when a new decision has to be created due to eligibility changes

Reassessment related logic after the system decides to create new decision is not working optimally. A number of queries that are fired in loops could be replaced by doing simple joins. SAMS has a number of cases that are active for over 10 years with different decisions each month due to changing income of the clients. The below queries need to improved so that the system performs better

Data from CreoleCaseDetermination, CreoleCaseDecision, CaseDecision,CaseDecisionObjectiveTag,CaseDecisionObjective, PaymentInstruction, PaymentInstrument tables should be fetched with a single query each for the tables

Insert into CREOLECASEDECISION is preceded by a lock on corresponding CASEDECISION table. We are not sure why this is required

CaseNomineeObjectiveFactory.searchObjectiveHistoryForCase method is called in loops and too many times and this is not efficient

Customer Name Ontario - Ministry of Community and Social Services
  • Attach files
  • Guest
    Reply
    |
    Aug 18, 2021

    Hi Vinod,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
    You are requesting an enhancement to improve the performance of CER reassessment processing.

    The theme is aligned with our current strategy for our product to continue investigating improvements that will help to optimize the reassessment of cases and we have accepted your suggestion as a consideration for a future release.
    Not all items under consideration will make it into a release and we may address the problem in a different way although we will consider your suggestion to enhance how determination, decision, case nominee, and financial data is retrieved. 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.
    Note: we are currently in the process of improving your RFE experience and will soon transition to an Ideas Portal provided by our trusted business partner Aha!
    Further communications with additional details will be shared shortly.

  • Guest
    Reply
    |
    Jul 22, 2021

    Hi Vinod,
    Thank you for providing the additional information requested. Within the next 30 days, we will review the details you have provided and inform you of our analysis and decision.
    Regards,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Vinod Musunuri
    Reply
    |
    Jul 21, 2021

    CaseNomineeObjective.searchObjectiveHistoryForCase is not performing as poorly as before but there is still the issue of unnecessary executions that needs to be improved. We are still hitting the DB a fair number of times unnecessarily

  • Guest
    Reply
    |
    Jul 15, 2021

    Hi Vinod,

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

    Related to the third issue you raised about the performance of the CaseNomineeObjectiveFactory.searchObjectiveHistoryForCase method,a SQL performance issue was resolved in method CaseNomineeObjective.searchObjectiveHistoryForCase in 7.0.9.0 iFix7 (Ticket 268598)
    and in v8, so while it still does loop, the overhead of any looping should now be less significant than before.

    Have you had the opportunity to determine whether you still feel that this performs poorly on 7.0.9.0 iFix 7, or was this issue raised based on earlier performance 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
    |
    Jun 30, 2021

    Hi Vinod,

    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.