Pass the Workday Integrations Workday-Pro-Integrations Questions and answers with Dumpstech

The requirement is to create a calculated field for a dashboard that displays a worker’s name and the number of days until their next birthday in the format "[Worker's Name]'s birthday is in [X] days" (e.g., "Logan McNeil's birthday is in 103 days"). This involves calculating the difference between today’s date and the worker’s next birthday, then formatting the output as a text string. Let’s break down the necessary functions:

Date Difference:To calculate the number of days until the worker’s next birthday, you need to determine the difference between the current date and the worker’s birthdate in the current or next year (whichever is upcoming). The Date Difference function calculates the number of days between two dates. In this case:

Use the worker’s "Date of Birth" field (from the Worker business object).

Adjust the year of the birthdate to the current year or next year (if the birthday has already passed this year) using additional logic.

Calculate the difference from today’s date to this adjusted birthday date. For example, if today is February 21, 2025, and Logan’s birthday is June 4 (adjusted to June 4, 2025), Date Difference returns 103 days.

Format Number:The result of Date Difference is a numeric value (e.g., 103). To ensure it displays cleanly in the output string (without decimals or unnecessary formatting), Format Number can be used to convert it to a simple integer string (e.g., "103").

Text Constant:To build the output string, static text like "’s birthday is in " and " days" is needed. The Text Constant function provides fixed text values to include in the final concatenated result.

Concatenate Text:The final step is to combine the worker’s name (e.g., "Logan McNeil"), the static text, and the calculated days into one string. Concatenate Text merges multiple text values into a single output, such as "Logan McNeil" + "’s birthday is in " + "103" + " days".

Option Analysis:

A. Format Date, Increment or Decrement Date, Extract Single Instance, Format Text: Incorrect. Format Date converts dates to strings but doesn’t calculate differences. Increment or Decrement Date adjusts dates but isn’t suited for finding days until a future event. Extract Single Instance is for multi-instance fields, not relevant here. Format Text adjusts text appearance, not numeric calculations.

B. Build Date, Format Date, Extract Single Instance, Format Text: Incorrect. Build Date creates a date from components, useful for setting the next birthday, but lacks the difference calculation. Format Date and Extract Single Instance don’t apply to the core need.

C. Date Difference, Format Number, Text Constant, Concatenate Text: Correct. These functions cover calculating the days, formatting the number, adding static text, and building the final string.

D. Increment or Decrement Date, Format Number, Text Constant, Concatenate Text: Incorrect. Increment or Decrement Date can’t directly calculate days to a future birthday without additional complexity; Date Difference is more appropriate.

Implementation:

Use Date Difference to calculate days from today to the next birthday (adjusting the year dynamically with additional logic if needed).

Apply Format Number to ensure the result is a clean integer.

Use Text Constant for static text ("’s birthday is in " and " days").

Use Concatenate Text to combine Worker Name, static text, and the formatted number.

References from Workday Pro Integrations Study Guide:

Workday Calculated Fields: Section on "Date Functions" explains Date Difference for calculating time spans.

Report Writer Fundamentals: Covers Concatenate Text and Text Constant for string building in reports.

This question addresses a troubleshooting scenario in Workday Pro Integrations, where a calculated field used as a field override in a Connector does not appear in the output, despite having a value. Let’s analyze the potential causes and evaluate each option.

Understanding Calculated Fields and Connectors in Workday

Calculated Fields: In Workday, calculated fields are custom fields created using Workday’s expression language to derive values based on other fields, conditions, or functions. They are often used in reports, integrations, and business processes to transform or aggregate data. Calculated fields can reference other fields (data sources) and require appropriate security permissions to access those underlying fields.

Field Override in Connectors: In a Core Connector or other integration system, a field override allows you to replace or supplement a default field with a custom value, such as a calculated field. This is configured in the integration’s mapping or transformation steps, ensuring the output includes the desired data. However, for the calculated field to appear in the output, it must be accessible, have a valid value, and be properly configured in the integration.

