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 Delivered
Categories Income Support
Created by Benoit Tremblay
Created on Mar 22, 2022

Request to provide status update events for PaymentInstrument table

EDSC need different statuses for PaymentInstrument records and we cannot add custom statuses into OOTB codetable. To address this we make up with our derived status in BDMPaymentInstrument table. Whenever a record is inserted or status is modified on PaymentInstrument table the BDMPaymentInstrument derived status should be updated. To address this, please provide events to register whenever a PaymentInstrument is created and whenever a status is created/updated. We could try to leverage event broadcast option but this could not be a correct way as this is not broadcast events to external systems.

Customer Name ESDC
Market Segment WH Government
Type of Request Customer Requirement
Market Opportunity

government requests it

RFP Due Date (If Applicable) Apr 22, 2022
CURAM:Workarounds + Proposed Solution

EDSC need different statuses for PaymentInstrument records and we cannot add custom statuses into OOTB codetable. To address this we make up with our derived status in BDMPaymentInstrument table. Whenever a record is inserted or status is modified on PaymentInstrument table the BDMPaymentInstrument derived status should be updated. To address this, please provide events to register whenever a PaymentInstrument is created and whenever a status is created/updated. We could try to leverage event broadcast option but this could not be a correct way as this is not broadcast events to external systems.

  • Attach files
  • Drake Broussard
    Reply
    |
    Jun 23, 2023

    Hi Benoit,

    We are pleased to inform you that your enhancement request has been delivered in the new release of Merative Social Program Management, version 8.1.0.0 on 19 June 2023.

    Financials processing has been enhanced to provide post insert and post modify hook points for the PaymentInstrument entity.

    This feature enables the compliant implementation of custom processing, such as the ability to store additional payment instrument statuses required for external payment processing.

    For more detailed information on this new capability, please visit Merative Social Program Management Support Docs. https://curam-spm-devops.github.io/wh-support-docs/spm/announcements/810_announcement

    Thank you for taking the time to share your ideas with us. We are now closing this request as delivered.

    Regards,

    SPM Product Management Team

  • CLAIRE MCGAFFEY
    Reply
    |
    May 15, 2023

    Hi Benoit,

    We are pleased to inform you that your enhancement request is included in our upcoming release of Merative Social Program Management v8.0.4.0.

    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

  • CLAIRE MCGAFFEY
    Reply
    |
    Aug 12, 2022

    Hi Benoit,

    We have reviewed your enhancement suggestion. Based on the information provided and discussions with Lab Services staff, our understanding of your request is as follows:

    - You are requesting an enhancement to provide a post processing hook point in the ProcessILIGroup and RollupPmtInstruction specialised readmulti classes, together with a modify event for Payment Instrument entity updates in order to support customizations related to external payment processing.

    The theme is aligned with our current strategy for our product to continue to provide extension points that enable compliant customization of financials processing 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

  • Benoit Tremblay
    Reply
    |
    May 11, 2022

    • Provide a post processing hook in ProcessILIGroup class file. Once a Payment Instrument processing done (either changed to processed, suspended) then invoke custom hook to perform post processing for that payment instrument.

    • Provide Payment Instrument Modify Event. Today in OOTB payment instrument events exist for Insert, Cancel, Regenerate but not for Modify. When a payment instrument is modified for any reason please raise an event such that clients can perform custom processing.

  • Guest
    Reply
    |
    Mar 31, 2022

    Hi Benoit,

    We would like to request some further information to help us evaluate this enhancement request.

    In product, the following two event types are available under the PaymentInstrument event class:
    - InsertPaymentIssued
    - ModifyPaymentIssued

    You can also configure new process enactments for these events that can be used to initiate workflow processes for any custom processing you might then want to execute when the events are raised.
    https://www.ibm.com/docs/en/spm/8.0.1?topic=reference-process-enactment

    Would these existing events and related functionality be sufficient to meet your requirements?

    If not could you explain why?

    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

  • Guest
    Reply
    |
    Mar 23, 2022

    Hi Benoit,

    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