Difference between revisions of "Action"

From Veloopti Help
Jump to: navigation, search
m
m
Line 11: Line 11:
 
: Operator level actions require the lowest level of permission to be run.  Any user in an application that is a member of the ''Operator'' role can run an operator level action.
 
: Operator level actions require the lowest level of permission to be run.  Any user in an application that is a member of the ''Operator'' role can run an operator level action.
 
;'''Power User'''
 
;'''Power User'''
: Power User level actions require more permissions than Operator level actions. Roles that can run Power User level actions can also run Operator level actions. Any user in an application that is a member of the "Power User" role can run Power User and Operator level actions.
+
: Power User level actions require higher permissions than Operator level actions. Roles that can run Power User level actions can also run Operator level actions. Any user in an application that is a member of the "Power User" role can run Power User and Operator level actions.
 
;'''Administrator'''
 
;'''Administrator'''
 
: Administrator level actions require the highest level of permissions. Roles that can run Administrator level actions can also run Power User and Operator actions.  Any user in an application that is a member of the "Administrators" role can run Administrator, Power User and Operator level actions.
 
: Administrator level actions require the highest level of permissions. Roles that can run Administrator level actions can also run Power User and Operator actions.  Any user in an application that is a member of the "Administrators" role can run Administrator, Power User and Operator level actions.
  
 
== Where actions can be run ==
 
== Where actions can be run ==
Actions can be run in two different locations: on servers; ''and'' through an event.
+
In Veloopti actions can be run in two different places: on a server; ''and'' through an event.
  
 
=== Actions on servers ===
 
=== Actions on servers ===
Actions can be run directly on a server that has a Veloopti agent installed. To do this, click on the server name in either the main node page, or the node page of an application. From the server there is a side menu item named ''Actions'' where actions can be run.
+
Actions can be run directly on a server that has a Veloopti agent installed. To do this, click on the node name in either the main node page, or on the node page of an application to view the node details. On the left side menu click on the item named ''Actions'' where actions can be manually run.
  
 
=== Actions on events ===
 
=== Actions on events ===
Actions can also be run from an Event. <more here>
+
Actions can be run from an Event after it has been received. To do this click on the event and navigate to the "Action" tab.  From here any actions configured to be able to run from the event can be run. Actions can only be run on open events.
 +
:[[file:Warning.png|20px]] &#160; &#160; &#160; &#160; &#160; &#160; '''Note: Unlike actions run on nodes, actions run from an event do not have levels of permissions associated with them. This means anyone who can see the event can run the action.'''
  
 
[[Category:Concepts]] [[Category:Actions]]
 
[[Category:Concepts]] [[Category:Actions]]

Revision as of 23:52, 8 August 2018

Home > An Overview > Concepts > Actions


1 Overview

An action is a executable binary or script that can be run locally on a node that has a Veloopti agent installed on it. An action can be initiated manually through the Veloopti GUI directly from a node; or manually and automatically through an event that is associated with the node. Actions come with three levels of permissions: Operator; Power User; and Administrator.

2 Permissions

There are three levels of permissions with running an action. Each permission is associated with a different role that is increment in capability.

Operator
Operator level actions require the lowest level of permission to be run. Any user in an application that is a member of the Operator role can run an operator level action.
Power User
Power User level actions require higher permissions than Operator level actions. Roles that can run Power User level actions can also run Operator level actions. Any user in an application that is a member of the "Power User" role can run Power User and Operator level actions.
Administrator
Administrator level actions require the highest level of permissions. Roles that can run Administrator level actions can also run Power User and Operator actions. Any user in an application that is a member of the "Administrators" role can run Administrator, Power User and Operator level actions.

3 Where actions can be run

In Veloopti actions can be run in two different places: on a server; and through an event.

3.1 Actions on servers

Actions can be run directly on a server that has a Veloopti agent installed. To do this, click on the node name in either the main node page, or on the node page of an application to view the node details. On the left side menu click on the item named Actions where actions can be manually run.

3.2 Actions on events

Actions can be run from an Event after it has been received. To do this click on the event and navigate to the "Action" tab. From here any actions configured to be able to run from the event can be run. Actions can only be run on open events.

Warning.png             Note: Unlike actions run on nodes, actions run from an event do not have levels of permissions associated with them. This means anyone who can see the event can run the action.