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
Categories Outcome Management
Created by Marc Zimmermann
Created on Jul 5, 2016

Auto-population of outcome plan with only with recommended objectives and activities

When the system property curam.outcomeplanning.outcomePlanAutoPopulateEnabled=true is set, new outcome plans are auto-populated with all objectives and activities for which a relevant recommendation exists (entity 'RecommendationAdmin').
There should either be a configuration option to define per individual recommendation (outcome plan/objective, outcome plan/activity and objective/activity etc.) whether it should be considered or not by the auto-population functionality.
Or it should at least be controllable through configuration how recommendations of the different recommendation types ‘Advised', ‘Discretionary' and ‘undefined (blank)' are handled (entity 'RecommendationAdmin', attribute 'RecommendationType'). For example: it should be possible to instruct the system to automatically add only those objectives and activities to the outcome plan, whose recommendation type is 'Advised' - in turn, objectives and activities, whose recommendation type is either undefined (blank) or 'Discretionary', should not be automatically added.

  • Attach files
  • Guest
    Reply
    |
    Sep 15, 2016

    Hi Marc,

    We acknowledge that this enhancement request is valid. However, it does not align with our current roadmap strategy and therefore it will not be addressed in the foreseeable future, it is for this reason that we are rejecting your request.

    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 tea

  • Guest
    Reply
    |
    Jul 8, 2016

    Hi Marc,

    Thank you for your enhancement request. We require some further analysis to determine whether or not it can be considered in a future release. I will provide another response when this investigation is complete.

    Thanks again,
    Eloise O'Riordan, Cúram SPM Offering Management team