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 Raguram Ramasubbu
Created on Dec 7, 2021

RELATED IDEAS

Include additional information in Un-handled server exception along with Stack Trace

Unhandled server exception is occured for various reasons and most of the time when it's not handled properly, it gets displayed in end-user's UI. When end-user come across the un-handled server error multiple times in a day, it doesn't give a good impression on application.

When the Curam Production application produces thousands of Unhandled server exceptions in a day from various type of transactions (online, deferred, etc..), it's hard to identify and categorize the errors from stacktrace as it doesn't log the respective Username who have initiated the transactions or respective primary key information such as caseID, concernRoleID, evidenceDescriptorID, etc..


It would be helpful to If stack trace logs the below information for detailed analysis.


1. User who has initiated the transaction. This can be either end user (online transaction), batch process name, Deferred Process name or web service, etc.?

2. The respective primary key information such as caseID, concernRoleID, etc.. from where the issue has been triggered? The primary key information is logged not in all instances.

Customer Name North Carolina - Dept of Health and Human Services
  • Attach files
  • Raguram Ramasubbu
    Reply
    |     Apr 8, 2022

    Thank You, Sheryl for your updates. I appreciate your effort for considering in the future roadmap.

  • Guest
    Reply
    |     Apr 6, 2022

    Hi Raguram,

    We have reviewed your enhancement suggestion.

    Based on the information provided, our understanding of your request is as follows:

    You are requesting that the content of the infrastructure messages that are logged when un-handled server exceptions occur be enhanced to include additional identification details such as Case ID to help identify and diagnose the issues that have occurred.

    The theme is aligned with our current strategy for our product and we have accepted your suggestion as a consideration for a future release.

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    Regards,
    Sheryl Brenton, SPM Product Management Team

  • Raguram Ramasubbu
    Reply
    |     Apr 6, 2022

    Hi Sheryl Brenton,

    Good morning. I just wanted to follow up to check whether you have any updates. Please let me know if you are looking for any additional information.

    Thanks,

    Ragu.

  • Guest
    Reply
    |     Mar 3, 2022

    Hi Raguram,

    Thank you for providing the additional information requested. Within the next 30 days we will review the details you have provided and inform you of our analysis and decision.

    Regards,
    Sheryl Brenton, SPM Product Management team

    Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.

  • Raguram Ramasubbu
    Reply
    |     Mar 1, 2022

    Here are the attachments.

    Thanks,

    Raguram.

    UHSE_TextHelper...
    UHSE_Record-Not...
    UHSE_ProgramRec...
    UHSE_ORA-02049.txt
    UHSE_NumberForm...
    UHSE_DPEnactmen...
    UHSE_ID_RECORD_...
    UHSE_DPEnactmen...
    UHSE_AssessBene...
    UHSE_DeferredSu...
    UHSE_TextHelper_CallServer.txt
    Open full size
    UHSE_Record-Not-Found_Caseheader.txt
    Open full size
    UHSE_ProgramRecommendation.txt
    Open full size
    UHSE_ORA-02049.txt
    Open full size
    UHSE_NumberFormatException.txt
    Open full size
    UHSE_DPEnactment_RelationshipCalculator.txt
    Open full size
    UHSE_ID_RECORD_CHANGED.txt
    Open full size
    UHSE_DPEnactment_PerformDeferredRecalculationsFromPrecedentChangeSet.txt
    Open full size
    UHSE_AssessBenefitCase_Failed.txt
    Open full size
    UHSE_DeferredSubmission.txt
    Open full size
    UHSE_TextHelper_CallServer.txt UHSE_Record-Not-Found_Caseheader.txt UHSE_ProgramRecommendation.txt UHSE_ORA-02049.txt UHSE_NumberFormatException.txt UHSE_DPEnactment_RelationshipCalculator.txt UHSE_ID_RECORD_CHANGED.txt UHSE_DPEnactment_PerformDeferredRecalculationsFromPrecedentChangeSet.txt UHSE_AssessBenefitCase_Failed.txt UHSE_DeferredSubmission.txt
  • Raguram Ramasubbu
    Reply
    |     Mar 1, 2022

    Thank You, Sheryl for your continuing investigation.

    • The 'Outcome Plan' stacktrace was shared as an example. We certainly build a business logic and implement a custom message to handle it better. However, if the un-handled server error shares the respective ID, it would be easier for the developer to identify the respective case and business scenario to recreate and fix the issue.

    • For your further analysis, I've attached various UHSE full stack trace from different functionalities. Please go over these and let me know if you are looking for additional information.

    Thanks,

    Raguram.





  • Guest
    Reply
    |     Feb 21, 2022

    Hi Raguram,

    Thank you for the responses to our questions and the two examples you provided.

    We have some follow-up questions and requests.

    We would like to better understand the Outcome Plan related stack trace example you provided in "664002BZ3G added attachment, UHSE_OutcomePlan.txt".
    When reading back the context panel details for this screen, do you always expect that Outcome Plan be present and if so, why is it not? If the record may or may not be there, that scenario is usually handled by writing business logic to handle the RecordNotFoundException and produce a more user friendly message or log the more specific details into the logs at that layer.

    There isn't enough of the exception trace present in the other example for us to try and understand what might be the cause and possible resolution to this Un-handled server exception.

    In general, these types of UHSEs should not be happening in the product and we would like to see more examples of these exceptions (with the full stack trace included) if you could provide them, in order to see if we can begin to identify patterns and better understand what further help the system could give to help you to diagnose them.

    The Outcome Plan example appears related to a customization you have made. Are there any examples you could also provide that you feel are UHSEs being caused by OOTB functionality?

    Also, any examples from the three areas you provided where the majority of the UHSE's are occurring would be useful:
    56,815 (~39%) exceptions were thrown for ‘DPEnactment’.
    22,874 (~16) exceptions were thrown for ‘PerformDeferredRecalculationsFromPrecedentChangeSet’.
    13,039 (~9%) exceptions were thrown for ‘DelyadEligibilityAssessment.reassessCase’.

    Regards,
    Sheryl Brenton, SPM Product Management team

    Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.

  • Guest
    Reply
    |     Feb 14, 2022

    Hi Raguram,

    Thank you for providing the additional information requested. Within the next 30 days we will review the details you have provided and inform you of our analysis and decision.

    Thank you,
    Sheryl Brenton, SPM Product Management team
    Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.

  • Raguram Ramasubbu
    Reply
    |     Feb 7, 2022

    Hi Sheryl Brenton,

    Thank you for your time taking to review and provide the updates. Please see my response for your questions.

    1. As per the analysis performed for the last two weeks (01/24 to 02/04), In total, there were around 145,291 ‘Un-Handled’ server exceptions and the majority of errors were from the following.

    • 56,815 (~39%) exceptions were thrown for ‘DPEnactment’.

    • 22,874 (~16) exceptions were thrown for ‘PerformDeferredRecalculationsFromPrecedentChangeSet’.

    • 13,039 (~9%) exceptions were thrown for ‘DelyadEligibilityAssessment.reassessCase’.

    2. For your reference, I have attached two exception logs. When we look at these exceptions from the server logs, we may not be able to track back as it doesn’t give any reference from where (case, participant, or any record ) the exception was thrown. Thus, it would be better if the exception includes additional key related information such as caseID, concernRoleID, outcomePlanID or the unique key to easily identify the source record and fix the respective problems.

    This would help to minimize the number of UHSE produced per day. Please let us know if you are looking for additional information.

    Thanks,

    Raguram.

    UHSE_OutcomePla...
    UHSE_Omega3Serv...
    UHSE_OutcomePlan.txt
    Open full size
    UHSE_Omega3ServerException (-130002).txt
    Open full size
    UHSE_OutcomePlan.txt UHSE_Omega3ServerException (-130002).txt
  • Guest
    Reply
    |     Jan 11, 2022

    Hi,

    We would like to gather further information from you related to this enhancement request.

    1. Are there particular areas of the application which are proving problematic and have you determined that this is a usage problem rather than an OOTB SPM product issue?
    2. Would it be possible for you to provide a few examples of such errors? The PII data can be removed from the examples, it is just to get a sense of what type of errors you are referring to and where they are originating from within the application.

    Please provide the requested information within 30 days so we may proceed with our evaluation. If we do not hear from you within that timeframe we will have to close the request due to insufficient information.

    Thank you,
    Sheryl Brenton, SPM Product Management team

    Note: We have improved the RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.

  • Guest
    Reply
    |     Dec 8, 2021

    Hi,

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required in order to complete our evaluation, we will send you a request for more information.

    Thank you,
    Eloise O'Riordan, SPM Product Management team

    Note: We have improved the RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
    Additional details can be found here.