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
Post 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 product management 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 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.
When a user attempts to delete a record on OpenPages, the system presents them with a pop-up ‘OK' / ‘Cancel'. It's a really good ‘user experience'.
We'd like to implement a similar two-pass logic, and being able to utilise this same approach would be ideal – particularly as all other options I can think of for achieving the same result are much worse.
It would be very useful if the base code (mentioned at the start), could be tightly packaged such that we could call it as a utility using a defined interface.
The input parameters I would expect to see would be - Object - Action (update/create/associate etc.) - Condition (e.g. Object1.Value > Object2.Value) - Popup wording (e.g. Are you sure you want to enter a date in the past?) Suggest to keep things simple, that OK & Cancel remain the only two options and OK always means proceed / Cancel means don't
I suspect this needs some restriction to stop it clashing with existing instances of this code (e.g. on delete & dis-associate)
Do not place IBM confidential, company confidential, or personal information into any field.