Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Sep 21, 2018

Scheduling agent triggers in different time zones (Other than UTC)

Currently the advances scheduling option for agents only takes time in UTC and triggers the same in UTC time zone. For different countries like US people want agents to be trig-erred in their time zone for example EST. EST has to be converted to UTC and set up in advances scheduling. This causes the problem when day light saving occurs. EST time changes but UTC doesn't. People have to manually change the configuration in prod before Day light saving. 

What is your industry? Other
How will this idea be used?

Sceduling agent triggers in EST time - Cases - IBM Support

We have used advanced scheduling option in RTAM. As per the Client requiements RTAM needs to triggered at 5:30 AM EST. The cloud servers are in UTC. So we have converted that time to UTC (9:30) and used it in advanced scheduling section. The issue is during daylight saving 9:30 UTC will be 4:30 EST and the RTAM details will be sent at 4:30 AM which is not as per the expectation of the clients. This has to be changed manually in confiugrator.

This will help people choose the agent trigger in their time zone


  • Guest
    Sep 18, 2020

    This idea has been created after detailed discussions with L3 and Support. This is currently under consideration.

  • Guest
    Feb 12, 2020

    Does advance scheduling support multiple triggers in a day? As per the configuration looks like just one time/per day.