Skip to Main Content
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

Status Not under consideration
Created by Guest
Created on Dec 15, 2019

Smart Navigator search criteria should be able to be captured via Weblogic's access logs mechanism

We use extended formatting for Weblogic access logs to capture and log input parameters of incoming requests as described in section "Setting Up HTTP Access Logs By Using Extended Log Format" of https://docs.oracle.com/cd/E13222_01/wls/docs90/config_wls/web_server.html#‌elf

This approach works fine for any facade interaction(using ActionServlet). But input parameters are not available for new Smart Navigator functionality which uses DataServiceServlet.

Issue here seems to be caused by the limitation mentioned below as per https://www.oreilly.com/library/view/java-servlet-programming/156592391X/ch04s04.html
"One word of warning: if the parameter information came in as encoded POST data, it may not be available if the POST data has already been read manually using the getReader() or getInputStream() method of ServletRequest (because POST data can be read only once)."

Having said this, Apache's ActionServlet(as we use in other facades) seems to have a way around this so our logging for Person search for example is able to retrieve request parameters fully, i.e. user entered search criteria along with some other metadata.

It is also worth mentioning the structure of the request parameters for SmartNavigator calls. JSON payload is passed in the key value of form parameter, rather than a value. See RequestParamsForSmartSearch.PNG and RequestParamsForPersonSearch.PNG for a comparison to Person search.

This is not necessarily causing an issue but seems a bit odd.

So, ask here is to update DataServiceServlet implementation to accommodate reading request parameters from http access logs.

Customer Name New Zealand MSD
  • Attach files
  • Guest
    Reply
    |
    Sep 20, 2021

    Hi Gokhan,

    As part of our efforts to be transparent about our intentions with each enhancement suggestion, the offering team has initiated an annual process to carefully review the list of open enhancements.
    As agreed through the account manager for MSD, we are closing this RFE as it was confirmed that it is no longer required.

    We acknowledge the benefit of your suggested enhancement and although we will not take any further action at this time your suggestion will be available in our ideas repository for future consideration.

    We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

    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.

  • Guest
    Reply
    |
    Jan 17, 2020

    Hi Gokhan,

    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

  • Guest
    Reply
    |
    Dec 16, 2019

    Hi Gokhan,

    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