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 Apr 21, 2020

Client used Replace_superclass on Address to remove the OOTB validations ERR_PDC_ENABLED_INVOCATION_NOT_ALLOWED

Client used Replace_superclass on Address to remove the OOTB validations ERR_PDC_ENABLED_INVOCATION_NOT_ALLOWED on premodify(), premodifyAddress(), premodifyAddressDetails() methods and replaced ERR_ADDRESS_XFV_ADDRESS_LINE1_LINE2 with a custom validation ERR_ADDRESSELEMENT_LINE1_IS_EMTPY in validateUSAddress() method. A hookpoint is required to customize these methods compliantly.

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |
    Oct 7, 2020

    Hi Maribeth,
    We have not received the additional information we previously requested from you that would allow us to fully understand and evaluate your enhancement request. Since we have not received the information within the 30 day timeframe, we are closing this request.

    If you are able to provide the additional information in the future, please open a new enhancement request and we will be glad to review. We do appreciate the time you take to share your ideas with us and utilize your inputs to improve our product offering.

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

  • Guest
    Reply
    |
    Jul 8, 2020

    Hello. Your comments have been provided to the developer. I'll post his response here upon receipt.

    Thank you,

    Maribeth Kane

  • Guest
    Reply
    |
    Jun 25, 2020

    Hi Maribeth,

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

    The API in question is intended for use only when PDC is configured off. When PDC is on, the dynamic evidence capabilities should be used to modify an address.

    We would need to understand why you need to go outside of this before we could open this up for customization as the concern is that by doing what is suggested the dynamic and static versions of the address could become out of sync.
    Can you please outline the requirement that you are trying to solve, what the business need is.

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

  • Guest
    Reply
    |
    Apr 22, 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