Curam by Merative Ideas Portal

Shape the future of Curam!

We invite you to shape the future of Curam, 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 Curam team to refine your idea

Help Curam prioritize your ideas and requests

The Curam 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 23, 2022

RELATED IDEAS

key needed to implement REST DELETE operation

There is a limitation in the product as it doesn’t allow additional information to be passed in the payload apart from the “key”



e.g. Please consider the following payload , in this case , along with key "obligation_exchange_id": "800782401_A", we have to get metadata and obligation information from interop team.


This is not possible in Curam as it gives following error



Though build rest Passes build rest -Denable.validations=true fails with following error



ERROR: The path parameters for /interface/bdm/obligation-exchange/delete/{obligation_exchange_id} DELETE method of BDMDoJInboundAPI.deleteDOJInbound facade operation do not match one to one with BDMDOJObligationExchangeKey input struct. Extra attributes are present in the input struct.




http://localhost:8080/Rest/v1/interface/bdm/obligation-exchange/delete/800782401_A


{


"obligation_exchange_id": "800782401_A",


"metadata": {


"metadataIdentificationID": "md1",


"transactionControlIdentificationID": "e0d3a750-ef6d-4222-92cf-dffa4814b9c0",


"transactionCount": 1,


"documentSource": "DOJ",


"documentRecipient": "SAM",


"documentFileDateTime": "2021-05-24T11:30:23",


"documentFileName": "FOE.DEBTORS.D20211201.T1550",


"documentFileControlID": 3090,


"documentFileWeekCode": "0000",


"documentFileDayCode": 0,


"documentFileEnvironmentType": "T"


},


"obligation": {


"metadataIdentificationID": "md1",


"obligationArrearsBalance": 10,


"obligationFixedAmount": 2500,


"obligationDebtPercentage": 35,


"obligationVendorCode": "00",


"obligationFixedAmountIndicator": true,


"obligationPaymentAmount": 255,


"obligationOutstandingFeeBalance": 38,


"person": {


"personSINIdentification": 800782401,


"personObligationID": "JJJ1010",


"personObligationIDSuffix": "A"


}


}



}

Customer Name ESDC
Market Segment Eligibility & Entitlement
Type of Request Customer Requirement
Market Opportunity

government needs it
CURAM:Workarounds + Proposed Solution

There is a limitation in the product as it doesn’t allow additional information to be passed in the payload apart from the “key”



e.g. Please consider the following payload , in this case , along with key "obligation_exchange_id": "800782401_A", we have to get metadata and obligation information from interop team.


This is not possible in Curam as it gives following error



Though build rest Passes build rest -Denable.validations=true fails with following error



ERROR: The path parameters for /interface/bdm/obligation-exchange/delete/{obligation_exchange_id} DELETE method of BDMDoJInboundAPI.deleteDOJInbound facade operation do not match one to one with BDMDOJObligationExchangeKey input struct. Extra attributes are present in the input struct.




http://localhost:8080/Rest/v1/interface/bdm/obligation-exchange/delete/800782401_A


{


"obligation_exchange_id": "800782401_A",


"metadata": {


"metadataIdentificationID": "md1",


"transactionControlIdentificationID": "e0d3a750-ef6d-4222-92cf-dffa4814b9c0",


"transactionCount": 1,


"documentSource": "DOJ",


"documentRecipient": "SAM",


"documentFileDateTime": "2021-05-24T11:30:23",


"documentFileName": "FOE.DEBTORS.D20211201.T1550",


"documentFileControlID": 3090,


"documentFileWeekCode": "0000",


"documentFileDayCode": 0,


"documentFileEnvironmentType": "T"


},


"obligation": {


"metadataIdentificationID": "md1",


"obligationArrearsBalance": 10,


"obligationFixedAmount": 2500,


"obligationDebtPercentage": 35,


"obligationVendorCode": "00",


"obligationFixedAmountIndicator": true,


"obligationPaymentAmount": 255,


"obligationOutstandingFeeBalance": 38,


"person": {


"personSINIdentification": 800782401,


"personObligationID": "JJJ1010",


"personObligationIDSuffix": "A"


}


}



}
  • Attach files
  • CLAIRE MCGAFFEY
    Reply
    |     Sep 14, 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 an enhancement to the REST Infrastructure to support the ability to allow additional information to be passed in the payload of a REST Delete operation.

    We do not intend to incorporate this capability into our product as it does not align with the product strategy we have in place for our REST Infrastructure. We are therefore closing this request and do not plan to take any further action.

    Thank you for taking the time to share your ideas with us. Although we cannot pursue all 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 6, 2022

    Hi [Benoit,

    We would like to request further information from you to better understand your business requirements and what you are trying to achieve by including a payload within a DELETE message request.

    Do you need all of that information that you are adding to the payload just to be able to identify the single resource that you are trying to delete? or for some other purpose?

    What it is that you are deleting?

    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 24, 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