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 Guest
Created on Mar 10, 2020

Need of Additional pre/post events in EvidenceController.

OOTB EvidenceController provides pre/post events for several different actions including:

1) EvidencePreActivationEvents
2) EvidenceActivationEvents
3) EvidencePreModifyEvent
4) EvidenceValidationEvents

However, there are several actions that lack event hookpoints. The two of concern with this RFE are the following:
1) preInsert
2) postModify

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |
    Jul 24, 2020

    Hi Shane,

    Requirements -

    The system should handle the following things while inserting/modifying the evidence of type "Names" in participant data case :

    Update the first name, last name, middle name to upper case.
    If there are any hyphens, It should be replaced with spaces.
    All the punctuation should be removed on first name, middle name and last name.

    Please refer the attached refer zip for reference.

    Thank you,

    John Coombes

  • Guest
    Reply
    |
    Jul 24, 2020

    Attachment (Description)

  • Guest
    Reply
    |
    Jul 24, 2020

    Hi Maribeth,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
    * You need additional pre/post events hook points in EvidenceController for preInsert and postModify that will allow you to compliantly tweak the Names data entered (for example; change the first name, last name, middle name to upper case, replace any hyphens with spaces and/or remove any punctuations) prior to storing it on the database.

    The theme is aligned with our current multi-year strategy for our product and has been accepted 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,
    Shane McFadden, IBM SPM Offering Management team

  • Guest
    Reply
    |
    Jun 9, 2020

    Hello. Following are our developer's response to your query. Please let me know if you have any other questions.

    Regards,

    Maribeth Kane

    Please add the following response

    Requirements -

    The system should handle the following things while inserting/modifying the evidence of type "Names" in participant data case :

    Update the first name, last name, middle name to upper case.
    If there are any hyphens, It should be replaced with spaces.
    All the punctuations should be removed on first name, middle name and last name.

    Technical details -

    The following method is overriden in a custom listener class

    @Override
    public void preModify(EIEvidenceKey eiEvidenceKey, EvidenceDescriptorModifyDtls paramEvidenceDescriptorModifyDtls,
    Object paramObject, EIEvidenceKey parentKey) throws AppException, InformationalException {

    if (CASEEVIDENCE.NAMES.equals(eiEvidenceKey.evidenceType)) {

    firstName = firstName.toUpperCase();
    lastName = lastName.toUpperCase();
    middleName = middleName.toUpperCase();

    firstName = firstName.replace('-', ' ');
    lastName = lastName.replace('-', ' ');
    middleName = middleName.replace('-', ' ');

    firstName = firstName.replaceAll("\\p{P}", "");
    lastName = lastName.replaceAll("\\p{P}", "");
    middleName = middleName.replaceAll("\\p{P}", "");


    firstName = firstName.replaceAll("[^\\w\\s]", "");
    lastName = lastName.replaceAll("[^\\w\\s]", "");
    middleName = middleName.replaceAll("[^\\w\\s]", "");

    if (!firstName.isEmpty() && !lastName.isEmpty()) {
    initials += firstName.charAt(0) + "" + lastName.charAt(0);
    }

    if (!firstName.isEmpty() && lastName.isEmpty()) {
    initials = firstName.charAt(0) + "";
    }

    details.getEvidenceData().getAttribute("firstName").setValue(firstName);
    details.getEvidenceData().getAttribute("lastName").setValue(lastName);
    details.getEvidenceData().getAttribute("middleName").setValue(middleName);
    details.getEvidenceData().getAttribute("initials").setValue(initials);

    ....
    }
    }
    As there is no existing event hookpoints for preInsert and preModify methods, The team implemented the above requirements non compliantly via Module.

  • Guest
    Reply
    |
    May 12, 2020

    Hello. I am waiting for the developer to respond to your feedback. Once I have it, I'll provide it here.

    Regards,

    Maribeth Kane

  • Guest
    Reply
    |
    May 11, 2020

    Hi Maribeth,

    In order to evaluate your request, we require that you provide more detail so that we can fully understand your requirements.

    Can you clarify why you need the hookpoints, what the use case or requirements are that you are implementing, and why the existing hookpoints aren't sufficient?

    This might give us more insights as to whether this is a requirement that might be relevant to other customers that we should put into the product.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Mar 11, 2020

    Hi Maribeth,

    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,
    Shane McFadden, Cúram SPM Product Management team