Command Center Release Notes

For supported versions details, please see: Lingoport_Suite_Installation#Supported_Versions

Supported Versions

Command Center 2.2.z Upcoming (September 2024)

TMS Integrations

• Smartling Integration using the Smartling API

New Features

Context in String Manager

To make user of Context in String Manager, an InContext server must be set in a TMS configuration. See how to capture context here: Incontext Server.

• Web application context accessible from String Manager
• Filter strings with or without context in String Manager

Schedule Translations

• Schedule sending files to be translated in Localyzer project advanced settings

Improvements

• Added Globalyzer Issue Density to Project Status API Output
• Improved TFS data source support
• Added commit author email and name in Git Data Source
• Map between unique file names (starting in LID) and repository file names
• Find Localyzer project based on target locales
• Better definition of Command Center developer v. translator roles

Command Center 2.1.24 Release Notes (July 2024)

TMS Integrations

• RWS Trados Enterprise Integration Improvements using the Trados Enterprise API
• Translated Integration as a new TMS
• Update the XTM token for one, many, or all XTM configurations
• Local Vendor TMS, where prep kits and translated files are pushed on the VM's File System, adding flexibility to testing or workarounds

UI/UX Improvements

• UI Performance Improvement: Project Page, String Manager, etc.
• UI Improvements, such as labels for icons, layout, sorting, etc.
• Improved ChatGPT logs and icons for Globalyzer issues
• Globalyzer Issues filtering by Rule Set
• Filtering and chips improvement: better filtering layout and "and" and "or" between chips
• Easier linking from items on one page to other items on another
• Ability to add or replace the locales for one project from another project's locales
• Deletion of Issues Comments

Miscellaneous

• Post-Import Processing: A new system file type that allows for processing once the translated files are imported
• Advanced Settings option to keep the prep kit tag in the translated files, for traceability

Command Center 2.0.13 Release Notes (April 2024)

Overall performance improvements

• Localyzer analysis performance improvements
• Issue search/filtering performance improvements
• Project page searching, filtering, sorting performance improvements

Introducing Localyzer String Manager!

 
 Introduction video

• Show each individual string coming from the source resource files (resx, json, properties, etc.)
• Easy navigation to the resource in the repository, for those with access privileges, such as developers
• Filter based on those which are
  • strings to be sent: check the content before it's sent to translation, verify grammar, spelling as desired
  • strings send to translation, not yet returned
  • fully translated strings
• Mark strings:
  • Not reviewed
  • To be reviewed
  • Reviewed
• Filter by the review state (see above)
• Sort by filename, strings, keys, time created
• Infinite scrolling: when thousands of strings are identified, keeps loading those strings as the user scrolls down
• Automatic refresh: as new analysis are carried out, the string manager will update automatically for the changes
• Clean up and restart from scratch

String Manager

Updated Projects Page

• Faster project page refresh, deep performance improvement
• Infinite scrolling
• Improved filtering
• Improved sorting, now includes sort by
  • Group name
  • Project name
  • Module name
  • Globalyzer issue density
  • Localyzer percent complete
  • Project status
  • Time since last changed

Historic Versions

Command Center 1.2.8 Release Notes (March 2024)

• Complete overhaul of the Issues page, especially around Globalyzer issues, including:
  • Performance
  • Comments
  • Filtering - New Filter selector; issues by scan; by Status; by Priority
  • Search - On issue text, on code line, on file name, on comments
  • Improved navigation from the Globalyzer page to the issues page
  • Issue detail
  • Status and status change
  • Code lines above and below issue line
  • Migration from EOL Jenkins/Dashboard
  • Display either as priority or as severity
• Simplified debug scripts execution
• Post import processing ability
• Improved ChatGPT processing on large number of issues
• Android pluralization support
• PO pluralization support
• Edit a Command Center project configuration while a project is running
• Allow project validation prior to saving the project configuration
• Sort the locales alphabetically when editing a project
• Delete all queued jobs ability
• Improved session management

Command Center 1.1.38 Release Notes (February 2024)

