Creating a Chore

[TM1begginer]

Hi, I am facing difficulties in creating a automated chore which needs to run every Monday and Thursday.

I don't think we have options to run the chore every Monday and Thursday in a week. Can we create a TI Process to run the chore. If yes, can anyone help me with the code or instructions.

Thanks
TM1Begginer.

[Alan Kirk]

Hi, I am facing difficulties in creating a automated chore which needs to run every Monday and Thursday.

I don't think we have options to run the chore every Monday and Thursday in a week. Can we create a TI Process to run the chore. If yes, can anyone help me with the code or instructions.

Two options.

The first is to schedule the chore for daily execution. In the first process of the chore determine what the day of the week is and quit the chore if it's not Monday or Thursday. For determining the weekday, see the heading "To Get The Weekday Of A Date As A Value" in this thread.

The second, and probably simpler way, is to create two chores instead of one, adding the same processes into both. Have one chore execute every 7 days on the Monday, and the other execute every 7 days on the Thursday.

[TM1begginer]

Hi Alan,

Thanks for the reply, I thought of the second option but was searching if I could find anything else.
I will create a 2 chores to run every Monday and Thursday in a week. I appreciate your quick response.

[Alan Kirk]

Thanks for the reply, I thought of the second option but was searching if I could find anything else.

Unfortunately that and the option of checking for the day of week are about it; the scheduling options for chores are not all that flexible.

Of course if Iboglix were to add TI commands which allow changing the scheduling of chores and turning them on and off, then we'd be able to have a daily chore running which activated or deactivated the chores for that particular day, or, say, at the end of the accounting month.

Since such commands would not lend themselves to "gee-whiz" semi transparent icon based sales presentations, though, I wouldn't hold my breath waiting for them to arrive.

(Yes, some of us have asked for them in the past. No, they are never delivered.)

[macsir]

I think you probably can run the process from a bat file if you can run it from process level and then schedule it using windows scheduler.

[Alan Kirk]

I think you probably can run the process from a bat file if you can run it from process level and then schedule it using windows scheduler.

Relying on external processes is a bit Heath Robinson though... it's just one extra thing to go wrong. Two, given that it relies on both Windows Scheduler and an application to execute the process.

In the case of the OP's situation, two chores is the simplest method.

The scheduling options / commands should be a lot more flexible... but probably never will be.

[macsir]

This is about a dream of fexible scheduling.

[Alan Kirk]

This is about a dream of fexible scheduling.

Tell me about it. It's so "off the radar" at Iboglix that they aren't even consistent about it. In the "classic" interface you can schedule anywhere between 0 and 999 days. (Though you can't set 0 for all fields, even if you don't want to schedule the thing at all.)

However in my bestest software buddy Performance Muddler you can only schedule up to 365 days ahead. Granted, in reality you'll rarely schedule beyond a year. (Though when one considers those pesky leap year things, an annual chore may in some cases need to be manually rescheduled the following day. TM1 users are, however, no strangers to manual rescheduling every 6 months ever since Applix unilaterally shifted from having chores triggered in UTC time instead of local time in the change from version 7 to 8.)

However the fact that they can't even keep the limitations consistent shows how little they appreciate (care, give a flying fig about, etc) the amount of time-wasting that can be involved with maintaining chore schedules.