What is the purpose of granting an ISU modify access to the Integration Event domain via an ISSG?

A vendor needs an EIB that uses a custom report to output a list of new hires and the date they are eligible for benefits. You have been asked to create a calculated field that adds each worker's hire date + 85 days and displays the result in YYYY-MM-DD format.

Which calculated field functions do you need to accomplish this?

What are the two valid data source options for an Outbound EIB?

You are creating an outbound connector using the Core Connector: Job Postings template. The vendor has provided the following specification for worker subtype values:

The vendor has also requested that any output file have the following format "CC_Job_Postings_dd-mm-yy_#.xml". Where the 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, and # is the current value of the sequencer at runtime. What configuration step(s) must you complete to meet the vender requirements?

Which features must all XSLT files contain to be considered valid?

What is the purpose of declaring and defining the namespace in an XSLT stylesheet?

Refer to the following XML and example transformed output to answer the question below.

Example transformed wd:Report_Entry output;

What is the XSLT syntax tor a template that matches on wd: Educationj3roup to produce the degree data in the above Transformed_Record example?

Refer to the following scenario to answer the question below.

You have configured a Core Connector: Worker integration, which utilizes the following basic configuration:

• Integration field attributes are configured to output the Position Title and Business Title fields from the Position Data section.

• Integration Population Eligibility uses the field Is Manager which returns true if the worker holds a manager role.

• Transaction Log service has been configured to Subscribe to specific Transaction Types: Position Edit Event.

You launch your integration with the following date launch parameters (Date format of MM/DD/YYYY):

• 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

To test your integration, you made a change to a worker named Jared Ellis who is assigned to the manager role for the IT Help Desk department. You use the Change Business Title related action on Jared and update the Business Title of the position to a new value. Jared Ellis' worker history shows the Title Change Event as being successfully completed with an effective date of 05/24/2024 and an Entry Moment of 05/24/2024 07:58:53 AM however Jared Ellis does not show up in your output. What configuration element would have to be modified for the integration to include Jared Ellis in the output?

How do you initially upload the XSLT file to a Document Transformation integration system?

Refer to the following scenario to answer the question below.

You are implementing a Core Connector: Worker integration to send employee data to a third-party active employee directory. The external vendor requires the following:

The Employee's Active Directory User Principal Name.

A mapping from Worker Type values to external worker type codes.

A specific filename format that includes a timestamp and sequence number.

You also need to ensure the document transformation occurs before the file is delivered to the endpoint. The connector's output must be transformed before the file is delivered to the vendor.

What step must be taken to ensure this occurs correctly?

Refer to the following scenario to answer the question below.

You have been asked to build an integration using the Core Connector: Worker template and should leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no change detection) for employees only and will include personal data.

What configuration is required to ensure that only employees, and not contingent workers, are output by this integration?

You are configuring integration security for a Core Connector integration system. How do you find the web service operation used by the connector template?

Refer to the following scenario to answer the question below.

You have been asked to build an integration using the Core Connector: Worker template and should leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no change detection) for employees only and will include personal data.

What configuration is required to ensure that when outputting phone number only the home phone number is included in the output?

Refer to the scenario. You are configuring a Core Connector: Worker integration to extract worker demographic and contact information. The integration uses the Data Initialization Service (DIS) and must include worker fields such as name, address, and a calculated field identifying workers eligible for a phone allowance.

During a Full File test run, the output file is missing all address-related information, even though the Address Line Data, Municipality, Region, and Postal Code fields were configured in the Configure Integration Field Attributes step. You also confirmed that the Worker Personal Data Section is marked as Include in Output.

What should you do to resolve this issue?

Refer to the following scenario to answer the question below.

You need to configure a Core Connector: Candidate Outbound integration for your vendor. The connector requires the data initialization service (DIS).

The vendor requests additional formatting of the candidate Country field. For example, if a candidate's country is the United States of America, the output should show USA.

What steps do you follow to meet this request?

Refer to the scenario. You are implementing a Core Connector: Worker integration to send employee data to a third-party active employee directory. The external vendor requires the following:

The Employee's Active Directory User Principal Name.

A mapping from Worker Type values to external worker type codes.

A specific filename format that includes a timestamp and sequence number.

You also need to ensure the document transformation occurs before the file is delivered to the endpoint. You must include an Employee’s Active Directory User Principal Name (generated by a Calculated Field).

How do you ensure this field is pulled into the output?

Refer to the following XML data source to answer the question below.

You need the integration file to format the ps:Position_ID field to 10 characters, truncate the value if it exceeds, and align everything to the left.

How will you start your template match on ps:Position to use Document Transformation (DT) to do the transformation using XTT?

You are creating a connector based integration where all fields are provided by the template. However, the vendor would also like the following configurations as well:

• A file name output to have the current date and integration run number

• Have internal values for a particular field transferred to their external values

What workflow would you follow to create this integration?

Refer to the following XML to answer the question below.

You need the integration file to format the ps:PositionJD field to 10 characters and report any truncated values as an error.

How will you start your template match on ps:Position to use Document Transformation (DT) to do the transformation using ETV with your truncation validation?

What is a key function and primary benefit of using a Document Transformation Connector within the integration capabilities of Workday?

Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled. The integration must extract worker contact details and job information, including a calculated field override that determines phone allowance eligibility.

While testing, the output contains no records, and the Messages tab shows exception logs stating you don't have access to the Exempt field. You note this is the same field being used for Population Eligibility in the integration.

What must you configure to resolve this security issue?

What attribute(s) can go into the xsl:stylesheet element?

Refer to the following scenario to answer the question below.

You need to configure a Core Connector: Candidate Outbound integration for your vendor. The connector requires the data initialization service (DIS).

The vendor needs the file to only include candidates that undergo a candidate assessment event in Workday.

How do you accomplish this?