Issue: Calculated Field Not Appearing in Output: If the calculated field has a value but doesn’t appear in the Connector’s output, the issue likely relates to security, configuration, or access restrictions. The question assumes the field has a value, so we focus on permissions or setup errors rather than data issues.

Evaluating Each Option

Let’s assess each option based on Workday’s integration and security model:

Option A: Access not provided to calculated field data source.

Analysis: This is partially related but incorrect as the primary cause. Calculated fields often rely on underlying data sources (e.g., worker data, organization data) to compute their values. If access to the data source is restricted, the calculated field might not compute correctly or appear in the output. However, the question specifies the field has a value, implying the data source is accessible. The more specific issue is likely access to the individual fields within the calculated field’s expression, not just the broader data source.

Why It Doesn’t Fit: While data source access is important, it’s too general here. The calculated field’s value exists, suggesting the data source is accessible, but the problem lies in finer-grained permissions for the fields used in the calculation.

Option B: Access not provided to all fields in the calculated field.

Analysis: This is correct. Calculated fields in Workday are expressions that reference one or more fields (e.g., Worker_ID + Position_Title). For the calculated field to be used in a Connector’s output, the ISU (via its ISSG) must have access to all fields referenced in the calculation. If any field lacks "Get" or "View" permission in the relevant domain (e.g., Worker Data), the calculated field won’t appear in the output, even if it has a value. This is a common security issue in integrations, as ISSGs must be configured with domain access for every field involved.

Why It Fits: Workday’s security model requires granular permissions. For example, if a calculated field combines Worker_Name and Hire_Date, the ISU needs access to both fields’ domains. If Hire_Date is restricted, the calculated field fails to output, even with a value. This aligns with the scenario and is a frequent troubleshooting point in Workday Pro Integrations.

Option C: Access not provided to Connector calculated field web service.

Analysis: This is incorrect. There isn’t a specific "Connector calculated field web service" in Workday. Calculated fields are part of the integration’s configuration, not a separate web service. The web service operation used by the Connector (e.g., Get_Workers) must have permissions, but this relates to the overall integration, not the calculated field specifically. The issue here is field-level access, not a web service restriction.

Why It Doesn’t Fit: This option misinterprets Workday’s architecture. Calculated fields are configured within the integration, not as standalone web services, making this irrelevant to the problem.

Option D: Access not provided to all instances of calculated field.

Analysis: This is incorrect. The concept of "instances" typically applies to data records (e.g., all worker records), not calculated fields themselves. Calculated fields are expressions, not data instances, so there’s no need for "instance-level" access. The issue is about field-level permissions within the calculated field’s expression, not instances of the field. This option misunderstands Workday’s security model for calculated fields.

Why It Doesn’t Fit: Calculated fields don’t have "instances" requiring separate access; they depend on the fields they reference, making this option inaccurate.

Final Verification

The correct answer is Option B, as the calculated field’s absence in the output is likely due to the ISU lacking access to all fields referenced in the calculated field’s expression. For example, if the calculated field in a Core Connector: Worker Data combines Worker_ID and Department_Name, the ISSG must have "Get" access to both the Worker Data and Organization Data domains. If Department_Name is restricted, the calculated field won’t output, even with a value. This is a common security configuration issue in Workday integrations, addressed by reviewing and adjusting ISSG domain permissions.

This aligns with Workday’s security model, where granular permissions are required for all data elements, as seen in Questions 26 and 28. The assumption that the field has a value rules out data or configuration errors, focusing on security as the cause.

Supporting Documentation

The reasoning is based on:

Workday Community documentation on calculated fields, security domains, and integration mappings.

Tutorials on configuring Connectors and troubleshooting, such as Workday Advanced Studio Tutorial, highlighting field access issues.

Integration security guides from partners (e.g., NetIQ, Microsoft Learn, Reco.ai) detailing ISSG permissions for fields in calculated expressions.

Community discussions on Reddit and Workday forums on calculated field troubleshooting (r/workday on Reddit).

