---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Locate and transform documents

# Use import mapping to locate and transform source employee documents {#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

Import mapping locates your source employee documents from your source document
repository and transforms them to import them to Employee Document Management.

Import maps define mapping variables used to acquire meta data from the source document
repository. It also allows you to correctly identify the employee documents you want to import
and maps them to required elements in Employee Document Management.  
The required elements for a local network directory:

* Employee name
* Document type
* File name
{#import-mapping__ul_bv3_gt3_2gb}  
The required elements for a third-party, cloud-based directory:

* items
* item
* Employee name
* Document type
* File name
* url
{#import-mapping__ul_b3h_yrx_lgb}

## Parsing for fields and values from an output file {#import-mapping__section_o45_lw3_2gb}

If your source document repository provides an output file, you can transform mapping locates, parse, and map the output file into values that Employee Document Management requires. To transform an output file, do the following:

* Create a Field mapping type that finds an array of items in the output file (JSON is an example of an output file).
* Create a Field mapping type that for each item in the array that locates the file ID.
* Create a Field mapping type that locates the employee mapped element.
* Create a Field mapping type that locates the docType mapped element.
* Create a Field mapping type that locates the fileName mapped element.
* Create a Field mapping type that locates the url mapped element.
{#import-mapping__ul_nvm_5y3_2gb}

## Extracting from a file name {#import-mapping__section_esl_vw3_2gb}

If your source employee documents have:

* A consistent naming convention.
* The employee file has all required meta data in the file name.
{#import-mapping__ul_ubj_fqj_2gb}You can use import maps to locate and transform the source employee document into values that Employee Document Management requires.  
For example, your employee documents have a consistent naming convention: Abel_Tuter_LOARequestLeave.pdfYou can map parts of the file name to the required elements for Employee Document Management:

* Employee name: abel.tuter
* Document type: LOARequestLeave
* File name: Abel_Tuter_LOARequestLeave.pdf
{#import-mapping__ul_gj4_1rj_2gb}

## Scripting {#import-mapping__section_v1n_wrj_2gb}

You can also use scripts to map source elements to the required map elements for Employee
Document Management. See [Scripts](https://www.servicenow.com/docs/access?context=c_Script&version=australia&pubname=australia-api-reference&ft:locale=en-US).  
Nota:  
The base system provides import map examples you can use as models.