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
Created by Guest
Created on May 5, 2016

There is no unique identifier to identify an instance of an error

Currently when a user reports a C�ram error to IT support staff it is difficult to track down that error in the logs. Staff have to go through multiple logs (each server in a cluster has a separate log) based on approximate time of when user reported the error and a user name as there is no error reference number attached to individual error entries. This is not related to any particular error. This request applies to absolutely all situations where an AppException is thrown and is displayed to a user on the screen. This request is to help with the operational support of C�ram in production.
A made up scenario describing what's happening now:
1. User jsmith is working with case management
2. User invokes case approval at 11:14 AM
3. Case approval fails for whatever reason and reports to the user "case approval failed".
4. User calls IT help desk at 11:25AM and says: "I am jsmith, I have got an error 'case approval failed' at around 11:10AM".
5. IT support tries to figure what went wrong - they search through 6 log files (one for each server in a cluster) for anything related to this user at around 11:10AM (the user was not accurate with time stamp so that makes it more difficult to identify which particular log entries we need to look at).
So what is required is a unique identifier in every error message so that support can identify that instance of the error.

Customer Name New Zealand MSD
  • Attach files
  • Guest
    Reply
    |
    Jan 22, 2021

    Hi Sriramganesh,

    We have re-reviewed your enhancement suggestion.

    We acknowledge the benefit of your suggested enhancement however other features are taking a priority in our planning at this time. Although we will not be addressing this item in the near term, your suggestion will be available for future consideration. This request will be closed and we will not be taking any further action.

    Thank you for taking the time to share your ideas with us. Although we cannot pursue all of the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.

    Regards,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Reply
    |
    Aug 15, 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

  • Guest
    Reply
    |
    Jun 10, 2016

    Creation of RFE from legacy PMR 5,987,999,796