When creating an outbound connector using the Workday Core Connector: Organization Outbound template, you need to configure the connector to meet specific vendor requirements, such as formatting output data and adjusting document retention policies. Let's break down the question and analyze the requirements and options based on Workday's integration framework, specifically focusing on the Core Connector and its configuration tasks.

Understanding the Requirements

Output Data Formatting:The vendor has provided a table specifying how organization types should appear in the output file (e.g., Cost Center as "CC", Pay Group as "PAY", Supervisory as "S", and any other value as "OTHER"). This indicates a need to transform or map Workday organization data into specific output values, which is typically handled by configuring how fields are processed or mapped in the integration.

Document Retention Policy Change:The vendor wants to change the default document retention policy from 30 days to 7 days. In Workday, document retention policies for integrations (e.g., files stored on SFTP or other delivery methods) are managed through integration settings, specifically attributes related to file retention or delivery options.

Analyzing Workday Core Connector: Organization Outbound

The Core Connector: Organization Outbound template is a pre-built Workday integration template used to extract organization-related data (e.g., cost centers, pay groups, supervisory organizations) and send it to an external system. It leverages Workday's integration framework, including integration maps, field overrides, and attributes, to customize data output and behavior.

Integration Maps: Used to define how data is transformed or mapped from Workday to the output format, often involving XSLT or predefined mappings.

Integration Field Overrides: Allow you to override or customize how specific fields are displayed or formatted in the output, such as mapping "Cost Center" to "CC" as per the vendor's table.

Integration Attributes: Control broader integration settings, such as delivery methods, file formats, and retention policies (e.g., document retention duration).

Integration Field Attributes: Typically focus on specific field-level properties but are less commonly used for retention policies or broad mappings compared to the above options.

Evaluating the Vendor's Output Requirements

The table provided (Cost Center → "CC", Pay Group → "PAY", Supervisory → "S", any other value → "OTHER") suggests a need to transform or override the default output values for organization types. This is a field-level customization, best handled by Integration Field Overrides, which allow you to specify custom values or formats for specific fields in the output.

For example, in the Core Connector, you can use Integration Field Overrides to map the Workday organization type (e.g., "Cost_Center") to the vendor's desired output ("CC"). This is a common practice for outbound integrations where external systems require specific formatting.

Evaluating the Retention Policy Change

The default document retention policy of 30 days needs to be changed to 7 days. In Workday, retention policies for integration output files (e.g., files delivered via SFTP or email) are configured as part of the integration's attributes, not field-level settings.

Integration Attributes are used to manage integration-wide settings, including delivery options, file retention periods, and other global configurations. You can specify the retention period (e.g., 7 days) in the attributes section of the Core Connector configuration.

This is distinct from field-level overrides or maps, as retention is not tied to individual data fields but to the integration's output management.

Analyzing the Options

Now, let's evaluate each option to determine which tasks are needed to meet both requirements:

A. Configure Integration Maps and Configure Integration Attributes

Integration Maps: These are used for broader data transformations or mappings, such as converting Workday XML to another format or defining complex data relationships. While they could theoretically handle the output value mappings (e.g., Cost Center → "CC"), they are typically more complex and less granular than field overrides for simple value changes.

Integration Attributes: Correct for configuring the retention policy (e.g., changing from 30 to 7 days), as attributes manage integration-wide settings like retention.

Why Not Sufficient?: Integration Maps are overkill for simple field value overrides like the vendor's table, and field-level customization is better handled by Integration Field Overrides for precision and ease.

B. Configure Integration Field Overrides and Configure Integration Field Attributes

Integration Field Overrides: Correct for mapping specific field values (e.g., Cost Center → "CC"), as they allow granular control over output formats for individual fields.

Integration Field Attributes: These are less commonly used and typically focus on field-specific properties (e.g., data type, length), not broad integration settings like retention policies. Retention is not managed at the field level, so this is incorrect for the retention requirement.

Why Not Sufficient?: Integration Field Attributes do not handle retention policies, making this option incomplete.

