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

Add a new idea Subscribe
Status Not under consideration
Categories Universal Access
Created by Sigitas Jakucionis
Created on Mar 12, 2018

RELATED IDEAS

IEG infrastructure to raise an event whenever the user navigates back - forth using back or next buttons

The changed field values are currently not persisted by the infrastructure if the user is going back. Minnesota has a requirement from state to persist data
(we plan to write into datastore) when the user navigates back using the back button. This can't be achieved with the current product and we think this will
be possible if the product can signal an event that the user is navigating backwards and with the event payload stuffed with details about the current page.

We are looking for an event to be raised when the user navigates backwards by clicking on the back button. We've already summarized the
kind of information that we are looking for, in the event payload. If the product can enable us to plugin a CustomFunction, we are
fine with that too, provided if its possible for the custom function to retrieve the information that we are interested in. Basically, the ID &
current state (field values) of the page from which the user is navigating backwards.

As a side note, the above requirement is not applicable for the online IEG scripts and is to be implemented for a custom case side script.

Customer Name Minnesota
  • Attach files
  • Guest
    Reply
    |     Jul 3, 2018

    Hi Sigitas,

    We have evaluated your request and have determined that it cannot be implemented at this time.
    The IEG infrastructure does not save the data when using the Back button but does when using the Next button, this is as designed.

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

    Thank you for your interest in the Cúram product.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     May 15, 2018

    Hi Sigitas,

    Thank you for providing this information.
    We will look into this further and get back to you shortly.

    Thank you,
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     May 14, 2018

    Are you implying that the functionality is available right now in HCR IEG scripts? Or the requested functionality can be built with the infrastructure available as of today?

    We are on IBM Curam 7.0. As of today, OOTB (HCR) when I launch "Apply for assistance with you Health care" script, move to "More about you" page, ,Enter partial information , Click Back and Click Next, I'm shown a blank "More about You" page with all the previously entered information lost.

    The reason why we created this enhancement request is to have some kind of pluggable/customizable mechanism through which we can capture current/partial state of the page when the citizen navigates backward.

    Thanks!

  • Guest
    Reply
    |     Apr 23, 2018

    Hi Sigitas,

    We have tried to re-create your issue however we did not experience the same problem as you described.
    Using the Back/Next IEG navigation buttons should provide the functionality required to persist the data.
    Could this be an issue with your customer implementation? What version of the product are you currently on?
    If you can provide any more information to help us with our evaluation of your problem, that would be very helpful.

    Thank you,
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     Mar 13, 2018

    Hi Sigitas,

    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,
    Sherry Byerly, Cúram SPM Offering Management team