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 IBM 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.

Status Not under consideration
Created by Guest
Created on Jul 7, 2022

Allow Application.prx to have Multiples within Same Component

Within the Scottish Government project we have multiple teams working in parallel not only on the same benefit but on different benefits.

It makes merging code very complex and time consuming between teams and branches, especially when conflicts arise due to the same file being changed. Even more so true, when it's a common file such as Application.prx

In some areas, SPM allows multiple versions of the same file, and then when ant targets run, the files are merged based upon rules. For example, we can have several DMX files within the same component all referencing the same table but split between a functional area. e.g APPRESOURCE_IMG.dmx, APPRESOURCE_PROP.dmx and so on. The generators manage this fine, and merge them into a single dmx file (APPRESOURCE.dmx)

The ask is, can the processing of the Application.prx file be changed to be managed in the same way?

At the moment, each component has a single Application.prx file - if we have multiple teams working in the same benefit, this file can change a lot. If each team could create a version of it (within the same component) which are then merged together (and then ultimately merged into the overarching project one) that would help with conflicts and speed up downstream merging.

Customer Name Scottish Government
Persona Based Summary

As a developer performing merge activities I want to be able to have no or reduced conflicts in Application.prx files.

Market Segment WH Government
Type of Request Idea
Market Opportunity

No market opportunity but will help merge and release processing on large scale govrnment projects.

Usage frequency + #/type of users impacted

At the moment, 6/7 teams are undertaking daily merges so this would have a postive impact across all these.

Workarounds + Proposed Solution

Manual effort to resolve conflicts associated to this particular Application.prx file.

  • Attach files
  • Admin
    Sep 1, 2022

    Hi Gary,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:

    • You are requesting an enhancement that allows multiple versions of the Application.prx file to exist within the same component that can then be merged into a single file to support a more efficient merging process on projects where multiple teams work in parallel on the same benefit.

    We acknowledge the benefit of your suggested enhancement however other features are taking a priority in our planning at this time.

    This request will be closed, and we will not be taking any further action.

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

    Thank you,

    Sheryl Brenton, SPM Product Management Team

  • Admin
    Jul 11, 2022

    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,

    Sheryl Brenton, SPM Product Management team