OVI Partner Fields in User-defined Forms
Oracle Taleo partner fields can be added into user-defined forms to show a candidate's/new hire's results for every external service request, past or current, for that partner.
Services, provided by certified third parties, that engage users outside of the Oracle Taleo system, can be integrated into Onboarding (Transitions) processes. If an Oracle Taleo service is enabled, an Onboarding (Transitions) administrator can create tasks to interact with it. Completion values returned after the external service provides its results can be displayed in forms.
An Oracle Taleo request is one entire conversation for one candidate/new hire between the Oracle Taleo Enterprise Edition system and a partner, from beginning to end, including as many back-and-forth exchanges as are required to complete the transaction and obtain a final result for the candidate/new hire. On the other hand, an Oracle Oracle Taleo Enterprise Edition result is a single field, either standard or user-defined by the partner, storing a single value like a status, an ID number, a total, or any information that the partner manages.
So for instance, one new hire process can be configured to kick off three different requests for three different partners, and each request may take a varied amount of time and require different participants to reach successful completion and deliver its results to Onboarding (Transitions) for the person. Then, if the same new hire is rehired later on, perhaps a differently-configured process will be appropriate, a shorter rehire process which is configured to only kick off one new request to one of those prior partners and new results will be imported back to Onboarding (Transitions).
In the form builder Field Chooser, there are two different types of results fields:
ServiceLastRequestResult: This category shows each user-defined field that has been created by each Oracle Taleo partner that is enabled on the zone. When placed onto a form, the assignee will see the single most recent value in that field from that partner, if any exists. These fields each yield a single value. Therefore they are useful for many things in a new hire's process for example to display the current information on a form, a PDF, a message template, a content page.
ServiceAllRequestResults: This category shows each enabled partner as a subcategory, and the user-defined fields of each partner can be configured to appear as children columns in a multi-row table on a form. When placed onto a form, the assignee will see all the data from ALL the prior requests for this candidate/new hire for this partner, showing the most recent one at the top. These fields can each yield several values, if more than one request has ever been made to this partner for this candidate/new hire within Onboarding (Transitions). Therefore they are useful to track historical information or to view improvements or changes in results over time. These multi-row fields can only be displayed in forms (not in PDFs, message templates, content pages, conditions).