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:
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM 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 IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Provide an Example for an Attribute Modification Notification in Dev Process
We are trying to upgrade from V5.2 to V5.3 of Change. An update was done to the transition_notice.pl script by IBM for that upgrade. So, none of our out of the box notification templates were working any longer. It took me several hours to figure out what had changed because the DEV process only provides examples of how to do a state to state notification. I propose that IBM also provide at least one example of a notification where a notification will also be generated for a reassignment. I came close to having to write up a PMR yesterday but did eventually figure out what you were looking for in the template.
NOTE: I also watched a video describing the process but it also did not provide any insight to how to do a reassignment notification.
I propose you create a resolver template (my_resolver.tmpl) and then add the following 2 lines to your email_templates.properties file.
# the following will be used to send an email any time the resolver attribute is modified
Would suggest you add another example of how to send 2 or more emails during a state transition (i.e. an example of using the "|" between templates.
Also, I would suggest to not use the package_template as the "preferred" way to implement this. It is far easier for an admin to create a package for this. Then if you neeed to tweak any of your templates all you need to do is uninstall/reinstall the package. Far easier than recreating a process just to tweak an email template.
Do not place IBM confidential, company confidential, or personal information into any field.