---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Register other applications

# Register other applications to request policy exceptions {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Enable other applications to request policy exception from any table such as Problem
or Incident and so on. The applications must be added and configured in the Integration
Registry.

## Antes de Iniciar

Role required: sn_compliance.manager, sn_grc.business_user

The GRC business user (sn_grc.business_user) or business user -- lite (sn_grc.business_user_lite) is the minimum required role to raise a policy
exception from an upstream application.

## Por Que e Quando Desempenhar Esta Tarefa

Starting with the New York release, users from any ServiceNow application can request for policy exceptions using
(GRC)'s policy exception management capability. For
example, users can request policy exception for a problem related to a group of
incidents that cannot be resolved for a specific duration. To be able to request
policy exception, you must register the application for policy exception and create
a UI action for requesting policy exception, unless one is provided with the ServiceNow application.

## Procedimento

1. Navigate to AllPolicy and CompliancePolicy ExceptionsIntegration Registry.
2. Click New.
3. On the form, fill in the fields.  
   {#enable-other-apps-to-request-policy-exceptions__table_yxw_n1t_3jb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Enter a name of the registry entry. |
   | Policy exception target table | Select the table on which a policy exception will be applied. |
   | Exception applied on | Target record on which the exception is applied. The options are: * One target record: Specific target record on which the exception is applied. Select the assessed object in the Compliance data source registry. * All target records: All target records on which the exception is applied. Select the policy exception target table on which the exception is applied. {#enable-other-apps-to-request-policy-exceptions__ul_sfx_rbs_ssb} |
   | Source type | Auto-populates Controls if the Exception applied on is One target record. Auto-populates Control objective if the Exception applied on is All target records. |
   | Policy categories | Select one or more categories for filtering policies. For example, if you select the Vulnerability Response category, and are requesting an exception using that application, the list of all policies is filtered by that category, saving you time. For more information, see [Define policy categories](https://www.servicenow.com/docs/KjNyft2QgqIVRPn8Z5kShg "You can filter policies by specific criteria to limit the number of policies displayed when you are creating policy exceptions."). |
   | Entity Mapping ||
   | Relationship | Select Reference field when the entity is a field in the Policy Exception \[sn_compliance_policy_exception\] table. Select Related list when the entity is in a related list of the Policy Exception table. |
   | Entity field | Enter the name of the field that points to the Entity \[sn_grc_profile\] table. This field displays only if you selected Reference field as the Relationship. |
   | Mapping table | Select the table that establishes a relationship between the Policy Exception table and the Entity table. This field displays only if you selected Related list as the Relationship. |
   | Policy exception target field | Select the field in the mapping table that points to the Policy Exception table. This field displays only if you selected Related list as the Relationship. |
   | Entity field | Enter the name of the field in the mapping table that points to the Entity table. |
   | Request Source Nota: The fields in this section are needed only if you are requesting a policy exception from a table other than the Policy Exception Target table. ||
   | Table | Select the table that contains the records from which the policy exception will be requested. |
   | Relationship | Select Reference field when the entity is a field in the Policy Exception \[sn_compliance_policy_exception\] table. Select Related list when the entity is in a related list of the Policy Exception table |
   | Request source field | Select the field that points to the request source table. This field displays only if you selected Reference field as the Relationship field in the Request Source section. |
   | Mapping table | Select the table that establishes a relationship between the Policy Exception table and the Entity table. This field displays only if you selected Related list in the Relationship field in the Request Source section. |
   | Policy exception target field | Select the field in the mapping table that points to the Policy Exception table. This field displays only if you selected Related list in the Relationship field in the Request Source section. |
   | Request source field | Select the field in the mapping table that points to the request source table. This field displays only if you selected Related list in the Relationship field in the Request Source section. |
   | Questionnaire Details ||
   | Exception questionnaire | Select a questionnaire template to generate a questionnaire for the requested policy exception. For more information, see [Create an exception questionnaire](https://www.servicenow.com/docs/dtJ6evhdXoCnZFovhfVvyA "When you are setting up the Policy Exception Integration Registry, you can define configurable questions that can be included in risk assessments created from templates. The Policy Exception Integration Registry can be associated with one template at a time."). |
   [Tabela 1. Policy Exception Integration Registry form]

   {#enable-other-apps-to-request-policy-exceptions__table_yxw_n1t_3jb}
4. Save the record.  
   The Reason Choices related list appears.  
   Nota:  
   The Reason Choices are available to the person who requests a policy exception to explain the purpose of the request. So define reasons that apply to your specific situation. For more information, see [Define policy exception reason choices](https://www.servicenow.com/docs/zQGOB79G2ae0nf5D2ZayNw "You can define reason choices to be available to any user who requests an exception.").
{#enable-other-apps-to-request-policy-exceptions__steps_hsc_3vy_wkb}