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 Mar 17, 2025

RELATED IDEAS

CER to support more than one match in readall clause

OOTB there are a number of ruleclasses and rulesets.

We can obtain rule objects using a 'readall' and moreover, some rules support a 'match' attribute which helps limit the objects returned.

For example,

<readall ruleclass="CaseHeader" ruleset="CaseEntitiesRuleSet">

<match retrievedattribute="caseID">

<reference attribute="caseID" />

</match>

</readall>

However, only 1 match is supported OOTB. The rules can filter objects post the readall but this can lead to concerns, especially around unexpected dependencies being created.


In several circumstances, it would be ideal to have more than 1 match critieria to enable more specific objects to be returned, no need for filtering logic and hence, rules readability and maintainence is improved.

See example below. If there was a second match item using typeCode there would be no need for the list item expression logic. Makes rules easier to read/maintain, etc.

Moreover, this returns back all communications for the case creating un-necessary change items in the dependency tables.


To reiterate, this idea is for the SPM rules framework to support more than 1 match criteria.


image.png
image.png
Customer Name Scottish Government
Persona Based Summary

As a system user, I want the rules to match on more than 1 criteria so less rule objects are returned and hence, less post readall filtering and less change items created.
Market Segment Eligibility & Entitlement
Type of Request Idea
Market Opportunity

Makes coding rules easier and we know this is a complex activity on all Curam projects. Also reduces subsequent processing if we are not creating unexpected change items.

Easier to sell our rules as configuration and simple to implement.
Usage frequency + #/type of users impacted

This enhancement would be of benefit every time rules are run, online and within batch. It would be a significant improvement and help rules maintainence.
CURAM:Workarounds + Proposed Solution

So Scottish Government are using filtering logic in the rules but due to unexpected precedent change items being created, then SQL data deletions and ongoing monitoring of dependency tables is being done.
  • Attach files
      Drop here to upload