Join the discussion
Question 28/61
This is the XML file generated from a Core Connector; Positions integration.

When performing an XSLT Transformation on the Core Connector: Positions XML output file, you want to show a hyperlink of positions that are not available for hiring as an entry in the Message tab.
What are all the needed ETV items to meet the above requirements?

When performing an XSLT Transformation on the Core Connector: Positions XML output file, you want to show a hyperlink of positions that are not available for hiring as an entry in the Message tab.
What are all the needed ETV items to meet the above requirements?
Correct Answer: B
In Workday integrations, the Extension for Transformation and Validation (ETV) framework is used within XSLT transformations to apply validation and formatting rules to XML data, such as the output from a Core Connector (e.g., Positions integration). In this scenario, you need to perform an XSLT transformation on the Core Connector: Positions XML output file to display a hyperlink for positions that are not available for hiring as an entry in the Message tab. This requires configuring ETV attributes to ensure the data is present and correctly targeted for the hyperlink.
Here's why option B is correct:
* Requirement Analysis: The requirement specifies showing a hyperlink for positions "not available for hiring." In the provided XML, the ps:Available_For_Hire field under ps:Position_Data indicates whether a position is available for hire (e.g., <ps:Available_For_Hire>true</ps:Available_For_Hire>).
For positions where this is false, you need to create a message (hyperlink) in the Message tab, which typically requires linking to a Workday ID (WID) or other identifier.
* ETV Attributes:
* etv:required="true": This ensures that the ps:WID value under ps:Additional_Information is mandatory for the transformation. If the WID is missing, the transformation will fail or generate an error, ensuring that the hyperlink can be created only for valid positions with an associated WID.
* etv:target="[ps:Additional_Information/ps:WID]": This specifies that the target of the transformation (e.g., the hyperlink) should be the WID value found at ps:Additional_Information
/ps:WID in the XML. This WID can be used to construct a hyperlink to the position in Workday, meeting the requirement to show a hyperlink for positions not available for hiring.
* Context in XML: The XML shows ps:Additional_Information containing ps:WID (e.g., <ps:
WID>73bd4d8562e04b1820f55818467905b</ps:WID>), which is a unique identifier for the position.
By targeting this WID with etv:target, you ensure the hyperlink points to the correct position record in Workday when ps:Available_For_Hire is false.
Why not the other options?
* A.
* etv:minLength="0"
* etv:targetWID="[ps:Additional_Information/ps:WID]"
* etv:minLength="0" allows the WID to be empty or have zero length, which contradicts the need for a valid WID to create a hyperlink. It does not ensure the data is present, making it unsuitable.
Additionally, etv:targetWID is not a standard ETV attribute; the correct attribute is etv:target, making this option incorrect.
* C.
* etv:minLength="0"
* etv:target="[ps:Additional_Information/ps:WID]"
* Similar to option A, etv:minLength="0" allows the WID to be empty, which does not meet the requirement for a mandatory WID to create a hyperlink. This makes it incorrect, as the hyperlink would fail if the WID is missing.
* D.
* etv:required="true"
* etv:targetWID="[ps:Additional_Information/ps:WID]"
* While etv:required="true" ensures the WID is present, etv:targetWID is not a standard ETV attribute. The correct attribute is etv:target, making this option syntactically incorrect and unsuitable for the transformation.
To implement this in XSLT for a Workday integration:
* Use the ETV attributes from option B (etv:required="true" and etv:target="[ps:Additional_Information
/ps:WID]") within your XSLT template to validate and target the ps:WID for positions where ps:
Available_For_Hire is false. This ensures the transformation generates a valid hyperlink in the Message tab, linking to the position's WID in Workday.
Workday Pro Integrations Study Guide: Section on "ETV in XSLT Transformations" - Details the use of ETV attributes like required and target for validating and targeting data in Workday XML, including handling identifiers like WID for hyperlinks.
Workday Core Connector and EIB Guide: Chapter on "XML Transformations" - Explains how to use ETV attributes in XSLT to process position data, including creating messages or hyperlinks based on conditions like Available_For_Hire.
Workday Integration System Fundamentals: Section on "ETV for Message Generation" - Covers applying ETV attributes to generate hyperlinks in the Message tab, ensuring data integrity and correct targeting of Workday identifiers like WID.
Here's why option B is correct:
* Requirement Analysis: The requirement specifies showing a hyperlink for positions "not available for hiring." In the provided XML, the ps:Available_For_Hire field under ps:Position_Data indicates whether a position is available for hire (e.g., <ps:Available_For_Hire>true</ps:Available_For_Hire>).
For positions where this is false, you need to create a message (hyperlink) in the Message tab, which typically requires linking to a Workday ID (WID) or other identifier.
* ETV Attributes:
* etv:required="true": This ensures that the ps:WID value under ps:Additional_Information is mandatory for the transformation. If the WID is missing, the transformation will fail or generate an error, ensuring that the hyperlink can be created only for valid positions with an associated WID.
* etv:target="[ps:Additional_Information/ps:WID]": This specifies that the target of the transformation (e.g., the hyperlink) should be the WID value found at ps:Additional_Information
/ps:WID in the XML. This WID can be used to construct a hyperlink to the position in Workday, meeting the requirement to show a hyperlink for positions not available for hiring.
* Context in XML: The XML shows ps:Additional_Information containing ps:WID (e.g., <ps:
WID>73bd4d8562e04b1820f55818467905b</ps:WID>), which is a unique identifier for the position.
By targeting this WID with etv:target, you ensure the hyperlink points to the correct position record in Workday when ps:Available_For_Hire is false.
Why not the other options?
* A.
* etv:minLength="0"
* etv:targetWID="[ps:Additional_Information/ps:WID]"
* etv:minLength="0" allows the WID to be empty or have zero length, which contradicts the need for a valid WID to create a hyperlink. It does not ensure the data is present, making it unsuitable.
Additionally, etv:targetWID is not a standard ETV attribute; the correct attribute is etv:target, making this option incorrect.
* C.
* etv:minLength="0"
* etv:target="[ps:Additional_Information/ps:WID]"
* Similar to option A, etv:minLength="0" allows the WID to be empty, which does not meet the requirement for a mandatory WID to create a hyperlink. This makes it incorrect, as the hyperlink would fail if the WID is missing.
* D.
* etv:required="true"
* etv:targetWID="[ps:Additional_Information/ps:WID]"
* While etv:required="true" ensures the WID is present, etv:targetWID is not a standard ETV attribute. The correct attribute is etv:target, making this option syntactically incorrect and unsuitable for the transformation.
To implement this in XSLT for a Workday integration:
* Use the ETV attributes from option B (etv:required="true" and etv:target="[ps:Additional_Information
/ps:WID]") within your XSLT template to validate and target the ps:WID for positions where ps:
Available_For_Hire is false. This ensures the transformation generates a valid hyperlink in the Message tab, linking to the position's WID in Workday.
Workday Pro Integrations Study Guide: Section on "ETV in XSLT Transformations" - Details the use of ETV attributes like required and target for validating and targeting data in Workday XML, including handling identifiers like WID for hyperlinks.
Workday Core Connector and EIB Guide: Chapter on "XML Transformations" - Explains how to use ETV attributes in XSLT to process position data, including creating messages or hyperlinks based on conditions like Available_For_Hire.
Workday Integration System Fundamentals: Section on "ETV for Message Generation" - Covers applying ETV attributes to generate hyperlinks in the Message tab, ensuring data integrity and correct targeting of Workday identifiers like WID.
Add Comments
- Other Question (61q)
- Q1. When creating an ISU, what should you do to ensure the user only authenticates via web ser...
- Q2. What is the purpose of granting an ISU modify access to the Integration Event domain via a...
- Q3. Refer to the following scenario to answer the question below. You have been asked to build...
- Q4. You need the integration file to generate the date format in the form of "31/07/2025" form...
- Q5. Refer to the following XML to answer the question below. Refer to the following XML to ans...
- Q6. What are the two valid data source options for an Outbound EIB?...
- Q7. Refer to the following scenario to answer the question below. You have configured a Core C...
- Q8. As of May 1, 2024 Brian Hill's annual salary is $60,000.00. On May 13, 2024 Brian Hill rec...
- Q9. You are creating an outbound connector using the Core Connector: Job Postings template. Th...
- Q10. What is the workflow to chain a Document Transformation system to a Connector integration ...
- Q11. What is the purpose of the <xsl:template> element?...
- Q12. You are configuring an EIB that uses a custom report as its data source. When attempting t...
- Q13. Refer to the following XML to answer the question below. (Exhibit) You need the integratio...
- Q14. A vendor needs an EIB that uses a custom report to output a list of new hires and their ch...
- Q15. What is the task used to upload a new XSLT file for a pre-existing document transformation...
- Q16. Refer to the following XML to answer the question below. Refer to the following XML to ans...
- Q17. You need the integration file to generate the date format in the form of "31/07/2025" form...
- Q18. How does an XSLT processor identify the specific nodes in an XML document to which a parti...
- Q19. Refer to the following scenario to answer the question below. Your integration has the fol...
- Q20. A vendor needs to create a Date Difference calculated field. However, the two dates needed...
- Q21. You have a population of workers who have put multiple names in their Legal Name - First N...
- Q22. What XSL component is required to execute valid transformation instructions in the XSLT co...
- Q23. Refer to the following scenario to answer the question below. You need to configure a Core...
- Q24. You have been asked to create an integration using the Core Connector: Worker with DIS tem...
- Q25. What is the relationship between the Integration System User (ISU), Integration System Sec...
- Q26. You are creating a connector based integration where all fields are provided by the templa...
- Q27. You need to create a report that includes data from multiple business objects. For a super...
- Q28. This is the XML file generated from a Core Connector; Positions integration. (Exhibit) Whe...
- Q29. Refer to the following XML and example transformed output to answer the question below. (E...
- Q30. When creating an ISU, what should you do to ensure the user only authenticates via web ser...
- Q31. What task is needed to build a sequence generator for an EIB integration?...
- Q32. Refer to the scenario. You are implementing a Core Connector: Worker integration to send e...
- Q33. What is the relationship between the Integration System User (ISU), Integration System Sec...
- Q34. Refer to the following XML and example transformed output to answer the question below. (E...
- Q35. Your manager has asked for a value on their dashboard for how many days away the birthdays...
- Q36. After configuring domain security policies, what task must you run to ensure the most rece...
- Q37. Refer to the scenario. You are configuring a Core Connector: Worker integration with the D...
- Q38. Refer to the scenario. You are configuring a Core Connector: Worker integration to extract...
- Q39. What is the workflow to upload an XSLT file for a brand new Document Transformation system...
- Q40. You have been asked to refine a report which outputs one row per worker and is being used ...
- Q41. What is the workflow to upload an XSLT file for a brand new Document Transformation system...
- Q42. Refer to the following XML and example transformed output to answer the question below. (E...
- Q43. This is the XML file generated from a Core Connector; Positions integration. (Exhibit) Whe...
- Q44. You need to filter a custom report to only show workers that have been terminated after a ...
- Q45. What is the workflow to chain a Document Transformation system to a Connector integration ...
- Q46. Which three features must all XSLT files contain to be considered valid?...
- Q47. Refer to the following scenario to answer the question below. You have been asked to build...
- Q48. Refer to the following XML to answer the question below. (Exhibit) You are an integration ...
- Q49. Your manager has asked for a value on their dashboard for how many days away the birthdays...
- Q50. A calculated field used as a field override in a Connector is not appearing in the output....
- Q51. Which features must all XSLT files contain to be considered valid?...
- Q52. Refer to the following scenario to answer the question below. You need to configure a Core...
- Q53. Your manager has asked for a value on their dashboard for how many days away the birthdays...
- Q54. Refer to the following XML to answer the question below. (Exhibit) Within the template whi...
- Q55. Which three features must all XSLT files contain to be considered valid?...
- Q56. You have configured a filename sequence generator for a connector integration. The vendor ...
- Q57. What is the relationship between an ISU (Integration System User) and an ISSG (Integration...
- Q58. A vendor needs an EIB that uses a custom report to output a list of new hires and their ch...
- Q59. How many integration systems can an ISU be assigned to concurrently?...
- Q60. What is the purpose of the <xsl:template> element?...
- Q61. Refer to the following scenario to answer the question below. You have configured a Core C...
[×]
Download PDF File
Enter your email address to download Workday.Workday-Pro-Integrations.v2026-03-13.q61.pdf
