Why don't you vote on PD enhancements? PLEASE RESPOND

[GeorgeMcGeachie]

I've posted a few messages previously on SCN about our ability to propose and vote on PowerDesigner enhancements via the Independent SAP Technical User Group (ISUG-TECH). I'm surprised and disappointed by the apparent lack of interest in using this mechanism, and I'm wondering why. I thought the best way to find out is to ask everybody on this forum, so here goes.

I'm not able to submit a poll to find out why there's an apparent lack of interest, so I have to do it via this discussion thread. So, please, can every one of you read the rest of this message, and then provide one of the following reasons "Why I don't / haven't used the ISUG-TECH enhancements process":

• I didn't know about it
  • (if this is your answer, please consider the others before replying)
• too busy doing the day job
• PowerDesigner is perfect, and nothing needs to change
• we are willing to follow SAP's roadmap
• we submit enhancement requests directly to SAP, and the process works for us
• can't join ISUG-TECH
  • (please say why not)
• never heard of ISUG-TECH
• you prefer a different way of submitting or voting for changes
  • (please say what that is)
• thanks for reminding me, I'll do it now
• anything else?
  • (please say)

Here are the statistics from the ISUG site (http://my.isug.com/p/is/ty/type=14😞

• there are 49 proposed enhancements currently open for voting
• only 20 of these have any votes at all (this includes saying that it's 'Not Needed')
• no enhancements submitted since September

If you have access to the list, you can tell us how important each change is to you:

     0 - no vote

     1 - not needed

     2 - not recommended

     3 - undecided

     4 - recommended

     5 - needed

Here are the names of the proposed enhancements that are currently open for voting:

• Need to save named model comparison settings
• better control of symbol display
• Print all Diagrams at once and deselect empty pages
• Need an OOM to OOM 'intelligent' generation
• Pan and Zoom functionality
• Support for Progress RDBMS
• Support PKEY sorting in MSSQL 2005
• Event Handle for pre and pos Check-in Check-out
• Recognise that attributes or columns have been moved, not deleted and re-created
• Select Connected Symbols on right click menu
• Invert Selection
• Show more details of model versions in list
• Show more details of object versions in list
• Show time recovery file created
• Increase buffer size for output window, and save model generation log file to defined path
• Focus (centre) the view of a diagram on selected symbols
• Select Connected symbols - extend to include graphical synonyms
• Allow Model Lists and List Reports to contain "Reports"
• Allow Model Lists and List Reports to contain "Diagrams"
• Ignore all diagrams and symbols in comparison
• rename model creation and modification dates
• New action type in Frameworks
• Default attributes for model symbols
• PDM MultiDimensional auto-layout without graphical synonyms
• Build in Plural Entity Names to the CDM and LDM
• Copy dependency matrices between packages, and between models
• Auto-construct relationship names
• Show relationships for entities in the browser
• Show inheritances for entities in the browser
• Drag and Drop in Model compare and merge
• Match attributes in different entities in Model merge and Compare
• Include existing entities as sub-types in Barker CDM entity
• LDM inheritance - attributes migrated from child to parent
• Replica LDM Attributes do not have domain associated
• Specify attributes as 'logical-only', and columns as 'physical-only'
• Use Glossary entries in Spell Checker
• Export results from 'Execute SQL' and 'View Data'
• Add Traceability Links from Views to Tables
• Run model checks before checking-in a model
• Extend naming standards support to include prime, modifier and class words
• Improve the handling of enumerations
• indicate inherited and foreign key attributes and columns in the browser
• Save default layout style for every diagram
• Delete unwanted library files
• include an object's 'neighbourhood' in a diagram
• include missing related objects in a diagram
• Allow Repository branch integration with a change list.
• Objects sequence pattern in PowerDesigner Browser
• Add support for materialized views in Sybase ASE

[GeorgeMcGeachie]

Of course, feel free to reply with "I do vote via ISUG"

Thanks