Hi Axel, I am just suprised that this ideas wasn't created long time ago. I fully agree, such an easy improvement that avoids again just extra code to do what is needed many times in projects.

Same goes for LaunchProcess action

Good idea, if also the public property has the default of 'No'.
One big reason is because of security/authorization, you don't want to have timers public that:

• should only run on a schedule, or only once: no public access needed
• you only want certain people to be able to start (you would then need to remember to check roles in every action that is built, and will be built somewhere in the future): no public access needed, just create a wrapper with role check and make that action public
• are visible for any module to start/link to one another: creates a chance to combine/clutter the environment with module-links that should not be linked

Of course, this also means developers should be aware of the risks and apply the correct setting to the timers (maybe include a help-link that guides the developer for proper use).

Solution for now is to make a public server action and call the wake timer in this public server action. The public server action can then be called in another module. In this way, you wake timers that are not in the same module.

@Ronnie Verheij: That is already a known solution and Axel Denis knows about this possibility, his idea states:

"...It would be way more handier if that WakeTimer action would be a public action so that we don't have to create wrappers for it anymore."

A public action that calls some method(s) in the module is called a wrapper action is, and a perfect solution if you also like to check roles (is the current user allowed to start this timer action?)

The idea Axel posted is just to reduce the amount of wrapper actions that just call a WakeTimer action.

And I noted, also think about security, ìf this idea gets implemented (to have timers/wake timer actions that can be set public), to have this 'Public' property set to 'No' by default, for reasons read my previous comment.