Human Resources Provisioning Service

1. HR data will be sent to CE via a REST interface. The URL will be provided by your project manager during implementation.

2. To import a data file, the customer will perform a multi-part file upload (HTTP POST), of an XML file. For example:

     curl --user username:password --form [email protected] https://final.url.com/kc-dev/hr-import/hrimport/import
   

   The output of the command will return a little JSON response which will include the importId:

   {
       "importId":"5702e73f-8978-42dd-aabd-78dffeba2f84",
       "status":"COMPLETE",
       "message":"Import has finished",
       "startTime":"1395694542611",
       "recordTotal":"33",
       "processedRecords":"33",
       "errorCount":"0"
   }
   

3. The format of the XML file is defined by the schema: hrmanifest.xsd. The schema will be used to validate the XML file upon upload to ensure it is a valid HR manifest.

4. A sample HR manifest XML file is provided for reference: hrExampleImport.xml.

5. The service expects that you will be sending a full dump of ALL active users from your HR system. Users will be treated differently based on their current status in the system:

   • New users will be created. The record for each new user will be validated to ensure all required fields are provided.
   • Existing users who are in the import will be updated. Each user record contains sub-records for names, phones, addresses, emails, degrees, and appointments. If these sub-records are present in the import the system will be updated to match. If these sub-records are not present in the import no change will be made to these values in the system. If these sub-records are present but empty all sub-records for that type will be deleted (eg. an empty sub-record will remove all degrees for the person within the system).
   • Existing users who are omitted from the import will be disabled in the system.

6. The import will run asynchronously. If the import is able to start successfully the HTTP POST will return with a status code of 200. The import will continue to process on the server.

7. Only one import can run on the server at a time. If an import is in process when the HTTP POST request is made the new import will not start and a status code of 400 will be returned.

8. Status of the current import can be checked with the command:

     curl --user username:password https://final.url.com/kc-dev/hr-import/hrimport/import/<importId>
   

9. The current import can be aborted with the command:

     curl --user username:password -X DELETE https://final.url.com/kc-dev/hr-import/hrimport/import/<importId>
   

XML Schema Versioning

1. Semantic version numbers will be recorded using both major and minor numbers:

     <schema version="1.0"
       targetNamespace="https://github.com/KualiCo/ce-tech-docs/tree/master/v1_0">
   

2. When building your HR manifest XML, be sure to indicate which version of the schema your data is compatible with:

     <hrmanifest schemaVersion="1.0">
   

3. Backwards compatibility will be maintained within the same major version number. When backwards compatibility is not possible, then the major version will be incremented and the targetNamespace will also change. For example:

     <schema version="2.0"
       targetNamespace="https://github.com/KualiCo/ce-tech-docs/tree/master/v2_0">
   

4. Note: Changes to the schema that would require a compatibility change, will be tied to a new version of the REST API as well. We will do our best to keep older versions of both the REST APIs and corresponding XML schemas working as long as possible. This will help minimize any impact to the customer as much as possible.