Skip to Main Content
IBM Data and AI RegTech Ideas Portal

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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

Shorter URL for this site is: or

Status Delivered
Workspace OpenPages Ideas
Component Reporting
Created by Guest
Created on Mar 29, 2019

Document Collation

With the maturation of the GRC domain, clients increasingly require the compilation of more complex documentation artifacts. For example, Model Risk Management clients frequently maintain Model Documentation, which are complex, technical reports that can be more than a hundred pages. The documentation is highly technical, and comprises formulas, tables, charts, images and footnotes. The reviewers of the Model also write an equivalently lengthy document as a record of their reviews. The compiled document includes hand-crafted technical writing and OpenPages reports. The final output is a PDF.
Model Risk Management is only one example where the compilation of documentation artifacts is required. Recently, OpenPages Service teams had six concurrent projects with documentation challenges, four that required some form of document compilation with PDF output and two that required Rich Text formatting in a PDF file.
OpenPages offers minimal support for this kind of artifact. Rich Text promises to support a part of the solution, but its capabilities are marginal. A separate enhancement request covers Rich Text.
The high level requirements for Documentation Compilation are:
• User or Services can define a documentation artifact that is the compilation of an ordered sequence of files that include a Title Page, a Table of Contents, OpenPages reports, the MS Word equivalent documents, and, possibly, other attached files such as Excel or Visio
• User can designate the format of the final artifact, though initially only PDF is required.