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,
Post an idea
Upvote ideas that matter most to you
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
Hi Shane,
We have received additional guidance from CMS that the RESTful webservices they are planning to deploy will make use of OAuth. As such, I hope PD will take this into consideration with their design and develop of outbound RESTful webservices support in Curam.
Best regards,
Jason
From CMS:
"Additionally, the REST/JSON migration will involve utilizing OAuth. OAuth provides clients a "secure delegated access" to server resources on behalf of a resource owner. It specifies a process for resource owners to authorize third-party access to their server resources without providing credentials. Designed specifically to work with Hypertext Transfer Protocol (HTTP), OAuth essentially allows access tokens to be issued to third-party clients by an authorization server, with the approval of the resource owner."
Hi Jason,
We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
* For SPM to include basic support for outbound Rest APIs in the form of an intermediary API or service that makes it simpler to call external HTTP APIs, and provides functionality to convert JSON to Java/Curam data types.
The benefit of providing this to customers would make it easier for them to make the external API calls from their code, and particularly the conversion of JSON, where we would use industry-standard 3rd party libraries under the hood. We already provide these libraries for the inbound REST APIs, and the bulk of the functionality needed to convert from Java to JSON, in the current REST infrastructure.
The theme is aligned with our current multi-year strategy for our product and we have accepted your suggestion as a consideration for a future release. Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement.
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.
Regards,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Note: we are currently in the process of improving your RFE experience and will soon transition to an Ideas Portal provided by our trusted business partner Aha!
Further communications with additional details will be shared shortly.
Hi Jason,
Thank you for providing the additional information requested. Within the next 30 days, we will review the details you have provided and inform you of our analysis and decision.
Regards,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Note: we are currently in the process of improving your RFE experience and will soon transition to an Ideas Portal provided by our trusted business partner Aha!
Further communications with additional details will be shared shortly.
Hi Shane,
Yes, you have understood the basic idea. However, please keep in mind, this request is not so much about making implementing outbound REST webservices simpler and easier but more about making the implementation of these webservices consistent, both within a project and across projects.
Regards,
Jason
Hi Jason,
We have reviewed your enhancement suggestion and require more information to properly understand the issue and the business scenario you are trying to support.
Based on the information provided, our understanding of your request is for SPM to include basic support for outbound Rest APIs in the form of an intermediary API or service that makes it simpler to call external http APIs, and provides functionality to convert JSON to Java/Curam data types.
The benefit of providing this to customers would make it easier for them to make the external API calls from their code, and particularly the conversion of JSON, where we would use industry standard 3rd party libraries under the hood. We already provide these libraries for the inbound REST APIs, and the bulk of the functionality needed to convert from Java to JSON, in the current REST infrastructure.
Please let us know if our understanding of your request is accurate 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,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi Jason,
Thank you for providing the additional information requested. Within the next 30 days, we will review the details you have provided and inform you of our analysis and decision.
Regards,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi, MSD in New Zealand have implemented 1 outbound REST service so far based on Jaxon libraries bundled with Curam.
Attachment (Description): CMS timeline for transition to RESTful webservices.