Workday Workday-Pro-Integrations - Workday Pro Integrations Certification Exam

The schedule must run every weekday and exclude weekends. “Configure to recur every weekday” is the only option that directly matches Monday through Friday processing. Configuring the schedule to recur every one day would run seven days a week unless additional restrictions were added, so it does not meet the “not on weekends” requirement. Recurring every five days is also incorrect because it creates a rolling five-day interval, not a Monday-to-Friday pattern. Recurring every seven days would run weekly, not every weekday. The phrase “since the last integration run” indicates incremental change processing, but the question is specifically asking for run frequency. Therefore, the weekday recurrence is the correct scheduling configuration.

================

When using Core Connector: Worker with DIS, to restrict the population to employees who:

Are on leave, and

Are located in San Francisco

You must configure Population Eligibility, which is the only place to filter the worker population included in the connector output.

From Workday Pro documentation:

“The Population Eligibility section defines which workers are eligible for extraction in the integration based on location, status, organization, and other conditions. Boolean calculated fields can be used here to define complex eligibility criteria.”

In this case:

Create a Boolean calculated field that returns true for “On Leave AND Location = San Francisco”

Use that field in Population Eligibility

Why the others are incorrect:

A, D. Field Overrides and Field Attributes only modify what data is extracted—not who is included.

C. Integration Attributes don’t control population filtering.

The Exempt field is being used in Population Eligibility, and eligibility fields must be readable by the ISSG. If the domain security policy for a field denies View access, Workday cannot evaluate the eligibility and returns no data.

From Workday security governance:

“For integrations using Population Eligibility, the ISSG must have View permission on all fields referenced in eligibility rules.”

If View is missing, the eligibility rule cannot execute → No workers are considered eligible → Output contains zero records → Error logged for denied field access.

Therefore, the solution is:

• Grant the ISSG View access to the domain that secures the Population Eligibility field

Modify access (A/C) is not needed — eligibility only needs read-access.

The scenario describes a Core Connector: Worker integration configured to output specific fields (Position Title and Business Title) for workers who meet the Integration Population Eligibility criteria (Is Manager = true) and where the Transaction Log service is subscribed to the " Position Edit Event. " The integration is launched with specific date parameters, and a test edit is made to Jared Ellis’ position, who is a manager. However, despite the edit being completed with an effective date of 05/24/2024 and an entry moment of 05/24/2024 07:58:53 AM, Jared does not appear in the output. Let’s analyze why and determine the correct configuration element to modify.

In Workday integrations, the Core Connector: Worker uses change detection mechanisms to identify and process updates based on the Transaction Log and date launch parameters. The Transaction Log service captures events such as the " Position Edit Event " and records them with an Effective Date (when the change takes effect) and an Entry Moment (when the change was entered into the system). The integration’s date launch parameters define the time window for which changes are retrieved:

As of Entry Moment: 05/25/2024 12:00:00 AM – This specifies the latest point in time for when changes were entered into Workday.

Effective Date: 05/25/2024 – This defines the date for which the changes are effective.

Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM – This indicates the starting point for entry moments from the last successful run.

Last Successful Effective Date: 05/23/2024 – This indicates the starting point for effective dates from the last successful run.

For an incremental run (like this one, since " Last Successful " parameters are provided), Workday processes changes where the Entry Moment falls between the Last Successful As of Entry Moment (05/23/2024 12:00:00 AM) and the As of Entry Moment (05/25/2024 12:00:00 AM), and where the Effective Date falls between the Last Successful Effective Date (05/23/2024) and the Effective Date (05/25/2024).

Now, let’s evaluate Jared Ellis’ edit:

Entry Moment: 05/24/2024 07:58:53 AM – This falls within the range of 05/23/2024 12:00:00 AM to 05/25/2024 12:00:00 AM.

Effective Date: 05/24/2024 – This falls within the range of 05/23/2024 to 05/25/2024.

At first glance, Jared’s edit seems to fit the date parameter window. However, the issue lies in the time component of the date launch parameters. Workday interprets these parameters with precision down to the second. The As of Entry Moment is set to 05/25/2024 12:00:00 AM (midnight), which is the very start of May 25, 2024. Jared’s Entry Moment of 05/24/2024 07:58:53 AM is correctly within the range from 05/23/2024 12:00:00 AM to 05/25/2024 12:00:00 AM. However, the Transaction Log subscription to " Position Edit Event " relies on the change being fully processed and available in the log by the time the integration runs.

The integration might have run at a point where the effective date window or the subscription logic did not correctly capture the event due to a mismatch in how the Effective Date is evaluated against the Last Successful Effective Date. Specifically, if the integration only processes changes with an Effective Date strictly after the Last Successful Effective Date (05/23/2024) up to the Effective Date (05/25/2024), and the logic excludes changes effective exactly on 05/24/2024 due to a boundary condition or a timing issue in the transaction log, Jared’s change might not be picked up.

