MENU
The following USER_IMPORT_MAPPING attribute is set up in Workday RAAS connection:
USER_IMPORT_MAPPING
{
"ImportType": "RAAS",
"ResponsePath": "wd:Report_Data.wd:Report_Entry",
"ImportMapping": {
"USERNAME": "wd:User_Name~#~string",
"SYSTEMUSERNAME": "wd:User_Name~#~string",
"FIRSTNAME": "wd:First_Name~#~string",
"CITY": "wd:Location.wd:Descriptor~#~string"
}
}
As per the above mapping, USERNAME is the user attribute defined in Workday, and User_Name is the attribute defined in EIC.
The statement is False. In the provided USER_IMPORT_MAPPING, USERNAME is the user attribute defined in EIC (Enterprise Identity Cloud), and wd:User_Name is the attribute defined in Workday. Here's a breakdown:
Saviynt's USER_IMPORT_MAPPING: This configuration within a connection (in this case, Workday RAAS) defines how data from the connected system (Workday) should be mapped to attributes within Saviynt's EIC.
ImportMapping: This section specifies the mapping between source attributes (Workday) and target attributes (EIC).
USERNAME: In the provided mapping, USERNAME (without the wd: prefix) is the target attribute, meaning it's an attribute within Saviynt's EIC.
wd:User_Name: The wd: prefix typically indicates a Workday attribute. Therefore, wd:User_Name is the source attribute from Workday.
~#~string: This likely indicates the data type of the attribute (string in this case).
Correct Interpretation: The mapping is saying: 'Take the value of the wd:User_Name attribute from Workday and map it to the USERNAME attribute in EIC.'
In essence: The USER_IMPORT_MAPPING defines how data from Workday is translated into Saviynt's internal data model, and in this case, USERNAME belongs to Saviynt (EIC), while wd:User_Name belongs to Workday.