This portal is to open public enhancement requests against IBM Z Software 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - Business Developer
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - Business Developer
We initially accepted this requirement, but deeper investigation is causing us to reject it. Providing an option to leave the blank constant fields in the forms would solve the problem of using testing tools such as RFT, but it would make the migrated forms very difficult to maintain using the TUI form editor.
The VAGen map editor created blank constant fields for all of the white space on the screen. This often caused frustration when modify field lengths, since all of the following fields on the map would also shift position.
We solved that problem in the EGL TUI form editor, by maintaining 'null' space between the user-defined fields instead of inserting blank constants. This allows individual fields to be modifed without impacting the position of subsequent fields. If we were to retain all of the blank constant fields from VAGen, then we would reintroduce the problem of shifting fields in the editor. The usability would be even worse in the EGL editor, because it has a graphical editor where you use drag/drop to create new fields. If we were to retain the blank constants, then you would not be able to drop a new field onto the form, because all of the white space would be taken up by the constants.
Therefore, adding this option would have a long term negative impact on the maintainability of the migrated forms.
We agree with this request, and will try do deliver the change in a 7.5.x fix pack.
Hi,...Could you paste in some sample ESF for a form(s) that this is occurring on? That would help.