Inject node with cronti

Core Development Feature Requests
8

These extra features do not prevent the inject node from being simple and well. Rather, they are features added to make it more functional while maintaining its simplicity. The alternatively offered cron-plus package is yes very complex. If I had integrated the cron-plus package, I would have broken the "golden" rule :slight_smile:

I would like to explain the new features a little more.

  1. Create cron of the spesific day of date: This feature is used when you want it to be triggered once every year on the same calendar day. For example, on June 4, 2022, on June 4, 2023, on June 4, 2024... By default, the time is set to 12:30. Time can be entered wherever the date is entered (datetime type)

  2. Create the cron for the week the date is in: This feature is used when you want the week of the specified calendar day to be repeated every year, triggering every day of the week. For example, the days to trigger for June 4, 2022 are May 30, May 31, June 1, June 2, June 3, June 4, and June 5, 2022, 2023, 2024... By default, the time is set to 12:30. Wherever the date is entered, the time can be entered (datetime type). In addition, the starting day of the week may differ depending on the country. In the example I gave, the day of the week is Monday.

  3. Create a cron that will run at regular intervals between two dates: This feature is used when you want it to be triggered every day or at certain periods, repeating every year between two specified calendar days. For example, it can be triggered every day from June 4, 2022 to July 10, 2022... In a different alternative example, it can be triggered every 2 days between June 8, 2023 and July 5, 2023... Years don't matter here. For ease of use, the selection screen can be simplified to select the day, month, hour, minute and period. By default it is set to 12:30. Time can be entered wherever a date is entered (datetime type)

  4. Create cron with various combinations of month, week, weekdays, hours, minutes and tick: This feature takes shape when fully triggered. Each entry is optional. Some can be filled if desired. All can be filled if desired. If desired, only 1 can be filled. All are left blank if desired. By default, the time is set to 12:30. Time can be entered wherever the date is entered (datetime type)
    More Examples:

    • If only the month(0..11) and week(0,1,2,-1) parameter is filled, the crontime expression that will be triggered every day from the first day of the week to the last day of that week is returned.
    • If only the month(0..11), week(0,1,2,-1) and weekdays(0..6) parameters are populated, the crontime expression for that weekday is returned.
    • If only the week(0,1,2,-1) parameter is populated, the crontime expression that will be triggered every day during that week is returned. Except for the last week of the month(-1).
    • If only the month(0..11) parameter is populated, the crontime expression is returned for each day in that month.
    • If only the weekdays(0..6) parameter is populated, the crontime expression is returned for this weekday every month.
    • If only the month(0..11) and weekdays(0..6) parameters are populated, the crontime expression is returned for these weekdays of this month.
    • If no parameters are filled in, the crontime expression is returned for each day of each month.

  5. Enter valid cron expression: For people who know how to use crontime expressions, it is a feature used to schedule from a shortcut. For example 0 2 * * *...

  6. Create cron of the spesific date: This feature is used when the selected day is desired to be repeated every month and every year. By default, the time is set to 12:30. Time can be entered wherever the date is entered (datetime type). For example, June 4th, July 4th, August 4th, September 4th 2022, 2023, 2024...

All these features can be achieved by offering only a few input fields. Yes, the inject node is a powerful node with its simplicity. I'm aware of this so I didn't want to use more extensive but more complex packages.

Instead of the datetime input fields, which include the year entry, only input fields with the used values can be put. That way you get a friendly interface.

There is a lack of information in its current state. I will add information sections for this.

1 Like