Integration


This is an IBM Automation portal for Integration 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.


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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Jul 10, 2025

RELATED IDEAS

Support for Local Timezone in Scheduler Node

When configuring the Scheduler node in ACE, the timezone option requires a specific IANA timezone or defaults to UTC. There's no way to simply use the local system timezone of the runtime environment.

This is a problem in scenarios where deployments span multiple environments with different local times. Hardcoding time zones adds overhead, increases the chance of misconfiguration, and doesn't adapt well in dynamic or containerized setups where the deployment region may vary.

If the Scheduler node allowed a local or system option for timezone, schedules could automatically align with the runtime's local clock. This would reduce config complexity, improve portability across environments, and make schedules easier to manage in CI/CD pipelines or cloud deployments.

Idea priority Medium
  • Admin
    Ben Thompson
    Jan 15, 2026

    Idea Review. Thank you for taking the time to raise this enhancement idea. The core aspect of this requirement centres around the portability of assets between different environments. Having a single BAR file that could be deployed to different integration servers running with different local explicit timezone settings, and have the message flow utilize the local timezone setting when making a decision about the absolute time at which to trigger a flow could be an advantage to a user. Given that this is more about ease of use and convenience for a specific method of deployment as opposed to a functional usecase that cannot be achieved with the product, this is currently a low priority for us, but nevertheless we are marking the idea for Future Consideration.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.