Passport: Pymetrics - UDF PYMETRICS_ASM_REQ_TEXT_UDF03 unexpectedly in new order request (causing "Invalid Package ID" error)
(Doc ID 2574760.1)
Last updated on AUGUST 12, 2019
Applies to:Oracle Taleo Platform Cloud Service - Passport Framework - Version 15A and later
Oracle Taleo Recruiting Cloud Service - Version 15A and later
Information in this document applies to any platform.
The Pymetrics passport service includes certain UDFs that, if populated with value, will be included in the new order service request sent to the provider's framework when the service is requested. UDF PYMETRICS_ASM_REQ_TEXT_UDF03 is an example of such a UDF. Normally the correct values to use for a Passport service's UDF are worked out between the customer (or customer's implementer) and the service's provider (which in this case is Pymetrics).
A requisition for which this UDF is not visible when viewed in Recruiting has a value for UDF PYMETRICS_ASM_REQ_TEXT_UDF03 in the service's new order request sent to Pymetrics. Pymetrics system was not configured to expect a value in this UDF for the relevant requisition's service parameter (Package) and therefore returned an error:
It was thought that the requisition would not have a value for UDF PYMETRICS_ASM_REQ_TEXT_UDF03 since the requisition is contextualized with Job Field = 'Campus' and the UDF is contextualized with Job Field = Pymetrics, and the UDF is not part of the relevant requisition's Form and is not seen in Recruiting for that requisition. However subsequent investigation shows that when exported, the requisition actually does have a value for UDF PYMETRICS_ASM_REQ_TEXT_UDF03 (which means the passport service on the Taleo side is doing what it is supposed to, the real issue is why is the UDF populated for the requisition).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document