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 Delivered
Categories Verification Engine
Created by Vinod Musunuri
Created on Jun 8, 2021

RELATED IDEAS

Verification Engine performance improvements

Verification Engine has too many inefficient and redundant calls to the database which is causing unnecessary slowness during evidence creation and product delivery creation. We have cases with very long life cycles with cases running over 10 years and monthly income reporting requirements which means we have cases with a number of evidences and related verifications. Some of the cases are failing with time outs during product delivery creation because of inefficient verification engine logic. The below improvements to verification engine are recommended

1. Whenever data related verification configuration is required read data using VerificationConfigurationCacheUtils instead of reading the data by making entity calls.
2. VerificationController.createProductDeliveryVerifications() does repeated verification checks of existing verifications which cases time outs. The problem is specifically with Verification.determineVerificationStatus() methods which reads all evidences related to the participant and does verifications for each of those and with more than 100 evidences on an IC for an evidence link earned income it easily goes to 10K verification checks when there is a need to do only 100 of them
3. VerificationItemProvided details are read in with one query for each record instead of reading the data using joins. When cases have more than a thousand such records this causes performance issues

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

    Hi Vinod,
    We are pleased to inform you that your enhancement request has been delivered in the new release of IBM Social Program Management, version 8.0.1.

    The way that verification engine processing works during product authorization has been enhanced. When evidence is captured for an integrated case for use by product delivery cases, and verifications are configured at the product delivery case level, the verifications are created during product authorization. During the process, the status of each verification that is created is determined.
    An improvement was made to help optimize product authorization, when an integrated case has a large amount of evidence of the same type that requires verification at the product delivery case level. Now, as each new verification is created, the status of only that verification is determined. Previously the status of all existing verifications for the evidence type was evaluated.

    For more information about this new capability, see the following section in the What's New Guide: Enhanced verification engine processing

    Thank you for taking the time to share your ideas with us. We are now closing this request as delivered.

    Regards,
    Shane McFadden, SPM Offering Management team

  • 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 the Verification Engine.

    The theme is aligned with our current strategy for our product to investigate improvements that will help to optimize processing in areas of SPM that are heavily used by caseworkers 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 suggestions related to how verification information is read and how verifications are created within product delivery cases.

    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

    Case workers are mainly impacted during authorize application function which creates a product delivery case and any required verifications. There were many time out due to inefficient and redundant code in the verifications logic. When there are many evidences of the same type on the IC that requires verification then for each such evidence verification logic is being executed in loops even though it is not needed. For evidence 1 when a verification record is being inserted all the previous verification on the cases for the income type are checked. Let us say one PDC already exists on the IC before the creation of the new PDC. Then 100 verifications exists before the creation of the product delivery cases for this particular evidence type. During the new PDC creation 100 new verifications are created. For the first verification being inserted 101 verification records status is determined by checking verification item provided. For the second verification 102 verifications and their corresponding verification items are checked and so on. This itself causes more than 10000 verification status determinations. Imagine an IC on which there are 5 PDCs that require verification for this evidence type. This will lead to more than 25K checks. This is causing time outs and not even allowing PDCs to be created

  • Guest
    Reply
    |     Jul 14, 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.

    We would like to get further information on what type of processing caused you to identified these concerns/problems with the performance of the Verification Engine.

    Are caseworkers affected by this when creating evidence in a case or manually creating a Product Delivery case? Or are administrators seeing this when Product Delivery cases are automatically created by the system?

    What type of case/evidence/verification structure is in place where the timeout issues are occurring? For example, are the Evidence and Verifications being created in an Integrated Case, or in the Product Delivery cases? or both?

    How often are the Product Delivery cases created? In cases where there are monthly income reporting requirements and a number of evidence records and related Verifications, can you explain more about why a change of circumstance that results in an update to evidence and the creation of a related verification would impact the creation of a Product Delivery case given it would likely already exist?

    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 10, 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.