Known Issues and Limitations

Issue 1 : Meta is not supported currently for this API

Issue Description 

There is no Meta support currently for this API. 

Impacted APIs

Suggested Workaround

Use the payload mentioned in the API usage section. For the supported codeValues go through Data Dictionary section.

Issue 2 :Event notification is not supported

Issue Description 

Event Notification mechanism is not supported for document upload.

Impacted APIs

Suggested Workaround

There are no workarounds available.

Issue 3: API throws Improper error status code when incorrect information is passed through payload and the API call fails

Impacted APIs

Issue Description 

API is throwing Improper error status code when incorrect information is passed through payload and the API call fails.

For example, while passing the invalid application ID, the API is throwing a 200 OK instead of 400 Bad Request and the error response message is also invalid. For request response details refer to the API Usage section in Chapter 2 - Use Case: Uploading a Recruiting Document.

Suggested Workaround

Please check the whole response message for every call to see if the document is uploaded successfully.

Issue 4: Improper error message is thrown when invalid application ID is passed in request payload

Impacted APIs

Issue Description 

API is throwing Improper error message when incorrect applicationID(itemID) is passed through payload and the API call fails.

Error message:

"developerMessage": {
                            "title": "Error",
                            "messageTxt": "No rows returned for query.  SELECT c.address1,c.address2,c.city,c.clientID,c.country,c.county,c.dedupeCrc32,c.dedupeKey,c.dedupeValue,c.eeoEthnicity,c.eeoGender,c.eeoVeteran,c.emailAddress,c.externalID,c.firstName,c.id,c.isa,c.isaID,c.jobTitle,c.lastName,c.maritalStatus,c.middleName,c.mode,c.nameSuffix,c.phone,c.phone2,c.phone2Type,c.phoneType,c.refIsa,c.refIsaID,c.soSecNum,c.state,c.status,c.timestampCreation,c.timestampDateOfBirth,c.timestampLastUpdate,c.timeZoneID,c.type,c.zip FROM portal.SourcingCandidate$$009 AS c  INNER  JOIN portal.RTiAssignment AS a  ON  c.id = a.candidateID  WHERE  a.clientID = ?  AND  a.id = ? "
                        }

Suggested Workaround

Make sure to pass valid applicationID value passed in the /events/data/eventContext/associatedObject/objectID/idValue path.

Issue 5: Improper error message is thrown when invalid documentTypeCode is passed in request payload

Impacted APIs

Issue Description 

Improper error message is thrown when an invalid documentTypeCode is passed in the request payload.

The error message should be updated because not all codes mentioned in this are currently supported by the Upload Recruiting Document API.

Currently Supported documentTypeCodes:

• applicant.resume
• applicant.attachment

Improper Error message :

 "developerMessage": {

                            "title": "Error",

                            "messageTxt": "DocumentUploadEvent is invalid or missing required information: found 'application.resume', 

                         expected one of applicant.attachment,applicant.coverletter,applicant.resume,application.attachment,application.taxform"

                        }

Suggested Workaround

Make sure to pass the following valid documentTypeCodes:

• applicant.resume
• applicant.attachment

Issue 6: When the file attachment is missing while calling the API, a 500 Internal Server Error is thrown instead of a 400 Bad Request response code

Impacted APIs

Issue Description 

When the file attachment is missing while calling the API, a 500 Internal Server Error is thrown instead of a 400 Bad Request response code.

Improper Error message :

 "userMessage": {
                            "messageTxt": "Error parsing file"
                        },

Suggested Workaround

Make sure to attach the file which you want to upload before calling the API.