SOT
    • Introduction
    • User manual
      • General Descriptions
        • Fine-grained access control
        • Ticket Management Groups
      • Ticket Management
        • Filter options
        • Ticket details
        • Ticket archiving
        • Ticket anonymization
        • Notifications
        • Ticket escalation mapping
      • Maintenance status widget
    • Operations manual
      • Overview
      • System Architecture and Interfaces
      • System Requirements
        • tm/ticket-service
      • Migration from Previous Versions
        • Migration to 7.3.0+
        • Migration to 7.4.0+
        • Migration to 7.4.1+
        • Migration to 7.8.0+
        • Migration to 7.9.0+
        • Migration to 7.10.0+
        • Migration to 7.11.0+
        • Migration to 7.12.0+
        • Migration to 7.13.0+
        • Migration to 7.13.1+
        • Migration to 7.14.0+
        • Migration to 7.16.0+
        • Migration to 7.17.0+
        • Migration to 7.20.0+
      • Setup and Configuration
        • Setup
          • Installation guide
        • Recommendations
        • Helm Configuration
        • Ticket Management global variables
        • tm/ticket-service
        • Ticket Management IAS dependencies
      • Start and Shutdown
      • Regular Operations
      • Failure Handling
      • Backup and Restore
      • Logging and Monitoring
        • Module Health Verification Endpoints and K8S Probes
      • Known Limitations
        • Maximum 2100 parameter support of MSSQL can lead to query failure
        • Users from different tenants can have issues when calling MACMA/MDM concurrently
        • Lost messages of Notification service if maximum retry is exceeded
    • Developer documentation
      • Getting Started
      • How-Tos
        • Domain Context Registration
        • Integrating Ticket Management Views
      • Failure Handling
        • Embedded View Blocked by Content Security Policy (CSP)
    • API documentation
      • HTTP API
    • Glossary
Ticket Management
  • Smart Operations Toolkit
    • Deviation Processor
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Process Quality
    • AI Services
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
  • Enterprise & Shopfloor Integration
    • Information Router
    • Master Data Management

SOT Learning Portal

  • Ticket Management
  • Operations manual
  • Migration from Previous Versions
  • Migration to 7.13.1+
7.22.2 7.22.0

Migration to 7.13.1+

Changes

  • Static resource for All Facilities is created with resource id urn:com:bosch:bci:tm:ts:All-Facilities and resource type urn:com:bosch:bci:tm:ticket-service:static:facilities

BREAKING API CHANGES

There are breaking API changes due to security reasons. The following endpoints are now protected and require the according privilege to call them:

  • The user requires the privilege read on the resource All Facilities (id: urn:com:bosch:bci:tm:ts:All-Facilities, type: urn:com:bosch:bci:tm:ticket-service:static:facilities) which is included in the role Ticket Management User, Ticket Management Expert, and Ticket Management Admin to call the following endpoint:

    • GET /BCI_TS/v1/{tenantId}/facilities

  • The user requires the privilege add on the resource All Tickets (id: urn:com:bosch:bci:tm:ts:All-Ticket, type: urn:com:bosch:bci:tm:ticket-service:static:tickets) which is included in the role Ticket Creator - All Tickets and Ticket Management Admin to call the following endpoint:

    • GET /BCI_TS/v1/{tenantId}/deviations/ticket-creation-schema

Certificate handling

Certificate handling has been changed in the 7.13.1 release. The environment variables JAVA_SERVER_KEY_PASS, JAVA_SERVER_CERT_FILE, and JAVA_SERVER_KEY_FILE were removed and are no longer supported. The environment variable USE_SYSTEM_CA_CERTS replaces the previous certificate handling.

If USE_SYSTEM_CA_CERTS is set to true, all default Ubuntu CA certificates and any custom certificates mounted under /certificates are imported into the trust store upon starting the image. All custom certificates mounted under /certificates must be in the PEM format and have a .crt extension.

If you have previously used the environment variables JAVA_SERVER_KEY_PASS, JAVA_SERVER_CERT_FILE, and JAVA_SERVER_KEY_FILE, you will need to update your deployment and mount paths to use the new USE_SYSTEM_CA_CERTS environment variable and /certificates directory.

The helm chart has been updated to reflect these changes. If you are using the helm chart, you can simply upgrade to the latest version and the changes will be applied.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2026, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses