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.
Select future or past or range for ambiguous sys-date and sys-time
Currently the system entities for date and time make a guess to fill in portions of the date and time that are not mentioned by the user.
"Monday" could be in the future or in the past.
"4/5" could be this year, last year or next year.
"five o'clock" could be AM or PM.
"September" could be in the past or in the future.
The person writing the dialog tree knows whether they would expect a date in the past or in the future, but currently there's no way to hint that to the system entity.
This idea is for the sys-date entity to have an attribute or method that allows for getting the date within the bounds expected. For example sys-date.future() or sys-date.past() or sys-date.within(start, end). These functions could return null if the date cannot be interpreted to fall within the specified bounds.
Do not place IBM confidential, company confidential, or personal information into any field.