Standard Assessment Questions from a Partner

These Questions came to our team via a Sales Engineer. The answers are after the "-" Please note only partners with a STANDARD INTEGRATION can be given access to a shared sandbox environment:

Not sure who I should be sending some of these questions to so please pass them along as necessary. All of this combined feels like a much larger picture that isn’t documented and too much for a forum post.

I’ve come across some new questions regarding standing up a new Status Update based Assessment integration now that I have access to the sandbox.

I’ve managed to create a new assessment on the sandbox account/customer, but this required using magic values provided by iCIMS support on the forum. How does this work in production? At minimum this magic value seems like it will not be the same across all customers. Is it normally iCIMS staff responsibility to setup assessments for customers? If customers are creating assessments themselves the value for what appears to be the list-of-assessments node seems undiscoverable to me so far.

- Assessments should be added via the List API. We have two fields, Assessment Type on the job and Assessment Name on the results. Assessment Type should be used to determine which questionnaire/test should be presented to the candidate. Assessment Name is used when returning the results and associating with the score. The LIST API is used to update both fields. Here a forum link that addresses the how to. https://developer.icims.com/how-do-we-create-assessment

Are any additional fields other than `value` available to use on assessments? Our integration will provide access to any of several thousand language tests and, if possible, I would like to avoid referencing them by name when creating the assignment on my side. The `id` field on assessments feels private, and if nothing else, - I’d prefer to avoid building large maps of AssessmentID -> PARTNER Test ID.

- When you create an assessment in iCIMS, the platform creates a unique id per customer id. How it is mapped is up to our partners.

To be clear: I expect most customers will only setup a few PARTNER integrated assessments within iCIMS, but on our side we have 40+ tests named something like “PARTNER Reading Comprehension Test”.

- It is up to the partner to decide the mapping

How am I supposed to map an initial Status Update request back to which assessment was selected? The only value provided leading in that direction is the “newStatus” field, but I see no documented way to query details of workflow statuses as a type to even get started.

- As stated in the first response, the assessment type should determine which test to present. After you receive the initial iCIMS POST, you should run a GET on the job to retrieve the assessmenttype field.

Is it possible to create the necessary workflow statuses within the sandbox myself? I’m unable to transition the candidate to a status that would trigger the integration without creating these. How is this handled in production normally?

- No, we do not give partners access to the user admin page of the sandbox. There is one workflow status given per partner.

Is it possible to have the sandbox configured to actually POST out the workflow status changes to my service? This would certainly be helpful for testing and validation. I’m aware that the FAQ suggests using a chrome extension, that isn’t a solid substitute for verifying that a request coming from iCIMS will contain what is expected.

- In the email sent with the sandbox credentials, there was a request for your endpoint. Please respond with that information so the configuration can be completed.

How are assessment statuses managed? Is there API access to manage these? The examples given in the documentation (https://developer.icims.com/Standard-Integrations/Assessments#Status_Update) all use completely undocumented values for the “id” field when PATCHing “assuessmentstatus”. Are these values consistent between customers?

- On the developer site, we list the standard statues. Here is the link: https://developer.icims.com/Data-Models/Recruiting-Workflow . The first call would be a POST to iCIMS. Any updates to the status/result set would be a PATCH.