BMC Helix Knowledge Management by ComAround architecture
The following diagram gives an overview of the BMC Helix Knowledge Management by ComAround architecture:
The components in a typical BMC Helix Knowledge Management by ComAround system are described below:
BMC Helix Knowledge Management by ComAround web platforms
The following web platforms are used by knowledge workers and end users:
Component | Description |
---|---|
ComAround Self-Service | Web platform for consumption of knowledge for the end users. The platform is designed to make knowledge articles easy to find and easy to read. |
ComAround Knowledge | Web platform for knowledge workers that includes all the capabilities of BMC Helix Knowledge Management by ComAround. This platform is used to create, maintain, and share knowledge as well as configure the administration settings for your company. |
ComAround Knowledge vNext | Web platform for knowledge workers that includes the decision tree capability. This platform is used to create, maintain, and share knowledge. |
Microsoft Azure Services
The following key Microsoft Azure services are used for cognitive search, data storage, and reporting insights:
Component | Description |
---|---|
Azure Application Service | Hosts web applications and backend functions. |
Azure Storage Service | Stores files in a geo-redundant storage account (GRS), and data is replicated to a secondary region to ensure durability and high availability. This service includes the following products:
|
Azure Cognitive Search | Powers the AI search capabilities in BMC Helix Knowledge Management by ComAround. |
Power BI | Provides data and insights in BMC Helix Knowledge Management by ComAround. |
Azure Analysis Services | Extracts data from BMC Helix Knowledge Management by ComAround as an insight connector. |
Azure API Management | Handles all API calls and creates API subsets. |
Third-party dependencies
The following third-party applications are used to enhance the knowledge workers' experience:
Component | Description |
---|---|
Froala Content Editor | Enables knowledge workers to create and edit knowledge articles in BMC Helix Knowledge Management by ComAround. |
Google Translation Service (Optional) | Translates knowledge articles in BMC Helix Knowledge Management by ComAround. |
Sendgrid (Optional) | Handles email communication in BMC Helix Knowledge Management by ComAround. |
Sizing considerations
When knowledge workers create content in BMC Helix Knowledge Management by ComAround, they must consider the following types of content size limitations:
- Article size limitations—These limitations apply to the article size and character count.
- Field-specific limitations—These limitations apply to individual fields in articles, folders, and links.
Article size limitations
When knowledge workers create articles, they must consider limitations related to article size and character count. These limitations affect the ability to save articles, use machine translation, and access version history.
Category | Limit (per single language version) | Impact if exceeded | Details |
---|---|---|---|
Article size | 1 MB | The article can't be saved. | The size of an article is calculated based on its text and formatting. Images and attachments are excluded from this calculation because they are stored separately. The actual size depends on character type and formatting, not the character count. For example, Chinese characters might consume more bytes than English characters. As a result, fewer Chinese characters can fit within the 1 MB limit. |
A single image or attachment must not exceed 350 MB. | |||
The combined size of all translations can exceed 1 MB, but each language version must remain within the 1 MB limit. For example, if an article is available in English, Swedish, and German, its total size can exceed 1 MB. | |||
Machine translation | 30,000 English characters | Machine translation is unavailable. | The limit applies to the total number of characters across all fields in an article. If exceeded, machine translation is unavailable, but manual translation remains possible. |
Version history | 31,940 English characters | The article can be saved, but it doesn't appear in the article history. | The limit applies to the total number of characters across all fields in an article. If exceeded, the article can be saved, but it is not included in the article history. As a result, version management is unavailable for this article version, and it can't be restored or refactored later on. |
Field-specific limitations
The following table lists character limits for specific fields in articles, folders, and links. If any of these limits are exceeded, the item cannot be saved. This rule applies even when other content size limits are within acceptable ranges. For example, if an article title is longer than 2,000 characters, the article cannot be saved. This restriction applies even when the total size of the article is within acceptable limits.
Item | Field | Limit (English characters) |
---|---|---|
Articles | Title | 2,000 |
Author Email | 2,000 | |
Author | 2,000 | |
External links | 128 | |
Folders | Title | 2,000 |
Author Email | 2,000 | |
Description | 2,000 | |
Author | 2,000 | |
External links | 128 | |
Links | Title | 2,000 |
Author Email | 2,000 | |
URL | 2,000 | |
Author | 2,000 | |
External links | 128 |