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:

Status Delivered
Created by Guest
Created on Nov 30, 2017

Need to include list of file names along with release notes

There is an enormous need to provide the list of file names that are modified, added and/or deleted for each release note item that is a part of an upgrade.

Having the file names for each release notes benefits us immensely as it will allow us to drive the entire upgrade based on release notes.

Currently our process includes the following steps:

1) *FOD :*
Obtain FOD(File of differences) between current code base installed in NC and the installed upgrade code base. For example if 6202 is current code base and 7010 is installed, we get the FOD between 6202 and 7010.

2) *Release notes:*
For each release notes that is included as part of upgrade is classified into different program categories and respective NC business representatives will analyze release notes and make sure that functional update is required for NCFAST.

3) *Code Merge:*
Once the decision is made, developers will be assigned the tasks to Merge the changes from OOTB to custom files(when necessary). This Merge will be done based on the release notes decision from business representatives for each program area.

As you can see based on the above, in order to be 100% sure of the impact of the upgrade, we have to end up doing double the work, as we are looking at/touching the same file when we analyze from the FOD as well as the ReleaseNotes that are included in the package.

**Problem and resolution:**

As we do not have list of files changed for each release note item, this makes it difficult for us to understand which files are modified for each release note item. If we have the list we can certainly know the set of files that has been changed for a particular release item and if we have customized any files in that set we can go ahead and do the analysis bring in the changes/remove the custom changes based on our findings and business decision on release notes.
Note : This is applicable for Message files, code tables, dmx files tab configuration files, efx files, rules files, etc. We understand the java files are black box and are included in jar but we need to know the files names so that if we have customized the file we can identify those. Note that there are about 168 Non-complaint java files we have in NCFAST that need to be addressed as part of the upgrade and if we have the list of OOTB java files that has been modified, it makes it easy for us to analyze the changes and remove Non complaint java files from custom. We do not want any files to excluded from the list.

We understand that the same file could be touched by multiple release note items and thus be listed multiple times, but that is 100% acceptable and expected. This will greatly streamline and improve our upgrade process to be much quicker than it is currently. There should be no files that are added/removed/updated that are not tied to a release note item. We are looking for each release note item in the ReleaseNotes file that is included package, to have every file modified for it.

Customer Name North Carolina - Dept of Health and Human Services, Minnesota, South Carolina, District of Columbia – Washington, Nebraska Health and Human Service System, IBM CORP
  • Attach files
  • Guest
    Sep 10, 2020

    Hi Jase,
    We are pleased to inform you that your enhancement request has been delivered and you can now request a report that lists all the files that have changed between your existing IBM® Social Program Management (SPM) version, starting from SPM 7.0.0, to the SPM version to which you are upgrading.

    When you plan an SPM upgrade, you can now request a customized report that clearly lists the files that have changed between two versions. The report lists the installation path and file name of each file that has been edited, added, or removed in a clear, easy to read CSV format. Therefore, the report reduces the analysis and execution that is required for SPM upgrades

    For more detailed information on this new capability, please view the following announcement from IBM Support: New customized file changes report reduces analysis and execution for upgrades ( )

    In addition, the release notes for the last few SPM releases were improved to include extra details in the Resolution and Technical sections which may also include the artifacts updated where applicable.

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

    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Apr 29, 2020

    Do we have any update on this? IBM Architect at NCFAST told us that PD is working toward the solution but we have not heard from PD yet.

  • Guest
    Jun 13, 2018

    Hi Jase,

    We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.

    IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

    IBM will update this request in the future.

    Thank you for your interest in the Cúram product.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Jan 3, 2018

    Hi Jase,

    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,
    Eloise O'Riordan, Cúram SPM Offering Management team