C. Configure Integration Field Overrides and Configure Integration Attributes

Integration Field Overrides: Perfect for mapping the vendor's output values (e.g., Cost Center → "CC", Pay Group → "PAY", etc.), as they allow precise control over field-level output formatting.

Integration Attributes: Correct for configuring the retention policy (e.g., changing from 30 to 7 days), as attributes manage integration-wide settings like file retention.

Why Sufficient?: This combination addresses both requirements—field-level output formatting and integration-wide retention policy changes—making it the most accurate choice.

D. Configure Integration Maps and Configure Integration Field Attributes

Integration Maps: As explained, these are better for complex transformations, not simple field value overrides like the vendor's table. They could work but are less efficient than field overrides.

Integration Field Attributes: As noted, these do not handle retention policies or broad integration settings, making them incorrect for the retention requirement.

Why Not Sufficient?: This combination fails to address retention effectively and uses Integration Maps when Integration Field Overrides would be more appropriate for the output formatting.

Conclusion

Based on the analysis, the vendor's requirements for output formatting (mapping organization types to specific values) and changing the retention policy (from 30 to 7 days) are best met by:

Integration Field Overrides: To customize the output values for organization types (e.g., Cost Center → "CC") as shown in the table.

Integration Attributes: To adjust the document retention policy from 30 days to 7 days.

The Document Transformation Connector is used in Workday to process and reformat XML outputs — often from Core Connector or EIB integrations — into custom formats like CSV, JSON, or flattened XML.

“The primary role of the Document Transformation Connector is to apply XSLT-based formatting, data reorganization, and validation to the output of Workday integrations before delivery to downstream systems.”

This is especially useful when third-party vendors require a specific format not natively supported by the integration system.

Why the other options are incorrect:

A. Managing business processes is not a DT Connector’s function.

B. Calculations are not the main purpose — that’s more for Calculated Fields or Studio.

D. While security is essential, secure connections are managed through Workday’s integration system and transport configuration, not the DT connector.

Overview

For an outbound Enterprise Interface Builder (EIB) in Workday, the option that uses a Workday-delivered transformation to output a format other than Workday XML is Alternate Output Format. This allows you to select formats like CSV, which Workday handles without needing custom coding.

How It Works

When setting up an outbound EIB, you can use a custom report as the data source. By choosing an alternate output format, such as CSV, Workday automatically transforms the data into that format. This is surprising because it simplifies the process, requiring no additional user effort for transformation.

Why Not the Others?

XSL Attachment Transformation (B): This requires you to provide your own XSL file, making it a custom transformation, not delivered by Workday.

Custom Transformation (C): This is clearly user-defined, not Workday-delivered.

Custom Report Transformation (D): This also involves user customization, typically through XSL, and isn't a pre-built Workday option.

Comprehensive Analysis

This section provides a detailed examination of Workday's Enterprise Interface Builder (EIB) transformation options, focusing on outbound integrations and the specific question of identifying the option that uses a Workday-delivered transformation to output a format other than Workday XML. We will explore the functionality, configuration, and implications of each option, ensuring a thorough understanding based on available documentation and resources.

Understanding Workday EIB and Outbound Integrations

Workday EIB is a no-code, graphical interface tool designed for both inbound and outbound integrations, facilitating the exchange of data between Workday and external systems. For outbound EIBs, the process involves extracting data from Workday (typically via a custom report) and delivering it to an external endpoint, such as via SFTP, email, or other protocols. The integration process consists of three key steps: Get Data, Transform, and Deliver.

Get Data: Specifies the data source, often a Workday custom report, which must be web service-enabled for EIB use.

Transform: Optionally transforms the data into a format suitable for the external system, using various transformation types.

Deliver: Defines the method and destination for sending the transformed data.

The question focuses on the Transform step, seeking an option that uses a Workday-delivered transformation to output a format other than Workday XML, which is typically the default format for Workday data exchanges.

Analyzing the Options

Let's evaluate each option provided in the question to determine which fits the criteria:

