Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Value Processors

Description

Example

CollectionValueProcessor

Takes elements out of a collection based on a mode.

Modes are first, last, max, minand none

CultureName2AttributeDropDownDefinitionValueProcessor

Resolves a source attribute to a valid language supported in the system

NullIfEmptyStringProcessor

Returns null if the source value is null or empty, if not it returns the trimmed value

RegexIfMatchThenElseValueProcessor

Returns the a value if a regex pattern matches the source attribute, if not another

RegexReplaceValueProcessor

Replaces the configured pattern in the source attribute

StringFormatValueProcessor

Formats the source attribute according to the input

StringToDateTimeConversionProcessor

Converts the source attribute to a date time

SubPropertyValueProcessor

Returns a sub property of a complex source attribute

SubstringValueProcessor

Returns a substring of the source attribute

TrimValueProcessor

Trims trailing and leading white spaces of a source attribute

Serialized or Explicit Attribute Value

An attribute value always has a serialized and an explicit value. The first one is set by the system while resolving an attribute mapping or by the import when there is a mapping configuration. The later is set whenever a user overrides this calculated or imported value. This is important to know when working with imports as the comparison between the source attribute and the target attribute always is done on the serialized value.

Let’s have a look at the following example.

Mr. Jones was hired to work for us and was therefore entered to the HR system from where we have imported him has Mr. Jones. On his first working day he tells his supervisor that he will marry next week and will be called Jones-Smith and asks him, if he could be named Jones-Smith in the system? His supervisor then renames him in the CoreOne Meta Directory to Jones-Smith.

A week passes and the change will be made officially even in the HR system. It’s important to know that we will now have a change in the import as the his record in the CoreOne Suite looks as following:

serialized

explicit

Jones

Jones-Smith

The import will always compare the source value to the serialized value and therefore detect a change. After the import, the record will look like this:

serialized

explicit

Jones-Smith

Jones-Smith