Skip to Main Content
Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

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

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your 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
    Reply
    |
    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.



  • Guest
    Reply
    |
    Feb 18, 2022

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