---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Approval field mapping

# Approval field mapping {#ariaid-title1}

Release version: Brazil  
Updated October 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Approval field mapping

This document outlines the mapping of approval fields, events, and rules within the Transaction Manager (TM) and their relationship to the quote table.
It provides essential information to help ServiceNow customers understand how approval states and events integrate with the Advanced Approvals configuration, facilitating troubleshooting and configuration validation.
Show full answer Show less  

## Approval fields

* **Approval State (txn.approvalState):** Represents the approval state of the transaction. It is updated by the Cancel Approval event to values such as "recalled" or "rejected". This field is a text field and is not mapped by default to the quote table unless a reason is identified. It is access-modifiable: No and used only for approvals.
* **Stage (txn.stage):** Maps to the *state* field in the quote table with a default value of "draft". This field holds the general state of the transaction and is included in the transaction-to-quote synchronization but is not shown in the Transaction Manager user interface. The approval state is held in a separate field.

## Approval events

These system events manage the approval lifecycle within the Transaction Manager:

* **Preview Approval (txn.approval.preview):** Previews approval conditions before an approval request.
* **Request Approval (txn.approval.request):** Submits an approval request.
* **Cancel Approval (txn.approval.cancel):** Recalls or rejects an approval request and updates *txn.approvalState* accordingly.
* **Approve Approval (txn.approval.approve):** Approves an approval request.
* **View Approval (txn.approval.view):** Displays approval status and history.

## Approval rules

Validation rules ensure consistency between the Transaction Manager approval state and the approval engine confirmation:

* **Validate Approval Submission (txn.approval.validateSubmission):** Validates that the submission state matches the approval engine. Errors prompt retry and administrator contact.
* **Validate Approval Completion (txn.approval.validateCompletion):** Ensures the transaction is only marked approved when confirmed by the approval engine.
* **Validate Approval Revision (txn.approval.validateRevision):** Confirms that recalled or rejected states are properly reflected before allowing edits.

## Components added by the approval blueprint

Importing the blueprint automatically adds critical elements to support Advanced Approvals:

* System events for all approval actions (Preview, Request, Approve, Cancel/Reject, View).
* Integrations facilitating data flow between microservices and the approval system.
* Approval validation rules and rule groups for submission, completion, and revision phases.
* The Approval State field for tracking approval progress.

## Related list support and tenant settings

* **Approvals tab:** Not supported as a related list; instead, approvals are accessed via a slideout triggered by a header event. No additional action is required by the user.
* **Approvals tenant setting:** Seeds the necessary system objects that Advanced Approvals requires for operation.  
Approval fields, events, and rules in Transaction Manager (TM) and how they map to the quote table. Use these names to check or troubleshoot your Advanced Approvals configuration.

## Approval fields {#r_approval_field_mapping__section_approval_fields}

{#r_approval_field_mapping__section_approval_fields__entry__3}

| Field | Description | Type |
|-|-|-|
| Approval State (`txn.approvalState`) | Approval state of the transaction. The Cancel Approval event updates this field to recalled or rejected. | Text |
[Table 1. Approval fields]

## Field mapping {#r_approval_field_mapping__section_field_mapping}

{#r_approval_field_mapping__section_field_mapping__entry__4}

| Transaction Manager field | Quote table column | Default value | Notes |
|-|-|-|-|
| `txn.approvalState` | Not mapped to the Quote table | Empty | Access modifiable: No. Conditions for inclusion: NOW Only - Approvals. Needed for approvals. This field maps to the Quote table only if a reason is identified. |
| `txn.stage` | State (`state`) | `draft` | Existing field. A separate field holds the approval state. Included in the TXN-Quote sync. Not shown in the Transaction Manager UI. |
[Table 2. Approval field mapping]

## Approval events {#r_approval_field_mapping__section_approval_events}

{#r_approval_field_mapping__section_approval_events__entry__3}

| Event | Variable name | Description |
|-|-|-|
| Preview Approval | `txn.approval.preview` | System event that previews the approval conditions. |
| Request Approval | `txn.approval.request` | System event that submits an approval request. |
| Cancel Approval | `txn.approval.cancel` | System event that recalls or rejects an approval request. Updates `txn.approvalState` to recalled or rejected. |
| Approve Approval | `txn.approval.approve` | System event that approves an approval request. |
| View Approval | `txn.approval.view` | System event that shows the approval status and history. |
[Table 3. Approval events]

## Approval rules {#r_approval_field_mapping__section_approval_rules}

{#r_approval_field_mapping__section_approval_rules__entry__4}

| Rule | Variable name | Description | Error message |
|-|-|-|-|
| Validate Approval Submission | `txn.approval.validateSubmission` (also listed as `txn.validateApprovalSubmission`) | Checks that the approval state in Transaction Manager matches the submitted state confirmed by the approval engine. | Error occurred during submission of approval request. Please try again. We couldn't submit this transaction for approval. Please try again. If the issue continues, contact your administrator. |
| Validate Approval Completion | `txn.approval.validateCompletion` (also listed as `txn.validateApprovalCompletion`) | Checks that the approval state in Transaction Manager matches the approved state confirmed by the approval engine. | Error occurred during submission of approval. Please try again. This transaction can't be marked as approved yet, the approval is still in progress. |
| Validate Approval Revision | `txn.approval.validateRevision` (also listed as `txn.validateApprovalRevision`) | Checks that the approval state in Transaction Manager matches the recalled or rejected state confirmed by the approval engine. | Error occurred during recall or reject. Please try again. This transaction is currently under approval and can't be edited. Please recall the approval request first. |
[Table 4. Approval rules]

## Components added by the approval blueprint {#r_approval_field_mapping__section_blueprint_components}

Importing the approval blueprint adds the following components:

* System events: Preview, Request, Approve, Cancel/Reject, and View.
* Integrations: data flow between the microservices and the approval system.
* Rules: Validate Approval Submission, Validate Approval Completion, and Validate Approval Revision.
* Rule groups: Approval Submission, Approval Completion, and Approval Revision.
* Field: Approval state.

## Related list support {#r_approval_field_mapping__section_related_lists}

{#r_approval_field_mapping__section_related_lists__entry__3}

| Related list | Support | Notes |
|-|-|-|
| Approvals tab | Not supported | The approvals slideout is accessible through a header event. No action needed. |
[Table 5. Approval related lists]

## Tenant setting {#r_approval_field_mapping__section_tenant_setting}

The Approvals tenant setting seeds the system objects that Advanced Approvals needs.

