Log chore registering/unregistering

[holger_b]

We keep having problems with the client's super users deactivating chores which they should not switch off - like the backup job.
Can anyone think of a way to log who deactivated a chore?

Thank you
Holger

[jim wood]

Even better, don't use chores. Use TM1RunTI and a separate scheduling tool instead. No locking for the full cycle of the chore and no user can deactivate it. I know id doesn't answer your question but it does give you a work around for the problem.

[holger_b]

Thank you Jim, I was not aware of TM1RunTI. This should also give us more flexibility re scheduling intervals. Very interesting!

Regards
Holger

[George Regateiro]

If you were to choose to keep it in TM1. I have started created an administration server with very limited access. This houses all the system admin chores and then interacts with the other servers using RunTI. This way I can consolidate my backup and other admin processes in one spot.

[holger_b]

This is sure a good idea from a technical proint of view! Still, in my consulting projects I prefer to have one or two admin users from the business department who understand what they are doing and act accordingly. I feel that if you try to lock things away you tend to forget something and you make your clients depend on you in a way which is not always useful.

The problem which we have here is that the admin user does not always foresee the impact of what he does, so maybe we will have to go into the direction in which you are pointing...

Thank you
Holger