Curam by Merative Ideas Portal
Hide about this portal

Shape the future of Curam!

We invite you to shape the future of Curam, 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 Curam team to refine your idea

Help Curam prioritize your ideas and requests

The Curam 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 Under review
Categories Social Program Management Platform
Created by Gary Parker
Created on Apr 4, 2025

RELATED IDEAS

Provide a hook point in the OOTB GenerateInstructionLineItems (GILI) batch to manipulate passed in dates

GILI (chunker) batch selects live financial components to process.

Within the selection criteria, a date range is determined, i.e. financial component nextProcessingDate falling inbetween this calculated range.

The passed in param dates (or financial calendar) are used to help determine this date range but there may be occasions when these dates may need to be manipulated, or calculated on the fly.

Can PD please consider a hook point so that custom logic could be applied to determine the date range used by the GIII chunker for it's financial component selection. It would be a hook point to potentially change the dates passed in (i.e. processingDate, processedDateTo and processedDateFrom) or, to calculate them for that day based on other specific business logic (e.g. a hook to potentially override the setProcessingDates() method).

This gives clients complete flexibility to manage and/or override dates based on their scenarios.

Customer Name Scottish Government
Persona Based Summary

As a batch user I want to be able to manipulate the dates passed into GILI (or calculate them on the fly) due to specific needs to allow correct financial components to be selected for processing.
Market Segment Eligibility & Entitlement
Type of Request Idea
Market Opportunity

The GILI is one of key financial batches that Curam has OOTB. Giving clients more options/flexibility to manage dates used in the selection criteria gives the client full control over processing of which financial components should be selected. It would be an additional selling point and reduce queries/PMR's etc. in this area.
Usage frequency + #/type of users impacted

GILI is run every night on most projects. The hook point being asked for would either be used every night as well if dates are being calculated there and then, OR used in specific scenarios (based on client needs).
CURAM:Workarounds + Proposed Solution

There is no workaround.

  • Attach files
      Drop here to upload
    • Admin
      Graham McCrindle
      Reply
      |       Apr 10, 2025

      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,

      Graham McCrindle, CURAM Product Management Team