Wiki source code of Shortcuts und Variablen
Last modified by Steffi F on 2025/12/15 13:50
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
3.1 | 1 | {{aagon.floatingbox/}} |
| 2 | |||
| |
4.1 | 3 | (% class="wikigeneratedid" %) |
| 4 | ACMP provides you with specific shortcuts and predefined variables that enable you to work consistently and efficiently across the entire console. | ||
| |
2.1 | 5 | |
| |
4.1 | 6 | (% class="wikigeneratedid" %) |
| 7 | These enable faster navigation, simplify recurring work steps, and ensure that configurations, scripts, and automations can be implemented in a uniform and clear manner. | ||
| |
2.1 | 8 | |
| |
4.1 | 9 | = Using Shortcuts = |
| |
3.1 | 10 | |
| |
4.1 | 11 | ACMP allows you to use global keyboard shortcuts to quickly perform various actions. Some of the shortcuts are solution specific. |
| |
3.1 | 12 | |
| |
4.1 | 13 | == **General actions** == |
| |
3.1 | 14 | |
| |
4.1 | 15 | |=Shortcuts|=Related actions |
| 16 | |F1|Open Online Help | ||
| 17 | |F5 |Refresh | ||
| 18 | |Ctrl + S|Save | ||
| 19 | |Ctrl + F|Find/Hide | ||
| 20 | |Ctrl + P|Print | ||
| 21 | |Ctrl + Q|((( | ||
| 22 | Open [[Quick Launch>>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Schnellsuche.WebHome]] | ||
| 23 | |||
| |
3.1 | 24 | {{aagon.infobox}} |
| |
4.1 | 25 | The Quick Launch itself contains related shortcuts in the search. |
| |
3.1 | 26 | {{/aagon.infobox}} |
| |
4.1 | 27 | ))) |
| |
3.1 | 28 | |
| |
4.1 | 29 | == **Item actions** == |
| |
3.1 | 30 | |
| |
4.1 | 31 | |=(% style="width: 225px;" %)Shortcut|=(% style="width: 1247px;" %)Related action |
| 32 | |(% style="width:225px" %)Ctrl + N|(% style="width:1247px" %)Add item | ||
| 33 | |(% style="width:225px" %)Ctrl + E|(% style="width:1247px" %)Edit item | ||
| 34 | |(% style="width:225px" %)Del|(% style="width:1247px" %)Delete item | ||
| 35 | |(% style="width:225px" %)Ctrl + D|(% style="width:1247px" %)Duplicate item | ||
| 36 | |(% style="width:225px" %)F9|(% style="width:1247px" %)Execute item | ||
| |
3.1 | 37 | |
| |
4.1 | 38 | == **Directory actions** == |
| |
3.1 | 39 | |
| |
4.1 | 40 | |=(% style="width: 228px;" %)Shortcut|=(% style="width: 1244px;" %)Related action |
| 41 | |(% style="width:228px" %)Shift + Ctrl + N|(% style="width:1244px" %)Add directory | ||
| 42 | |(% style="width:228px" %)Shift + Ctrl + E|(% style="width:1244px" %)Edit directory | ||
| 43 | |(% style="width:228px" %)Shift + Ctrl + Del|(% style="width:1244px" %)Delete directory | ||
| 44 | |(% style="width:228px" %)Shift + Ctrl + R|(% style="width:1244px" %)Rename directory | ||
| |
3.1 | 45 | |
| |
4.1 | 46 | = Using Variables = |
| |
3.1 | 47 | |
| |
4.1 | 48 | ACMP specific variables can be used throughout the ACMP console to dynamically customise content. |
| 49 | These are specified in the format %variable name%, e.g. %TicketID%. | ||
| |
3.1 | 50 | |
| |
4.1 | 51 | To make it easier for you to work with variables, you can display all existing variables at any time using the Ctrl +Space key combination in a kind of context menu. The variable names are close to the content. You can use variables to refer to ticket-related and contact-related fields, as well as to insert your own custom fields. |
| |
3.1 | 52 | |
| |
4.1 | 53 | == Contact fields == |
| |
3.1 | 54 | |
| |
4.1 | 55 | |**Variable name**|**Corresponding field**|**Content** |
| 56 | |Contact_Company|Company name| | ||
| 57 | |Contact_CostUnit|Cost Unit| | ||
| 58 | |Contact_Department|Departments| | ||
| 59 | |Contact_Fax|Fax number| | ||
| 60 | |Contact_FirstName|First name| | ||
| 61 | |Contact_Fullname|Full name|Created from the first and last name | ||
| 62 | |Contact_LastName|Last Name| | ||
| 63 | |Contact_Mail|Email address| | ||
| 64 | |Contact_Mitarbeiterstatus_Status|Employee status| | ||
| 65 | |Contact_Phone|Phone| | ||
| 66 | |Contact_Phone2|Phone 2| | ||
| 67 | |Contact_Phone3|Phone 3| | ||
| 68 | |Contact_Phone4|Phone 4| | ||
| 69 | |Contact_Titles|Title| | ||
| 70 | |Contact_CustomFieldN|Custom Field N|N custom contact fields can be configured here. N stands for the unique numbering. | ||
| |
3.1 | 71 | | |
| 72 | |||
| |
4.1 | 73 | == Ticket field == |
| |
3.1 | 74 | |
| |
4.1 | 75 | |**Variable name**|**Corresponding field**|**Content** |
| 76 | |Ticket_Assignee|Assignee| | ||
| 77 | |Ticket_Assignee_FamilyName|Family name assignee| | ||
| 78 | |Ticket_Assignee_IsGroup|Assignee is group|((( | ||
| 79 | Possibe value: | ||
| |
3.1 | 80 | |
| |
4.1 | 81 | * Yes |
| 82 | * No | ||
| |
3.1 | 83 | ))) |
| |
4.1 | 84 | |Ticket_Assignee_Name|Name of editor| |
| 85 | |Ticket_Caption|Title|If the ticket is created by email, the title of the ticket corresponds to the subject line of the email. | ||
| 86 | |Ticket_Category|Category| | ||
| 87 | |Ticket_CategoryPath|Category path|Removed paths to the category of the tickets | ||
| 88 | |Ticket_CreationDate|Creation date| | ||
| 89 | |Ticket_Creator|Creator| | ||
| 90 | |Ticket_CreatorType|Creator type|((( | ||
| 91 | Possible values: | ||
| |
3.1 | 92 | |
| |
4.1 | 93 | * 0 (Email) |
| 94 | * 1 (ACMP user) | ||
| |
3.1 | 95 | * 2 (Self Service) |
| 96 | ))) | ||
| |
4.1 | 97 | |Ticket_Description|Description| |
| |
3.1 | 98 | |Ticket_Impact|Business Impact|((( |
| |
4.1 | 99 | Possible values: |
| |
3.1 | 100 | |
| 101 | * Company | ||
| 102 | * Department | ||
| 103 | * Single Client | ||
| 104 | * Single Server | ||
| 105 | * Site | ||
| 106 | ))) | ||
| |
4.1 | 107 | |Ticket_Keywords|Keywords| |
| 108 | |Ticket_LastModified|Last modified| | ||
| 109 | |Ticket_Priority|Priority|((( | ||
| 110 | Possible values: | ||
| |
3.1 | 111 | |
| 112 | * Trivial | ||
| 113 | * Normal | ||
| |
4.1 | 114 | * Important |
| 115 | * Critical | ||
| |
3.1 | 116 | ))) |
| |
4.1 | 117 | |Ticket_Resolution|Resolution|((( |
| 118 | Possible values: | ||
| |
3.1 | 119 | |
| |
4.1 | 120 | * No solution |
| 121 | * Not comprehensible | ||
| 122 | * Incomplete | ||
| 123 | * Duplicate | ||
| 124 | * Not solved | ||
| 125 | * Solved | ||
| |
3.1 | 126 | ))) |
| |
4.1 | 127 | |Ticket_Resolution_Quantifier|Solution weighting| |
| |
3.1 | 128 | |Ticket_State|Status|((( |
| |
4.1 | 129 | Possible values: |
| |
3.1 | 130 | |
| |
4.1 | 131 | * Created |
| 132 | * Viewed | ||
| 133 | * In progress | ||
| 134 | * Waiting | ||
| 135 | * Closed | ||
| |
3.1 | 136 | ))) |
| |
4.1 | 137 | |TicketGUID|Ticket-GUID|The unique ticket GUID is generated automatically and identifies the ticket in the database. The ticket GUID cannot be changed and is intended for use with the Web Interface. |
| 138 | |TicketGuidUrl|Ticket-GUID-URL|This is where the ticket GUID is customised for use in hyperlinks. In connection with the web server URL, the ticket can be accessed directly from the Web Interface here. | ||
| 139 | |TicketID|Ticket-ID|The unique ticket ID is generated automatically and identifies the ticket in the ACMP Console. The ticket ID cannot be changed. | ||
| 140 | |Ticket_CustomFieldN|User defined ticket field N|N user-defined ticket fields can be configured here. N stands for the unique numbering. | ||
| |
3.1 | 141 | |
| |
4.1 | 142 | == Comment fields == |
| |
3.1 | 143 | |
| |
4.1 | 144 | |**Variable name**|**Corresponding field**|**Content** |
| 145 | |Comment_Text|Comment| | ||
| 146 | |Comment_Creator|Username| | ||
| 147 | |Comment_Creator_Name|First name of the creator| | ||
| 148 | |Comment_Creator_FamilyName|Last name of the creator |