To resolve this, modifying the Date launch parameters is necessary. Adjusting the As of Entry Moment to a later time (e.g., 05/25/2024 11:59:59 PM) or ensuring the Effective Date range explicitly includes all changes effective on or after 05/23/2024 through 05/25/2024 would ensure Jared’s edit is captured. This adjustment aligns the time window to include all relevant transactions logged before the integration run.

Let’s evaluate the other options:

A. Integration Population Eligibility: This is set to " Is Manager = true, " and Jared is a manager. This filter is working correctly and does not need modification.

B. Integration Field Attributes: These are configured to output Position Title and Business Title, and the edit was to the Job Profile (part of Position Data). The fields are appropriately configured, so this is not the issue.

D. Transaction Log Subscription: The subscription is set to " Position Edit Event, " which matches Jared’s edit. The subscription type is correct, so no change is needed here.

Thus, the issue stems from the date launch parameters not fully encompassing the timing of Jared’s edit in the Transaction Log, making C. Date launch parameters the correct answer.

Workday Pro Integrations Study Guide References

Workday Integrations Study Guide: Core Connector: Worker – Section on " Change Detection Using Transaction Log " explains how Transaction Log subscriptions filter events based on date parameters.

Workday Integrations Study Guide: Launch Parameters – Details the role of " As of Entry Moment " and " Effective Date " in defining the scope of incremental runs.

Workday Integrations Study Guide: Incremental Processing – Describes how " Last Successful " parameters establish the baseline for detecting changes in subsequent runs.

For recurring integration schedules, Workday limits how far into the future a recurrence can be scheduled. The maximum end date is tied to the next calendar year, not simply to the same month next year or the current year. Therefore, December 31st of the next calendar year is the correct maximum end date. This allows the integration to continue through the full next calendar year without requiring a shorter May-based cutoff. The current calendar year would end too soon for a monthly recurring schedule configured to continue beyond year-end. The second calendar year option extends too far and exceeds the normal scheduling limit. This question tests schedule governance, not transformation or report logic.

================

To create a connector-based integration with additional custom configurations such as dynamic file naming and internal-to-external value mapping, the following steps must be followed:

Enable Needed Integration Services:

This step involves activating the required integration services to ensure that the necessary API calls, security, and processing capabilities are available within Workday.

Configure Integration Field Attributes:

Integration Field Attributes allow customization of fields within the integration, enabling changes to formats, mappings, and transformations, such as including a dynamically generated file name with the current date and integration run number.

Configure Integration Maps:

Integration Maps are used to transform internal values into external values as per the vendor’s requirements. This ensures that data fields in Workday align correctly with external system specifications.

Configure Sequence Generator:

The Sequence Generator is used to append unique identifiers to output files, ensuring each integration run produces a uniquely named file (e.g., including the current date and run number).

This workflow ensures that the integration is set up efficiently while meeting the vendor’s additional configuration needs.

The requirement is population filtering, not output formatting. In a Core Connector: Worker integration, Integration Population Eligibility determines which workers qualify for extraction before the connector produces the output file. To include only active workers in the Clinical Staff job family, the eligibility rule must evaluate worker status and job family together. Integration Field Overrides are used when replacing or adding output values, such as a calculated License ID. Integration Attributes control connector-level configuration and do not restrict the worker population. Transaction Log configuration controls which transaction types are detected for change processing, not whether a worker belongs to the desired eligible population. Therefore, the correct configuration step is Integration Population Eligibility.

================

The Integration System User (ISU) in Workday is a specialized user account designed for automation and system-level integrations. It can be assigned to any number of integration systems concurrently — there is no limit.

From Workday documentation and Pro training:

“A single ISU can be assigned to multiple integration systems across tenants and environments, provided it has the correct permissions and security group assignments. Workday does not impose a hard limit on the number of systems an ISU can be linked to.”

This design provides scalability for environments with multiple integrations (e.g., EIBs, Core Connectors, Studio integrations) without needing to create redundant users.

Incorrect Options Explained:

A, B, C: These options imply arbitrary limits (one, three, five), which do not exist in Workday ' s ISU architecture.

This question involves configuring an outbound connector using the Core Connector: Job Postings template in Workday Pro Integrations. We need to meet two specific vendor requirements:

Map worker subtype values according to the provided table (e.g., Seasonal (Fixed) = " S " , Regular = " R " , Contractor = " C " , Consultant = " C " , and any other value = " U " ).

Format the output file name as " CC_Job_Postings_dd-mm-yy_#.xml " , where:

" dd " is the current day at runtime,

" mm " is the current month at runtime,

" yy " is the last two digits of the current year at runtime,

