MENU
Refer to the following scenario to answer the question below.
You have been asked to build an integration using the Core Connector: Worker template and should leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no change detection) for employees only and will include personal data. The vendor receiving the file requires marital status values to be sent using a list of codes that they have provided instead of the text values that Workday uses internally and if a text value in Workday does not align with the vendors list of codes the integration should report "OTHER".
What configuration is required to output the list of codes required from by the vendor instead of Workday's values in this integration?
The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data. The vendor requires marital status values to be transformed from Workday's internal text values (e.g., 'Married,' 'Single') to a specific list of codes (e.g., 'M,' 'S'), and any Workday value not matching the vendor's list should output 'OTHER.' Let's analyze the configuration:
Requirement:Transform the 'Marital Status' field values into vendor-specific codes, with a fallback to 'OTHER' for unmapped values. This is a field-level transformation, common in Core Connectors when aligning Workday data with external system requirements.
Integration Maps:In Core Connectors, Integration Maps are the primary tool for transforming field values. You create a map that defines source values (Workday's marital status text) and target values (vendor's codes). The 'Default' setting in an integration map specifies what value to output if a Workday value isn't explicitly mapped. Here, setting the default to 'OTHER' ensures that any marital status not in the vendor's list (e.g., a new Workday value like 'Civil Union' not recognized by the vendor) is output as 'OTHER.'
Option Analysis:
A . Configure Integration Maps with a blank Default: Incorrect. A blank default would leave the field empty or pass the original Workday value for unmapped cases, not 'OTHER,' failing the requirement.
B . Configure Integration Attributes with a blank Default: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery method), not field value transformations. They don't support mapping or defaults for specific fields like marital status.
C . Configure Integration Maps with 'OTHER' as a Default: Correct. This uses Integration Maps to map Workday values to vendor codes and sets 'OTHER' as the default for unmapped values, meeting the requirement fully.
D . Configure Integration Attributes with 'OTHER' as a Default: Incorrect. Integration Attributes don't handle field-level transformations or defaults for data values, making this option inapplicable.
Implementation:
Edit the Core Connector: Worker integration.
Use the related action Configure Integration Maps.
Create a map for the 'Marital Status' field (e.g., 'Married' 'M,' 'Single' 'S').
Set the Default Value to 'OTHER' in the map configuration.
Test the output to ensure mapped values use vendor codes and unmapped values return 'OTHER.'
Reference from Workday Pro Integrations Study Guide:
Core Connectors & Document Transformation: Section on 'Configuring Integration Maps' explains mapping field values and using defaults for unmapped cases.
Integration System Fundamentals: Highlights how Core Connectors transform data to meet vendor specifications.