Cloud - Customer Actions
- CrossALM
- Daniel Triftshaeuser
- Kristin Hildebrand
Customer Actions correspond to all of the actions available to users. This includes technical actions executed by the system, as well as freely definable actions.
In order to configure the Customer Actions navigate to Customer Actions and press the Add Customer Action button.
Fill the following information
Action Type
Mandatory
First configure the mandatory actions that will be used by the system.
Action Type | Comment | Recommended Description |
|---|---|---|
Initial | Used right after creation via the plugin | Created, New |
Delete | Used after the transport request is deleted either in the managed system or via the plugin. The transport remains in the list with this status description. | Deleted |
Release | Used when the transport has been released in the managed system and therefore, cannot be deleted anymore. | Released |
Couple | Used when wanting to add transport requests that already exist in the managed system | Couple, Added, New |
Decouple | Used for removing the link of the transport to the specified Jira issue and makes it disappear from the list | Decouple a description is not relevant, as the it will vanish from the list |
Custom | You are also free to define your own actions. You can define as many custom actions as you see fit. Action type Custom is not used for technical operations on the transport itself and acts as a custom label. | up to you |
Import | Uses to import transport request in the next system. | Import |
ToC | Used to create and import a transport of copies in the next system. The ToC will be shown in the list. | Transport of copies |
After creating the Customer Actions you will be able to see them on the list.
You can edit an Action by pressing the edit button or delete it by pressing the delete button.