" # " is the current value of the sequencer at runtime.

Let’s break down the requirements and evaluate each option to determine the correct configuration steps.

Understanding the Requirements

1. Worker Subtype Mapping

The vendor provides a table for worker subtype values:

Internal Seasonal (Fixed) maps to " S "

Internal Regular maps to " R "

Internal Contractor maps to " C "

Internal Consultant maps to " C "

Any other value should be assigned " U "

In Workday, worker subtypes are typically part of the worker data, and for integrations, we use integration mappings to transform these values into the format required by the vendor. The integration mapping allows us to define how internal Workday values (e.g., worker subtypes) map to external values (e.g., " S " , " R " , " C " , " U " ). If no specific mapping exists for a value, we need to set a default value of " U " for any unmatched subtypes, as specified.

This mapping is configured in the integration system’s " Integration Mapping " or " Field Mapping " settings, depending on the template. For the Core Connector: Job Postings, we typically use the " Integration Mapping " feature to handle data transformations, including setting default values for unmapped data.

2. Output File Name Format

The vendor requires the output file to be named " CC_Job_Postings_dd-mm-yy_#.xml " , where:

" CC_Job_Postings " is a static prefix,

" dd-mm-yy " represents the current date at runtime (day, month, last two digits of the year),

" # " is the current value from a sequence generator (sequencer) at runtime.

In Workday, file names for integrations are configured in the " File Utility " or " File Output " settings of the integration. To achieve this format:

The date portion ( " dd-mm-yy " ) can be dynamically generated using Workday’s date functions or runtime variables, often configured in the File Utility’s " Filename " field with a " Determine Value at Runtime " setting.

The sequence number ( " # " ) requires a sequence generator, which is enabled and configured to provide a unique incrementing number for each file. Workday uses the " Sequence Generator " feature for this purpose, typically accessed via the " Create ID Definition / Sequence Generator " task.

The Core Connector: Job Postings template supports these configurations, allowing us to set filename patterns in the integration’s setup.

Evaluating Each Option

Let’s analyze each option step by step, ensuring alignment with Workday Pro Integrations best practices and the vendor’s requirements.

Option A:

• Enable the Sequence Generator Field Attribute

• Configure the Sequence Generator

• Configure the Worker Sub Type Integration Mapping leaving the default value blank

Analysis:

Sequence Generator Configuration: Enabling the " Sequence Generator Field Attribute " and configuring the sequence generator is partially correct for the file name’s " # " (sequencer) requirement. However, " Sequence Generator Field Attribute " is not a standard term in Workday; it might refer to enabling a sequence generator in a field mapping, but this is unclear and likely incorrect. Sequence generators are typically enabled as an " Integration Service " or configured in the File Utility, not as a field attribute.

Worker Subtype Mapping: Configuring the worker subtype integration mapping but leaving the default value blank is problematic. The vendor requires any unmapped value to be " U, " so leaving it blank would result in missing or null values, failing to meet the requirement.

Date in Filename: This option doesn’t mention configuring the date ( " dd-mm-yy " ) in the filename, which is critical for the " CC_Job_Postings_dd-mm-yy_#.xml " format.

Conclusion: This option is incomplete and incorrect because it doesn’t address the default " U " for unmapped subtypes and lacks date configuration for the filename.

Option B:

• Enable the Integration Mapping Field Attribute

• Configure the Worker Sub Type Integration Mapping leaving the default value blank

• Configure the Sequence Generator

Analysis:

Sequence Generator Configuration: Configuring the sequence generator addresses the " # " (sequencer) in the filename, which is correct for the file name requirement.

Worker Subtype Mapping: Similar to Option A, leaving the default value blank for the worker subtype mapping fails to meet the vendor’s requirement for " U " as the default for unmapped values. This would result in errors or null outputs, which is unacceptable.

Date in Filename: Like Option A, there’s no mention of configuring the date ( " dd-mm-yy " ) in the filename, making this incomplete for the full file name format.

Integration Mapping Field Attribute: This term is ambiguous. Workday uses " Integration Mapping " or " Field Mapping " for data transformations, but " Field Attribute " isn’t standard for enabling mappings. This suggests a misunderstanding of Workday’s configuration.

Conclusion: This option is incomplete and incorrect due to the missing default " U " for worker subtypes and lack of date configuration for the filename.

Option C:

• Enable the Integration Mapping Integration Service

• Configure the Worker Sub Type Integration Mapping and include a default value of " U "

• Configure the Sequence Generator

Analysis:

Sequence Generator Configuration: Configuring the sequence generator is correct for the " # " (sequencer) in the filename, addressing part of the file name requirement.

Worker Subtype Mapping: Including a default value of " U " for the worker subtype mapping aligns perfectly with the vendor’s requirement for any unmapped value to be " U. " This is a strong point.

