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 Mar 21, 2017

RELATED IDEAS

Participant Data Case creation to be supported for Custom Concern Role Types

OOTB functionalities such as PDC creation and Population of evidence
details should be supported for custom Concern Role Types, or a
provision should be made to select the concern role types for which
these functionalities can be applied to.

1. Participant Data Case creation:
Curam OOTB creates Participant Data Cases for two OOTB Concern Roles: Person and Prospect Person. The Employment Management Solution on the AMS project in Vienna requires a new custom Concern Role - Enterprise and the dynamic evidences functionality should be reused for this new Concern Role type.

However, adding this new Concern Role alone in the code table ConcernRoleType does not suffice as OOTB does not let create Participant Data Case for newly added Concern Role because of validations checking for only Person and Prospect Person Concern Role types.

2. Populating Evidence Details:
OOTB Curam supports display of Dynamic Evidence data only for the Person and Prospect Person Concern Roles. The Employment Management Solution requires an additional Concern Role - Enterprise. Hence the OOTB Codetable ConcernRoleType has been extended by the inclusion of a new Concern Role Type.

While trying to display the Dynamic Evidences stored against the Participant of this new custom Concern Role type on a Custom page (under a custom navigation) via the OOTB API, the OOTB API does not return Evidence information including the Evidence Corrections for this new Concern Role Type.
The API returns data only for OOTB Person and Prospect Person Concern Role types. The Core OOTB API needs to be made extensible to allow the API to fetch Evidence data even for newly added Concern Roles.

Customer Name Austria - Arbeitsmarktservice Osterreich (AMS)
  • Attach files
  • Guest
    Reply
    |     May 17, 2017

    Hi Slobodanka,

    We have evaluated your request and have determined that it cannot be implemented at this time as it does not align with our current roadmap strategy and it is therefore not something that we plan to address in-product.

    PDC solution was architected and implemented strictly to the Person and Prospect Person, it is not a generic implementation that can be extended to other concern role types.
    It would require redesign-rearchitecture to support the requested enhancement and at this time, we do not see the value in this enhancement request for the product. Support for Person and PropsectPerson concern role types satisfies the majority of customer usage at present in terms of capturing and maintaining evidence at participant level so there isn't a pervasive need to justify the cost of implementing a generic approach.

    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 team

  • Guest
    Reply
    |     Mar 22, 2017

    Hi Slobodanka,

    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