CoreOne Universal Connector Mappings

Introduction

In order to connect source attributes (let’s say the first name in SAP HCM) to a target attribute (let’s say the first name in the CoreOne Meta Directory) we have to configure a MappingConfiguration. There are rather simple ones where we simply map one attribute to another one and there are more complex ones where we also transform the data. This page describes the available mappings.

Mapping Types

There are two types of mappings, AttributeMappingand PropertyMapping. AttributeMapping are used to map to an attribute of an entity such as a first name of an Core Identity. Some entities have predefined properties that are not stored as attributes. To map those, you have to configure an PropertyMapping. An example for a PropertyMapping is the tenant on a Core Identity.

Attribute Mappings

Mapping Configuration	Description	Example
`FixObjectAttributeConfiguration`	Can be used to map an target attribute to a fixed value.	`new FixObjectPropertyMappingConfiguration<bool>(CoreIdentityDefinition.PropertyNames.Active,true)`
`SoureParameterAttributeMappingConfiguration`	Can be used to map a target attribute to a source attribute	`new SourceParameterAttributeMappingConfiguration(7, "sAMAccountname")`
`SwitchCaseAttributeMappingConfiguration`	Can be used to map an target attribute to a fixed value based on the source value	`new SwitchCaseAttributeMappingConfiguration(500044, "TwoFAMethode", new Dictionary<string, object> {{ "TOT Pin", true}}, false )`

Property Mappings

Mapping Configuration	Description	Example
`ConcatCollectionPropertyMappingConfiguration`	Can be applied to a source list and will return all values that match a criteria with the option to replace those values with new ones. I.e. the source collection is a list of customers ids. If customer id 1000 is present in the list, return the customer name “BestRun”. Multiple of such conditions can be applied.
`ConcatCollectionPropertyRegexMappingConfiguration`	Can be applied to a source list and will return all values that match a regex pattern with the option to replace those values with new ones. I.e. the source collection is a list of customers ids. If the id matches 100*, return the customer name “BestRung”.
`FixObjectPropertyMappingConfiguration`
`ResolvedCoreIdentityIdByAttributeValueMappingConfiguration`
`ResolvedCoreIdentityIdByForeignIdMappingConfiguration`
`ResolvedCoreIdentityIdByObjectIdMappingConfiguration`
`ResolvedResourceIdByAttributeValueMappingConfiguration`
`ResolvedResourceIdByForeignIdMappingConfiguration`
`ResolvedResourceIdByObjectIdMappingConfiguration`
`ResolvedResourceIdByResourceDefinitionAttributeValueMappingConfiguration`
`ResolvedRoleIdByAttributeValueMappingConfiguration`
`ResolvedRoleIdByForeignIdMappingConfiguration`
`SourceParameterPropertyMappingConfiguration`
`SourceParameterPropertyMappingDateTimeFormatConfiguration`
`SwitchCasePropertyMappingConfiguration`

Value Processors

Some of the mapping processors can be further enhanced with value processors. In this case, the resolved value will be further transformed by using a list of value processors. The following are the values processors that are available.

Value Processors	Description	Example
`CollectionValueProcessor`
`CultureName2AttributeDropDownDefinitionValueProcessor`
`NullIfEmptyStringProcessor`
`ReferenceToInputPlaceholder`
`RegexIfMatchThenElseValueProcessor`
`RegexReplaceValueProcessor`
`StringFormatValueProcessor`
`StringToDateTimeConversionProcessor`
`SubPropertyValueProcessor`
`SubstringValueProcessor`
`TrimValueProcessor`