Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
XSL Processing When Exporting Candidate Files from Transitions
Summary
XSL Processing When Exporting Candidate Files from TransitionsContent
We are working on setting up an export to pull Candidate Files (files uploaded by new hire in Transitions) and are having an issue with the XSL post-processing step.
When we run the export without the XSL post-processing step, an XML file gets created that appears to be formatted as expected; however, when we add the XSL post-processing step, it transforms the file and puts the file category codes together in one field.
Please see the included image for further illustration.
Have any other customers been successful in developing this type of export process using XSL?
Tagged:
0