As a machine or resource owner, you do not see all entitled actions for a provisioned item.
In an environment where you know that an action was entitled for your user or business group, you expect to see all actions when you select an item in your Items list.
The availability of actions depends on the type of provisioned resource, operational state of the resource, and how it was configured and made available. The following list provides some reasons why you do not see all configured actions.
The action is not applicable based on the current state of the provisioned resource. For example, Power Off is available only when the machine is powered on.
The action is not applicable to the selected item type. If the item does not support the action, it does not appear in the list. For example, the Create Snapshot action is not available for a physical machine, and the Connect by Using RDP action is not available if the selected item is a Linux machine.
The action is applicable for the provisioned resource type, but the action is disabled in the Infrastructure blueprint. If the action is disabled, it never appears as an available action for any of the items that were provisioned using the blueprint.
The action is not included in the entitlement used to provision the item on which you need to run the action. Only entitled actions, either as part of an IaaS blueprint or as an XaaS resource action, can appear in the Actions menu.
The action is created as an XaaS resource action but was not included in the entitlement used to provision the item on which you need to run the action. Only entitled actions appear in the Actions menu.
The action might be limited based on the configured target criteria for XaaS resource actions or resource mappings to provisioned IaaS machines.
- Verify that the action is applicable to the provisioned item or the state of the provisioned item.
- Verify that the action is configured and included in the entitlement used to provision the item.