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 Dec 4, 2024

RELATED IDEAS

Scheduler node cron expression

The scheduler node doesn't support the bar override property values we set and fails to deploy refer to case TS017743219 and On the node scheduler properties give a field where we can enter the cron expression we need directly and also an easily manageble way to stop and start specific scheduler node in a message flow . for e.g in a flow if i have multiple scheduler nodes i need a way to stop and start these without having to redeploy the flow.

Idea priority High
  • Admin
    Ben Thompson
    Reply
    |     Dec 20, 2024

    Thank you for taking the time to raise this enhancement request. We have also looked through the case which you referenced with our support team. For the benefit of other readers, the suggestion here is that the scheduler node should always accept a Linux Cron expression property as opposed to the existing multiple properties of the message flow node which provide a range of calendar and repeat interval options.


    We accept that for a subset of our users (most likely those with a Linux / sysadmin / technical background) the usability of a cron expression might be preferential as an alternative to the current approach which was devised to be acceptable for users who are somewhat less technical. In line with this, we are updating the status of the idea to be Future Consideration in order to see if there would be strong support for this request from our community, whilst noting that this is unlikely to be a high business priority for us anytime soon.


    Given this, in the interim it is probably also worth commenting on how the specific use cases can be achieved with the product today. Specifically four types of usecase were highlighted:


    1. Run every minute

    2. Run at 07:15 in the morning every day MON-FRI

    3. Run every 30 minutes between morning 8 to evening 17 daily from MON-FRI

    4. Run only on the 10th of every month at 07:00AM only


    1. Use case 1 can be achieved with a Scheduler node by setting the "Repeat Interval" radio button, with Interval = 1, Interval Unit = Minutes, and Days selection boxes tick Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.


    2. Use case 2 can be achieved with a Scheduler node by setting the "Calendar" radio button, with Run every = Day, "at"= 07:15 … You would then need to wire a transformation node after TimeoutNotification and discard the propagation if the day of the week is SAT or SUN.


    3. Use case 3 could be achieved using a TimeoutControl + TimeoutNotification node combination. More information about timeout request messages is available here:

    https://www.ibm.com/docs/en/app-connect/13.0?topic=flows-sending-timeout-request-messages

    <TimeoutRequest>
      <Action>SET | CANCEL</Action>
      <Identifier>String (any alphanumeric string)</Identifier>
      <StartDate>String (TODAY | yyyy-mm-dd)</StartDate>
      <StartTime>String (NOW | hh:mm:ss)</StartTime>
      <Interval>Integer (seconds)</Interval>
      <Count>Integer (greater than 0 or -1)</Count>
      <IgnoreMissed>TRUE | FALSE</IgnoreMissed>
      <AllowOverwrite>TRUE | FALSE</AllowOverwrite>
    </TimeoutRequest>


    StartTime=08:00,Interval=1800 seconds (30 minutes), Count=18 (there are 9 hours between 8am and 5pm). You would then need to wire a transformation node after TimeoutNotification and discard the propagation if the day of the week is SAT or SUN.


    4. Use case 4 can be achieved with a Scheduler node by setting the "Calendar" radio button, with Run every = Month, "on the" = 10, "at"= 07:00


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.