Skip to content
English
Go to eletive.com
  • There are no suggestions because the search field is empty.

Segment Aliases

Aliases is a way of recognizing one or several values into one segment. 
By utilizing aliases you can make sure that segments between Eletive and your HR system are recognized, ensuring segment consistency over time, avoiding segment duplication within an attribute.

  • Aliases is a list of stored values tied to one segment.
  • SCIM 2.0 alias can be configured to be any of the defined Aliases. This is the value returned by the SCIM 2.0 API endpoint GET /Users. 

When provisioning user data into Eletive, it is advisable to configure aliases to maintain segment alignment and data integrity.

Managing Segment Aliases 

  • Manually in Eletive - in segment list click on the Action dots / Edit for the segment you wish to manage aliases for
  • Or through Mass edit segments and aliases

Use case example 1 - Aliases to consolidate values into one segment 

The standard attribute Country is a good example showcasing the potential use of aliases. Each standard country segment has a set of predefined aliases based on ISO-3166 country codes. 


For example standard country segment Sweden  has alias values 752, SE and SWE. 

Use case example 2 -Alias and Segment name as key-value pairs

Choice-type attributes are string fields that accept a single input value. Because label values in your source data may evolve over time, Eletive responds by generating new segments whenever a label changes.

Historical data remains linked to the previous segment, while new data is assigned to the updated segment—this approach maintains data integrity but may result in duplicate segments for the same attribute.

To prevent this, it's possible to store static ID values as the input sent to Eletive rather than the label values. In such cases, segment names (label values) fall outside the user provisioning scope and need to be managed manually, preferably using the Mass Edit feature. As an example: 

  • Key: "hr_001" --> value provided to attribute Department through User provisioning
  • Value: "Human Resources"  --> applied Segment name 

New departments will be created automatically, using the key as both the Segment name and alias. The Segment name should then be updated to reflect the appropriate label value.

Existing departments will not be affected, as the key is consistently received. However, any updates to labels must be reflected by updating the Segment name to the latest label value.