--- title: "Business Rule Designer – Change Management" slug: "business-rule-designer-change-management" status: "update" updated: 2026-11-12T05:29:40Z published: 2026-11-12T05:29:40Z canonical: "help.symphonysummitai.com/business-rule-designer-change-management" --- > ## 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. # Business Rule Designer – Change Management Business Rules bring automation into everyday Change Management operations by allowing administrators to define what should happen, when it should happen, and under which conditions. Using the Business Rule Designer, administrators can configure rules to handle routine tasks such as updating Change records, triggering notifications, escalating high-risk changes, and coordinating related record updates. Whether it is validating critical information before a Change progresses, automatically updating records after implementation, or scheduling periodic activities, Business Rules help organizations reduce manual effort and keep operations running smoothly. With flexible execution modes, configurable conditions, and multiple action types, administrators can tailor automation to their operational needs while ensuring consistent and controlled Change processes. #### Key Benefits The following infographic depicts the key benefits of Business Rules in Change Management. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Infographic_CM_BR_Benefits.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=EwCsOLx68LLBufM4mFXPK0SxlTHpESGyUHx8%2BRWydOA%3D) #### Use Case Let us explore the following use case for better understanding. | **Use Case** | **Solution** | | --- | --- | | Ira is a Change Analyst at **NovaTech** who manages changes across multiple enterprise applications. She is responsible for ensuring that each Change record contains the required implementation and risk details. One afternoon, Ira updates a Change to the status **“Ready for Implementation”**, but the record is missing mandatory information such as *Implementation Plan*, *Backout Plan*, and *Risk Assessment*. NovaTech wants to ensure that analysts **cannot proceed with the Change** without providing all required implementation and risk information. | A Business Rule is configured in **After** execution mode under **Change Management**. The rule runs **immediately after** Ira submits the Change record and checks whether the required implementation and risk details are available. If any required information is missing, the configured action is triggered to prevent the Change from proceeding without complete information. | #### Configure Business Rules for Change Management To configure a business rule, perform the following steps: 1. Login as an Administrator and select the **Admin** Workspace. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-qd44ifgr.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=J8Esc7mvBSMI2WNYo%2Fir9TTMij4vP%2F9%2FNR2KGov47Nw%3D) Figure: Workspace - Admin 1. Select Infrastructure from the left panel and then select **Business Rule**. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-qhnpf6rf.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=su19Abd3zhx47sTVxdXsxUv0Nv6NHzMaiWMn0N0if4c%3D) Figure: Infrastructure - Business Rule 1. The Business Rule page is displayed. Select the **Department** from the left panel. ![A close-up of a computer screen Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-x2d05v5s.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=q%2F%2BR1203zAX4QffVscPIGp7D%2Ft5grgXNyUBiknupegE%3D) Figure: Department 1. Select **Add New** from the right panel to create a new business rule. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/BR_CM_Addnew.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=VoUxXwCF4Pr%2Bi1ZKP%2FGVlh3fg1O2wVjtP47bMFpdaU8%3D) Figure: Business rule – Add New 1. Fill in the details for the **Rule Definition** section as shown in the following screen. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-fgybzb7l.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=Qvs6MkKsY6%2BHwOKlPI24EQMFD517TwkFjpf4lxVX7cc%3D) Figure**:** Rule Definition The below table describes the fields in the **Rule Definition** of the Business Rule Designer. | **Field** | **Description** | | --- | --- | | Department | Select one or more Tenants from the drop-down list. | | Business Rule Name | Enter the name to be given to the Business Rule. | | Business Rule Description | Enter a description about what the business rule will accomplish. | | Execution Order | Enter a numeric value representing the order in which the rule should be executed. Business Rules are executed based on their configured **Execution Order**. A higher execution order takes higher priority. For example, a rule with an execution order of **1000** runs before a rule with an execution order of **500**. If multiple Business Rules have the same execution order, the **most recently created rule** takes priority. The system allows multiple Business Rules to have the same execution order. | | Active | Enable the Active check box to make the Business Rule active. | 1. Select the **Change Management** from the **Module** dropdown. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-G8KSFW07.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=ER1iOpUPZl%2FD1UzzfRdGQGgFR46546ZLhZtMHPbI60Y%3D) Figure**:** Module Selection 1. Choose when to execute the Business Rule. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-sv8cuz5b.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=KzBVVhkmbLCKcl5XF5rqRvDX5IXok08GV8cBvFH509M%3D) Figure**:** Execution Mode Selection ****After and Async Business Rules**** **After Business Rule** Use an **After Business Rule** in Change Management when a field or related record must be updated **immediately after the change record is submitted**, and the results must be visible to the user right away. When a Change record is created or updated, the After rule executes after the data is saved to the database. During this time, the **Change record is temporarily frozen**, and no additional updates are allowed until the rule finishes processing. This mode suits actions that must occur *before the user continues working*, ensuring accuracy and consistency in the Change Records data. **Async Business Rule** The **Async Business Rule** runs **asynchronously in the background** and does *not* freeze the Change record. Users can continue working—adding work notes, updating Change details, and linking related records—while the background processing continues independently. This mode is ideal for **non‑urgent or backend operations** such as updating related tables, recalculating downstream fields, synchronizing CI data, linking multiple incidents to a CR, or sending notifications. Async rules minimize user wait time because the work happens behind the scenes. ****Example Use Cases**** **Scenario 1 — Automatically Escalating High-Risk Changes — After** **Context:** A Change Analyst submits a Change to modify a critical production server. During assessment, the Change meets the organization's criteria for a **High-Risk Change**. **Scenario:** An **After Business Rule** automatically updates the Change's risk classification and triggers the configured escalation when the defined high-risk conditions are met. **What Happens:** - The Change is submitted with the required risk-related information. - The After Business Rule evaluates the configured conditions. - The Change is classified according to the applicable risk criteria. - The configured escalation or routing action is triggered immediately. **Why After:** Because the risk classification needs to be established **as soon as the Change is submitted**, ensuring the Change follows the appropriate review path. **Scenario 2 — Closing Related Incidents After Successful Implementation — Async** **Context:** A Change is created to permanently resolve an issue affecting multiple users. Several Incidents are linked to the Change. **Scenario:** After the Change reaches **“Implemented”** or **“Closed,”** an **Async Business Rule** updates the linked Incidents according to the configured business logic. **What Happens:** - The Change reaches the configured status. - The Async Business Rule identifies the related Incidents. - The configured updates are applied to the related records. - The Change remains available while the related-record processing happens in the background. **Why Async:** Updating multiple related Incidents can be a time-consuming backend operation and does not need to prevent the Change user from continuing their work. 1. Select the trigger type from the dropdown. ![A close-up of a computer screen Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-ua3dkv22.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=Wzdk%2BnctXxqaG5nJBYvzcmUWJNPfYZ%2FZJ2qgkOCktXU%3D) Figure**:** Trigger Selection ****Trigger Types**** The following trigger types are supported for Change Management: - **Create:** Select this check box to execute the business rule when a record is created. - **Update:** Select this check box to execute the business rule when a record is updated. - **Schedule:** Select this check box to execute the business rule when a record is scheduled. > [!NOTE] > Note: > > If **Schedule** check box is selected, then **When** must be selected as **Async**. > > Calendar icon is displayed if the schedule job is configured for this business rule. **Scheduled Business Rules** Business Rules configured with the **Schedule trigger** execute automatically at defined intervals. This can be used for scenarios such as: - Sending notifications - Auto-updating Change Records - Monitoring records based on SLA or timelines Administrators can also define whether the rule should execute: - Anytime - Only during business hours - Only outside business hours > [!NOTE] > Note: > > Scheduled Business Rules are useful for automating **periodic Change lifecycle activities** such as review and closure. 1. Choose the conditions based on which the rule executes. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-b5k7g8x7.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=C0EXJpAhx%2FxyB50eI12fZG4T9NtGHZBeLMV7rL%2BW26g%3D) **Figure:** Condition #### Condition A condition is made up of a field, an operator, and a value. You can formulate complex conditions for rules that include several conditions by utilizing logical operators such as **AND** or **OR** operators. You can use the condition builder to determine when the Business Rule actions should be executed. When a request arrives, there are two options the user can select: - **Conditions based on criteria**: Select this radio button to specify the conditions based on which the action would be executed. - **No Condition**: Select this radio button if there are no conditions. ****Grouping of Conditions**** When there are multiple conditions which need to be computed together, these conditions can be grouped together in a Business Rule. This can be achieved by using the AND/OR conditions and by using the grouping functionality provided in the tool. Here is an example scenario which shows how we can use Grouping of Conditions to achieve the best results: Example: **Scenario:** Fredrick wants to automatically move eligible Change records to the appropriate next status when they meet specific implementation and risk criteria, ensuring that Changes follow the defined lifecycle without unnecessary manual intervention. **Solution** **Trigger** - Module: Change Management - Trigger Type: Schedule **Condition** 1. Status = Implemented 2. AND Priority = Low 3. AND Change Type = Normal 4. OR (Change Type = Emergency AND Risk = Medium) **Action** - Update field **Status = Closed** ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/grouping%20condition.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=zmkOtMUZcDmNELkqFUyiR9KimGpaSdHp2Gse%2FflmN4s%3D) **Figure:** Example of grouped condition **Fields** Based on the selected module, the fields related to the module are populated in the drop-down list from which you can select the required option. The supported Fields and Field types are as listed below: #### Actions An **Action** is performed automatically once the condition is met. You can define a Business Rule with **only action** and no condition or with both. Business Rule **Actions** are a configurable way to: - Update Fields - Notification - API **Update Fields** The Update Fields section allows you to update any of the supported fields. Once you select the Field from the dropdown, the Value field will appear based on the field selected. To Update a Field, perform the following steps: 1. Select the **Update Fields** option. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-8lbf4oux.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=dCopZlTppklvOMc6MBAwB%2FRlZFeo4xCje1BjFYrPU%2F0%3D) Figure: Update Fields 2. Under **Update Action Type**, select the update action mode. ![A close-up of a computer screen Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-oxkw748x.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=rKpQhsG4zk%2BJN73KIQLjOKe58%2FTmDquEFoztPO1yLJs%3D) Figure: Update Action Type > [!NOTE] > Note: > > **Update values first time:** If selected, the field will be updated only first time when the condition and trigger is met. > > **Update values every time:** If selected, the field will be updated every time the condition and trigger is met. 3. Click **Add** icon to add a condition field and select the **Field** value from the dropdown. ![A close-up of a computer screen Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-8qwic8yi.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=OotmfqTLg6MMrV2ozY9NZucNtulp0GZCxkFE3nIq%2Bug%3D) Figure: Update Action Type 4. Once you select the Field, the Value field will appear as shown. ![A close-up of a computer screen Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-c9nef5w5.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=L3bv%2FhoY5cc11qJGwC7jLXfCl%2Fy4R6hoSPnN4CydWXg%3D) Figure: Value Field 5. Select the appropriate Value from the dropdown. Note that the only valid status transitions are allowed for Update Action. Refer the [Status Transitions](/apex/docs/status-transition) for more information. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-h9j6zhlj.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=1jjDRnxchSzSF4XOHEih98xY1C3TCbBY89WGsZZR67Y%3D) Figure: Select Value Field 1. . Once done, click **Submit**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-wgyh773a.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=t5H3Gro7cntuei5KcesAOzjjZN%2FdgMwnIDQPMhhh5J0%3D) Figure: Submit #### **Status-Based Update Behavior** When updating the **Status field**, only valid status transitions are allowed. Supported Status Transitions are based on the status transition configuration done at Admin level. For more information, refer to Status Transition. #### Notifications Under this tab, you can configure the notifications for the business rule. **Business Rule**s can send notifications to recipients when defined conditions are met. **E- Mail Notification** Email notifications are a way to keep the recipients updated on the progress of your projects through emails. To create an Email Notification, perform the following steps: 1. Select **Notifications** and click **Add Notification**. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-cycmmf4b.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=8srNYc5Ch1c4E4q3N9l56wgxvSFpXyaiF5VaXg65EBk%3D) Figure: Add Notifications The **Notification** pop-up is displayed. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Notification_CM.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=3VlySKK57db9ZBs1U2wseYkjXpMq4aWIVBrdxzCMUPk%3D) Figure: Notification 1. Enter the **Notification Name** and select the notification medium i.e., **Email or SMS**. 1. Under the **Recipient** section, select the recipients. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/CR_Notification_List_Recep.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=%2BKuo6%2BcpXrPtuqG6xlqPV0wwGU5SBlYehvU%2Fq3DDYII%3D) Figure: Recipient Selection 2. Type in the **Email Subject** and **Email Body** as required. > [!NOTE] > Note: > > Use Dollar ('$') and type a character to trigger suggestions for Change Record Attributes. > > **Screenshot** > > ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/CR_Description_Attributes.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=8aeXDwo5v2%2BKY5Bd9KDtQWap9p7wFolWodvoquVjq6s%3D) > > Figure: Description - Change Record Attributes ****Recipients**** Understanding and using the recipient section appropriately helps in effectively notifying the stakeholders. The recipient is divided into two sections which are displayed based on the selected medium: **To** - The "To" field is used to specify the primary recipients of the notification. These are the individuals or groups that the sender expects to read and respond. Include the main recipients who are directly involved or expected to act. **Cc** - The "CC" field is used to include additional recipients who may be interested in the notification content. CC recipients are not the main addressees but are still receiving a copy for information. Inform others or keep them in the loop without making them the primary audience. You can add the type of recipient based on their groups. The types of recipients are explained in the following table: | **Group** | **Members** | **Description** | | --- | --- | --- | | By Caller Group | - Caller - Caller's cc book - Caller's Customer SPOC - Caller's Line Manager - Caller's Reporting Manager | - Caller - Select User who called to raise the ticket. - Caller’s cc book - Add the caller’s cc list. - Caller’s Customer SPOC – The point of contact for the caller. - Caller’s Line Manager - Line Manager of the user. - Caller’s Reporting Manager - Reporting manager of the user. | | By Analyst Group | - Analyst - Workgroup - Workgroup -Additional Owners - Workgroup Owner | - Analyst – Analyst who is working on the ticket. - Workgroup – The workgroup members who are part of the team. - Workgroup – Any additional owners/stakeholders who need to be informed. - Workgroup Owner – The owner of the Workgroup. | | By Designation | Search and select the required Designations. | By selecting this option, you can search a recipient by searching with the Designation of the required user. | | By Workgroup | Search and select the required Workgroups. | By selecting this option, you can search a recipient by the required Workgroup. | | By Customer | Search and select the required customer | By selecting this option, you can search a customer. | | Custom Email ID | Type in required e-mail id. | You can add the email id of the recipient manually using this option. | | By Custom Attribute | Search and select the required Attribute. | By selecting this option, you can search a recipient by the required custom attribute. | | By Approver | Search and select the required Approver Group. | By selecting this option, you can search a recipient by the required Approver Group. > [!NOTE] > Note: > > **Authorizer:** Workgroup Owner or By Tenant Configuration when enabled. > > **RCA Reviewer:** Based on the Reviewer configured. | #### **SMS Notification** To create an SMS notification, perform the following steps: 1. Under the **Notifications** tab, click **Add Notification.** The **Notification** pop-up is displayed. ![A screenshot of a computer Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-13sb05w7.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=8L7N8HSs66D6XsuPe44yx9nLUOKtWs7Z2S2fjkYzN3I%3D) Figure: Add Notifications 1. Select **Medium** as **SMS** to create SMS notification. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-bctqnhzx.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=6196Y%2BZVgpIYt5CqnSmCkuQ20cGqc6xLliJd1%2FQKcgw%3D) Figure: Medium – SMS 1. Fill in the required details. For more information, see Field Description. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Notification-SMS.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=%2BOltOz%2FYRgHO7pY%2BsNHucIIkSlBB2F89%2FDoDZTrXI8U%3D) Figure: SMS Configuration > [!NOTE] > Note: > > Use Dollar ('$') and type a character to trigger suggestions for Change Record Attributes in **Description**. 1. Click **Save**. A new SMS Notification is created and displayed under the Unlinked Notifications section. ![A screenshot of a search notification Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-bso908fv.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=Gol1jW%2F3vaL1mPVlGjdB7Y8PRrLQVkaiHoqcHASp0J0%3D) Figure: Unlinked Notification > [!NOTE] > Note: > > Click (Edit) icon to edit the template details as shown above. Click (Delete) icon to delete a template. ****Field Description**** The following table describes the fields on the **Notification** pop-up: | **Field** | **Description** | | --- | --- | | Notification Name | Type in the name for the SMS notification template. | | Medium | Select the medium as SMS to configure SMS notification. | | To | Add the main recipients of the email. \| **Group** \| **Members** \| \| --- \| --- \| \| By Caller Group \| - Caller - Caller's cc book - Caller's Customer SPOC - Caller's Line Manager - Caller's Reporting Manager \| \| By Analyst Group \| - Analyst - Incident Vendor SPOC - Incident Workgroup - Incident Workgroup -Additional Owners - Incident Workgroup Owner \| \| By Designation \| Search and select the required Designations \| \| By Workgroup \| Search and select the required Workgroups \| \| By User Type \| Search and select the required User Types \| \| Custom Number \| Enter a valid number \| \| By Approver Group \| Search and select the required Approver Group \| | | **Group** | **Members** | | By Caller Group | - Caller - Caller's cc book - Caller's Customer SPOC - Caller's Line Manager - Caller's Reporting Manager | | By Analyst Group | - Analyst - Incident Vendor SPOC - Incident Workgroup - Incident Workgroup -Additional Owners - Incident Workgroup Owner | | By Designation | Search and select the required Designations | | By Workgroup | Search and select the required Workgroups | | By User Type | Search and select the required User Types | | Custom Number | Enter a valid number | | By Approver Group | Search and select the required Approver Group | | Message Expiry Time (Mins.) | Specify the message expiry time in minutes | | Description | Type in the detailed description. | #### API Action API stands for application programming interface. It is a set of protocols and tools that allow the Apex Platform to interact with other third-party applications. This can include anything from retrieving or transferring data to third-party applications, managing or controlling software. To add API, perform the following steps: 1. Under the **API** tab, click **ADD API.** The **API** pop-up is displayed. ![A white rectangular object with black dots Description automatically generated](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-2pfhmlkn.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=9giwmdXGktvTZ7uqgR%2BTwo7w77UK5626mWxxsFXB6D8%3D)Figure: API 1. Fill in the required details. For more information, see **Field Description**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/br-pm-apex-aspen-spring-26-documentation-v1-image-z6aw1dc3.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=T3BQe%2FdZ8o7iNmCHnFoviypiJsDv9516t2jpN9%2BEonc%3D) Figure: API Configuration 1. Click **SAVE**. A new API is created and displayed under the **Unlinked Notifications** section. ****Field Description**** The following table describes the fields on the **API** pop-up: | Field | Description | | --- | --- | | API Configuration Name | Type in the Name for the API Configuration. | | Method | Select the required Method from the drop-down list. The available methods are: - GET - for new request - POST - add new data - PUT - replace existing data | | API Timeout (In seconds) | Specify the Timeout in seconds | | API URL | Specify the API URL | | Params | You can send path and query parameters with your requests using the **Params** tab. To send a path and query parameter, 1. Click the **Params** tab. 2. Click + icon to add a new row. 3. Enter the **Key**, **Value,** and **Description**. 4. Slide the toggle button to right- hand side to make this path/query parameter active. | | Authentication | Authentication involves verifying the identity of the client sending a request, and authorization involves verifying that the client has permission to carry out the endpoint operation. Open the **Authorization** tab to configure your access details. Select the required Authentication type from the drop-down list. The available types are: - API Key - Bearer Token - Basic - OAuth 2.0 | | Headers | Some APIs require you to send headers along with requests, typically to provide additional metadata about the operation you are performing. You can set these up in the **Headers** tab. Enter any key-value pairs you need and will send them along with your request. | | Body | The **Body** tab allows you to specify the data you need to send with a request. | | Response | Under this tab, you can view the API response. | **Linked to this Business Rule** Under this section, you can view the list of APIs linked to this Business Rule. Also, you can edit and delete the APIs available under this section. **Linked to other Business Rule** Under this section, you can view the list of APIs linked to other Business Rules. Also, you can edit and delete the APIs available under this section. **Unlinked APIs** Under this section, you can view the list of unlinked notifications. These notifications are created but not linked with any business rule. #### Business Rule Execution Behavior **Execution Order** Business Rules are executed **before workflows**. **Loop Prevention** - Business Rules do not re-trigger within the same session due to workflow updates. - They may trigger again in a new execution cycle if conditions are met. > [!NOTE] > Note: > > This prevents recursive execution between Business Rules and workflows. **Change History** Click **Change History** on the right-side action panel. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/BR_Change_History.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=ovhfyBaikYmS1WcjgWrsKCQ5julpSi7L0qLTgvUgh78%3D) Updates made through the **Update Fields** action gets recorded in the Change Record's **Change History**, consistent with manually made updates (for example, “Status changed from New to In Progress” ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/BR_Change_History_List.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A39%3A59Z&se=2026-11-20T22%3A39%3A59Z&sr=b&sp=r&sig=gnvQ2nn6bJJu%2FugCSOSk%2FVbOiZ4Y3tpW09buc332m7o%3D) Figure: Change History Details