---
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


---

# Technical debt settings

# 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  
Control which server and reason criteria the scheduled job uses to create TRM technical debt records.  
Note:  
The Technical debt settings page requires Technology Portfolio Management plugin (sn_apm_tpm) version 1.11.1 or later. If this version isn't installed, contact your system administrator to update the plugin.

By default, the scheduled job Populate TRM technical debts in the EA Workspace creates a separate technical debt record for each server on which unapproved software runs. You can change
this so that the job creates one technical debt record for a software product regardless of how many servers it runs on.

You can also choose which reasons the job uses to create technical debt. If you clear a reason, the job stops creating new technical debt records for that reason, and any existing active records for that
reason move to the Archived state.  
Note:  
Changing the server configuration requires you to delete all existing technical debt records first. The system blocks the change until you do.{#eaw-setup-tech-debt__eaw-setup-tech-debt-note-1}  
An organization early in its technology governance practice might not be concerned yet with whether a software product is cataloged in the TRM at all. However, it does want to enforce version compliance for products that are cataloged. That organization can clear the reasons related to whether the product is defined or approved, and keep only the version- and edition-related reasons selected. As the organization's practice matures, it can select additional reasons to build a stricter definition of technical debt.
* **[Configure technical debt settings](https://www.servicenow.com/docs/UR0EzwLITH56iBnGbzsixA)**   
  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.

**Related concepts**   

* [TRM technical debt](https://www.servicenow.com/docs/HEkoFsVUp0qKsWmSFMbFGw "Manage the TRM technical debts that are created for the products that aren’t approved for the usage.")  
**Related tasks**   

* [Configure technical debt settings](https://www.servicenow.com/docs/UR0EzwLITH56iBnGbzsixA "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.")  
**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.")