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
This is still an important requirement for MSD.
As per discussion with Merative product management team last week (Jan 2023) I am adding some clarifications about our use cases.
Our use existing and anticipated use cases for modularisation.
Over the last few years we have built a number of REST APIs in CMS to help with data set up for automated testing. For security reasons these APIs must not be deployed into production environment.
Currently we do not have inbound REST APIs for prod use (mainly due to authentication issue listed in https://merative.ideas.aha.io/ideas/SOCPM-I-197 Rest service : Accept authentication credentials in the http header). So at this stage we are just not deploying REST.ear into prod environments.
As soon as we need to introduce inbound APIs (e.g. in order to support custom built responsive app for provider interactions) we will not have a mechanism to isolate test APIs from prod APIs.
We do have existing need to integrate CMS with other NZ government agencies - we expect that we'd have better flexibility for isolating and deployment of changes to REST services for different agencies if we had a good modularisation of REST APIs.
We expect this to help with:
Separating release and change of APIs when dealing with different agencies
Potentially have better tunability for performance requirements of each individual API
Hi Priyabrata,
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.
Shane McFadden, Cúram SPM Product Management team
Hi Priyabrata,
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