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 Jul 10, 2018

Date selection not triggering onChange event in corresponding input field.

When a user enters a value in a date input field, the 'onchange' event is triggered.

When a user chooses to use the popup date control to choose a date instead, that date value is programmatically set against the input value by Curam OOTB UI code. This means an onchange event is not triggered by the DOM, since its not a user event.

This request is for Curam UI code to additionally trigger an 'onchange' event when setting the value of the input field via the date control.

As per Curam Web client reference document, a FIELD can have a SCRIPT child, to respond to events. However, this is not working for 'onchange' when a user selects a date using the popup date control. This means the customer is unable to tie events into the field changing for a date to control other UI aspects in their page.

  • Attach files
  • Guest
    Reply
    |
    Sep 26, 2018

    Hi Andrew,

    We have evaluated your request and have determined that it cannot be implemented at this time.

    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
    |
    Jul 25, 2018

    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