--- title: "Update Operational Risk" slug: "update-operational-risk-crescendo631" tags: ["Update Operational Risk Rule"] updated: 2025-03-19T16:31:26Z published: 2025-03-19T16:31:26Z canonical: "help.symphonysummitai.com/update-operational-risk-crescendo631" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Update Operational Risk Updating a Operational Risk on a change form using a Business Rule Designer is be a powerful way to automate workflow processes, ensuring that any changes in Operational Risk is promptly and accurately reflected on the Change Transaction Form. ## Prerequisites 1. Configure Operational Risk Value. For more information, refer [Configure Operational Risk Value Mapping](https://help.symphonysummitai.com/summit-platform/docs/risk-assessment-operational-risk-value-mapping-crescendo631). 2. Configure Operational Risk in Manage Change Record transaction form. For more information, refer [Manage Change Record](https://help.symphonysummitai.com/summit-platform/docs/manage-change-record-transaction-form-crescendo631). ## Configure BRD to Update Operational Risk Configure Business Rule to Update the Operational Risk field on the Record after submission. This update process is automated using a Business Rule Designer, which allows for the creation of rules that trigger updates based on specific conditions and criteria. To update the change record with the Operational Risk, configure the following Operational rule. 1. Log in as an Application Designer. 2. Navigate to **Service Management** > **Design Studio** > **Change** > **Business Rule Designer**. 3. Click **New** on the list page to configure a Operational Rule. The configuration page displays the following steps as described. GeneralTriggerConditionsActionsPublish The General properties of Business Rule Designer for updating the Operational Risk involves defining the BRD update with a name, providing an Execution Order, selecting the required platform components such as Domain, Sub Domain and Department. Choosing the Transaction Form on the Table field against which the Update rule must be run. For more information, refer [General Properties of Business Rule Designer](https://help.symphonysummitai.com/summit-platform/docs/define-characteristics-4). ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/uor.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=MWRZydqxtiVAg2eKeg3bNiwIDrv%2BPQA1ltAneLjdbmI%3D)Figure: General Properties For more information, refer the following table: | Field | Description | | --- | --- | | Name | Enter the name as **Update Operational Risk**. As the purpose of the BRD is to update the Operational Risk field on the Manage Change Record. | | Description | Describe about the BRD its purpose in the Risk Assessment and more about update workflow automation. | | Execution Order | Enter a value for Execution Order, based on the configured value the BRD is executed. Ensure to configure this Rule with the second highest value. > [!NOTE] > Note > > The highest value in the Execution Order is executed first. Always ensure to have the execution order as below: > > 1. First highest value to Update Business Risk. Example: 350 > 2. **Second highest value to Update Operational Risk.** > > **Example: 300** > 3. Third highest value to Update Overall Risk > > Example: 250 | | Domain | Select **Domain**from the dropdown. Ensure to have the all the Risk Assessment Admin and Transaction Forms from the same Domain. | | Sub Domain | Select **Sub Domain** from the dropdown. Ensure to have Ensure to have the all the Risk Assessment Admin and Transaction Forms from the same Sub Domain. | | Department | Select **Department / Tenant** from the Dropdown. Ensure to have the all the Risk Assessment Admin and Transaction Forms from the same Department. | | Table | Select **Manage Change Record** as a Table value, the Business Rule is run for the selected Record from the Table, for which the field is updated based on the BRD’s update and condition criteria. > [!NOTE] > Note > > This selection is important as the Operational Risk is configured on this transaction form for which an update Operational rule is being set. | | Active | Enable Active control for the rule to be available for use when the Change Record’s Business Risk field is updated. | Click **Next** to configure **Trigger**. Process the Business Rule After the Transaction is **Created** and **Updated**. For more information, refer [Trigger](https://help.symphonysummitai.com/summit-platform/docs/trigger). **After** the **Change Record** is **Created** and **Updated** from the **Manage Change Record** Form, this particular **Update Operational Risk** Business Rule is executed. Which then updates Risk field with the configured value in the Transaction Form. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/trigger.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=6PTDLdapxZ6Nwj8rJnkl%2BQ%2BHgL%2Br2mSz3AIT35Nn%2Fy4%3D) Figure: Trigger Click **Next** to configure **Conditions**. In Conditions step you configure the conditional filter to execute the business rule. If the conditions are met then the Business Rule is executed. Enabling the Operational Risk field to populate with the Risk value. For more information, refer [**Conditions**](https://help.symphonysummitai.com/summit-platform/docs/condition). ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/boc.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=UU8%2BjmBlVA%2FUd5YOTjFQvdsKocGLBmAHbl28mzXE430%3D)Figure: Conditions To configure Condition, perform the following steps: 1. Select to Run **Based on Condition.** 2. Click **+Add Filter Set** and + add icon to insert an additional Filter and configure the below two conditions. | Field | Description | | --- | --- | | Field | Select **Operational Risk Value** from the Transaction Form for both the conditions. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/orv.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=cJcJslLu9jBf2FMl1LkSF11KWift57Bkr34kuRAjdMY%3D)Figure: Field | | Operator | Select Dynamic scale Operator for the below field values. For more information, refer [Dynamic Operator.](https://help.symphonysummitai.com/summit-platform/docs/conditions-crescendo631) 1. **Dynamic Greater than or equal To** ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/condition1.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=pObG3m%2BbsHzbQY6fwmsIWDe%2B3%2FjXhGsa%2Fk9iuR%2BGIM0%3D) Figure: First Filter Dynamic Operator 2. **Dynamic or Less than or equal To** ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/condition2.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=zk3vW5cttLrszziwZk2MELxdkPWfZAY30oC0uzYTrcA%3D) Figure: Second Filter Dynamic Operator | | Value | Select **Operational Risk Value Mapping** from the first condition’s Admin Table, where the **From Scale** is configured. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/orvm1.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=1XshDhVCDVXL4aQjKFpFhtlMoC7WdnenKzaGpEYiOoc%3D) Figure: Value Select **From Scale** as a value for the first condition and **To Scale** value for the second condition. > [!NOTE] > Note > > If Dynamic Scale operator is selected in your condition, then you are enabled to select the Admin Table for the first dynamic operator defined in the condition. When you hover on the second Table, it displays "Table can be changed in the first dynamic condition." ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/33.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=S%2FcgMAwBiVVBOO8BgDHEgTT7AFaFTAoTfrbIpFaMT8M%3D) | Click **Next** to configure **Actions**. In the Action Step, you are enabled to configure the Update action for the fields when the Business Rule is executed. Powered with Dynamic Operator this works effortlessly by executing the workflow to update the required fields on the Form. For more information, refer [Update Fields](https://help.symphonysummitai.com/summit-platform/docs/update-fields). ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/uf.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=o1C7U0SvinjPVJlxK5r2IVZp1a29LgVbNZKvxkvmJRw%3D)Figure: Update Fields Select Operational Rule to Execute Every Time. For other field descriptions, refer the following table: | Field | Description | | --- | --- | | Field | Select **Operational Risk** from Manage Change Record form. This will update **Operational Risk** field’s value from the Mange Change Record to the Change Record’s **Operational Risk** field after submitting the form. | | Operator | Enable the **Dynamic** operator to display the value fields. This operator is powerful to calculate Operational Risk’s dynamic field value and update on the **Operational Risk** field value. | | Value | By default, Admin Table **Operational Risk Value Mapping** is selected and you are enabled to select column name as **Operational Risk** value. | | Override | By default, Override is enabled. | Click **Next** to Publish the Business Rule. Upon **Publishing** the configured Business Rule, it takes effect after the record is created and updated as mentioned in the Trigger step. Select **Published** and click **Submit**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/published.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A17Z&se=2026-11-22T15%3A44%3A17Z&sr=b&sp=r&sig=oofP9NoSz8p8mijF%2Bzku%2FmmSqaa6ikOgoqSxoi7JY3E%3D)Figure: Publish Primary entity in the platform topology which is required to create other components. Sub Domains are subsidiaries under Domains that are used to design the next level of platform components to function independently as required by business units. Tenant is a platform component that is created inside the Sub Domain to leverage the independent functionality of a department along with data privacy.