Business Rules for Knowledge Management extend the existing Business Rule Designer to the Knowledge module. A Knowledge Management (KM) administrator can create rules that respond to Knowledge Article (KA) events and automatically send an email notification or invoke an API.
This enhancement keeps the same Business Rule experience as other modules, but only shows the fields, operators, recipients, keywords, and actions that apply to Knowledge Management.
Key benefits
Automates Knowledge Article events without requiring manual monitoring.
Provides a consistent rule-building experience across Knowledge Management and other supported modules.
Supports event-based and scheduled automation.
Enables targeted email notifications using Knowledge-specific recipients and attributes.
Supports integrations with external or internal systems through API actions.
Prevents irrelevant module fields and actions from appearing in Knowledge rules.

Use Case User Persona: Admin | Solution |
|---|---|
NovaTech Technologies manages Knowledge Articles for employees across many departments. Authors submit articles for review, but administrators need a consistent way to alert the right reviewers so articles are not delayed in the review process. | NovaTech configures a Knowledge business rule to notify the appropriate reviewer when an author submits an article. How NovaTech uses the Knowledge business rule?
|
Configure a Knowledge business rule
Knowledge business rules help automate article actions without manual follow-up. They can run on create, update, or scheduled events.
To configure a business rule for Knowledge Management, perform the following steps:
Login as an Administrator and select the Admin Workspace.

Figure: Workspace - Admin
Select Infrastructure from the left panel and then select Business Rule.

Figure: Infrastructure - Business Rule
The Business Rule page is displayed. Select the Department from the left panel.

Figure: Department
Select Add New from the right panel to create a new business rule.

Figure: Business rule – Add New
In Rule Definition, enter the business rule name, description, execution order, and active state as required. For more information, refer to Field Description.
Figure: Business Rule for KMField
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.
Select the Knowledge Management from the Module dropdown.
Figure: Module SelectionChoose when to execute the Business Rule.
Figure: Execution Mode Selection
After and Async Business Rules
After Business Rule
Use an After Business Rule in Knowledge Management when a field or related record must be updated immediately after the knowledge record is submitted, and the results must be visible to the user right away.
When a knowledge record is created or updated, the After rule executes after the data is saved to the database. During this time, the knowledge record is temporarily frozen, and no additional updates are allowed until the rule finishes processing.
Async Business Rule
The Async Business Rule runs asynchronously in the background and does not freeze the knowledge record. Users can continue working while the background processing continues independently.
This mode is ideal for non‑urgent or backend operations. Async rules minimize user wait time because the work happens behind the scenes.
Select the trigger type from the dropdown.
Figure: Trigger Selection
Trigger Types
The following trigger types are supported for Knowledge 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:
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:
Scheduled Business Rules are useful for automating periodic Knowledge Article activities, such as identifying articles approaching expiry and notifying Knowledge Owners and Workgroup Owners for timely review.
Choose the conditions based on which the rule executes.
Figure: ConditionConfigure the condition, or select No Condition. For more information, refer to Conditions.
Configure at least one Notification or API action. For more information, refer Notification and API.
Review the configuration and submit the rule.
Conditions
A condition determines which Knowledge Articles cause the configured actions to run. Each condition consists of:
Field
Operator
Value
After you select Knowledge as the module, the Condition Builder displays only Knowledge Article attributes. Criteria can use existing Business Rule condition logic, including AND and OR where supported.
Administrators can select one of the following options:
Conditions based on criteria: Run the action only when the configured criteria are true.
No Condition: Run the action whenever the selected trigger occurs, regardless of Knowledge Article attributes.
Condition behavior
Selection | System behavior |
|---|---|
Field | Displays the supported Knowledge Article attributes. |
Operator | Displays only operators supported by the selected field’s data type. |
Value | Displays an appropriate input, selection, or lookup based on the field and operator. |
No Condition | The rule does not check attribute criteria. |
For example, selecting a checkbox field provides Boolean-compatible operators and values, while selecting a date field provides date-compatible operators and a date value control. Operators that do not require a value must not display or require a value entry.
For more information, refer Business Rule Conditions
Supported standard attributes
Field name | Field key | Type | Data type | Source or behavior |
|---|---|---|---|---|
KR ID | KR_ID | Number | Integer | System-generated Knowledge Record identifier. |
Title | KR_TITLE | Text | String | Knowledge question or title. |
Status | KR_STATUS | Dropdown | String | Supports New, Submitted, Authorized, Not-Authorized, Approved, Rejected, Published, Retired, and Draft. |
Life Cycle Status | KR_LIFECYCLE_STATUS | Dropdown | String | Read-only lifecycle stage. |
Workgroup | KR_WORKGROUP | Dropdown | Integer | Knowledge Article workgroup. |
Classification | KR_CLASSIFICATION | Tree view | Integer | Classification on the General tab. |
Category | KR_CATEGORY | Tree view | Integer | Category on the General tab. Supports is and is under for child categories. |
Important Record | KR_IMPORTANT | Checkbox | Boolean | Important Record setting on the Access tab. |
Restricted to Analysts | KR_RESTRICTED_ANALYST | Checkbox | Boolean | Restricts the article to analysts. |
Self-Help Article | KR_SELF_HELP | Checkbox | Boolean | Indicates whether the record is a self-help article. |
Public Article | KR_PUBLIC | Checkbox | Boolean | Indicates whether the article is public. |
Has Attachment | KR_HAS_ATTACHMENT | Checkbox | Boolean | Indicates whether the article contains an attachment. |
Supported date attributes
Field name | Field key | Type | Data type | Notes |
|---|---|---|---|---|
Expiry Date | KR_EXPIRY_DATE | Date | Date | Supported for the expiry-date model only. Review-cycle behavior is not included. |
Actions
After the trigger occurs and the configured condition evaluates to true, the system performs the action. If you select No Condition, the system performs the action whenever the trigger occurs.
Knowledge business rules support the following action tabs:
Notification
API
The Update Fields action is not available for Knowledge business rules.
Notification action
Use the Notification action to send an email when a Knowledge business rule trigger occurs and its condition evaluates to true.

