qKnow Professional Edition v3.1.3 focuses on optimizing task status awareness, file previewing, and homepage notification configurations within the knowledge governance process.
Key updates include adding message notifications for structured and unstructured extraction tasks, introducing kkFileView deployment configurations for file previews, and enabling homepage notification visibility control via parameter management.
These updates aim to further reduce repetitive operations during task execution and platform configuration.
From "Task Submission" to Real-Time Status Awareness
In the construction of enterprise knowledge bases and knowledge graphs, file uploading is just the beginning. Once the knowledge governance workflow begins, a piece of knowledge material typically undergoes the following process:
File Preparation → Structured/Unstructured Extraction → Task Execution → Status Check → Exception Handling → Utilization of Extraction Results
Knowledge extraction itself often requires a certain amount of execution time. If users have to constantly return to the task page and manually refresh to check progress after submitting a task, several practical issues arise:
- Where is the task currently executing?
- Is it complete?
- Has an exception occurred?
- If processing multiple tasks simultaneously, has a task finished without being noticed?
Beyond task status, internal enterprise deployment environments also impact daily usage. For instance, file preview functions may face different access conditions in public versus private networks. Additionally, if page notifications can only be controlled by modifying front-end configuration files, it increases daily maintenance costs.
Therefore, the focus of qKnow Professional Edition v3.1.3 is not simply adding more pages, but continuing to refine the connection between these high-frequency operations:
Task Execution → Status Feedback → File Viewing → Platform Configuration
01. New Message Notifications for Extraction Tasks
Knowledge extraction is a critical part of the qKnow governance workflow. Whether it is structured data extraction or unstructured document extraction, tasks require actual execution time after submission.
Previously, after submitting these tasks, users had to manually refresh the page to check progress. This meant the workflow was often:
Submit Task → Wait → Refresh Page → Check Status → Wait Again → Refresh Again
When the number of extraction tasks is high, this method can easily lead to missed tasks or delayed processing.
System Notifications in the Top Right Corner
qKnow Professional Edition v3.1.3 introduces message notification data for both structured and unstructured extraction processes. Once a task is executed, the system continuously updates task progress information in the top right corner.
Unlike the past, where users had to enter the task page to check status, users can now perceive the execution status of extraction tasks while using other platform features. This shifts the task viewing method from:
Users actively seeking status
to:
The system actively providing status feedback based on task changes.
Covering Execution, Completion, and Exception States
Notifications do not only appear when a task ends. According to the release notes, the system automatically pushes messages for the following states:
- Task Executing
- Task Completed
- Task Exception
This allows users to more timely distinguish whether a task is still running, or if it has finished normally or encountered an exception requiring further handling. This feedback is particularly important for enterprise users who need to submit multiple knowledge extraction tasks at once.
From "Watching Tasks" to "Waiting for Status Changes"
From an operational logic perspective, the update can be understood as:
- Past: Submit task → Enter task page → Manual refresh → Check status → Refresh again → Wait for completion.
- Now: Submit task → Use other platform features → System message updates task status → Decide next steps based on completion or exception messages.
This adjustment does not change the execution logic of the extraction tasks themselves but reduces the need for users to repeatedly refresh pages to confirm status.
Value for Batch Knowledge Processing
Enterprise knowledge governance often involves processing more than one task at a time. For example, during centralized knowledge base construction, there might be:
- Multiple unstructured document extraction tasks.
- Multiple batches of structured data extraction.
- Content processing occurring simultaneously in different knowledge bases.
As the number of tasks increases, relying solely on users to actively check can lead to missed completions or unnoticed exceptions until the data is actually used. Unified message notifications help shorten the time gap between a task status change and user awareness.
Note: While message notifications improve status awareness, they do not replace task exception diagnosis. If a task fails, specific causes must still be located using task details, logs, and actual file or data content.
02. New kkFileView Configuration for File Preview
In a knowledge platform, file management usually involves more than just uploading and parsing. Users often need to view file content directly. During knowledge governance, it is frequently necessary to confirm:
- If the uploaded file is correct.
- If the file content is complete.
- Which material is currently being processed.
- If the file content matches the knowledge base classification.
Therefore, although file preview is a basic function, it directly impacts the efficiency of knowledge material management.
Limitations of Original Preview Addresses
Previously, qKnow file preview used the address provided by the platform. However, in actual deployment, network environments vary significantly across enterprises. For example, some clients use:
- Enterprise intranet deployment.
- Isolated network deployment.
- Custom network access environments.
In these scenarios, the original preview address might fail to display files correctly due to different network access conditions. The core issue is not that the file itself cannot be read, but that the file preview capability needs to match the enterprise's actual deployment environment.
System Deployment Configuration Adds kkFileView
To address this, qKnow Professional Edition v3.1.3 adds kkFileView configuration to the system deployment settings and synchronizes the file preview address. Users can complete the configuration for file preview capabilities by enabling the corresponding configuration when deploying the platform.
From a deployment logic perspective, this can be understood as:
Deploy qKnow → Configure and Start kkFileView → Platform Uses Corresponding Preview Service → View Knowledge Files
This provides a clearer configuration entry for file preview methods to align with the actual deployment environment.
Adapting to Intranet Deployment Scenarios
For enterprise clients, the actual environment is often not a uniform public network deployment. Especially in sectors like government, manufacturing, water conservancy, and energy, platforms are frequently deployed on enterprise servers or internal networks. Therefore, whether the preview service can be configured alongside the deployment environment directly affects the usability of knowledge file management.
The value of this update lies in incorporating the previously relatively fixed file preview method into the platform's deployment configuration system.
Note: Adding the kkFileView configuration does not mean all preview issues will automatically disappear. Actual deployment still requires ensuring the corresponding service starts correctly and meets basic conditions for servers, network access, and permissions.
03. Homepage Notifications Moved to Parameter Management
In addition to knowledge extraction and file preview, this version also adjusts the control method for homepage notifications.
Previously, the display logic for homepage notifications was configured in the system's front-end configuration file. If an enterprise wished to hide homepage notifications, they had to:
Locate Front-end Config File → Modify Configuration → Restart Project
The issue with this approach is that a page display requirement, which is essentially a simple switch, required entering the technical configuration layer. This is inconvenient for general platform administrators.
Homepage Notification Switch Enters Parameter Management
qKnow Professional Edition v3.1.3 migrates homepage notification-related parameters to Parameter Management. Users can now directly control the homepage notification via parameter data:
- Show
- Hide
There is no longer a need to modify the front-end configuration file and restart the project every time.
From Code Configuration to Platform Parameter Configuration
- Before: Modify front-end config file → Save config → Restart project → View page changes.
- After: Enter Parameter Management → Adjust corresponding parameter → Control homepage notification visibility.
This effectively transforms an action偏向 "system development
configuration" into "platform runtime parameter management," reducing the maintenance cost for simple display adjustments.
While this change does not involve knowledge extraction algorithms or core knowledge base capabilities, it reduces frequent but unnecessary technical maintenance operations for long-running platforms.
04. What Problem Do These Three Optimizations Solve?
Viewing these three features together, they address different points in the usage of the knowledge platform:
Extraction Task Message Notifications solve the issue of not knowing where a submitted task is executing. It shifts task status from "requires active refresh to view" to "system actively reminds."
kkFileView Preview Configuration solves the issue of files being in the platform but unable to be previewed in certain enterprise deployment environments. By adding a deployable preview service configuration, file viewing becomes more adaptable to the enterprise's actual operating environment.
Homepage Notification Parameter Management solves the issue of a simple page notification switch requiring code configuration changes and project restarts. Through parameter management, this technical configuration operation is further transformed into platform configuration.
Therefore, while these three adjustments belong to tasks, files, and system parameters respectively, they point in the same direction: reducing the need for extra manual operations, repeated confirmations, and technical intervention in the knowledge governance process.
Conclusion
Once knowledge governance capabilities enter the stage of continuous use, users care about:
- Where is the task execution?
- Can I know immediately if an exception occurs?
- Can files be previewed normally in our specific deployment environment?
- Do page display requirements require finding a technician to modify configuration every time?
qKnow Professional Edition v3.1.3 makes adjustments primarily around these questions:
- On the knowledge extraction side: Structured and unstructured extraction tasks add message notifications, allowing the system to automatically update task information based on executing, completed, or exception states.
- On the file management side: System deployment configuration adds kkFileView and adjusts the file preview address, making file preview capabilities further adaptable to different enterprise deployment environments.
- On the platform configuration side: Homepage notification control is migrated from front-end configuration files to parameter management, allowing users to directly control visibility via parameters, reducing maintenance costs associated with modifying configuration files and restarting projects.
These adjustments do not change the core business logic of enterprise knowledge governance, nor do they replace task log analysis, network environment configuration, or system operation and maintenance management. However, for an enterprise agent platform that needs to run for the long term, what truly affects the user experience is often not just whether core functions exist, but also:
- Whether tasks can provide timely feedback.
- Whether files can be viewed normally.
- Whether configurations can be adjusted conveniently.
The qKnow Professional Edition v3.1.3 upgrade continues to supplement these basic but high-frequency links, making the usage chain from extraction and viewing to daily management of enterprise knowledge smoother.
Top comments (0)