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

Add a new idea Subscribe
Status Not under consideration
Categories Social Enterprise Collaboration
Created by Faisal Shafique
Created on Jun 14, 2023

RELATED IDEAS

Allow replace super class to be compliant

Setting replace super class to true has been an easy way to override OOTB behaviour. This was made a non-compliant customisation at a later date. This request is to remove that non-compliancy and make it a compliant change because:

- OOTB functionality can be overridden with lesser customisation with this approach. We're having to customise screens in addition to facades just to avoid this non-compliancy. This means that at every upgrade, in addition to checking Java code impact, we also have to compare the screens for any changes even though we haven't changed the screen itself and only change is to point it to a different facade. This problem multiplies by many factors if the Java customisation is buried deep in a service layer class and to do it compliantly would mean that you will have to customise lot more classes to do it. All of this adds to upgrade and ongoing maintenance costs considerably in terms of not only manual file comparisons that have to be made but additional code that has to be maintained now because of additional customisations. This request is to make it a compliant change since it's not always practical to follow it.

- An alternative could be other ideas e.g. a pre/post hooks are generated for facades and BPOs are automatically called which customers can then just implement without having to set replace super class to true. Most of the time it's only additional logic that's required pre or post OOTB functionality.

Customer Name Scottish Government
Persona Based Summary

As an SPM Developer I want replace super class = true to be a compliant change so that I don't have to customise as much which makes upgrade activities difficult for me.
Market Segment Health & Human Services
Type of Request Idea
Market Opportunity

This reduces upgrade and ongoing maintenance costs to customers due to additional customisations that we are having to do because of this non compliancy.
Usage frequency + #/type of users impacted

Frequently during development phase and will still be required during maintenance phase.
CURAM:Workarounds + Proposed Solution

Work around is to customise more artefacts to avoid this non-compliancy.
  • Attach files
  • Admin
    Graham McCrindle
    Reply
    |     Sep 8, 2023

    Hi Faisal

    We have reviewed your enhancement suggestion.

    Based on the information provided, our understanding of your request is as follows:

    • You have requested that we consider allowing the replacement of a superclass.

    We do not intend to change our policy with regards to allowing projects to replace Superclasses and this does not align with our product strategy, The ability to replace a Superclass was removed as part of the decision to no longer ship source code and at this time we do not intend to reverse this decision. We also believe that allowing a client to replace a superclass can introduce instability to OOTB functionality. We do intend to do a review of our current compliance guide and will look to provide additional guidance on how clients can extend while not replacing the superclass. We are therefore closing this request and do not plan to take any further action.

    Thank you for taking the time to share your ideas with us. Although we cannot pursue all the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.


    Regards,

    Cúram Offering Management

  • Garry Heap
    Reply
    |     Jun 19, 2023

    Attached some examples to support this

    ReplaceSupercla...
    ReplaceSuperclass.pptx
     ReplaceSuperclass.pptx
    Open full size
    ReplaceSuperclass.pptx
  • CLAIRE MCGAFFEY
    Reply
    |     Jun 15, 2023

    Hi Faisal,

    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