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 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 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
TFUI - Enable Workflow Validations and Operations on SAVE
Many of the data quality rules span objects - Eg. Impact booking date must be GT Event Occurrence Date. Form rules only allow for rules on a single object so cannot be used. Workflow rules for validations and operations only run on workflow transition - so cannot be used.
The user can therefore update and save the object without any validation rules or operations taking place.
We want to migrate away from using triggers, but currently these are required to maintain data integrity.
Whilst it is possible to work around this by perhaps having read only date fields and building a workflow to 'edit a copy of the date' fields - it is pretty convoluted and not a good user experience.
Do not place IBM confidential, company confidential, or personal information into any field.