Before this integration, the entire New Hire onboarding process was carried out in Taleo. Post this integration, the IT tasks for the new hires will be taken out of Taleo and will be managed through ServiceNow. ServiceNow will send the information of the userID, Hardware and Email information back to Taleo through automated feeds.
Along with this, the ServiceNow Request ID will also be stored in Taleo in the candidate's profile for service request tracking.
All the IT tasks in the onboarding process will be carried in ServiceNow. All the fields required to create a ServiceNow ticket to process the IT tasks that will be provided back to Taleo.
- The onboarding workflow will capture the UserID with domain information in the messaging form.
- The form will have instruction to input the domain name as '@domain-name.com' for new hires who will have their userIDs created and 'domain-name.com' for new hires who will be getting NT IDs (userIDs) created.
After the form will be submitted, the field information will be exported and extract all the necessary information to create a ticket in service catalog with identifiers.
The integration will be a two communication with Service Now and will comprise of three(3) Taleo-ServiceNow integration feeds.
A set of information will be required to initiate a service request in ServiceNow. The current source of that information is (let say) Oracle. Going forward, this information will be stored in Taleo and sent over to ServiceNow in an XML file that would be received by the Integration Layer (BizTalk) who would further process the information and send them thru via web-services to ServiceNow environment.
Once, ServiceNow receives the required information from the Integration Layer (BizTalk), would interpret the incoming information via Business Rules and log a New Hire Onboarding request (order guide) in ServiceNow.
The New Hire Onboarding request would create respective mandatory tasks to be sent out to respective teams in ServiceNow to fulfill their triggered requests.
For instance, those tasks would be,
- User ID creation & email address creation/provisioning
- Hardware Request
- VPN provisioning
Once these tasks are processed, information would flow back to the Integration Layer (BizTalk), who would route the information back to Taleo application.
HIGH-LEVEL WORKFLOW DIAGRAM:
FAQs:
Why there are three layers of integration?
Ans: Microsoft BizTalk acts as a middleware system since Taleo has very limited integration capabilities.
What is BizTalk?
Ans: Microsoft BizTalk Server (or simply "BizTalk") is an Inter-Organizational Middleware System (IOMS) that enables companies to automate business processes, through the use of adapters which are tailored to communicate with different software systems used in an enterprise.
Created by Microsoft, it provides enterprise application integration, business process automation, business-to-business communication, message broker and business activity monitoring.
