Skip to Main Content
Digital Business Automation Ideas

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

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,

  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 notifications 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 that cannot be implemented in a reasonable time.

Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):

  • Cloud Pak for Automation - incl Business Automation Studio, Business Automation Insights

  • Business Automation Workflow (BAW) - incl BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content and Capture Services - incl Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager

  • Automation Decision Services (ADS) - incl ADS, Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • IBM Blueworks Live

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Created by Guest
Created on Jan 6, 2022

Log the query that was performed by the bot in any SQL command error

We build queries in ibm rpa by concatenating ibm rpa variables with pre-build int queries. Sometimes those variables may have incorrect values, and the query will fail.

The problem is, IBM RPA will not log query in most cases, and when it does, it logs the variables as in ${variable} instead of the value.

So let's say I have a simple select "Select * from Person where name='${name}' " and for some reason the ${name} variable has an incorrect value, I would need to reproduce the error again in Studio with the exact same data to get the same error.

If when the command failed, it logged the exact query it sent to the DB it would speed up a lot debugging SQL logic errors.

Idea priority High
  • Guest
    Feb 18, 2022

    Two main reasons:

    1- It's not just the log message, the user needs to use a setVar to put the whole query in a variable, log this variable, and then use this variable in the SQL commands. It's 3 commands to do something that should be doable with one. Not only that, they only do this once instructed by support (i.e. there is no reason to do this unless you start having problems with your query), and with this more likely than not they would be able to figure it out the problem by themselves. And if they follow this route they would have this log every time the query runs, not only when it fails.


    2-In some commands we abstract the call from the customer, as in "SQL Procedure" and "Run SQL procedure". Users only enter with the proc name, and the bot itself creates the call, so in those cases, the workaround from 1 isn't doable. The only other alternative would be to log all variables before calling the proc.



  • Admin
    Joba Diniz
    Feb 18, 2022

    Lucas - Since it's possible to add log message commands to log additional information, then why would this be necessary?