Configure Attribute Flow Rules Workday-V21

EmpowerID supports the configuration of attribute synchronization rules for flowing attribute changes between directories and the EmpowerID Identity Warehouse. Attribute Flow rules are visually configured and are always relative to the relationship between an attribute in a directory and the corresponding attribute in the EmpowerID Identity Warehouse. Attribute Flow rules define the specific fields and attributes that are synchronized between the EmpowerID Identity Warehouse person objects and the external user accounts to which they are linked. Additionally, Attribute Flow rules can be weighted by account store. For example, if you have connected EmpowerID to an HR system as well as Active Directory, and you want any changes made to an attribute in the HR system to take priority over changes made in Active Directory or EmpowerID (while allowing changes to be made in any system), you would give a higher score for each CRUD operation originating from the HR account store and correspondingly lower scores for the Active Directory account store.

The following flow rules are available:

  • No Sync ( Red Circle) — When this option is selected, no information flows between EmpowerID and the native system.

  • Bidirectional Flow (Bidirectional Green Arrow) — When this option is selected, changes made within EmpowerID update the native system and vice-versa. For most attributes, this is the default setting.

  • Account Store Changes Only (Left Pointing Arrow) — When this option is selected, changes can only be made in the native system and are then passed to EmpowerID. For Workday, attributes should only flow from Workday to EmpowerID. The Workday connector is read-only.

  • EmpowerID Changes Only (Right Pointing Arrow) — When this option is selected, changes can only be made in EmpowerID and are then passed to the native system.

The following CRUD operations are available:

  • Create — This operation is used to create an attribute value for an existing attribute when the value of that attribute is null.

  • Update — This operation is used to update the value of an attribute.

  • Delete — This operation is used to delete the value of an attribute.

  1. On the Account Store Details page for the Workday account store, select the Attribute Flow Rules tab.

  2. Review the attribute flow and revise as needed. EmpowerID translates the attributes in Workday to SCIM for use with the connector and represents those attributes in EmpowerID as External Directory Attributes. You map these attributes to EmpowerID Person attributes to ensure that any changes occurring to user attributes in Workday flow to the EmpowerID Person, as well as any other user accounts owned by the Person.

  3. To change the score for any of the available CRUD operations (Create, Update and Delete), enter the new score in the appropriate field. By default, scores are weighted evenly, which means that a change to an attribute originating in one connected external directory has the same authority as a change to an attribute occurring in another connected external directory.

    Attribute translation from Workday to the EmpowerID SCIM connector is as follows:

Workday Attribute

SCIM Attribute

EmpowerID Person Attribute

Country_Reference.ISO_3166-1_Alpha-2_Code

addresses[?@.type=="BUSINESS"].country

Country

Business_Site_Summary_Data.Name

siteName

JobLocationName

Organization_Data.Organization_Name.COST_CENTER

Organization[?(@.organizationType=='COST_CENTER')].organizationName

CostCenter

Organization_Data.Worker_Organization_Data.Cost_Center_Reference_ID

['urn:ietf:params:scim:schemas:extension:AdAdditionalData:2.0:User']['WorkDayDataExtension']['departmentNumber']

DepartmentNumber

Organization_Data.Organization_Name.Division

Organization[?(@.organizationType=='Division')].organizationName

Division 

Worker_Data.Worker_ID

urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.EmployeeNumber

EmployeeNumber 

Legal_Name_Data.Name_Detail_Data.First_Name

name.givenName

FirstName

Legal_Name_Data.Name_Detail_Data.Middle_Name

name.middleName

MiddleName 

Legal_Name_Data.Name_Detail_Data.Last_Name

name.familyName

LastName 

Preferred_Name_Data.Name_Detail_Data.First_Name

nickName

PreferredFirstName

Preferred_Name_Data.Name_Detail_Data.Last_Name

preferredLastName

PreferredLastName

Address_Data.Municipality

addresses[?(@.type=='BUSINESS')].locality

City

Country_Region_Descriptor

addresses[?(@.type=='BUSINESS')].region

State

Address_Data.Postal_Code

addresses[?(@.type=='BUSINESS')].postalCode

PostalCode

Address_Data.AddressLineData 

addresses[?(@.type=='BUSINESS')].streetAddress

StreetAddress

PhoneData.PhoneNumber.Communicationtype=WORK

phoneNumbers[?(@.type=='work')].value

BusinessPhone

Position_Data.Business_Title

title

Jobtitle 

Organization_Data.Organization_Name.COMPANY

Organization[?(@.organizationType=='COMPANY')].organizationName

Company 

Worker_Type_Reference.Employee_TypeID

userType

EmployeeType

Worker_Data.User_ID

userName

LogonName 

Worker_Status_Data.Active

active

Status

Worker_Status_Data.Hire_Date

hireDate

HireDate

Worker_Status_Data.Termination Date

terminationDate

TerminationDate

Manager_as_of_last_detected_manager_change_Reference. EmployeeID

['urn:ietf:params:scim:schemas:extension:enterprise:2.0:User']['manager']['value']

ManagerPersonID

FirstName, Lastname

displayName

DisplayName 

Country_Reference.ISO_3166-1_Alpha-3_Code

addresses[?(@.type=='BUSINESS')].country

Country

Email_Address_Data.Email_Address

emails[?(@.type=='work')].value

Email

PhoneData.PhoneNumber.Communicationtype=FAX

phoneNumbers[?(@.type=='fax')].value

Fax

PhoneData.Phonenumber.Communicationtype=HOMEPHONE

phoneNumbers[?(@.type=='home')].value

HomeTelephone

NumberData.Phonenumber.Communicationtype=MOBILENUMBER

phoneNumbers[?(@.type=='mobile')].value

MobilePhone

PhoneData.Phonenumber.Communicationtype=TELEPHONE

phoneNumbers[?(@.type=='other')].value

Telephone

 

name.honorificSuffix

GenerationalSuffix

WorkerData.User_ID

externalId

EmailAlias

 

EmpowerID only considers scores for attribute CRUD operations when multiple account stores with the same user records are connected to EmpowerID.

Â