Figure: Notification
Notification configuration
Field or section | Behavior |
|---|---|
Notification Name | Enter a name that identifies the notification configuration. |
Medium | Email only. SMS is not supported for Knowledge business rules. |
To | Add one or more supported primary recipients. |
Cc | Supports the same recipient types available in the To field. |
Subject | Enter the email subject. The Knowledge Article ID can be pre-populated in line with the existing Business Rule behavior. |
Email Body | Enter the notification message. You can use HTML content. |
Supported recipients
The To and Cc fields support the following recipient types:
Recipient type | Supported selections |
|---|---|
By Workgroup | Select a specific workgroup or the owner workgroup of the Knowledge Article. |
By Customer | Search for and select a customer. |
Custom Email IDs | Enter one or more email addresses manually. |
For more information, refer Business Rule Notification.
API action
Use the API action to invoke an internal or third-party endpoint when a Knowledge business rule triggers and its condition evaluates to true. For example, an organization can call an external service after a user creates or updates a Knowledge article.
API configuration
Field or section | Description |
|---|---|
API Configuration Name | Enter a name that identifies the API configuration. |
Method | Select a supported HTTP method. The system supports PUT. GET remains subject to RBAC validation and final confirmation. |
API URL | Enter the endpoint URL to invoke. |
Params | Configure path or query parameters as key-value pairs. |
Authentication | Configure the authentication required by the endpoint. |
Headers | Add request headers and associated values. |
Body | Configure the request payload where applicable. |
Response | View the response returned by the endpoint. |
For more information, refer Business Rules API
Example use-cases
Notify the Knowledge owner before article expiry
A KM Administrator creates a scheduled rule to identify published articles that are approaching their expiry date.
Module: Knowledge
Trigger: Schedule
Condition: KR_STATUS equals Published AND KR_DAYS_TO_EXPIRY is less than or equal to the configured threshold
Action: Send an email to the KR Owner and Workgroup Owner
This rule helps Knowledge teams review articles before they expire and reduces the risk of outdated content remaining available.
Notify an approver when someone submits an article
A KM Administrator creates a rule that runs whenever someone submits a Knowledge Article for approval.
Module: Knowledge
Trigger: Update
Condition: KR_STATUS is Submitted
Action: Send an email to the KR Approver
The notification can include the Knowledge Article ID, title, department, workgroup, and other supported Knowledge keywords.
Invoke an integration for a newly published article
A KM Administrator creates a rule that calls an integration endpoint after someone publishes an article.
Module: Knowledge
Trigger: Update
Condition: KR_STATUS equals Published
Action: Invoke a configured API and pass Knowledge Article details in the request
Use this rule to synchronize published Knowledge content with another authorized application.
Send an email for every Knowledge Article update
A KM Administrator creates a rule that notifies a configured recipient whenever someone updates a Knowledge Article, without evaluating a condition.
Module: Knowledge
Trigger: Update
Condition: No Condition
Action: Send an email notification to the configured recipient. Add the Knowledge Article ID to the subject and include relevant attributes, such as status, lifecycle status, customer, log time, importance, and expiry date, in the email body.
Because the rule has no condition, it sends a notification for every Knowledge Article update that triggers it.