Details
-
Epic
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
Connected On-prem server [Full Launch Finalization]
Description
This epic collects actions on completing and hardening Connected On-Prem server key functionalities. After this epic is completed Connected On-Prem server is feature complete and ready for production.
RnD Work:
Rest API for Downloading Statistics
- As a Customer Organisation License Manager, I want the on-prem license server to provide a REST API for downloading usage statistics, so I can monitor and analyze license consumption efficiently.
- Acceptance Criteria:
- REST API is available for authorized users.
- Endpoint provides data in a structured format (e.g., JSON).
- Data includes details like active licenses, usage times, products used.
Error Reporting from On-Prem to Cloud
- As a Qt Company IT Operator, I want the license server to report critical errors to the cloud in real-time, so I can be notified and troubleshoot issues effectively.
- Acceptance Criteria:
- Error logs are automatically sent to a secure cloud endpoint.
- The report includes error details, timestamps, and relevant system data.
- An option exists to disable or customize the frequency of error reporting for privacy or compliance reasons.
End-to-End Testing Suite for Product Readiness
- As a QA engineer, I need to develop an end-to-end automated testing suite for the on-prem server, so that we can ensure all new features function as expected and are reliable for release.
- Acceptance Criteria:
- Tests cover REST API functionality, server parameter changes, error reporting, and server-client connectivity.
- Tests include edge cases and stress testing scenarios.
- A test report is generated after each run with detailed results.
Server optimization
- Especially for Squish license processing, the server needs to be able to handle high request load and high number of concurrent reservation/extend request.
- Acceptance Criteria:
- Reservation process, database usage and architecture refactored to meet performance requirements for squish
Server Node locking
- As a Customer Organisation License Manager I want to have full self service for offline entitlement.json management so that node locking can be done in Qt Customer Portal by the authorized users.
- Acceptance Criteria:
- UI in QCP which allows submitting hardware finger print information
- Entitlement.json can be regenerated once per 6 months by default
PM Work:
Security and Compliance Verification
- As a product manager, I want to verify that the on-prem server enhancements meet security and compliance standards, so that our customers can deploy it without legal or data protection concerns.
- Acceptance Criteria:
- Security audit is completed, and results are documented.
- Compliance checks for relevant standards (e.g., GDPR, ISO/IEC) are performed.
- Any vulnerabilities or compliance issues analysed and put to roadmap.
Development of Sales Material
- As a Sales person, I want to have comprehensive sales materials for the Qt License Server, so that the sales team can effectively promote and explain the benefits of the solution to potential customers.
- Acceptance Criteria:
- Sales material includes a product brochure, feature highlight sheets, and a slide deck for presentations.
- Visuals, such as infographics are created to illustrate the new functionalities.
- Materials are reviewed by the sales team.