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 Future consideration
Categories Social Program Management Platform
Created by Guest
Created on Jul 21, 2016

RELATED IDEAS

Cannot store concern role images in a CMIS CMS

The current implementation of our CMIS integration functionality does not support the ability to store participant photos that are stored on the ConcernRoleImage table in a Content Management System when CMIS integration is enabled.

We need to consider providing this capability, including an application property to control whether images should be stored in the CMS or C�ram database.

This enhancement was raised by our customer who believes this will allow them to make better use of their CMS solution, in terms of consistency of approach and also to prevent the need to store large image files in the database.

The requirement was also considered as part of the original set of requirements captured when CMIS integration functionality was first introduced and included the following:

1) Store a participant image selected from a local server in the CMS when attaching an image to a participant
2) Retrieve participant image from the CMS when displaying a participant image
3) Provide ability to browse the Document Management system and select a participant image
4) Provide an option to store a new version of a participant image in the CMS if the existing image is removed and a new image added

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
  • Guest
    Reply
    |     Aug 6, 2016

    Hi,

    We acknowledge that this is a valid enhancement request. It will be considered for inclusion in a future release of the product. Thank you for your interest in the Cúram product.

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