--- 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 --- # Migrating from HR Document Templates to Document Templates # Migrating from HR Document Templates to Document Templates {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 min. de leitura Review these guidelines to successfully migrate from HR Document Templates to Document Templates. Document Templates provides the latest experience of HR Document Templates functionality with additional features and capabilities. Importante: Starting with the Australia release, HR Document Templates is being prepared for future deprecation. It will be hidden and no longer activated on new instances, but will continue to be supported. Use [Document Templates](https://www.servicenow.com/docs/CLhHPzMDfL6oJ6lOzXVr6A "With the ServiceNow Document Templates application, you can create HTML and PDF document templates to generate standard letters or documents. You can automate and simplify the process of filling, signing, and reviewing a document online.") that provides the latest experience for this functionality. For migration guidelines, see [Migrating from HR Document Templates to Document Templates](https://www.servicenow.com/docs/6sGo8iXlrqVNNp1jDNT~JA#migration-hrdt-dt "Review these guidelines to successfully migrate from HR Document Templates to Document Templates. Document Templates provides the latest experience of HR Document Templates functionality with additional features and capabilities."). For deprecation details, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0867184) article in the Now Support knowledge base. Review the following details to understand the key offerings and differences between HR Document Templates and Document Templates. {#migration-hrdt-dt__table_zcy_f2n_vbc__entry__3} | Table/Feature | HR Document Templates | Document Templates | |-|-|-| | Template | HR Document Template \[sn_hr_core_document_template\] | Document Template \[sn_doc_template\] | | Document Type/Category | Document Type \[sn_hr_core_document_type\] | Category \[sn_doc_template_category\] | | Criteria | HR Criteria \[sn_hr_core_criteria\] | User Criteria \[user_criteria\] | | PDF template mappings | PDF Template Mapping \[sn_hr_core_pdf_template_mapping\] | Template Mapping \[sn_doc_pdf_template_mapping\] | | Participants | Participants are not supported. You must directly map user fields in HTML template body or PDF template mappings. | Participants are supported. Participant details are stored in the Participant \[sn_doc_participant\] table. You must map participants for signing in HTML body and PDF template mappings. For an HTML template, see [Create participants for an HTML document template](https://www.servicenow.com/docs/0O3oLaJvhBj_erR_QwuzHQ "Define actions and the order of actions for participants. The type of action and order are considered while initiating document tasks."). For a PDF template, see [Create participants for a PDF document template](https://www.servicenow.com/docs/pDbVx6mBzK1EPQmlCuKKyQ "Define actions and the order of actions for participants. The type of action and order are considered while initiating document tasks."). | | HTML Template Translation | - | Supported See [Use Localization Framework for Document Templates](https://www.servicenow.com/docs/nJMf4TkvQ8~I47nmuwb9vA "Translate content in Document Templates and document blocks Localization Framework.") | | HTML template blocks | - | Supported See [Document blocks in Document Templates](https://www.servicenow.com/docs/fQgRgMkGD0Rq2RWkzYkYwA "Replace blocks of text in a document based on certain rules so that you do not have to create multiple template versions of the same document."). | | HTML template scripts | - | Supported See [Document template scripts](https://www.servicenow.com/docs/ntffgrTKOjiLkri1sHe8wA "With document template scripts, you can dynamically change the text in the body of the HTML template. Document template scripts allow you to perform simple tasks, such as displaying HR data, and complex ones, such as making advanced database queries."). | | HTML template TOC | - | Supported See [Create a TOC configuration in Document Templates](https://www.servicenow.com/docs/6WkjvhX1am2b4Ul~WmmZ0Q#create-toc-doctemp "Create a TOC configuration to generate Table of Contents in a PDF document that is generated from an HTML document."). | | User action | Only one action type is supported: Signing | Different action types are supported (Fill, Review and Signing) based on the template type. For an HTML template, see Action type in [Create participants for an HTML document template](https://www.servicenow.com/docs/0O3oLaJvhBj_erR_QwuzHQ "Define actions and the order of actions for participants. The type of action and order are considered while initiating document tasks."). For a PDF template, see Action type in [Create participants for a PDF document template](https://www.servicenow.com/docs/pDbVx6mBzK1EPQmlCuKKyQ "Define actions and the order of actions for participants. The type of action and order are considered while initiating document tasks."). | | Tasking | Tasking is done through HR tasks. | Tasking is done through document tasks based on configured participants. | | Signing type | For HTML, only ServiceNow signing is supported. For PDF, all three signing types are supported: ServiceNow Sign, DocuSign, and AdobeSign. | For both HTML and PDF, all three signing types are supported: ServiceNow Sign, DocuSign, and AdobeSign. Nota: * Template must be created in ServiceNow. * Only signing is supported in external system. * Templates that are created in DocuSign or AdobeSign are not supported in the Document Templates application. {#migration-hrdt-dt__ul_hlw_t2r_bcc} | | HR case fields to be used in case template ||| | Document template | PDF template (pdf_template) | Document template (document_template). | | Document type/category | Document type (document_type) | Document template category (document_template_category) | | HR service configuration ||| | Case option | Automatically create draft document | Automatically Initiate Document tasks Automatically initiate document tasks based on participant configuration. See . | [Tabela 1. Functionality and Table Comparison: HR Document Templates and Document Templates] {#migration-hrdt-dt__table_zcy_f2n_vbc} ## Migrate HR Document template (HTML) to Document Template {#ariaid-title2} Follow the steps for migrating HR Document template (HTML) to Document template (HTML). ### Antes de Iniciar Role required: admin ### Procedimento 1. Create a document template category in the Category \[sn_doc_template_category\] table (if HR Document template has a document type associated with it). 2. Navigate to Document TemplateHTML template. 3. Click New. 4. Fill in the form fields, such as Name, Table, Category, Body, Language, similar to HR Document template and save it. If there is any signature token (Signature token: ${signature}, ${\<-user_field-\>.signature}) in HTML body, remove it and save the template. 5. If HR document template has HR criteria associated with it, select the corresponding user criteria in the new document template. 6. Find participants based on signature tokens in old HR document template body, and create participant records in the Participant related list in the new Document Templates. After a participant is created, add the signature token by clicking Insert signature. In the legacy HR Document Templates body, signature token is supported in the format ${\<-user_field-\>.signature} while in new Document Templates body, signature token is supported in the format ${signature:\<-participant_user_name-\>}. 7. Publish the template by clicking Publish. 8. Update the case template to use the new document template or category. See the HR case fields in the Functionality and Table Comparison: HR Document Templates and Document Templates table in [Migrating from HR Document Templates to Document Templates](https://www.servicenow.com/docs/6sGo8iXlrqVNNp1jDNT~JA#migration-hrdt-dt "Review these guidelines to successfully migrate from HR Document Templates to Document Templates. Document Templates provides the latest experience of HR Document Templates functionality with additional features and capabilities."). ## Migrate HR Document template (PDF) to Document Template {#ariaid-title3} Follow the steps for migrating HR Document template (PDF) to Document Template (PDF). ### Antes de Iniciar Role required: admin If you want to migrate your AdobeSign or DocuSign templates to Document Templates: 1. Download your organization's AdobeSign or DocuSign PDF templates from AdobeSign or DocuSign accounts, and convert those templates to fillable forms. 2. Manually create corresponding Document Template PDF template records and upload the downloaded PDFs. See the steps mentioned in the following procedure. 3. Update the HR Service and HR Template configurations as required to align with the new PDF Document Templates that have been created. {#hr-dt-pdf__ol_adh_mmr_nfc} ### Procedimento 1. Create a document template category in the Category (sn_doc_template_category) table (if HR Document template has a document type associated with it). 2. Navigate to Document TemplatePDF template. 3. Click New. 4. Fill in the form fields, such as Name, Table, Category, and Language, similar to that of HR Document Templates. 5. If HR document template has HR criteria associated with it, select the corresponding user criteria in the new document template. 6. Select Attachment type as Select from document revision, and add Document revision used in the HR document template. 7. Select the corresponding signing type and Save. 8. Click the Parse PDF related link. Template mapping records are created. Update the mapping fields. 9. Create a participant record with action type Sign for each user who needs to sign the document. Nota: This step is required only when legacy HR Document Template has PDF Template mapping record with Document field type as Signature. 10. Publish the template by clicking Publish. 11. Update the case template to use the new document template or category. For more information, see the HR case fields in the Functionality and Table Comparison: HR Document Templates and Document Templates table in [Migrating from HR Document Templates to Document Templates](https://www.servicenow.com/docs/6sGo8iXlrqVNNp1jDNT~JA#migration-hrdt-dt "Review these guidelines to successfully migrate from HR Document Templates to Document Templates. Document Templates provides the latest experience of HR Document Templates functionality with additional features and capabilities.").