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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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 Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including 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) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Specific links you will want to bookmark for future use
At the top of the log files we would like you to have information about the client version.
In case the client updated its version, we suggest a WARN in the file informing that the version was updated. If the log file is deleted, we ask that the new log always have the current client version in the first message in the file.
This information would be very important in AgentService, Studio and Bot Execution logs but if possible, we would like this information in all possible logs.
In the AgentService log, when the schedule is sent to the queue, we need the script version and the script name to be shown in the log, currently we only have the schedule name information and the guid.
When the schedule is changed or created, we need the log where the broadcast is received to show the schedule name, script name and script version.
When the connection to the queue is lost and then is restabilized, we need the log to contain the information of the amount of the time that it couldn't reach the queue (the time atleast the connection was down). We need this to also show up when it's a lost connection to the API.
Do not place IBM confidential, company confidential, or personal information into any field.