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 Andrew Wylie
Created on Jan 23, 2019

System timeout warning popup remain open after countdown

Current codebase Cúram v7.0.1.1 ifix3

Cúram System timeout warning popup remain open after countdown to zero.

1. Currently when a user session is nearing expiration, a popup dialog appears 2 minutes before the session is set to expire on the server, with a message warning the user. The message counts down 2 minutes. Continue and Quit are the two options available.
a. Continue closes the popup dialog and allows the user to continue their work
b. Quit closes the popup and redirects the user to the Cúram logon page.
2. When the countdown reaches zero, the system automatically Quits the application and redirects the user to the Cúram logon screen with a message that their session has expired being displayed.

Customer Name Ontario - Ministry of Community and Social Services
  • Attach files
  • Guest
    Reply
    |
    May 30, 2019

    Hi Andrew,

    We have evaluated your request and have determined that it cannot be implemented at this time when compared against other priorities we have on our backlog.

    Your request may be resubmitted for consideration after 12 months from the date of decline.

    Thank you for your interest in the Cúram SPM product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Apr 25, 2019

    Hi Andrew,

    In order to evaluate your request, we require that you provide more detail on the business use case you are trying to support so that we can fully understand your requirements.
    What would the proposed flow in the application be if this enhancement was completed? I.e. On a session time out, what must the user do to continue working with the application, what is the proposed screen flow for this?

    We have a security concern with your proposal. For example, if the user left the machine idle after filling in some personal data (for example on a IEG page). When the session times out and the popup remains open, the personal data is still visible in the main page behind the popup. Anybody can view the data until the popup is manually closed and redirected to a different/login page.

    In relation to the other request about redirecting to an alternative page after a timeout. We suggest that you customize the OOTB Curam login page to redirect/forward the HTTP request coming into Curam login page to whatever page you want. The flow would be as follows:
    • The session timeout occurs and the popup is displayed for some minutes before redirecting to Curam login page.
    • The Curam login page receives the request and forwards it to the customer’s SSO login page.
    • Based on the customer’s SSO configuration, the SSO will allow the user to enter the credentials to authenticate
    • Or in case SSO session is still valid (if the SSO timeout is more than Curam’s default timeout of 30 mins), the SSO will send SAML assertion (or whatever trust association it has with the appserver) to the appserver to refresh the timeout/LTPA.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Jan 24, 2019

    Hi Andrew,

    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