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 Not under consideration
Created by Guest
Created on Apr 14, 2020

CLIENT has a requirement to add the rules for custom MO prior quarter program

CLIENT has a requirement to add the rules for custom MO prior quarter program

Hence customized 'convertTimeLineAttributeToElement' method for attributes named 'eligiblePrograms' and 'householdSizes'

However, no hookpoint exists to allow such a customization to be made compliantly. Hence they have used the decompiled copy of OOTB class and customized convertTimeLineAttributeToElement.

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |
    Oct 7, 2020

    Hi Maribeth,
    We have not received the additional information we previously requested from you that would allow us to fully understand and evaluate your enhancement request. Since we have not received the information within the 30 day timeframe, we are closing this request.

    If you are able to provide the additional information in the future, please open a new enhancement request and we will be glad to review. We do appreciate the time you take to share your ideas with us and utilize your inputs to improve our product offering.

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

  • Guest
    Reply
    |
    Jun 25, 2020

    Hello. Your feedback has been provided to the developer. I'll post their response here upon receipt.

    Thank you,

    Maribeth Kane

  • Guest
    Reply
    |
    Jun 19, 2020

    Hi Maribeth,

    Thanks for your previous response.

    To achieve the requirement, the CER rule attributes for the custom MO prior quarter program can be implemented as needed. Date and/or timeline manipulation can be done at that point in the rules. The rules can then be annotated appropriately to ensure they are extracted for display rule purposes.

    Please provide an explanation of why your requirement was not achievable in rules.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Jun 9, 2020

    Attachment (Description): As indicated.

  • Guest
    Reply
    |
    Jun 9, 2020

    Hello. Following is feedback from our developer. Also attached is the file he references. Please let me know if you have any other questions.

    Regards,

    Maribeth Kane

    The class DecisionDetailsRuleObjectXMLFormatter was modified to manipulate the date used by two rule attributes when formatting the rule objects. The customized version of this class is attached for reference.

  • Guest
    Reply
    |
    May 12, 2020

    Hello. I am waiting for the developer to respond to your feedback. Once I have it, I'll provide it here.

    Regards,

    Maribeth Kane

  • Guest
    Reply
    |
    May 11, 2020

    Hi Maribeth,

    In order to evaluate your request, we require that you provide more detail on why you need to do this so that we can fully understand your requirements.

    In general, there should be no need to change an infrastructural class like DecisionDetailsRuleObjectXMLFormatter to handle specific rule attributes.

    The rule attributes 'eligiblePrograms' and 'householdSizes' would generally just need to be annotated in the display ruleset for them to be available in the generated display rule XML e.g.





    More examples can be found here in the Knowledge Center.
    https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.10/com.ibm.curam.content.doc/HowToBuildAProductCookbook/r_PRODHOW_Building2MainCategoryDisplayClassSample1.html

    Let me know after reviewing this information if this request is still required and if so the details why.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Apr 15, 2020

    Hi Maribeth,

    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,
    Shane McFadden, Cúram SPM Product Management team