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.
In ClearQuest a lot of different hook types (access control, initialization, choicelist, etc) are defined. For the normal (positive) workflow everything goes fine. Every step will be visible by special hooks. Saving will end with validation-, commit- and notify-hook.
But we also need a hook-type for the negative case of workflow. Saving the record will not be possible and the user will cancel the action. Fore that case we need a own hook called: "Cancel-Hook" or "Revert-Hook"
Actually we have identified two different use cases:
In the "Initialization-Hook" (first Hook after access-controll) we open a log file. This logfile depents to a user. If everything goes fine, than the user will save the modified record and we will close the log-file in the "notification-hook" (last Hook after Commit). But if something goes wrong or the user decides to revert/cancel the record, we are not able to react and close the logfile in the correct way.
An other use-case is the logging of user-actions. If everytime a revert occurs after a special validation, this will give us some information about wrong implementations. Actually this information is not available for us, because we have not such a hook.
Do not place IBM confidential, company confidential, or personal information into any field.