PrismHR API user-related processes for initial and ongoing imports

PrismHR Import Users (initial imports), and PrismHR Import Ongoing (includes ongoing user imports) handle Active / Inactive user records in PrismHR and ClientSpace in the following manner.

Initial Imports: Insert

PrismHR User Status	ClientSpace User Status	After Import ClientSpace User
Active	N/A	Inactive
Inactive	N/A	Inactive
Excluded	N/A	Not Imported

Initial Imports: Update

PrismHR User Status	ClientSpace User Status	After Import ClientSpace User
Active	Active	Active
Active	Inactive	Inactive
Inactive	Active	Inactive
Inactive	Inactive	Inactive
Excluded	Not Imported	Not Imported

Ongoing Imports: Insert

PrismHR User Status	ClientSpace User Status	After Import ClientSpace User
Active	N/A	Inactive
Inactive	N/A	Inactive
Excluded	N/A	Not Imported

Ongoing Imports: Update

PrismHR User Status	ClientSpace User Status	After Import ClientSpace User
Active	Active	Active
Active	Inactive	Inactive
Inactive	Active	Inactive
Inactive	Inactive	Inactive
Excluded	Not Imported	Not Imported

When retrieving User Details for a User from an Import Queue record, if PrismHR returns an error "User xxxx does not exist," the existing ClientSpace User record is set to Inactive (if it exists). The queue record is set to Completed with the message “User 'userId' cannot be found in Prism, inactivated in ClientSpace (if exists), queue record automatically Completed."