Creating new applicantworkflows



We are having an issue when creating a new applicantworkflows object.

The field is status. We are getting a FIELD-NOT-ACCESSIBLE error.

When we try and leave the field blank, we are getting a FIELD_REQUIRED error.

Entry: A client clicks the submit candidate button on our platform.
We make a series of API calls to insert the candidate into iCims and attach them to a requisition.
We create a new applicant workflows object.
Exit: Status field returns Field Not Accessible.

Submitted by iCIMSUNIFIL on September 18, 2018 Permalink

Hi, Are you trying to override the apply process? What type of integration are you building? If it is overriding apply, that is prohibited within iCIMS.

Submitted by iCIMSUNIFIL on September 19, 2018 Permalink

Hi,

It isn't that we are trying to override apply. When a recruiter is using our search platform and finds a candidate they like, we are trying to facilitate them uploading the candidate into the iCims system and tying them to a requisition. This is about bringing a passive candidate sourced through an external resume database. Is it the tying to a requisition part that is an issue?

Submitted by iCIMSUNIFIL on September 24, 2018 Permalink

It sounds like you are trying to do candidate matching. Here is how that process should work.
https://developer.icims.com/standard-integrations/candidate-matching/active-candidate-matching

We prohibit allowing a vendor to add passive candidates to the platform automatically. The customer has to select the candidates for import.

In reply to by iCIMSUNIFIL