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 Future consideration
Created by Guest
Created on Dec 1, 2017

Closed tabs should not appear when a browser is closed instead of logging out manually

AMS customer is using Kerberos Single Sign On(SSO) to login to Curam application instead of Curam login screens. They don't have a logout button. They just close the browser when they are done as there is no log out button.

We observed the below behavior in Curam
* Login (SSO) to Cúram as Case Worker and open some tabs.
* Close all the open tabs and close browser (IE) as well.
* Close the browser instead of logout as logout feature is removed from AMS application.
* Login (SSO) again. Some tabs are still open which were closed in previous login.

Expected:
If the browser was closed(instead of manual logout), all the closed tabs should not appear, when we login again.

Actual:
If the browser was closed(instead of manual logout), all the closed tabs appear when we login again.

Analysis:
We changed the setting of tabSessionUpdateCountThreshold(added this in
ApplicationConfiguration.properties) from default value 10 to 1. However, setting this to 1 is not the right solution from performance perspective. We saw that CPU usage went high with just 1 user and in a
multi user environment setting this value to 1 is not preferred.

We need a solution to achieve this.

Customer Name Austria - Arbeitsmarktservice Osterreich (AMS), New Zealand MSD
  • Attach files
  • Guest
    Reply
    |
    Sep 28, 2018

    Hi Gopichand,

    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 13, 2017

    Hi Gopichand,

    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,
    Eloise O'Riordan, Cúram SPM Offering Management team