Kenexa     Kenexa XML Integrations                                                     

 

 

 

Foundation Data Integrations:

Foundation data can be imported from an external system into Kenexa Recruiter BrassRing. Foundation Data is comprised of a client’s HRIS source codes, department codes, location codes, and any additional information in drop down lists.

Foundation data is data that can be included on your Kenexa Recruiter BrassRing requisition form as a custom drop-down list. Foundation data often appears in the form of tables (drop-down lists) in your HRIS system. These tables can be uploaded into Kenexa Recruiter BrassRing during your initial system implementation and kept in synch in real-time through the Foundation Import integration type.

Special Instruction for Foundation Integrations

For each foundation data item, all three tags (<Code>, <Description> and <Status>) are required.


1. The <Code> tag sets the foundation option code and serves as a record key to identify whether it is an update to an existing record or an insert of a new record.
2. The <Description> tag sets the description of an option, which is what will be displayed to the end user in the UI.
3. The <Status> tag flags each item as being active or inactive. An ‘I’ Status is used to “delete” the record from the user interface. Records are not actually removed from Kenexa Recruiter BrassRing for historical and reporting purposes but instead marked inactive. Acceptable values for Status codes are “A” (Active) or “I” (Inactive) only.

Note:The file size limit for Foundation Imports should be 64KB per transaction. Wait for the response (success or failure) then send the next transaction of up to 64KB.

Sample XML

<?xml version="1.0"?>

<Envelope version="01.00">

       <Sender>

             <Id>HRISUSER</Id>                         <!-- Configured for a Client - Integration User - this information does not change once Kenexa provides -->

             <Credential>100</Credential>         <!-- Configured for a Client - Client ID - this information does not change once Kenexa provides -->

       </Sender>

       <Recipient>

             <Id/>

       </Recipient>

       <TransactInfo transactType="data">

             <TransactId>5555</TransactId>                     <!-- This is for tracking purpose for use to the Client only. It can be numeric or alphanumeric -->

             <TimeStamp>2006-02-28 09:22:10AM</TimeStamp>    <!--date-time value for troubleshooting and tracking -->

       </TransactInfo>

       <Packet>

             <PacketInfo packetType="data">

                    <PacketId>1</PacketId>

                    <Action>SET</Action>

                    <Manifest>MANIFESTNAME</Manifest>    <!-- Manifest is configured for a client at the time of integration. Provided by Kenexa-->

             </PacketInfo>

             <Payload><![CDATA[<?xml version="1.0"?>

<Foundation_Data>

       <Foundation_Item>

             <Code>0001</Code>

             <Description>Code 1</Description>

             <Status>A</Status>  <!-- Makes an option Active -->

       </Foundation_Item>

       <Foundation_Item>

             <Code>0002</Code>

             <Description>Code 2</Description>

             <Status>I</Status>  <!-- Makes an option InActive -->

       </Foundation_Item>

</Foundation_Data>

]]></Payload>

       </Packet>

</Envelope>

© 2008 Kenexa