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 Future consideration
Categories Social Program Management Platform
Created by Guest
Created on Mar 3, 2020

RELATED IDEAS

Require configurable validations for withdrawal process of an Application Case

As per the current implementation of curam.workspaceservices.intake.impl.WithdrawalRequestImpl class the system is behaving like:

When a user withdraw an Application Case, he can either select a withdrawal reason or enter details in other withdraw reason but State of Missouri allows
user to enter both details at same time.
The State of Missouri has a requirement to remove OOTB validations ERR_TWO_REASONS_ENTERED from crossFieldValidation() method and remove ERR_APPLICATION_CANNOT_BE_WITHDRAWN from insert() method from curam.workspaceservices.intake.impl.WithdrawalRequestImpl class.
As, no configurable validations are available for the mentioned validations, Hence state team have used the decompiled copy of OOTB class and removed the validations from code instead of controlling them with configuration validation settings.

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |     Mar 27, 2020

    Hi Maribeth,

    We acknowledge that this enhancement request has been accepted for consideration.

    It may not be delivered within the release currently under development, however, the theme is aligned with our current multi-year strategy and will be considered for a future release.

    IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

    Thank you for your interest in the Cúram product.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     Mar 4, 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