---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/employee-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Using Enterprise Service Management Integrations Framework

# Using Enterprise Service Management Integrations Framework {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Understand how you can use Enterprise Service Management Integrations Framework to connect
with a third-party system.

## Antes de Iniciar

Role required: sn_hr_integr_fw.admin

## Procedimento

1. Create a source.  
   For more information, see [Create a source in Enterprise Service Management Integrations Framework](https://servicenow-prod.fluidtopics.net/nvQp7m0k2od9Q50wmKW6nQ "Create a source record that represents the third-party system which is integrating with your HR Service Delivery application.").
2. Create an integration service for the source.  
   For more information, see [Create an integration service in Enterprise Service Management Integrations Framework](https://servicenow-prod.fluidtopics.net/3_JUWztA9nNt2nxSGFLm6A "Create an integration service to connect with the third-party system.").
3. Create a scheduled job and trigger the run job flow for the source.  
   * Entries are created in the Integration Job Tracker \[sn_hr_integr_fw_job_tracker\] table. Entries are created for active Scheduled Pull services in the Integration Service Job Tracker \[sn_hr_integr_fw_service_job_tracker\] table.
   * Import sets are created and attached to the service job tracker, and load start time is populated. Once data is loaded in the import set tables, the state of the service job tracker changes to loaded and the load end time is populated.
   * Once data is loaded for all the services, transformation begins based on the service order defined in the Integration Service \[sn_hr_integr_fw_service\] table. The states of services change to complete, and then the state of the job tracker record changes to complete. For more information, see [View job tracker details](https://servicenow-prod.fluidtopics.net/DBNWJPXePaFDn2dzTxbTGw "View details of the source job and service job, such as when did the job begin and end, when did the records start loading into staging tables, or did the job run completely or fail in between.").
   {#use-integrations-framework__ul_kzt_sjn_bnb}