Workday Pro Integrations Certification Workday-Pro-Integrations Exam Questions

Answer : C

This question is about the correct order of Workday security assignment for integrations. Workday clearly specifies the security structure:

''You assign the ISU to the Integration System Security Group (ISSG).

Then you assign the ISSG to the domain security policies.''

This is because domain security policies apply to security groups, not directly to ISUs.

Correct Relationship Order:

Create ISU

Create/assign ISU to ISSG

Assign ISSG to the domain security policies (Get/Put/View)

That aligns exactly to option C.

Answer : D

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.

Workday Pro: Integrations -- Integration System Security User Management

Workday Community: How ISUs Function in Multi-Integration Environments

Answer : D

An Outbound EIB (Enterprise Interface Builder) requires a data source to extract information from Workday. The two valid data source types are:

Custom Report (Advanced or Simple)

Workday Web Service (WWS)

From Workday documentation:

''Outbound EIBs support either a Custom Report marked as Web Service Enabled, or a Workday Public Web Service (WWS) operation, as the data source.''

Custom Reports allow user-defined data with filtering.

Web Services allow access to standard operations like Get_Workers.

Why the other options are incorrect:

A . Business Process is not a data source type.

B . XpressO Reports are not supported for integrations.

C . Business Processes cannot feed EIBs directly as data sources.

Answer : B

The scenario describes a Core Connector: Worker integration with specific configurations, and a test case where Jeff Gordon's data doesn't appear in the output despite an Edit Position event. Let's analyze why Jeff Gordon is excluded and what needs to change:

Current Configuration:

Integration Field Attributes: Outputs Position Title and Business Title from Position Data.

Integration Population Eligibility: Filters workers where 'Is Manager' = True (only managers).

Transaction Log Service: Subscribes to 'Position Edit Event' transactions.

Launch Parameters:

As of Entry Moment: 05/25/2024 12:00:00 AM

Effective Date: 05/25/2024

Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM

Last Successful Effective Date: 05/23/2024

Test Case:

Worker: Jeff Gordon (not a manager).

Action: Edit Position, updating Business Title.

Event Details: Effective Date 05/24/2024, Entry Moment 05/24/2024 07:58:53 AM.

Result: Jeff Gordon does not appear in the output.

Analysis:

Date Parameters: The integration captures changes between the Last Successful As of Entry Moment (05/23/2024 12:00:00 AM) and the current As of Entry Moment (05/25/2024 12:00:00 AM). Jeff's Edit Position event (Entry Moment 05/24/2024 07:58:53 AM) falls within this range, and its Effective Date (05/24/2024) is before the integration's Effective Date (05/25/2024), making it eligible from a date perspective.

Transaction Log: Subscribed to 'Position Edit Event,' which matches Jeff's action (Edit Position), so the event type is correctly captured.

Field Attributes: Outputs Position Title and Business Title, and Jeff's update to Business Title aligns with these fields.

Population Eligibility: Filters for 'Is Manager' = True. Jeff Gordon is explicitly noted as 'not assigned to the manager role,' meaning 'Is Manager' = False for him. This filter excludes Jeff from the population, regardless of the event or date eligibility.

Why Jeff is Excluded:The Integration Population Eligibility restriction ('Is Manager' = True) prevents Jeff Gordon from being included, as he isn't a manager. This filter applies to the entire worker population before events or fields are considered, overriding other conditions.

Option Analysis:

A . Transaction Log Subscription: Incorrect. The subscription already includes 'Position Edit Event,' which matches Jeff's action. Modifying this wouldn't address the population filter.

B . Integration Population Eligibility: Correct. Changing this to include non-managers (e.g., removing the 'Is Manager' = True filter or adjusting it to include all employees) would allow Jeff Gordon to appear in the output.

C . Date Launch Parameters: Incorrect. Jeff's event (05/24/2024) falls within the date range, so the parameters are not the issue.

D . Integration Field Attributes: Incorrect. The attributes already include Business Title, which Jeff updated, so this configuration is irrelevant to his exclusion.

Modification Needed:Adjust the Integration Population Eligibility to either:

Remove the 'Is Manager' = True filter to include all workers, or

Modify it to align with the scenario's intent (e.g., 'Worker Type equals Employee') if managers were an unintended restriction.

Implementation:

Edit the Core Connector: Worker integration.

Use the related action Configure Integration Population Eligibility.

Remove or adjust the 'Is Manager' = True condition.

Relaunch the integration and verify Jeff Gordon appears in the output.

Reference from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on 'Configuring Integration Population Eligibility' explains how eligibility filters the worker population before event processing.

Integration System Fundamentals: Details how population scoping interacts with event subscriptions and launch parameters.

Answer : C

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.

Answer : D

To chain a Document Transformation system to a Connector Integration, you must configure the Connector Integration System's Business Process (BP) to include a 'Service step of Fire Integration', which triggers the Document Transformation after the connector completes.

From Workday documentation:

''To execute a Document Transformation after a connector integration, use the Fire Integration service step in the connector's business process to trigger the Document Transformation integration.''

This allows Workday to chain multiple integrations, such as taking the output of a Core Connector and sending it through a transformation step (e.g., XSLT) before delivering to an endpoint.

Why other options are incorrect:

A . Fire Integration in the DT BP is not used to call itself.

B . 'Integration step' in BP is not a valid step type.

C . Same issue --- DT's own BP doesn't call itself or other integrations.

Answer : D

Key Points:

The correct approach is adjusting the connector's filename launch parameter, which allows setting a static filename and meeting the vendor's requirement of no longer needing unique filenames.

This method ensures that the filename sequence generator is bypassed without disrupting the integration process.

Comprehensive Detailed

In Workday Pro Integrations, filename sequence generators are commonly used to generate unique filenames to avoid overwrites in integrations. However, when a vendor no longer requires unique filenames, modifications must be made to use a fixed filename instead.

Why Option D?

Adjusting the connector's filename launch parameter lets you set a static filename at runtime, effectively overriding any sequence generator settings.

Unlike deleting the sequence generator (which could cause errors), this method ensures smooth execution of the integration with a fixed filename.

This aligns with Workday's best practices for integration configurations, particularly in External Integration Business (EIB) and other Workday connector integrations.

Steps to Implement:

Access the integration's configuration in Workday.

Locate the filename launch parameter for the connector.

Set it to a static value (e.g., 'data.txt') to ensure consistent naming.

Supporting Documentation:

Workday documentation on integration configurations, particularly for EIB systems, confirms that filename settings can be adjusted via launch parameters.

The 'Get_Sequence_Generators Operation Details' in Workday API documentation supports modifying filename configurations through launch parameters.