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 Garry Heap
Created on Feb 5, 2020

Various ResolverAdaptors are marked as INTERNAL but are needed in JUnits, e.g. JUnits testing rules Custom Functions

For example StringResolverAdaptor, MoneyResolverAdaptor, DateResolverAdaptor, BooleanResolverAdaptor.

This ends up with the following error in Eclipse:

Access restriction: The method 'MoneyResolverAdaptor.getValue(RulesParameters)' is not API (restriction on required library 'EJBServer/components/Datastore/lib/Datastore.jar')

Fix is to change <accessrule kind="nonaccessible" pattern="curam/expression/impl/*" /> to <accessrule kind="accessible" pattern="curam/expression/impl/*" />

Customer Name Scottish Government
  • Attach files
  • Guest
    Reply
    |
    Feb 11, 2020

    Hi Garry,

    We have evaluated your request and have determined that it cannot be implemented at this time.

    We had a look at the example class you attached and have decided that these are classes that we will not be exposed as external. They are effectively internal rules class and we agree that the customer can test the custom functions themselves which use these rules classes (as we do not see the value in that).

    I will attach an example of a unit test that was written for the IEG component to test a custom function in that component if the customer is looking for an example of how to achieve that.

    Your request may be resubmitted for consideration after 12 months from the date of decline.

    Thank you for your interest in the Cúram SPM product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Feb 11, 2020

    Attachment (Description)

  • Garry Heap
    Reply
    |
    Feb 10, 2020

    Attachment (Description): Sure, they are all instances of where we have created a mock as part of the test

  • Guest
    Reply
    |
    Feb 7, 2020

    Hi Garry,

    In order to evaluate your request could we get an example from the customer of one of these JUnit tests?
    We would like to see what the customer is trying to achieve and in doing so, could offer some assistance or alternative mechanism to allow them to do so.

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

  • Guest
    Reply
    |
    Feb 6, 2020

    Hi Garry,

    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