Wiki source code of Benutzerdefinierte Felder
Last modified by Sabrina V. on 2026/07/29 07:35
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.1 | 1 | {{aagon.priorisierung}} |
| 2 | 100 | ||
| 3 | {{/aagon.priorisierung}} | ||
| 4 | |||
| 5 | {{aagon.floatingbox/}} | ||
| 6 | |||
| |
22.1 | 7 | Under “Custom Fields,” you can define the fields you need for Client Automation. ACMP provides you with a wide range of fields that are populated automatically. The custom fields serve as an extension that allows you to add additional fields and name and populate them according to your preferences. These fields can therefore highlight missing data and information within the console. |
| 8 | You can create custom fields for the following categories: Assets, Clients, Contacts, Licenses, Products, Tickets, and Contracts. | ||
| |
1.1 | 9 | |
| 10 | {{aagon.infobox}} | ||
| |
22.1 | 11 | You can create custom fields only if you are a tenant administrator. |
| |
1.1 | 12 | {{/aagon.infobox}} |
| 13 | |||
| |
22.1 | 14 | = **Organizing Custom Fields** = |
| |
1.1 | 15 | |
| |
22.1 | 16 | Each category can be structured hierarchically, with folders forming the top level of the hierarchy. Within the folders, you can create as many subfolders as you like, as well as tables in which the fields are created. |
| |
1.1 | 17 | |
| |
22.1 | 18 | Using the action bar, you can add, edit, or delete the respective elements (folders, tables, and fields). |
| |
1.1 | 19 | |
| |
22.1 | 20 | = **Adding Fields** = |
| |
1.1 | 21 | |
| |
22.1 | 22 | To add a new field, you must first select the category (e.g., Assets). You can then either create a new folder or choose an existing one. This is a prerequisite for creating a new table or selecting an existing one in which the field will be created. Now select the //Add Field// ([[image:image-20220523101635-1.png]]) button. |
| |
1.1 | 23 | |
| 24 | {{aagon.infobox}} | ||
| |
22.1 | 25 | Please note that the fields inherit their cardinality. When you add a new table, you must assign the cardinality (1:1 or 1:n fields). |
| |
1.1 | 26 | {{/aagon.infobox}} |
| 27 | |||
| 28 | {{figure}} | ||
| |
4.1 | 29 | [[image:63_System_Einstellungen_BenutzerdefinierteFelder_741.png||alt="Benutzerdefiniertes Feld hinzufügen.png" data-xwiki-image-style-alignment="center"]] |
| |
1.1 | 30 | |
| 31 | {{figureCaption}} | ||
| |
22.1 | 32 | Add a Custom Field |
| |
1.1 | 33 | {{/figureCaption}} |
| 34 | {{/figure}} | ||
| 35 | |||
| |
22.1 | 36 | Enter a description and a name for the field in both German and English, then click //> Next//. On the next page, you can configure the settings and choose from 8 field types to determine the behavior of the custom field. |
| |
1.1 | 37 | |
| 38 | {{aagon.infobox}} | ||
| |
22.1 | 39 | If you enter only the German or English name, the missing value will be filled in with the value you entered. |
| |
1.1 | 40 | {{/aagon.infobox}} |
| 41 | |||
| |
22.1 | 42 | Here, you can enter an English and a German name, as well as a description, for the field. On the next page, you'll specify the field type. You have the following options: |
| |
1.1 | 43 | |
| |
22.1 | 44 | |=Field type|=(% style="width: 498px;" %)Using|=(% style="width: 781px;" %)Configuration options |
| 45 | |Checkbox|(% style="width:498px" %)Use the checkbox for Boolean values.|(% style="width:781px" %)No additional settings are available for this field type. | ||
| 46 | |Combobox|(% style="width:498px" %)A Combobox allows you to select a value from a list.|(% style="width:781px" %)Specify the field size (text characters) and select the type of Combobox (fixed list or a list that allows user input). You can also specify list items that will be listed as available values. | ||
| 47 | |Date|(% style="width:498px" %)Use these field types to represent a date.|(% style="width:781px" %)Choose between the formats //Date//, //Time //and //Date and Time//. | ||
| 48 | |Hyperlink|(% style="width:498px" %)Use this field type to display a clickable hyperlink.|(% style="width:781px" %)No additional settings are available for this field type. | ||
| 49 | |IP address|(% style="width:498px" %)Use this field type to display an IP address.|(% style="width:781px" %)Specify whether the field type is an IPv4 or an IPv6 address. | ||
| 50 | |Memo|(% style="width:498px" %)Use the “Memo” field to define a multi-line free-text field.|(% style="width:781px" %)Specify the field size and the number of visible rows. | ||
| 51 | |Text|(% style="width:498px" %)This field type allows you to enter a single line of text.|(% style="width:781px" %)Specify the maximum length of the field content. | ||
| 52 | |Number|(% style="width:498px" %)Use the number to represent all types of numerical values.|(% style="width:781px" %)First, specify whether the value is a whole number, a decimal, a currency, or a memory. If you select a decimal, you can specify the number of decimal places. If you select a currency, you can also specify a minimum and maximum value. | ||
| |
1.1 | 53 | |
| 54 | {{aagon.infobox}} | ||
| |
22.1 | 55 | Please note the following regarding the “Combobox,” “Memo,” and “Text” field types: The larger the maximum value, the more storage space is required per entry in the database, since storage space is always reserved for the maximum value. |
| |
1.1 | 56 | {{/aagon.infobox}} |
| 57 | |||
| 58 | == Assets == | ||
| 59 | |||
| |
22.1 | 60 | Within Asset Management, you can create individual inventories of fixed assets and tangible assets. Assets must be assigned to an asset type. To use custom fields in assets, simply go to //Asset Management// > //Hardware Assets// > //Asset types// > //Add Asset Type// > //Custom Fields (Step 3 of 5)//. Here, you can drag the fields you created earlier from the left side to the right half of the wizard or double-click to copy them in, and specify whether a field is required. You can also change the order of the fields used. Custom fields are useful when you want to provide additional information for your assets. For example, you might want to note the SIM card number, IMEI, or PIN for a cell phone, or the license plate number of a company vehicle. |
| |
1.1 | 61 | |
| |
22.1 | 62 | You can also use the custom fields for assets in a query if the query base is Asset Management. |
| |
1.1 | 63 | |
| 64 | {{aagon.infobox}} | ||
| |
22.1 | 65 | Several custom fields are already provided to ensure that asset types are used correctly. Therefore, when you first configure the fields, several tables and [[field>>doc:ACMP.610.ACMP-Solutions.Asset Management.Assets organisieren.WebHome||anchor="HIncludedAssetTypes"]] are displayed. |
| |
1.1 | 66 | {{/aagon.infobox}} |
| 67 | |||
| 68 | == Clients == | ||
| 69 | |||
| |
22.1 | 70 | You can access the custom fields for clients through multiple Queries. To do this, you must use either “Clients” or “Deactivated Clients” as the query base in order to display these fields. |
| |
1.1 | 71 | |
| |
22.1 | 72 | In addition to the various ways to access them, you can also display the fields via the Client Details. Within the tree structure, there is a section with the same name where all the fields you have defined are listed. You also have the option to [[customize>>doc:ACMP.610.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen auswerten.WebHome]] and modify there. |
| |
1.1 | 73 | |
| |
22.1 | 74 | == Contacts == |
| |
1.1 | 75 | |
| |
22.1 | 76 | With the custom extension for contact data, you can configure additional fields that may not be included in the predefined fields but are important for your company (e.g., the birthdate of contacts). The contact list can be accessed via the ribbon bar under Master Data. |
| |
1.1 | 77 | |
| |
22.1 | 78 | In addition to the contact list, you can also display the custom fields in a query. The query base must be based on either Helpdesk or Contacts. You can then retrieve the custom fields in a query. |
| |
1.1 | 79 | |
| 80 | {{aagon.infobox}} | ||
| |
22.1 | 81 | To use the fields in tickets, you must select them as [[contacted-related fields>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Helpdesk.WebHome||anchor="HTicketFields"]] under Helpdesk / Ticket Fields. |
| |
1.1 | 82 | {{/aagon.infobox}} |
| 83 | |||
| |
22.1 | 84 | == Licenses == |
| |
1.1 | 85 | |
| |
22.1 | 86 | After you have added a license in License Management, you can view the details of the open license in the right-hand pane, where the custom fields are displayed under the tab of the same name. The settings can only be changed when you edit the current license. |
| 87 | If you want to run a query based on the licenses in Query Management, the basis must be “Licenses” in order to view the custom fields. | ||
| |
1.1 | 88 | |
| |
22.1 | 89 | == Products == |
| |
1.1 | 90 | |
| |
22.1 | 91 | Products can also be accessed via License Management. Under the details of the respective product, you can view the custom fields you previously created. To change the values and content, you must edit the product. |
| 92 | If you should execute a query based on the custom fields, the query base must be “Products/Compliance.” | ||
| |
1.1 | 93 | |
| |
22.1 | 94 | == Tickets == |
| |
1.1 | 95 | |
| |
22.1 | 96 | The custom fields that you can view directly in the tickets can be configured under //System > Settings > Helpdesk > Ticket Fields//. Under the ticket related fields, you’ll also see the basic fields, which include, for example, the [[keyword search>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Helpdesk.WebHome||anchor="HTicketFields"]]. |
| |
1.1 | 97 | |
| |
22.1 | 98 | You can also execute a query based on the tickets by creating a new query and assigning the Helpdesk as its query base. This allows you to retrieve the custom fields from the tickets. |
| |
1.1 | 99 | |
| |
22.1 | 100 | == Contracts == |
| |
1.1 | 101 | |
| |
22.1 | 102 | Contracts can be accessed via the ribbon bar under Master Data. You can use the custom fields to add any missing fields that may not be covered by the default settings. Alternatively, you can also execute a Query based on “Contracts.” |
| |
1.1 | 103 | |
| |
22.1 | 104 |

