---
sourceDocument: Brazil Enterprise Architecture
sourceDocumentLink: https://www.servicenow.com/docs/r/application-portfolio-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enterprise Architecture

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# Configure technical debt settings

# Configure technical debt settings {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure whether the server is part of a technical debt record's identity and select which reasons the scheduled job uses to create technical debt.

## Before you begin

The Technical debt settings page requires Technology Portfolio Management plugin (sn_apm_tpm) version 1.12.1 or later. If this version isn't installed, contact your system administrator to update the plugin.

Role required: sn_apm.apm_admin

## About this task

Use the technical debt settings to control how the scheduled job Populate TRM technical debts in the EA Workspace identifies and creates technical debt records.

## Procedure

1. Navigate to WorkspaceEnterprise Architecture Workspace.
2. Open the Setup page by selecting the Setup icon ![]().
3. Select Technical debt, and then select Settings.
4. Under Create technical debt records, select an option.  
   * One technical debt record per server: Creates a separate technical debt record for each server on which the software runs. This is the default option.
   * One technical debt record for all identified servers: Creates a single technical debt record for the software, regardless of how many servers it runs on. The record doesn't show an installed-on server value.

   {#eaw-configure-tech-debt__ul_server_config_options}  
   Note:  
   Regardless of which option you select, you can view all the servers a software product is installed on from the Discovered Technology related list on the technical debt record.
5. Select Save.  
   Note:  
   If technical debt records already exist, you must delete all of them before you can change this option. Contact your system administrator to run a background script that deletes the existing records.
6. Under Create technical debt when any of these conditions are met, select or clear the check boxes for the reasons you want the job to use.  
   * When the software is not defined in the TRM
   * When the software is not approved for production
   * When the software version is not defined in the TRM Product Lifecycle
   * When the software version is not approved for production

   {#eaw-configure-tech-debt__ul_reason_config_options}  
   Note:  
   At least one reason must be selected. If you clear all the check boxes, an error message appears and the setting isn't saved.
7. Select Save.  
   A confirmation message appears. Any active technical debt records whose reason you cleared move to the Archived state on the next run of the scheduled job.
{#eaw-configure-tech-debt__steps_yyh_wkg_jkc}

## Result

The scheduled job Populate TRM technical debts in the EA Workspace uses the updated server and reason configuration starting with its next run. You don't need to restart the instance or re-register the
job.
**Related concepts**   

* [Technical debt settings](https://www.servicenow.com/docs/o8pDx2B5coF0boARkCHDlQ "Control which server and reason criteria the scheduled job uses to create TRM technical debt records.")
* [Technical debt calculation](https://www.servicenow.com/docs/Dn9Fxcic2TBTXHQvvJrIxQ "Technical debt records identify products used in business applications that aren't approved in the TRM or that use unapproved versions. View technical debt records to understand conformance gaps and plan remediation.")  
**Related tasks**   

* [Update TRM technical debt data using scheduled job](https://www.servicenow.com/docs/O2BAZHwURCmgvYYQr3YlIQ "Run the scheduled job to update technical debt data based on Technology Reference Model (TRM) phases. This job identifies products not approved for use in your enterprise and can be scheduled to run periodically.")  
**Related reference**   

* [TRM technical debt states and transitions](https://www.servicenow.com/docs/gagEVaUCPyGscjporpJodA "A TRM technical debt record persists across scheduled job runs and moves between Active, Resolved, and Archived states instead of being deleted and re-created.")

*[\>]: and then