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

RELATED IDEAS

Curam modeled REST API class we need a way to read headers

We have REST APIs to expose to other webapplications. Most of them are GET, where we fetch resources from Curam SPM to the calling application/interfaces.


As part of the request we expect a unique key (GUID) to be passed in request header by them which will be consumed for fetching data in Curam.


In Curam modeled REST API class we are not finding a way to read those headers from the HTTP Request. Please note we cannot pass this “guid” in query parameter for security constraints which works fine in Curam as we receive it in the input as part of modelled struct.


Hence we would like to know how Curam supports to get the key-values passed in the request header for any GET operation.



There is documentation in Curam to support some defined request headers,


https://www.ibm.com/docs/en/spm/8.0.1?topic=methods-request-headers


We would like to know how to send the custom key-values and access those in our REST API java method

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

government needs it
CURAM:Workarounds + Proposed Solution

We have REST APIs to expose to other webapplications. Most of them are GET, where we fetch resources from Curam SPM to the calling application/interfaces.


As part of the request we expect a unique key (GUID) to be passed in request header by them which will be consumed for fetching data in Curam.


In Curam modeled REST API class we are not finding a way to read those headers from the HTTP Request. Please note we cannot pass this “guid” in query parameter for security constraints which works fine in Curam as we receive it in the input as part of modelled struct.


Hence we would like to know how Curam supports to get the key-values passed in the request header for any GET operation.



There is documentation in Curam to support some defined request headers,


https://www.ibm.com/docs/en/spm/8.0.1?topic=methods-request-headers


We would like to know how to send the custom key-values and access those in our REST API java method
  • Attach files
  • Benoit Tremblay
    Reply
    |     Sep 28, 2023

    CoE sees that IDs are sent based on API, we can close this issue.

  • Mahesh Hadimani
    Reply
    |     Jan 17, 2023

    Is there any update on this, we still have an outstanding issue with the project to pass in identifiers for cross tracking requests accross various components of the solution.

  • 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