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 Social Program Management Platform
Created by Guest
Created on Apr 11, 2019

RELATED IDEAS

Window Options in core dialogs

As I suggested in the PMRs TS002103762 and TS002103949 already I think that it should be avoided to set dialog widths that belong to Curam Core, as it is generally not so good to customize a whole dialog just because the width does not fit into a localized version of a dialog. If it cannot be avoided then the width should be set in an embedded vim file if possible, so that only this part is customized then.
This is important for german localisations in general as german texts are over all about 30% larger than english texts.

Customer Name Dataport, anstalt des offentlichen Rechts
  • Attach files
  • Guest
    Reply
    |     May 14, 2019

    Hi Dataport,

    We have evaluated your request and have determined that it cannot be implemented at this time due to the required infrastructure change.

    1. Our understanding of your request is that you want to move the specification of the WINDOWS_OPTIONS and related attributes (height) to the child page (i.e. the VIM) from the parent (UIM) page.
    2. The current schema definition of a VIM which does not support such an option is as designed.
    If we ever wanted to add support at the VIM level for these options, we would need to manage the situation where both options (parent page and included page) are managed - i.e., which takes precedence.
    VIMs are supposed to be re-usable content, which is ‘played’ by the including parent page, it should not dictate to that page how it is ‘played’.

    Therefore, based on this, it seems the best option is for you is to customize the OOTB core page or raise a support case and state that the actual OOTB page, in this case, is too small for the localizable German content you want to add.
    The OOTB label widths are designed to cater for an extra 30% added on for localizable content so this could be a very specific example rather than an application wide issue.

    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 12, 2019

    Hi Dataport,

    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