Version 2.0
TSM Version 2.0 Documentation
Type | Area | Description |
---|---|---|
Feature | TSM Forms | Form Designer Extension: Expanded form configuration for additional modules: Inventory, Catalog, Registry. Important: Reconfiguration of affected forms is required as part of the upgrade. |
Feature | Omnisearch | Filter Button: A new "Filter" button in the toolbar enables full-text search across all modules in the application. Users can select a specific module and apply filters within it. The default sorting is by last visited record, with the ability to see history and wait time for the next filter submission. |
Feature | Selfcare Portal | Standardized Selfcare Portal: Standardized selfcare portal for use in the retail segment. |
Feature | TSM Expression Language | Extended language support with control flow constructs (if/switch/cycle). Includes expanded autocomplete and integrated documentation. |
UX | In-place Edit | For fields with editing options (pencil icons), users can now confirm changes more easily. For example, when changing a value in a list, users can open the selection, make changes, and confirm, all without needing to open the entire form. |
Feature | Notifications | Standard notifications in TSM Core can be configured by users (e.g., new tasks, comments, worklog updates). Simplified configuration will be available for predefined events, and notification settings will be streamlined. |
Feature | Application Sorting | Drag-and-drop sorting for records in the application (e.g., tickets, user numbers, catalog items). Sorting is saved in the database using LexoRank algorithms. |
Feature | Color Settings | Colors can now be set via the configuration interface, no longer requiring complex scripting. The user interface has been updated to allow easier color selection. Important: Color evaluation has been moved to TQL (backend), and validation of existing settings is required. |
Feature | Map | Standardization of map components in TSM. Users can select map layers to display regions, services, outages, etc., with data visualized by type. |
Feature | Dictionaries | Extended configuration options for user dictionaries, including placement in the menu, quick form insertion, and extended search options. |
Feature | Excel Import | Support for importing data using spreadsheet components. Users can import records and populate form fields directly via spreadsheets. |
Feature | Backup/Restore | Configuration Import/Export: Export and import TSM configurations, compare differences, and synchronize between production and non-production environments. Backup sets can be defined for managing configuration transfers. |
Feature | Process Engine | Simplified process display for "plans" (future processes). Processes will be displayed visually based on task definitions and current data. |
Feature | Reporting | Added support for filtering aggregated results (e.g., displaying average order processing times greater than two days). The query language has been extended with clauses similar to SQL’s "group by" and "having". |
Testing | Automated Testing | Automated tests are now treated as a specific ticket type. Test requests can be managed via TSM Process Engine and utilize a combination of REST/SOAP calls and UI testing with Cypress. Test processes have been enhanced to simplify writing and evaluating tests. |
Cleanup | Public API | Cleanup of unused objects in the Public API. Important: As part of the upgrade, it will be necessary to validate and review existing API usages. |
Infra | TSM Management Service | System monitoring during runtime, with dynamic scaling based on load. |
Infra | Virtual Threads | Virtual Threads in Java improve performance by handling IO-bound operations without the need for system resource allocation, enabling faster and more scalable microservices. |
Infra | UI Optimization | Optimized bundles and lazy loading of components. The frontend has been broken down into independent microfrontend components to improve loading time and reduce the initial page load time significantly. |
Infra | Archiving and Purging | Lifecycle management of all entities in TSM. Lifecycle stages include LIVE, HOT, and ARCHIVED, with support for partitioning to optimize performance and purging of old records. |
Infra | Technical Dependency Upgrade | Upgraded libraries: Java 21, Kotlin 1.9, Spring Cloud 2022.0.4, ElasticSearch 8.7, Kafka 3.0, Postgres 14-16, Angular v16, PrimeNG v16, Camunda 7.2. |
Performance | Notification Storage Change | Notifications are now stored primarily in ElasticSearch, with a lifecycle management policy for short-term database storage. Retention periods for notifications in the DB can be configured or eliminated to save space. |