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.
