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 Sigitas Jakucionis
Created on May 1, 2018

Bootstrap property to start with overriden date and time but letting time to run

Bootstrap property curam.test.override.date only overrides date only and time is always 00:00. This is insufficient for some testing scenarios where application needs to distinguish records by timestamp.

We request a property which makes application start with overridden date and time and from there time would run and records would get differing time stamps.

Customer Name Minnesota
  • Attach files
  • Guest
    Reply
    |
    Jan 8, 2019

    N/A

  • Guest
    Reply
    |
    Jan 7, 2019

    NA

  • Guest
    Reply
    |
    Dec 14, 2018

    N/A

  • Guest
    Reply
    |
    Dec 13, 2018

    N/A

  • Guest
    Reply
    |
    Nov 29, 2018

    N / A

  • Guest
    Reply
    |
    Nov 26, 2018

    N/A

  • Guest
    Reply
    |
    Aug 2, 2018

    Hi Sigitas,

    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

  • Sigitas Jakucionis
    Reply
    |
    Jul 6, 2018

    The requested feature has technical and operational benefits.

    The real-lime use case for this feature is while testing renewals, change in circumstance and reasonable opportunity period in METS.

    The current bootstrap feature in Curam freezes time whenever someone overrides the date. This essentially means the clock doesn't move forward rather is stuck in time. Any feature which uses date time in curam will always have the same date timestamp if the actions were performed subsequently. To accomplish this as of today the development team will have to always stop the server update the bootstrap with updated time and again repeat the process. This process in itself adds additional overhead during testing. Developers cannot use sysdate time related queries or if used then they cannot be tested by override date feature.

    If the bootstrap date can move forward from the given date then it means that the system is working in future and above mentioned overhead can be eliminated.



    1. For example, one of our custom feature called Reasonable Opportunity Period (ROP) is extremely time sensitive and a lot of requirements depend on the latest(by date time) action that took place. Using bootstrap configuration for time travelling would mean that all actions are recorded as if it occurred concurrently. That is, all actions have the same timestamp. This breaks a lot of our implementation that tries to derive the latest action by looking at when it occurred.

    2. Most of our test cycles have the same set of test cases but with a different start date. For example our current test cycle should begin with a sysdate of 9/1/2018 and continues through 9/30/2018 with a cycle duration of 30 days. Currently we configure bootstrap date to 9/1/2018 on the first day of test cycle and reset it 9/2/2018 on the second day of test cycle, so on & so forth. With a moving time, we can set it only once at the beginning of cycle and with 30 passing days, the clock would move from 9/1/2018 through 9/30/2018 with no intervention.

  • Guest
    Reply
    |
    Jul 3, 2018

    Hi Sigitas,

    In order to evaluate your request we require that you provide some real world business examples of where a time aspect of a scenario would need to be overridden for a test.

    If we do not receive this information within 30 days, this request will be closed.

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

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