Alternate Output Format (A)

Description: This option is available when configuring the Get Data step, specifically when using a custom report as the data source. It allows selecting an alternate output format, such as CSV, Excel, or other supported formats, instead of the default Workday XML.

Functionality: When selected, Workday handles the transformation of the report data into the chosen format. For example, setting the alternate output format to CSV means the EIB will deliver a CSV file, and this transformation is performed by Workday without requiring the user to define additional transformation logic.

Workday-Delivered: Yes, as the transformation to the alternate format (e.g., CSV) is part of Workday's report generation capabilities, not requiring custom coding or user-provided files.

Output Format Other Than Workday XML: Yes, formats like CSV are distinct from Workday XML, fulfilling the requirement.

From resources like Workday HCM features | Workday EIB, it's noted that custom reports can use CSV as an alternate output format, and this is managed by Workday, supporting our conclusion.

XSL Attachment Transformation (B)

Description: This involves attaching an XSL (Extensible Stylesheet Language) file to the EIB for transforming the data, typically from XML to another format like CSV or a custom structure.

Functionality: The user must create or provide the XSL file, which defines how the data is transformed. This is used in the Transform step to manipulate the XML output from the Get Data step.

Workday-Delivered: No, as the XSL file is custom-created by the user. Resources like r/workday on Reddit: EIB xslt Transformation discuss users working on XSL transformations, indicating they are user-defined, not pre-built by Workday.

Output Format Other Than Workday XML: Yes, it can output formats like CSV, but it's not Workday-delivered, so it doesn't meet the criteria.

Custom Transformation (C)

Description: This option allows users to define their own transformation logic, often through scripting or other custom methods, to convert the data into the desired format.

Functionality: It is a user-defined transformation, typically used for complex scenarios where standard options are insufficient.

Workday-Delivered: No, as it explicitly states "custom," meaning it's not provided by Workday.

Output Format Other Than Workday XML: Yes, it can output various formats, but again, it's not Workday-delivered, so it doesn't fit.

Custom Report Transformation (D)

Description: This might refer to transformations specifically related to custom reports, potentially involving user-defined logic to manipulate the report data.

Functionality: From resources like Spark Databox - using custom report transformation, it involves using custom XSL transformations, indicating user involvement. It seems to be a subset of custom transformations, focusing on report data.

Workday-Delivered: No, as it involves custom XSL, which is user-provided, not pre-built by Workday.

Output Format Other Than Workday XML: Yes, it can output formats like pipe-delimited files, but it's not Workday-delivered, so it doesn't meet the criteria.

The task is to write XSLT within a template matching wd:Report_Data/wd:Report_Entry to categorize wd:Job_Skills data, outputting "HR Skills" if the value contains "HR" and "NON-HR Skills" if it does not, using a series of elements. The correct syntax must use the contains() function to check for the substring "HR" within wd:Job_Skills, as the question implies partial matching (e.g., "HR Specialist" or "Senior HR"), not exact equality.

Let’s analyze each option:

Option A:

xml

HR Skills

NON-HR Skills

Issues:

is misused here. It outputs the result of the expression (e.g., "true" or "false" for a comparison), not the conditional text. The inside won’t execute as intended.

The = operator checks for exact equality (e.g., wd:Job_Skills must be exactly "HR"), not substring presence, which contradicts the requirement to check if "HR" is contained within the value.

is malformed (self-closing without a test attribute) and misplaced.

Verdict: Incorrect syntax and logic.

Option B:

xml

HR Skills

NON-HR Skills

Issues:

Similar to A, outputs the boolean result of contains() ("true" or "false"), not the conditional text "HR Skills" or "NON-HR Skills."

The elements are inside invalid tags (self-closing, no test), rendering them ineffective.

While contains() is correct for substring checking, the structure fails to meet the requirement.

Verdict: Incorrect structure despite using contains().

Option C:

xml

HR Skills

NON-HR Skills

Analysis:

Uses correctly with test attributes, satisfying the "series of elements" requirement.

