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 Income Support
Created by Benoit Tremblay
Created on Mar 22, 2022

RELATED IDEAS

In BDM once a priority is calculated we want OOTB to use the priority as is

In BDM once a priority is calculated we want OOTB to use the priority as is. But as part of case deduction creation the OOTB does again override the priority to a different number by processPriority() method. This function should not override the given priority even if that priority is in use. The reason for this is, in BDM the priority for case deductions are allocated in ranges based on its admin Deduction, for example 1-99. Now for any reason if there are case deductions already created up to 99 then the next case deduction for the same type should continue at 99. Whereas OOTB tries to change this to be 100 or even high numbers when next set is already in use. As a result this case deduction will be deducted in lower priority and this is not acceptable.


So we suggest the OOTB function should not be overriding again the given priority atleast based on an application property, as there is no impact in deduction processing by generate ILIs for BDM when two case deductions have same priority

Customer Name ESDC
Market Segment WH Government
Type of Request Customer Requirement
Market Opportunity

Government needs it
RFP Due Date (If Applicable) Apr 22, 2022
CURAM:Workarounds + Proposed Solution

In BDM once a priority is calculated we want OOTB to use the priority as is. But as part of case deduction creation the OOTB does again override the priority to a different number by processPriority() method. This function should not override the given priority even if that priority is in use. The reason for this is, in BDM the priority for case deductions are allocated in ranges based on its admin Deduction, for example 1-99. Now for any reason if there are case deductions already created up to 99 then the next case deduction for the same type should continue at 99. Whereas OOTB tries to change this to be 100 or even high numbers when next set is already in use. As a result this case deduction will be deducted in lower priority and this is not acceptable.


So we suggest the OOTB function should not be overriding again the given priority atleast based on an application property, as there is no impact in deduction processing by generate ILIs for BDM when two case deductions have same priority.
  • Attach files
  • Guest
    Reply
    |     May 13, 2022

    Hi Benoit,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:

    You are requesting that the priority of case deductions created within a case retain their originally configured values rather than being overridden within a case.

    We acknowledge the benefit of your suggested enhancement however other features are taking a priority in our planning at this time.

    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.

    Thank you,

    Sheryl Brenton, SPM Product Management team

  • Guest
    Reply
    |     Apr 5, 2022

    Hi Benoit,

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

    Within an individual PD case when deductions are created, the priority of each deduction that is created is determined using the administratively configured priority as well as the priority entered by the user. As mentioned in the description no two deductions in a case can end up with the same priority because even if a user tries to assign the same priority to two case deductions of the same type the system will update the priority of one of those to a different number. Despite this, the user can determine the ordering they want for deductions in an individual case by updating them as necessary.

    Because of this no deduction in an individual case should end up being deducted in a lower priority than desired.

    If the existing behavior for the creation and prioritization of deductions in an individual case is not sufficient to meet your needs, can you please explain why and provide further details about the business requirements you are trying to meet.

    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,

    Sheryl Brenton, SPM Product Management team

  • Guest
    Reply
    |     Mar 23, 2022

    Hi Benoit,

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

    Thank you,

    Sheryl Brenton, SPM Product Management team