Workday-Pro-Integrations Exam Dumps

The scenario involves a Core Connector: Worker integration using DIS to export a full file of employee personal data, with the requirement to output only the home phone number when including phone data. Workday's 'Phone Number' field is multi-instance, meaning a worker can have multiple phone types (e.g., Home, Work, Mobile). Let's determine the configuration:

Requirement:Filter the multi-instance 'Phone Number' field to include only the 'Home' phone number in the output file. This involves specifying which instance of the phone data to extract.

Integration Field Attributes:In Core Connectors, Integration Field Attributes allow you to refine how multi-instance fields are handled in the output. For the 'Phone Number' field, you can set an attribute like 'Phone Type' to 'Home' to ensure only home phone numbers are included. This is a field-level configuration that filters instances without requiring a calculated field or override.

Option Analysis:

A . Configure an integration map to map the phone type: Incorrect. Integration Maps transform field values (e.g., 'United States' to 'USA'), not filter multi-instance data like selecting a specific phone type.

B . Include the phone type integration field attribute: Correct. This configures the 'Phone Number' field to output only instances where the phone type is 'Home,' directly meeting the requirement.

C . Configure the phone type integration attribute: Incorrect. 'Integration attribute' refers to integration-level settings (e.g., file format), not field-specific configurations. The correct term is 'integration field attribute.'

D . Configure an integration field override to include phone type: Incorrect. Integration Field Overrides are used to replace a field's value with a calculated field or custom value, not to filter multi-instance data like phone type.

Implementation:

Edit the Core Connector: Worker integration.

Navigate to the Integration Field Attributes section for the 'Phone Number' field.

Set the 'Phone Type' attribute to 'Home' (or equivalent reference ID for Home phone).

Test the output file to confirm only home phone numbers are included.

Reference from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on 'Integration Field Attributes' explains filtering multi-instance fields like phone numbers by type.

Integration System Fundamentals: Notes how Core Connectors handle multi-instance data with field-level attributes.

The requirement is to filter a custom report to show only workers terminated after a user-prompted date. In Workday, filters are defined in the Filter tab of the custom report definition, and conditions can be combined using AND/OR logic to refine the dataset. Let's analyze the requirement and options:

Key Conditions:

Workers must be terminated, so the 'Worker Status' field must equal 'Terminated.'

The termination must occur after a user-specified date, so the 'Termination Date' must be greater than the prompted value.

Both conditions must be true for a worker to appear in the report, requiring an AND combination.

Option Analysis:

A . Worker Status is equal to the value 'Terminated' OR Termination Date is greater than a value retrieved from a prompt: Incorrect. Using OR means the report would include workers who are terminated (regardless of date) OR workers with a termination date after the prompt (even if not terminated), which doesn't meet the strict requirement of terminated workers after a specific date.

B . Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a value retrieved from a prompt: Incorrect. Worker Status shouldn't be a prompted value (it's fixed as 'Terminated'), and 'less than' would show terminations before the date, not after.

C . Worker Status is equal to the value retrieved from a prompt OR Termination Date is equal to a value retrieved from a prompt: Incorrect. Worker Status shouldn't be prompted, and 'equal to' limits the filter to exact matches, not 'after' the date. OR logic also broadens the scope incorrectly.

D . Worker Status is equal to the value 'Terminated' AND Termination Date is greater than a value retrieved from a prompt: Correct. This ensures workers are terminated (fixed value) AND their termination date is after the user-entered date, precisely meeting the requirement.

Implementation:

In the custom report's Filter tab, add two conditions:

Field: Worker Status, Operator: equals, Value: 'Terminated'.

Field: Termination Date, Operator: greater than, Value: Prompt for Date (configured as a report prompt).

Set the logical operator between conditions to AND.

Test with a sample date to verify only terminated workers after that date appear.

Reference from Workday Pro Integrations Study Guide:

Workday Report Writer Fundamentals: Section on 'Creating and Managing Filters' details combining conditions with AND/OR logic and using prompts.

Integration System Fundamentals: Notes how filtered reports support integration data sources with dynamic user inputs.

In this case, you're asked to create a calculated field that:

Filters dependent records

Includes only child relationships

This means:

The worker has multiple dependents (a multi-instance field).

You need to extract only those dependent(s) where the relationship is ''Child''.

To achieve this in Workday, use:

True/False Condition check if the relationship descriptor = 'Child'

Extract Multi-Instance filters the multi-instance field (Dependents) using the above condition to return only matching records

This two-step logic filters multi-instance relationships correctly.

Why the other options are incorrect:

A and B are missing Extract Multi-Instance, which is required to filter multi-values.

C includes Text Constant unnecessarily --- only True/False Condition and Extract Multi-Instance are required.

You are asked to create a calculated field that:

Takes the Hire Date

Adds 85 days

Formats it as YYYY-MM-DD

To accomplish this in Workday, you need the following calculated field functions:

Numeric Constant define 85

Increment or Decrement Date add 85 days to the Hire Date

Format Date convert the resulting date to YYYY-MM-DD

Why other options are incorrect:

A . Date Constant would define a fixed date, not a dynamic calculation.

B . Date Difference is for subtraction between two dates.

C . Date Constant is still incorrect for offsetting a variable date.

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).

Reference (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.