However, wd:Job_Skills='HR' tests for exact equality, not whether "HR" is contained within the value. For example, "HR Specialist" would fail this test, outputting "NON-HR Skills" incorrectly.

Verdict: Semantically incorrect due to exact matching instead of substring checking.

Option D:

xml

HR Skills

NON-HR Skills

Analysis:

Correctly uses with test attributes, aligning with the question’s requirement.

The contains() function properly checks if "HR" is a substring within wd:Job_Skills (e.g., "HR Manager" or "Senior HR" returns true).

not(contains()) ensures the opposite condition, covering all cases (mutually exclusive).

outputs the exact strings "HR Skills" or "NON-HR Skills" as required.

Note: The closing tag is a typo in the option (should be ), but in context, it’s an obvious formatting error, not a substantive issue.

Verdict: Correct logic and syntax, making D the best answer.

Correct Implementation in Context:

xml

HR Skills

NON-HR Skills

Example Input: Senior HR Analyst → Output: HR Skills

Example Input: IT Specialist → Output: NON-HR Skills

Workday Pro Integrations Study Guide: "Configure Integration System - TRANSFORMATION" section, detailing and contains() for conditional XSLT logic in Workday.

Workday Documentation: "XSLT Transformations in Workday" under EIB, confirming wd: namespace usage and string functions.

W3C XSLT 1.0 Specification: Section 9.1, "Conditional Processing with ," and Section 11.2, "String Functions" (contains()).

Workday Community: Examples of substring-based conditionals in XSLT for report transformations.

The scenario requires configuring a Core Connector: Candidate Outbound integration with the Data Initialization Service (DIS) to include only candidates who have undergone a candidate assessment event in Workday. Core Connectors are event-driven integrations that rely on business process transactions or specific data changes to trigger data extraction. Let’s analyze how to meet this requirement:

Understanding Core Connector and DIS:The Core Connector: Candidate Outbound integration extracts candidate data based on predefined services and events. The Data Initialization Service (DIS) ensures the initial dataset is populated, but ongoing updates depend on configured integration services that define which candidates to include based on specific events or conditions.

Candidate Assessment Event:In Workday, a "candidate assessment event" typically refers to a step in the recruiting business process where a candidate completes an assessment. The requirement to filter for candidates with this event suggests limiting the dataset to those who triggered an assessment-related transaction.

Integration Services:In Core Connectors, integration services determine the scope of data extracted by subscribing to specific business events or conditions. For this scenario, you can configure the integration services to monitor the "Candidate Assessment" event (or a related business process step) and include only candidates who have completed it. This is done by selecting or customizing the appropriate service within the Core Connector configuration to filter the candidate population.

Option Analysis:

A. Configure the integration services to only include candidates with assessments: Correct. This involves adjusting the integration services in the Core Connector to filter candidates based on the assessment event, ensuring only relevant candidates are included in the output file.

B. Set the integration transaction log to subscribe to specific transaction types: Incorrect. The integration transaction log tracks processed transactions for auditing but doesn’t control which candidates are included in the output. Subscription to events is handled via integration services, not the log.

C. Make the Candidate Assessment field required in integration field attributes: Incorrect. Integration field attributes define field-level properties (e.g., formatting or mapping), not the population of candidates included. Making a field "required" doesn’t filter the dataset.

D. Create an integration map to output values for candidates with assessments: Incorrect. Integration maps transform or map field values (e.g., converting "United States" to "USA") but don’t filter the population of candidates included in the extract. Filtering is a service-level configuration.

Implementation:

Edit the Core Connector: Candidate Outbound integration.

In the Integration Services section, select or configure a service tied to the "Candidate Assessment" event (e.g., a business process completion event).

Ensure the service filters the candidate population to those with an assessment event recorded.

Test the integration to verify only candidates with assessments are extracted.

References from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on "Configuring Integration Services" explains how services define the data scope based on events or conditions.

Integration System Fundamentals

