Integrate other ServiceNow, Inc. applications with GRC and easily report risk events from within those applications. This integration saves time for all users.

1. Navigate to Risk Events > Administration > Integration Configuration.
2. On the form, fill in the fields.

   Table 1. Risk Event Integration Configuration form

   Field	Description
   Number	Auto-generated number.
   Active	Option to allow the creation of risk event from the application table.
   Integration name	Short and unique title for the integration. For example, to report a risk event from an incident table, you can enter Incident-risk-event-integration.
   Application table	Application table to be used for reporting risk events. The table selected here determines the upstream application that will be used for reporting risk events.
   Source for name	The mode used to populate the name of the risk event: Form field: Select this option if you want the value from a specific selected field to be used as the risk event name. Default value: Enter a custom value. The risk event is created with the name you enter here.
   Source for description	The mode used to populate the description of the risk event.
   Source for entity	The mode used to populate the source of entity of the risk event.
   Source for date of discovery	The mode used to populate the source of date of discovery.
   Name	Field in the application table used to populate the value of the Name field of the risk event. This field appears only when Form field is selected from the Source of name field.
   Default Name	Default name to be used for the risk event. This field appears only when Default value is selected from the Source of name field.
   Description	Field in the application table from which the description of the risk event is populated. This field appears only when Form field is selected from the Source of description field.
   Default description	Description to be used for the risk event. This field appears only when the Default value is selected from the Source of description field.
   Entity	Field from the application table that is a reference to a GRC entity or reference to a record to which a GRC entity points. This field appears only when Form field is selected from the Source of entity field.
   Default Entity	Default entity for risk events created from the table you selected in the Application table field. This field appears only when Default value is selected from the Source of entity field.
   Date of discovery	Field in the application table from which the date of discovery of the risk event is populated. This field is visible only when Form field is selected from the Source of date of discovery field.
   Default date of discovery	Date of discovery of the risk event.
   Default event type	Type of event. For example, if the event is financial or non-financial.
   Event subtype	Subtype of the event. For example, if the event is actual or potential.
   Source for Non-Financial impact	Mode used to populate the source of non-financial impact.
   Non-Financial impact	Field in the application table from which the non-financial impact of the risk event is populated. This field appears only when Form field is selected from the Source of non-financial field field.
   Default non-financial impact	Severity of the risk event. The choices are Low, Medium, or High.
   Source for expected loss	The mode used to populate the source of expected loss.
   Expected loss	Field in the application table from which the expected loss of the risk event is populated. This field appears only when the Default event type is Financial impact and Form field is selected from the Source of expected loss field.
   Default expected loss	Monetary value of the loss. This field appears only when the Default event type is Financial impact and Default value is selected from the Source of expected loss field.
   Display UI Action Based On
   Mode	The mode used to create the UI action. The choices are: Simple: Use this mode to set simple filter conditions. For example, if the impact of an incident is high, the Report a Risk Event UI action must be created. Advanced: Use this mode if you want to write a script to query other tables along with the table selected in the Application table field. This is primarily used for cases, where there is advanced logic on when this should appear the user must write a code for it.
   Role condition	Roles that can report risk events from the upstream application.
   Script	Field to write custom-script to query any table. Note: This option to write a script is only available to users who also have the sn_grc.developer role. This field appears when the Mode field has Advanced selected.

3. Click Submit.
   Any other application table which extends the task table can configure this integration. For details, see KB0780985.