Date in Filename: This option doesn’t mention configuring the date ( " dd-mm-yy " ) in the filename, which is essential for the " CC_Job_Postings_dd-mm-yy_#.xml " format. Without this, the file name requirement isn’t fully met.

Integration Mapping Integration Service: Enabling the " Integration Mapping Integration Service " is vague. Workday doesn’t use this exact term; instead, integration mappings are part of the integration setup, not a separate service. This phrasing suggests confusion or misalignment with Workday terminology.

Conclusion: This option is partially correct (worker subtype mapping) but incomplete due to the missing date configuration for the filename and unclear terminology.

Option D:

• Enable the Sequence Generator Integration Service

• Configure the Sequence Generator

• Configure the Worker Sub Type Integration Mapping and include a default value of " U "

Analysis:

Sequence Generator Configuration: Enabling the " Sequence Generator Integration Service " and configuring the sequence generator addresses the " # " (sequencer) in the filename. While " Sequence Generator Integration Service " isn’t a standard term, it likely refers to enabling and configuring the sequence generator functionality, which is correct. In Workday, this is done via the " Create ID Definition / Sequence Generator " task and linked in the File Utility.

Worker Subtype Mapping: Configuring the worker subtype integration mapping with a default value of " U " meets the vendor’s requirement for any unmapped value, ensuring " S, " " R, " " C, " or " U " is output as specified in the table. This is accurate and aligns with Workday’s integration mapping capabilities.

Date in Filename: Although not explicitly mentioned in the steps, Workday’s Core Connector: Job Postings template and File Utility allow configuring the filename pattern, including dynamic date values ( " dd-mm-yy " ). The filename " CC_Job_Postings_dd-mm-yy_#.xml " can be set in the File Utility’s " Filename " field with " Determine Value at Runtime, " using date functions and the sequence generator. This is a standard practice and implied in the configuration, making this option complete.

Conclusion: This option fully addresses both requirements: worker subtype mapping with " U " as the default and the file name format using the sequence generator and date. The terminology ( " Sequence Generator Integration Service " ) is slightly non-standard but interpretable as enabling/configuring the sequence generator, which is correct in context.

Final Verification

To confirm, let’s summarize the steps for Option D and ensure alignment with Workday Pro Integrations:

Enable the Sequence Generator Integration Service: This likely means enabling and configuring the sequence generator via the " Create ID Definition / Sequence Generator " task, then linking it to the File Utility for the " # " in the filename.

Configure the Sequence Generator: Set up the sequence generator to provide incremental numbers, ensuring each file has a unique " # " value.

Configure the Worker Sub Type Integration Mapping with a default value of " U " : Use the integration mapping to map Internal Seasonal (Fixed) to " S, " Regular to " R, " Contractor to " C, " Consultant to " C, " and set " U " as the default for any other value. This is done in the integration’s mapping configuration.

Filename Configuration (Implied): In the File Utility, set the filename to " CC_Job_Postings_dd-mm-yy_#.xml, " where " dd-mm-yy " uses Workday’s date functions (e.g., %d-%m-%y) and " # " links to the sequence generator.

This matches Workday’s documentation and practices for the Core Connector: Job Postings template, ensuring both requirements are met.

Why Not the Other Options?

Options A and B fail because they leave the default worker subtype value blank, not meeting the " U " requirement.

Option C fails due to missing date configuration for the filename and unclear terminology ( " Integration Mapping Integration Service " ).

Option D is the only one that fully addresses both the worker subtype mapping (with " U " default) and implies the filename configuration, even if the date setup isn’t explicitly listed (it’s standard in Workday).

Supporting Documentation

The reasoning is based on Workday Pro Integrations best practices, including:

Workday Tutorial: Activity Creating Unique Filenames from EIB-Out Integrations – Details on using sequence generators for filenames.

Workday Tutorial: EIB Features – Explains integration mappings and default values.

Get_Sequence_Generators Operation Details – Workday API documentation on sequence generators.

Workday Advanced Studio Tutorial – Covers Core Connector templates and file name configurations.

r/workday Reddit Post: How to Create a New Sequence Generator for Filename for EIB – Community insights on sequence generators.

The requirement is for the integration to run at the end of each month, so the schedule must be configured using a monthly recurrence pattern. “Day(s) of the Month: Last Day of the Month” directly matches the requirement because it automatically handles months with different lengths, including 28, 29, 30, and 31 days. A dependent recurrence is used when one process depends on another scheduled process, which is not stated here. A custom recurrence is unnecessary because Workday provides a specific monthly scheduling option for the last day of the month. “Day of the Week: Last Sunday” would not reliably run at month-end. Since the file must include changes since the last run, a recurring monthly schedule is the correct design.

================