Introduction
All used attributes can be found here. The properties of a specific attribute, such as the data type, a short description, the usage type, etc. can be viewed. New attributes are configured like resources or roles, using drop-down lists. Below is a brief description of some selected configuration options:
- Datatype: Here you can choose from a variety of data types. These include String, Html, Date, Asset, etc.
- Required Field:
not mandatory: no entry is required
mandatory with warning: The user can continue the process with the warning that the information must be supplied.
mandatory with error: The process cannot continue without the entry. - Attribute Usage Type: describes what the attribute is used for. For example, the attribute FirstName has the usage type CoreIdentity Attribute. Since a CoreIdentity is always assigned a first name.
- Validator Regex: A validation rule for the attribute is generated with the help of regular expressions (regex). This means that a desired structure is mandatorily specified for the attribute. For example, if the attribute is a password, the regex can be used to specify that the password must contain a number x of special characters and at least one uppercase letter, etc. The regex can also be used to generate a validation rule for the attribute.
In addition to the standard attributes, very specific attributes can also be recorded and assigned to the corresponding locations, whether resources, roles, OU, CoreIdentities, etc.
Standard Attribut
...
There are many entities in the CoreOne Suite Meta Directory such as Core Identites, Organization Units and more. Each of those entities contains a certain set of properties. Those properties are predefined and can not be changed as they are essential for the basic operation of the software. Properties are any things from internal id, to relations to other objects or other basic information. In many cases, those properties are not sufficient to cover a customers use case. For example you might wanna use at cost center on an organization unit or the civil status of a person on a Core Identity. This is where attributes come into play. You can create your own attributes and then extend any entity in the CoreOne Suite Meta Directory by adding an appropriate attribute. This page gives you an overview on those attributes.
Properties
Any attribute consists of the following properties.
Property | Data Type | Mandatory | Example | Description | ||
|---|---|---|---|---|---|---|
Name | String |
| Cost Center | The default name used to display the attribute in the system. | ||
Systemname | String |
| ext_cost_center | You can always change the name or the translation of your attribute later on but the system name must always stay the same. The system name is used in many places from configurations to the API. To ensure that all configurations and external systems will work as expected even after you renamed an attribute, the system name is used there. To indicate a customer attribute, each attribute that you are creating must start with | ||
Translation key | String | Customer.OrganizationUnit.CostCenter | When set, the translations files will be checked against the configured translation key. If a translation is present in the current users language, that translation is used instead of the name. | |||
Placeholder Name Key | String | Customer.OrganizationUnit.CostCenter.Placeholder | The translation of this will be used as a html | |||
Description | String | The cost center of the organization unit from SAP | The description of the attribute. | |||
Datatype | Drop Down |
| String | Select any of the supported Data Types | ||
Mandatory | Drop Down |
| Mandatory | Defines if whether or not a value must be entered or not in the UI.
| ||
Updatable | Bool | True | Whether or not the attribute value can be updated by the user, an administrator or the sytem. | |||
Unique | Bool | True | Whether or not the attribute value has to be unique in the assigned context. So if you assign it to an organization unit and a core identity type, the uniqueness is checked within the context. So you can create one core identity and one organization unit with the same value, but not two core identities with the same value. | |||
Encrypted | Bool | False | Whether or not the system should store the entered value as a symmetrically encrypted value or not. | |||
Multi value | Bool | False | Whether or not more than one value can be entered and stored. | |||
Drop Down Value | Bool | False | If you would like to present the user with a list of predefined drop down value, mark it as a drop down value.
| |||
Validator Regex | String | [A-Za-z] | A regex that will be applied against the input value. | |||
Validator Regex Name Key | String | Customer.OrganizationUnit.CostCenter.LetterValidationMessage | The translation key that will be translated to the users language and presented to him in case the defined regex does not match. | |||
Order | Int | 1 | If more than one attributes are present on an form, this number will define the ordering. | |||
Attribute Group | Drop Down | Default | An entries of the defined Attribute Groups | |||
Attribute Usage Type | Multi Select | Organization Unit | Where the attribute can be assigned to. | |||
Asset Type | Drop Down | If you did choose asset as an attribute type, you will need to select the specific asset type. |
Drop Down Values
If you created an attribute with the drop down property enabled, you will find a drop down value tab on the detail page of an attribute. Here you can add or edit drop down values. Once you add or edit an entry, you will need to provide the following properties.
Property | Data Type | Mandatory | Example | Description |
|---|---|---|---|---|
Name | String |
| Cost Center One | The default name used to display the drop down value in the system. |
Translation key | String | Customer.OrganizationUnit.CostCenter.CostCenterOne | When set, the translations files will be checked against the configured translation key. If a translation is present in the current users language, that translation is used instead of the name. | |
Used Value | Dependend on the attributes data type | 334432 | This might be the same as the name, but does not have to. For example you could use a readable name as the name of the drop down value, but the internal identifier from SAP as the actual used value. Whenever the value is displayed, the name or the translation will be used, but when provisioning the value to a target system, the used value will be used. |