Timers - what is the difference between servicecenter/waketimer-action?

Timers - what is the difference between servicecenter/waketimer-action?

  
Hi,

I was wondering the following.

I have no rights to start timers via servicecenter.
However, I can make a button in a screen that allows me to call WakeTimer.

For some reason I feel this is something weird in the design.
Why should a end-user have the right to run a timer, yet a user of servicecenter cannot?


hmm I think it make more sense in production environments, where a application user is totally different of a service center user.(and must be this way for security reasons).
J,

Because when an end user (that normally cannot create an eSpace to run a timer themself!) starts a timer, that's by design within the context of the application, and the end user is granted the right Roles etc. In Service Center, you can run any odd timer given the right priviliges.