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 Social Program Management Platform
Created by Guest
Created on Mar 27, 2019

RELATED IDEAS

Requesting ability to customize or replace REST's exception mapper with a custom exception mapper in the REST framework

MyBenefits is a web application built for the citizens of Ontario. Currently MyBenefits application interacts with SAMS – Curam application – via SOAP APIs. There is a mapping between Curam's message catalogue and the error messages defined by MyBenefits. Most of the error messages in the MyBenefits application are mapped to Curam's message catalogue. When there is an application exception, it is returned along with its message catalogue in the SOAP response.

Curam V7 will be rolled out to SAMS production shortly. And MyBenefits application will move all its SOAP calls to REST calls. And all the newer API will be developed on REST. Therefore, we built couple of sample REST APIs to test the plumbing. While testing the APIs, we realized that the OOTB's REST response for application or business exception does not contain message catalogue. Also, there is no complaint way to customize OOTB's exception mapper or provide our own exception mapper.

Due to the above limitation, MyBenefits will not be able to start using the REST API's (therefore not being able to use Curam to its full potential).

Displaying the error message description does not allow interfacing systems to clearly distinguish between one error over another. There is no way to distinguish between 2 error messages with the same content but different error code.

At the bare minimum Curam must return the error code to the consuming services. Error description or HTTP status code is not sufficient.

Customer Name Ontario - Ministry of Community and Social Services
  • Attach files
  • Guest
    Reply
    |     Sep 5, 2019

    Hi Santhosh,

    We are happy to inform you that your enhancement request has been delivered in the new release of IBM Cúram Social Program Management, version 7.0.8.0.

    In order to provide adequate information for use by the consumer of the API, for exceptions that originate as application exceptions, the error response returned by the REST APIs has been updated to now include an additional attribute that contains the corresponding unique catalog string identifier of the underlying application exception. For other types of exceptions, this attribute is omitted from the error response.

    We hope that this addition to the product will meet your requirements sufficiently.

    I will now close this ticket as delivered.

    Thank you for your interest in the Cúram product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |     Jun 5, 2019

    Hi Santhosh,

    We acknowledge that this enhancement request based on the addition of the message catalogue to the OOTB REST response for application or business exception 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.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |     May 30, 2019

    Hi,

    Client has agreed that the addition of the message catalogue to the OOTB REST response for application or business exception would satisfy their need.

    Thanks
    Santhosh Kumar

  • Guest
    Reply
    |     May 28, 2019

    Hi Santhosh,

    In order to fully evaluate your request, we require that you provide more details.

    Would the addition of the message catalogue to the OOTB REST response for application or business exception satisfy your enhancement request?

    If we do not receive this information within 30 days, this request will be closed.

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

  • Guest
    Reply
    |     Mar 28, 2019

    Hi Santhosh,

    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