How Tascus Client App Updates Affect Your System

Purpose:
This document outlines how updates to the Tascus client application affect your local installation, test or build sequences, and production data stored on your server. Our goal is to ensure transparency, minimize disruption, and maintain backward compatibility during all updates.

1. What is the Tascus Client App?

The Tascus Client App is the local application installed on operator workstations. It runs production sequences, captures data, and interacts with the Tascus Server.

2. What Happens During an Update?

Tascus updates are periodically released to improve functionality, enhance usability, fix bugs, and add new features. When an update is applied:

• The client executable and user interface files are replaced with the latest versions.

• Configuration files and workstation settings are retained.

• The client re-establishes communication with your Tascus Server once restarted.

3. Impact on Sequences

• No Loss of Custom Sequences:
  Sequences created or customized in your environment are stored on your Tascus Server and are not affected by client updates.

• Backward Compatibility:
  We maintain compatibility with existing sequence steps. If any breaking changes are required in the future, we will provide a detailed migration guide and update path.

• New Step Types or Features:
  Updates may introduce new sequence steps or features, which will become available for use after the update. You are not required to use them unless you choose to.

• Sequence Compatibility Between Versions:
  If you create or edit sequences using a new client version and include any of the new step types or features, these sequences will not run on older client versions.
  To avoid this, we recommend keeping all client devices on the same version across your site.

4. Impact on Production Data

• No Data Loss:
  All production data, including scanned barcodes, measurements, operator logs, and pass/fail results, is stored on your local or central Tascus Server. This data remains intact and unaffected by client updates.

• Data Compatibility:
  The client is designed to communicate with your existing database schema. We carefully manage changes to ensure that all historical and live data remains accessible and usable.

• Database Migrations (if applicable):
  In rare cases, a database schema update may be required. These are done automatically or guided by our support team, depending on your setup. You will be notified in advance of any such changes.

5. Client Version Management and Update Location

• Version Mismatch Between Devices:
  Devices not updated to the latest version will not be able to use newly added features or steps. Keeping clients up to date ensures consistent functionality across workstations.

• Check Client Versions:
  You can view the client version installed on each device under:
  Main Menu > Site Licenses
  This list helps identify which devices need updating.

• Set Update Location:
  Also under Main Menu > Site Licenses, you can define the Client Update Location — the shared network path or URL where devices will look for the latest installer.

6. Summary

7. What You Need to Do

• Install Updates:
  If updates are distributed as installers, run the latest installer on each client workstation. In centrally managed environments, use your usual deployment method or configure the update location in the app.

• Stay Consistent Across Devices:
  Keep all devices running the same version to avoid feature or sequence compatibility issues.

• Test New Features (Optional):
  Consider testing new updates in a staging environment before full deployment, especially if your team has customized sequences.

• Need Help?
  Contact our support team or your dedicated support channel if you have any issues or questions about updates.