--- sourceDocument: Australia Customer Success Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/acct-lifecycle-events Release : - australia ft:locale : - de-DE ft:publication_title : - Australia Customer Success Management ft:clusterId : - actle bundleId : - actle workflow : - Customer and Industry --- # Define risk criteria # Define risk criteria {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer Use the engagement risk definition to configure the metrics required to define the risk signals for an engagement. ## Vorbereitungen * Role required: sn_acct_lc.customer_success_agent * Data source and data context engine mapping must be setup for metric based risk definitions. See [Data Context Engine](https://servicenow-prod.fluidtopics.net/y5PLBXWzvitoRxO0iwWvfg "The Data Context Engine breaks down silos by aggregating data from multiple sources—both internal and external—collecting it in one place to enable data-driven, actionable decisions.") for details. * For table based risk definitions, an active context engine mapping with source table as Engagement must be defined. {#account-lifecycle-setup-risk-defn__ul_zpp_1k5_ydc} ## Warum und wann dieser Vorgang ausgeführt wird You can define the risk conditions, risk category, and threshold values for an engagement in two ways: Metric based risk definition : Use this option to create or update risks if the specified threshold is breached. The context engine data records are generated after the last scheduled job is run. The context in this case is the engagement table. If the threshold specified in the risk definition is breached, a risk is generated. Table based risk definition : Use this option to create or update risks for all records that match the condition in the selected table. When the scheduled job is run, if an active risk that matches the criteria is present, a new risk occurrence record is created. If no active risks are present for the source record+engagement+category combination, a new risk signal is generated for each record. New risks are generated automatically when the Customer Success Risk Analyzer scheduled job is executed. ## Prozedur 1. Navigate to AllSuccess ConfigurationAll Risk DefinitionsNew. 2. Enter the following details: {#account-lifecycle-setup-risk-defn__table_i5y_ynt_ydc__entry__2} | Field | Description | |-|-| | Name | Enter a name for the risk definition. | | Category | Select a category for the risk definition. The risk categories displayed here are defined in the [Create a customer success choice record](https://servicenow-prod.fluidtopics.net/FV4hRoyIgaIlbtPKfUFRuA "Create a record to set up the categories for the customer success choices."). | | Type | Select the type of risk definition. This can be: * Metric * Table {#account-lifecycle-setup-risk-defn__ul_fgk_jst_ydc} | | Description | Enter a description for the risk definition. | | Metric based: This option is used to create or update risks if a risk threshold is breached. If you are creating a metric based risk definition, select the metric, define the thresholds, set up the template, and specify conditions to define the list of applicable engagements. || | Metric | Select the metric definition that has been configured in the Data Source table and mapped with the context engine mapper. See [Data Context Engine](https://servicenow-prod.fluidtopics.net/y5PLBXWzvitoRxO0iwWvfg "The Data Context Engine breaks down silos by aggregating data from multiple sources—both internal and external—collecting it in one place to enable data-driven, actionable decisions.") for details. | | Threshold condition | Specify the threshold condition for the risk definition. If this threshold condition is breached, a risk signal is generated. For example, for the Daily collection of CSAT, the metric threshold condition is set to be less than 50. If the value falls below 50, a risk is generated. | | Threshold | Specify the base threshold for the metric definition. | | Applicable engagements | If you select an applicable engagement, this risk definition will be evaluated for the engagements in the Applicable engagements list. | | Table based: This option is used to create or update risks in all records in the matching table and the specified condition. If you are creating table based risk definition, you must select the table, specify the condition, and set up the template with fields and values to generate risks in the specified format. || | Source table | Select the source table for which the risk definition is to be created. Hinweis: A context mapper must have been defined that associates the source and the context tables. See [Data Context Engine](https://servicenow-prod.fluidtopics.net/y5PLBXWzvitoRxO0iwWvfg "The Data Context Engine breaks down silos by aggregating data from multiple sources—both internal and external—collecting it in one place to enable data-driven, actionable decisions.") for details. For example, if you want to define risk signals for a contract, and select Contract as your source table, a context mapping with a Contract to Engagement association must have been defined. | | Conditions | Specify any conditions that need to be used for the risk definition for the selected source table. Risks are generated for the records in the source table that satisfy the specified conditions. | | Template | Click the Template tab to define the fields for the risk definition. The following are mandatory fields: * Short description * Description * Reported by {#account-lifecycle-setup-risk-defn__ul_mc3_nh5_ydc} | [ ] {#account-lifecycle-setup-risk-defn__table_i5y_ynt_ydc} 3. Click Submit to create the risk definition. 4. If you want to define risk threshold overrides for a metric based definition, open the risk definition you have created, navigate to the Risk Threshold Overrides related list and click New. Enter the following details: * Engagement risk definition: This is the engagement risk definition for which you are creating an override condition. * Threshold: Specify the override threshold value. * Click Add Filter Condition or Add Or Clause to specify additional override conditions. * Rank: Specify a rank for this override condition. 1 is highest rank. If an engagement matches multiple threshold overrides, the engagement with the highest rank is considered first. {#account-lifecycle-setup-risk-defn__ul_dmc_2p5_ydc} 5. Click Submit to create the override condition. 6. Click Publish. When the next scheduled job is run, the risk signals are generated. Navigate to Data Context EngineContext Engine Data to see the date and time the risk signals are generated.
{#account-lifecycle-setup-risk-defn__steps_ppm_szz_12c} * **[Sample risk definitions](https://servicenow-prod.fluidtopics.net/jxivy4BCFGy4wop_KWcaZQ)** These are sample risk definitions available with the base system and can configured based on your requirements.