Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
For future reference, pasting an extract from the Support Case which resulted in this RFE where IBM recreated the issue and confirmed that it impacts other panels too, not just IBM SAP Adapter panels / SNC...
"While investigating this it became clear that the same behavior is seen on other panels too, especially those like the SNC properties panel that appear on the main canvas area. for example, DFDL annotation settings also do not register as 'dirty' until another field is clicked.
This is due to the use of the Eclipse WorkbenchPart firePropertyChange method. We are not currently aware of a way to have this Eclipse code register a field as 'dirty' without having to click away first."
Good update, thanks. We've experienced this issue across multiple property panels / properties. It's become commonplace now to observe or trip-over instances where properties are not marking up resource files as "dirty" / requiring to be saved. The instances above can merely be used as examples, as you say a wider code base but certainly seems to be a fundamental issue not just impacting one file type.
RFE Review. Thank you for taking the time to raise this RFE. We agree that usability would definitely be enhanced if this behaviour were improved. The precise two examples are helpful - Given the size of the Eclipse codebase, and the volume of feature requests we receive, we would be particularly interested if readers were to suggest any particular places they have identified this quirk which are of particular annoyance. We will watch this RFE with interest for supportive comments from other users to help sponsor its priority. Status of the RFE is updated to Uncommitted Candidate.