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 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 a 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Provide the ability to disable or customize the CQ web client “Print” button / icon. Allow:
1. Enable or Disable the print button function. (minimally).
2. Assign a default custom report per record type to the print button (ideally).
The current CQ web client has a Print button that dumps a “Report” of all of the record type fields in table form for a specific selected record. If a field is a reference field, its child record is also dumped.
There are several issues with this ranging from company disclosure / security to presentation.
Consider a Defect record type that has many fields defined: some are company internal, some may be customer private and others may be public. Some fields are references to other CQ record types. These other record types may be internal or public as a whole, or they may contain a mix of fields as well. This defect record type has references to an internal Test record type. This Defect record has a Public / Private field that is checked to specify if the is public (default is private).
If a CQ web client user selects the print button/icon for a selected defect record, they get a default dump of all of the fields, including referenced record, company private and public. The format is not friendly. There are no company markings in this report – no headers, footer, propriety markings, etc.
This dumped report may inadvertently be sent to a customer or other organization containing internal data.
Our only recourse is to try to train our users to not use the CQ web client default print button. We must train them to use the Report Launcher with our custom reports. One problem is ensuring training is provided to all on-site and remote users, they remember this training and they do not forget and use the easily visible default print button. This has a high probability of human error.
Minimally, we should be able to disable the CQ web client print button so that accidental printing cannot occur. Maybe include an option where attempted use of the print button would display a customizable pop-up message. Then we could remind the users to use the Report Launcher.
We have built pull reports using Crystal Reports and access them using the Report Launcher either directly (web browser) or via the “Manage Reports” button in the CQ Web client.
- One set of reports is for internal use and includes our internal private fields. - One set of reports is for customer and public use and does NOT include company internal and private. - A record type may have multiple reports to use for different purposes. - We have formatted the report into a preferred layout and included only desired fields. - We have included appropriate headers, footers, company markings, etc.
Ideally, we would be able to assign a default report per record type to the CQ web client print button. That way we can default to a safe public report. Or, allow multiple reports to me assigned to a record type and have the print button have the user select the desired report. Then is it the company's decision of which reports to load. A naming convention could be used to distinguish private and public reports. Or allow for Private and Public sections in the pop-up report selection window similar to the query tree has private and public section.
In a CQ web client, a user selects a record type (Defect, Enhancement, Test, Configuration Item, etc). Instead of using “Manage Report” (which does not sound seem like a “Print” option) to open the Report Launcher, a user sees the easy, readily available print button / icon and selects it. This opens a “Report” window with a tabular dump of the selected records content, including any child record content. The user either prints this or saves it as a PDF. The user may then inadvertently send this to an outside organization, such as a customer not realizing that the default dump contains company proprietary information. Additionally, the report is not formatted in a desired layout and contains no header, footer or proprietary markings.
Do not place IBM confidential, company confidential, or personal information into any field.