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 Future consideration
Created by Garry Heap
Created on Sep 16, 2022

Remove Personal Info PII from logs


It recently came to light that PI was leaking into the SPM logs. SOme of this has been traced to OOTB Informationals, for example "Caused by: curam.util.exception.InformationalException: This phone number already exists for FIRSTNAME LASTNAME (32)."


Request is to have a mechanism to disable this being logged (understanding that the message may be a valid thing for the caseworker to see).


Due to this, and related issues, the client has had to disable all access to logs as it is a security risk with the unknown amount of PI going into logs.


This then has the obvious impact of making support/debug etc difficult.


Customer Name Scottish Government, Ontario
Market Segment Eligibility & Entitlement
Type of Request Customer Requirement
Market Opportunity

impact of making support/debug etc difficult.

  • Attach files
  • Garry Heap
    Reply
    |
    Feb 24, 2023

    Here is another example, happened again last night during batch run


    [Thu Feb 23 22:00:23 UTC 2023] [servername] [batch.sg.sh] [CustomLoaderBatch] [INFO] ```BATCH CustomLoaderBatch REPORT - 21:58:08.087 INFO StagingID:1859235571 curam.util.exception.InformationalException: This phone number already exists for firstname surname (age).

    at curam.util.exception.InformationalManager.buildAllExceptionsNoTrace(InformationalManager.java:427)

    at curam.util.exception.InformationalManager.buildAllExceptionsNoTrace(InformationalManager.java:394)

    at curam.util.exception.InformationalManager.buildAllExceptionsNoTrace(InformationalManager.java:378)

    at curam.util.exception.InformationalManager.failOperation(InformationalManager.java:222)

    at curam.dynamicevidence.validation.impl.MultiFailOperation.failOperationWithMPO(MultiFailOperation.java:115)

    at curam.dynamicevidence.validation.impl.DuplicateEvidenceAttributeValidator.validateDuplicateAttributes(DuplicateEvidenceAttributeValidator.java:716)

    at curam.dynamicevidence.validation.impl.DuplicateEvidenceAttributeValidator.validateEvidence(DuplicateEvidenceAttributeValidator.java:315)

    at curam.dynamicevidence.validation.impl.DuplicateValidator.validate(DuplicateValidator.java:394)

    at curam.dynamicevidence.validation.impl.DynamicEvidenceValidation.validate(DynamicEvidenceValidation.java:165)

    at curam.dynamicevidence.impl.StandardDynamicEvidenceImpl.validate(StandardDynamicEvidenceImpl.java:704)

    at curam.core.sl.infrastructure.impl.EvidenceController.performValidations(EvidenceController.java:8370)

    at curam.core.sl.infrastructure.impl.EvidenceController.modifyEvidence(EvidenceController.java:4392)

    at curam.pdc.impl.PDCPhoneNumber.modifyPhoneNumberEvidence(PDCPhoneNumber.java:362)

    at curam.pdc.impl.PDCPhoneNumber.modify(PDCPhoneNumber.java:270)

    at curam.core.impl.MaintainConcernRolePhone.modifyPhoneNumber(MaintainConcernRolePhone.java:119)

    at curam.core.facade.impl.Participant.modifyPhoneNumber(Participant.java:1240)

    at curam.core.facade.impl.Person.modifyPhoneNumber(Person.java:6370)

  • CLAIRE MCGAFFEY
    Reply
    |
    Nov 9, 2022

    Hi Gary,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:

    • You are requesting an enhancement to provide the ability to specify that certain messages should not be included in system logs in order to help prevent PII from being included in the logs.

    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.

    Thank you,

    Sheryl Brenton, SPM Product Management Team

  • CLAIRE MCGAFFEY
    Reply
    |
    Sep 26, 2022

    Hi Gary,

    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 to complete our evaluation, we will send you a request for more information.

    Thank you,

    Sheryl Brenton, SPM Product Management Team