---
sourceDocument: Australia Sales Customer Relationship Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/order-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Configure approval events

# Configure approval events {#ariaid-title1}

Release version: Australia  
Updated June 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read  
Configure the approval system events that control the approval buttons and stage transitions for a ServiceNow CPQ implementation.

## Before you begin

Role required: admin or sn_adv_appr_mgmt.approval_rule_admin

The environment setup must be complete so that the approval system events, integrations, rules, and fields are seeded in your instance. For more information, see [Set up the environment to manage approvals](https://www.servicenow.com/docs/JWW47Ycu9Z53OKQ1oCz3_g "Complete the setup tasks before creating approval configurations and workflows. These prerequisites enable the approval system for a ServiceNow CPQ implementation.").

## About this task

Configure these events without creating any additional events. The events fall into two groups based on how they are triggered.  
{#configure-approval-events__table_event_groups__entry__3}

| Event | Trigger type | What you configure |
|-|-|-|
| Preview Approval (txn.approval.preview) | Layout button | Event access rules that control when the button is visible, plus a layout button with a UI effect that opens the embedded SN approval component. |
| Recall Approval (txn.approval.recall) | Layout button | Event access rules that control when the button is visible, plus a layout button with a UI effect that opens the embedded SN approval component. |
| View Approval (txn.approval.view) | Layout button | Event access rules that control when the button is visible, plus a layout button with a UI effect that opens the embedded SN approval component. |
| Request Approval (txn.approval.request) | Fired by the embedded component | The stage transition that occurs after the action completes. No layout button is needed. |
| Approve Approval (txn.approval.approve) | Fired by the embedded component | The stage transition that occurs after the action completes. No layout button is needed. |
| Cancel Approval (txn.approval.cancel) | Fired by the embedded component | The stage transition that occurs after the action completes. No layout button is needed. |
[Table 1. Approval event groups]

{#configure-approval-events__table_event_groups}

## Procedure

Configure the Preview Approval event (txn.approval.preview). The UI effect on the Preview Approval button opens the embedded SN approval component in Preview mode, showing the seller which approvals are triggered and who the approvers are before submitting. The Request Approval button inside this component triggers the Request Approval event.

1. Configure the event access that controls when the Preview Approval button is visible.
   1. Navigate to CPQ AdministrationTransactionEvents.
   2. Open the Preview Approval event (txn.approval.preview).
   3. Select Edit Event Access in the top right.
   4. Ensure the Default Access is set to Active.
   5. Configure the visibility condition to show this event when txn.approvalState equals empty ("").  
      The Preview button appears only when no approval is in progress.
   6. Select Save.

   {#configure-approval-events__substeps_preview_access}  
   Tip:  
   The preceding conditions reflect the default. Adjust them to match your stage structure---for example, if there are additional stages where the Preview button should or should not appear, add or modify conditions accordingly.
2. Add the Preview Approval button to the layout.
   1. Navigate to TransactionLayouts and open your layout.
   2. In the Header Buttons section, add a new button and label it Preview Approval or a label of your choice.
   3. In Button Properties, enable the Event Button toggle, then in the Event field select Preview Approval.  
      This links the button visibility to the event access rules you configured.
   4. Enable the UI Effect Button toggle, then set the UI effect properties:  
      * Set UI Effect Type to Approvals.
      * Set UI Effect Target to Modal or Slideout, depending on your preferred display.
      * Set Mode to Preview.
      {#configure-approval-events__ul_preview_ui_effect}
   5. Select Save.

   {#configure-approval-events__substeps_preview_button}  
   The Preview Approval button appears in draft state and opens the embedded approval component in Preview mode.

Configure the View Approval event (txn.approval.view). The UI effect on the View Approval button opens the embedded SN approval component in Status mode, showing the current approval status, approver details, history, and a Recall button for pending approvals. The Recall button appears on the header of the transaction.

3. Configure the event access that controls when the View Approval button is visible.
   1. Open the View Approval event (txn.approval.view).
   2. Select Edit Event Access in the top right.
   3. Ensure the Default Access is set to Active.
   4. Configure the visibility condition to show this event when txn.approvalState is not empty, for example, when it equals requested, approved, recalled, or rejected.  
      The View button appears only after an approval is initiated.
   5. Select Save.

   {#configure-approval-events__substeps_view_access}  
   Tip:  
   You control which approval states cause this button to appear. For example, if you do not want the View button visible after an approval is fully completed, you can exclude the approved state from the condition.
4. Add the View Approval button to the layout.
   1. In your layout, go to Header Buttons and add a new button.
   2. Label it View Approval or a label of your choice.
   3. In Button Properties, enable the Event Button toggle, then in the Event field select View Approval.
   4. Enable the UI Effect Button toggle, then set the UI effect properties:  
      * Set UI Effect Type to Approvals.
      * Set UI Effect Target to Modal or Slideout.
      * Set Mode to Status.
      {#configure-approval-events__ul_view_ui_effect}
   5. Select Save.

   {#configure-approval-events__substeps_view_button}  
   The View Approval button appears after an approval is initiated and opens the embedded approval component in Status mode.

Configure the stage transitions for the action events. The Request Approval, Approve Approval, and Cancel Approval events are fired automatically by the embedded SN component when the seller or approver takes an action. Each event runs txn.approval.getState---a built-in integration that fetches the current approval state from ServiceNow---and updates the txn.approvalState field. No layout button is needed for these events.

5. Configure the stage transition for the Request Approval event (txn.approval.request).  
   This event is triggered when the seller selects Request Approval inside the embedded SN component.
   1. Navigate to TransactionEvents.
   2. Open the Request Approval event (txn.approval.request).
   3. Select Edit Event Access in the top right.
   4. Ensure the Default Access is set to Active and select Done.
   5. Scroll to the Stage Transition section.
   6. Enable the Transition after actions toggle.
   7. Set After all actions run, transition to forward.
   8. Select Add New Action.
   9. To add rule group to an event, select the Rule grouping and then assign the txn.approval.submission rule grouping.
   10. Select Save.

   {#configure-approval-events__substeps_request_transition}  
   Tip:  
   If your stage sequence differs from the default, verify the forward transition points to the correct next stage. You can also add a Rule Grouping action on this event if additional rules need to run at submission time.  
   When a seller submits a request, the transaction moves forward to the Pending Approval stage.
6. Configure the stage transition for the Approve Approval event (txn.approval.approve).  
   This event is triggered when all required approvers approve the request, either inside the embedded SN component or by email. It updates txn.approvalState to approved.
   1. Open the Approve Approval event (txn.approval.approve).
   2. Select Edit Event Access in the top right.
   3. Ensure the Default Access is set to Active and select Done.
   4. Scroll to the Stage Transition section.
   5. Enable the Transition after actions toggle.
   6. Set After all actions run, transition to forward.
   7. Select Add New Action.
   8. To add rule group to an event, select the Rule grouping and then assign the txn.approval.completion rule grouping.
   9. Select Save.

   {#configure-approval-events__substeps_approve_transition}  
   Tip:  
   If you have additional stages between Pending Approval and Approved, verify the forward transition lands on the correct destination. Entry criteria on the Approved stage validates the state before allowing entry regardless.  
   When all approvers approve, the transaction moves forward to the Approved stage.
7. Configure the stage transition for the Cancel Approval event (txn.approval.cancel).  
   This event is triggered when the seller selects Recall inside the embedded SN component (Status mode), or when an approver rejects the request, ending the approval cycle. It updates
   txn.approvalState to recalled or rejected accordingly.
   1. Open the Cancel Approval event (txn.approval.cancel).
   2. Select Edit Event Access in the top right.
   3. Ensure the Default Access is set to Active and select Done.
   4. Scroll to the Stage Transition section.
   5. Enable the Transition after actions toggle.
   6. Set After all actions run, transition to backward.
   7. Set If available from current stage, go back to Draft.
   8. Select Add New Action.
   9. To add rule group to an event, select the Rule grouping and then assign the txn.approval.revision rule grouping.
   10. Select Save.

   {#configure-approval-events__substeps_cancel_transition}  
   Tip:  
   If you want the transaction to return to a different stage on recall or rejection---for example, a dedicated Rejected stage rather than Draft---change the target stage here and verify that stage exists in your blueprint with appropriate entry criteria.  
   On recall or rejection, the transaction returns to the Draft stage so the seller can make changes and resubmit.
8. Configure the event access that controls when the Recall button is visible in the transaction header.
   1. Navigate to CPQ AdministrationTransactionEvents.
   2. Open the Recall Approval event (txn.approval.recall).
   3. Select Edit Event Access in the top right.
   4. Ensure the Default Access is set to Active.
   5. Configure the visibility condition to show this recall event: Disable when txn.approvalState Does Not Equal "requested" Hide when txn.approvalState Does Not Equal "requested".  
      The Recall button appears only when an approval is in progress.
   6. Select Save.

   {#configure-approval-events__recall_access}  
   Tip:  
   The preceding conditions reflect the default. Adjust them to match your stage structure---for example, if there are additional stages where the Preview button should or should not appear, add or modify conditions accordingly.
9. Add the Recall Approval button to the layout.
   1. Navigate to TransactionLayouts and open your layout.
   2. In the Header Buttons section, add a new button and label it Recall Approval or a label of your choice.
   3. In Button Properties, enable the Event Button toggle, then in the Event field select Recall Approval.  
      This links the button visibility to the event access rules you configured.
   4. Select Save.
   {#configure-approval-events__substeps_recall_button}

## Result

All five approval events are configured. The Preview and View buttons appear in the layout according to the approval state, and each action event moves the transaction to the correct stage.

## What to do next

Configure the stages and entry criteria that validate each approval state transition. For more information, see [Configure stages and entry criteria](https://www.servicenow.com/docs/HEASBpfO8iRPkSUZJnykMg "Configure the stages and entry criteria that validate each approval state transition, ensuring a transaction can enter a stage only when its approval state confirms it belongs there.").

*[\>]: and then