• Relaxing ICU message format issues: Instead of blocking issues, ICU message format errors are now Warnings; To see them, either go to the issue list or click on the 'Informational Issues' from the Localyzer page in Command Center.
• Check Send: from the Advanced Settings page, clicking the 'Check Send' button will check any prep kit in a halted state and try to resend them to the TMS. For instance, if the token for a TMS expired as translations were sent, and the token has been replaced, click 'Check send' to re-submit to the TMS. Other case when translation did not make it to the TMS are for example network glitches or changes in the TMS.
• Reset Project: ability to clean up any unwanted outstanding kits or other items in the on-boarding and restart sending translation using the latest Prep Kit #. Useful when some locales have been dropped from old outstanding kits still in translation for instance.
• Scheduling WorldServer import: Fixed an issue on the scheduler for WorldServer
• TMS/MT Connection Renaming: ability to rename a connection and reflect the change automatically in all the projects using that connection
• Indicate the last SHA for system files so it makes it clear which version of the system files are on Command Center

Command Center 1.1.35 Release Notes (January 2024)

• InContext Translation Support When creating a TMS connection, configure also a connection to a Lingoport InContext Server. See About InContext Translation . Then when on-boarding a project, if a TMS connection with InContext Translation support is used, configure the Instrumentation locale. That will allow the context capture of the running application in that locale.
• Analysis Performance Improvements
• Pseudo-localization, trackback, instrumentation Performance Improvements
• Start Tracking: After on-boarding, when all is copacetic, click the 'Create project baseline' on the left panel to start tracking any changes to the resource files.
• Troubleshooting File System: A new file system, independent for projects, can be used to check your system as one wants. See https://github.com/Lingoport/CommandCenterConfig/blob/main/debug/list_kits.sh as a sample to get started
• System Environment Variables: For any scripts, such as troubleshooting, transforms, etc., use System Environment Variables
• DITA Sample Transform: see https://github.com/Lingoport/CommandCenterConfig/tree/main/transforms/dita to help with your DITA on-boarding
• Advanced Localyzer Settings

• Fixed an issue around casing between the repository locales and the TMS or MT locale.

Command Center 1.1.32 Release Notes (December 2023)

• AWS S3 Data Source Credential Support. See also Git to AWS S3 System
• Gerrit Data Source Credential enhancement for slashes in project URL
• Trados Enterprise TMS support
• LocalyzerQA support in Command Center, using tags to link a LocalyzerQA application and Command Center projects
• Changing TMS for a project keeps the on-boarding as close as possible, to make switching TMSs as simple as possible
• Pseudo-Localization Remote Calling
• New Version Indicator: Command Center indicates when a new version is available.
• Better logging on project configuration changes
• Enhancement in TMS management - internal file configuration.
• Enhancement in Queue management - interaction between queue and maintenance mode.
• Enhancement to Globalyzer and Localyzer handling of issues
• Fix issue on Toggle UI elements
• Fix issue in Saving projects

Command Center 1.1.11 Release Notes (October 2023)

• XTM TMS integration support
• WorldServer TMS integration support
• Custom Data Source
• Gerrit Data Source Credential
• GitLab Merge Request
• Alpha ChatGPT Translation Support
• Alpha ChatGPT Globalyzer Support

In addition to the Underlying Localyzer engine features:

• Localyzer 9.2 Korea
• Localyzer 9.1 Joetsu

Command Center 1.0.154 Release Notes (September 2023)

The Korea/1.0.154 release is the initial release of Command Center. Command Center's application supersedes the Lingoport Suite's Jenkins and Dashboard, and simplifies a number of tasks previously done via either, including

• Administration of the system
• Configuration and on-boarding of individual projects
• Search on project, search on issues
• Filtering on projects, filtering on issues
• Sort on projects, sort on issues
• Improved reporting and logging
• Improved performance

Below are some of the major features in Command Center:

• Support for SAML/SSO: The Globalyzer Server can now be configured with SAML/SSO, in addition to LDAP. This allows seamless integration with third party identity providers.
• Support for Globalyzer 6.8.0: Command Center allows for fast and easy Globalyzer project creation. For information on Globalyzer, please see: Globalyzer
• Support for Localyzer 9.2.0: Command Center allows for fast and easy Localyzer project creation. For information on Localyzer, please see: Localyzer
• Figma Integration: Use Command Center to translate Figma designs.
• Project Tagging: Projects can be organized and filtered using tags.
• API calls: Initial API calls to list projects, duplicate a project, or get the status of a project in Command Center.
• Execution Queue: See what is in the execution queue, delete from the queue, interrupt a running job.
• Improved Issue Management: The user interface for issues has been entirely redesigned.
• Space and System Requirements Improvements: In Command Center, no files are pushed to the database as was the case with Dashboard.
  A repository/branch is cloned only once in a workspace, even if many projects are created off of that workspace.
• Access to Code: Source code and resource files are only accessible via the repository, so that only those allowed repository users can see the code.