The requirement is to create a calculated field for a dashboard that displays a worker’s name and the number of days until their next birthday in the format "[Worker's Name]'s birthday is in [X] days" (e.g., "Logan McNeil's birthday is in 103 days"). This involves calculating the difference between today’s date and the worker’s next birthday, then formatting the output as a text string. Let’s break down the necessary functions:

Date Difference:To calculate the number of days until the worker’s next birthday, you need to determine the difference between the current date and the worker’s birthdate in the current or next year (whichever is upcoming). The Date Difference function calculates the number of days between two dates. In this case:

Use the worker’s "Date of Birth" field (from the Worker business object).

Adjust the year of the birthdate to the current year or next year (if the birthday has already passed this year) using additional logic.

Calculate the difference from today’s date to this adjusted birthday date. For example, if today is February 21, 2025, and Logan’s birthday is June 4 (adjusted to June 4, 2025), Date Difference returns 103 days.

Format Number:The result of Date Difference is a numeric value (e.g., 103). To ensure it displays cleanly in the output string (without decimals or unnecessary formatting), Format Number can be used to convert it to a simple integer string (e.g., "103").

Text Constant:To build the output string, static text like "’s birthday is in " and " days" is needed. The Text Constant function provides fixed text values to include in the final concatenated result.

Concatenate Text:The final step is to combine the worker’s name (e.g., "Logan McNeil"), the static text, and the calculated days into one string. Concatenate Text merges multiple text values into a single output, such as "Logan McNeil" + "’s birthday is in " + "103" + " days".

Option Analysis:

A. Format Date, Increment or Decrement Date, Extract Single Instance, Format Text: Incorrect. Format Date converts dates to strings but doesn’t calculate differences. Increment or Decrement Date adjusts dates but isn’t suited for finding days until a future event. Extract Single Instance is for multi-instance fields, not relevant here. Format Text adjusts text appearance, not numeric calculations.

B. Build Date, Format Date, Extract Single Instance, Format Text: Incorrect. Build Date creates a date from components, useful for setting the next birthday, but lacks the difference calculation. Format Date and Extract Single Instance don’t apply to the core need.

C. Date Difference, Format Number, Text Constant, Concatenate Text: Correct. These functions cover calculating the days, formatting the number, adding static text, and building the final string.

D. Increment or Decrement Date, Format Number, Text Constant, Concatenate Text: Incorrect. Increment or Decrement Date can’t directly calculate days to a future birthday without additional complexity; Date Difference is more appropriate.

Implementation:

Use Date Difference to calculate days from today to the next birthday (adjusting the year dynamically with additional logic if needed).

Apply Format Number to ensure the result is a clean integer.

Use Text Constant for static text ("’s birthday is in " and " days").

Use Concatenate Text to combine Worker Name, static text, and the formatted number.

References from Workday Pro Integrations Study Guide:

Workday Calculated Fields: Section on "Date Functions" explains Date Difference for calculating time spans.

Report Writer Fundamentals: Covers Concatenate Text and Text Constant for string building in reports.

To surface a Calculated Field in a Core Connector: Worker (CCW) outbound, you use an Integration Field Override to substitute the connector’s default source with your calculated value. An integration map (Option A) is intended to translate or normalize code values (for example, mapping internal Worker Type codes to the vendor’s codes), not to replace the source of a field. Integration attributes (Option D) and integration field attributes (Option C) manage connector behavior and attributes, but they do not replace a field’s data source with a calculated field. Therefore, the correct method to “pull” a calculated field into the CCW output is an Integration Field Override (Option B).

Why the other elements in the scenario matter (and how they’re handled) — with exact extracts from your materials:

Mapping Worker Type to external codes → Integration Maps (supports, but not the asked action):Your deployment guides call out maintaining and using Integration System Maps for code translations. This is exactly where you’d map “Worker Type” to the external system’s codes, but it is not how you inject a calculated field into the payload.

“Maintenance of Integration System Maps”

“WORKDAY SETUP – NON STATIC MAPS” and “WORKDAY SETUP – STATIC MAPS” (table of contents for configuration of maps)

