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 this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to 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 Power teams 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.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
System-period temporal tables are great, but "system-time" is not appropriate in many applications. Quoting from an article by Philip Nelson on DB2 Temporal Support - A Practical Introduction:
Temporal support consists of two key concepts : system time and business time. System time support can be thought of as an audit trail of when changes occurred to data (although it may not in itself suffice as an audit trail for regulatory purposes without other safeguards being built in). Business time defines when data is effective from a business point of view.
In DB2 for LUW it is referred to as Application-Time Temporal Support.
Application-time temporal support allows:
Using the history to provide undo/redo support
Business applications: Price changes for a future date, adjusting transactions (i.e. adjust effective date due to late delivery), retroactive (transaction entered after event took place), automatic purging or "death of row" on the assigned end date, and many other applications
Vendor or home grown System management and change control applications: Ability to schedule a policy change in advance, schedule job change, on boarding and off boarding activities in advance (i.e. add/remove application menu access), ability to record a change with proper date and time after it took place
There are thousands of other examples and applications
Do not place IBM confidential, company confidential, or personal information into any field.