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 Submitted
Created by Guest
Created on Apr 27, 2026

Add ability to change pod timezone for Business Automation Studio similar to what is possible for Workflow Runtime

The Workflow Runtime pod allows a user to set the Timezone for the pod:
https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=parameters-business-automation-workflow-runtime-workstream-services
environment_config.timezone    Timezone of the Workflow server. The default value is Etc/UTC.

Runtime setting exists in yaml - https://github.com/icp4a/cert-kubernetes/blob/25.0.0/descriptors/patterns/ibm_cp4a_cr_production_FC_workflow.yaml

This setting changes the pod timezone for the server being used:

In BAW CR,
baw_configuration:
environment_config:
timezone: America/Winnipeg

Inside a BAW pod, say icp4adeploy01-bawins1-baw-server-0
sh-5.1$ hostname
icp4adeploy01-bawins1-baw-server-0
sh-5.1$ date
Wed Apr 8 13:38:42 CDT 2026
sh-5.1$

The authoring environment parameters does not list any timezone element. 
https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=parameters-business-automation-studio

Authoring - does not have an equivalent setting: https://github.com/icp4a/cert-kubernetes/blob/25.0.0/descriptors/patterns/ibm_cp4a_cr_production_FC_workflow_authoring.yaml

It does have the ability to change the JVM to use a different timezone, but this only changes the behavior inside the JVM and would not impact operator traces or other pod level timestamps.

We opened a case with Support and the product development team suggested the following as a possible workaround:
"
$ oc project
Using project "Project_Name" on server "Server_Name".

$ oc patch statefulset icp4adeploy01-bastudio-deployment -n Project_Name --type='json' -p='[
{
"op": "add",
"path": "/spec/template/spec/containers/0/env/-",
"value": {
"name": "TZ",
"value": "America/Winnipeg"
}
}
]'

statefulset.apps/icp4adeploy01-bastudio-deployment patched

$ date
Fri Apr 24 08:59:37 AM CDT 2026
"

However, I noticed icp4adeploy01-bastudio-deployment-1 was restarted once, then terminated, the started back, I tried to check and found the date was still show UTC time, not CDT time.

sh-5.1$ date
Fri Apr 24 14:06:12 UTC 2026
sh-5.1$ hostname
icp4adeploy01-bastudio-deployment-1"

This is expected behavior, so the provided workaround would have to be re-applied for each pod restart. We would like to see that a similar parameter get added to the Business Automation Studio to allow pod locale setting to be configured at the CR level such that the value could be controlled like in a Runtime.

Idea priority High