Some of the global scripts, added this way only make sense when used interactively. Most of the data gathering or diagnostic ones would probably fall under this category. But our reboot entry might be reused in action operations, too. Instead of configuring such commands individually in global scripts and each action, we would have a single place to control how the rebooting happens. Maybe we want to change the reboot command to issue a pending reboot in 10 minutes. That way, a system administrator who might be working on the system has some time to cancel the reboot and investigate the problem in more detail.

We already have the global script for rebooting created. If we had a trigger that warranted rebooting the whole system, we would create an action with the appropriate conditions. In the action properties, global scripts may be reused by choosing Remote command in the Operation type drop-down when editing an operation. Then, in the Type drop-down, Global script must be selected and a specific script chosen:

As these scripts can be used both from the frontend and in actions, they're not just called frontend scripts; they are global scripts.