Filename requires timestamp/sequence number → Sequence Generator (supports the scenario):Your Time Tracking/PECI deployment guide explicitly includes a Sequence Generator configuration that’s used with certified connectors to build compliant, unique file names (often with timestamps and/or sequence numbers) before delivery.

“3.6 Sequence Generator” (configuration item for certified integrations used in file naming)

Transformation before delivery → Standard integration flow (transform then deliver):The same deployment materials describe document/file delivery mechanics (for example, SFTP), which occur after the integration produces/transforms the document. This supports the scenario requirement that transformation happens prior to transmission.

“4. FILE DELIVERY SERVICE … 4.4 SFTP Configuration” (document delivery occurs after the integration generates/transforms the output)

Security posture for integrations (context):For outbound/system users and secure delivery, the Workday Authentication & Security guide documents integration-appropriate authentication (e.g., X.509) and general integration security steps — relevant background for productionizing CCW but not directly affecting how to bring a calculated field into the payload.

“X509 Recommended for web services users and integrations that use an integration system user account.”

Putting it all together for the scenario:

Use Integration Field Override to point the CCW field to your Calculated Field for UPN → (Correct answer: B).

Use Integration Maps to translate Worker Type to the vendor’s codes (supports the mapping requirement).

Configure filename rules via Sequence Generator to include timestamp and sequence in the produced file name (supports the file-naming requirement).

Ensure the document transformation runs as part of the integration generation step and then deliver via SFTP (file delivery service).

References (Workday Pro: Integrations-aligned materials):

GPC_PECI_TimeTracking_DeploymentGuide_CloudPay.pdf — Sections “3.6 Sequence Generator” and “4. File Delivery Service” (delivery occurs after file generation/transform).

GPC_PECI_DeploymentGuide_CloudPay_2.9.pdf — Map configuration sections (“WORKDAY SETUP – NON STATIC MAPS”, “WORKDAY SETUP – STATIC MAPS”).

GPC_PECI_UserGuide_CloudPay_2.1.1.pdf — “Maintenance of Integration System Maps.”

Admin-Guide-Authentication-and-Security.pdf — Integration security notes, including X.509 recommendation for integrations.

The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data, with a requirement to include a calculated field in the output. Core Connectors rely on predefined field mappings, but custom calculated fields need specific configuration to be included. Let’s analyze the solution:

Requirement:Output the value of a calculated field created for this integration. In Workday, calculated fields are custom-built (e.g., using Report Writer or Calculated Fields) and not part of the standard Core Connector template, so they must be explicitly added to the output.

Integration Field Overrides:In Core Connectors, Integration Field Overrides allow you to replace a delivered field’s value or add a new field to the output by mapping it to a calculated field. This is the standard method to include custom calculated fields in the integration file. You create the calculated field separately, then use overrides to specify where its value appears in the output structure (e.g., as a new column or replacing an existing field).

Option Analysis:

A. Configure Integration Field Attributes: Incorrect. Integration Field Attributes refine how delivered fields are output (e.g., filtering multi-instance data like phone type), but they don’t support adding or mapping calculated fields.

B. Configure Integration Field Overrides: Correct. This configuration maps the calculated field to the output, ensuring its value is included in the exported file.

C. Configure Integration Attributes: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery protocol), not field-specific outputs like calculated fields.

D. Configure Integration Maps: Incorrect. Integration Maps transform existing field values (e.g., "Married" to "M"), but they don’t add new fields or directly output calculated fields.

Implementation:

Create the calculated field in Workday (e.g., via Create Calculated Field task).

Edit the Core Connector: Worker integration.

Navigate to the Integration Field Overrides section.

Add a new override, selecting the calculated field and specifying its output position (e.g., a new field ID or overriding an existing one).

Test the integration to confirm the calculated field value appears in the output file.

References from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on "Configuring Integration Field Overrides" explains how to include calculated fields in Core Connector outputs.

Integration System Fundamentals: Notes the use of overrides for custom data in predefined integration templates.