We are pleased to announce the release of TEAMATE 12.1.5!

TEAMATE is the third stop of the 12.1.5 release train. Next and final stop, TEAMS-IDE Server. All aboard:)

• TEAMS-Designer Change Log

  Bug

  • PDTEAMS-66  TEAMS-Designer TFOM reports does not show well when font scale is 150%
  • PDTEAMS-87  TEAMS-Designer keeps giving “The system configuration(s) defined for the model is
    not valid” every time we do TA
  • PDTEAMS-103 Some model multimedia in library modules is not being exported to TEAMS-RDS properly
  • PDTEAMS-123 If multiple modules at different levels share same hierarchy label, use the RU and its repair notes closer to
    the aspect.
  • PDTEAMS-389 TEAMS-Designer GUI allows the User to delete ALL ports and then may hang
  • PDTEAMS-404 TEAMS-Designer crash and model corruption with auto layout
  • PDTEAMS-405 TEAMS-Designer allows to delete a connected port
  • PDTEAMS-415 Incorrect text in GUI: Serviceability Analysis Analysis
  • PDTEAMS-447 When library module ‘A’ s imported by reference into Model ‘C’ exporting run-time files of
    ‘C’ fails
  • PDTEAMS-477 Vague message when adding a module and no name is entered
  • PDTEAMS-478 &482 Hierarchy list assigned to the model appears to be corrupted
  • PDTEAMS-479 Some module properties cannot be entered when creating a new module
  • PDTEAMS-484 Cannot load a tmsx file into TEAMS-Designer
  • PDTEAMS-485 Data from misc tab on module properties dialog is not saved
  • PDTEAMS-486 Error message when saving a model
  • PDTEAMS-493 When clicking the “X” in the upper right corner of the TEAMS canvas repeatedly closes and opens the
    model
  • PDTEAMS-494 After opening a TMSX file and performing a “SaveAs”, model remains as Read Only
  • PDTEAMS-508 Model opens when closing existing model
  • PDTEAMS-528 IDLENGTH should be 50 to match XSD
  • PDTEAMS-533 Port deletion causes a link to connect to an imaginary port
  • PDTEAMS-606 Designer crashes while doing auto layout on the attached model
  • PDTEAMS-640 Clicking on some Help buttons does nothing
  • PDTEAMS-647 Test Why link in the “Preview in Browser” generated HTML, does not show the Why notes and shows
    Style-sheet directory structure
  • PDTEAMS-648 TEAMS crashes when ‘Serviceability analysis’ with User Role ‘All’ and symptom
  • PDTEAMS-665 TEAMS-Designer msi installer gives “Windows defender smartscreen prevented an unrecognised app”
    Unknown publisher
  • PDTEAMS-671 TEAMS-Designer crashes while resizing TFOM summary window
  • PDTEAMS-677 Crash while doing Serviceability Analysis on a model with a very long name
  • PDTEAMS-679 TEAMS crashes while creating a model with a very long name
  • PDTEAMS-691 Publisher for installer msi is “Qualtech Systems Inc.,” instead of “Qualtech Systems,
    Inc.”
  • PDTEAMS-697 Some Help buttons need to display appropriate pages
  • PDTEAMS-698 Cancelling Serviceability Analysis brings up a dialog window

  Task

  • PDTEAMS-117 Append the License Terms users accept during install with a link to QSI Master agreement on our website
  • PDTEAMS-565 Make Fault Isolation Manual and diagnostic strategy export part of new licensed module
  • PDTEAMS-569 Upgrade teams-designer.sln to Visual Studio 2017
  • PDTEAMS-573 Update build script(s) to compile using Visual Studio 2017
  • PDTEAMS-574 Update installer to package Visual Studio 2017 redistributable
  • PDTEAMS-577 Update jquery to latest version
  • PDTEAMS-578 Update OpenSSL library to latest version
  • PDTEAMS-579 Update libcurl library to latest version
  • PDTEAMS-580 Update zlib library to latest version
  • PDTEAMS-581 Update bcrypt library to latest version
  • PDTEAMS-582 Update cimage library to latest version
  • PDTEAMS-583 Update libexpat to latest version
  • PDTEAMS-584 Update Liquid XML to latest version with Visual Studio 2017 bindings
  • PDTEAMS-588 Update SoftwareKey libraries to latest version
  • PDTEAMS-592 Include teams-designer-lite.xsd in installation
  • PDTEAMS-602 Update modelgen project to Visual Studio 2017
  • PDTEAMS-603 Update teams concurrent project to Visual Studio 2017
  • PDTEAMS-644 Upgrade FlexLM libraries to latest version
  • PDTEAMS-685 Update build script to code sign binaries using SHA-256
  • PDTEAMS-711 Function to convert time from a fractional number of hours to a more user-friendly form is broken and should
    be rewritten

  Epic

  • PDTEAMS-568 Upgrade the application to Visual Studio 2017
  • PDTEAMS-570 Update all third-party libraries to latest version

  Story

  • PDTEAMS-157 Create a spreadsheet report that shows %FI up to 3 components for each symptom when generate FIM
  • PDTEAMS-623 As a user, I want auto layout across all levels of a model
  • PDTEAMS-638 As a developer, I want to replace Windows HTML Help with HTML export of Confluence space TEAMS-Designer
    Help
  • PDTEAMS-667 As a user, I want splash screen to show latest Windows version first
• TEAMS-RDS Change Log

  Bug

  • PDRDS-176 Importing user’s fails when updating a non-existing user
  • PDRDS-177 Importing user’s fails when language and time zone are empty
  • PDRDS-197 TEAMATE manifest is not getting recreated upon bulk user import
  • PDRDS-199 Case Assignment screen forgets notification target environment when a new user is selected
  • PDRDS-201 Sort Model revision numerically instead of alphabetically in Validate Models
  • PDRDS-210 Model with plus sign does not appear in Consolidate Models screen
  • PDRDS-205 ‘Case Assignment’ Screen’s search filter does not print (split) the printed number correctly – of Cases (Unresolved) Vs Cases (Resolved)
  • PDRDS-216 Live TEAMS-RT session is not appearing in System Health Status dashboard
  • PDRDS-219 System Health Status not showing any sessions after only 2 TEAMS-RT sessions ran in empty database.
  • PDRDS-220 The histogram plot showing # of BAD, # of Suspect when RT session is clicked in System Health Status screen, is missing
  • PDRDS-222 TEAMS-RDS guided troubleshooting is not taking over from where TEAMS-RT left-off
  • PDRDS-223 Resumption of suspended TEAMS-RT session does not resume from step suspended
  • PDRDS-234 Model does not show any parameter updates under parameter estimation
  • PDRDS-237 Occasionally system health status details appears for a different session than the one clicked in system health status
  • PDRDS-242 DBAGENT fails to log the SESSION_STATUS in Linux with “Column count doesn’t match value count at row 1”
  • PDRDS-245 My sensor client session does not appear under Live TRT Sessions in System Health Status on Linux
  • PDRDS-278 TEAMS-RDS Service Launcher is unsigned
  • PDRDS-284 Serial number for multiple systems is displayed in Health Status page when only one of the systems has a live RT session
  • PDRDS-297 MSI installer flags SmartScreen filter with Unknown publisher
  • PDRDS-308 Dispatch Job REST service does not fail gracefully when symptoms are not provided
  • PDRDS-325 Multimedia file cache stuck with a 0 byte sized file until file is manually deleted from file system
  • PDRDS-340 Importing users from CSV only imports one group when multiples are specified
  • PDRDS-341 TEAMATE Consolidate Models fails when using /RDS/sync/models or /RDS/sync/logs against an accessible server

  Task

  • PDRDS-236 MySQL model agent should have improved error messages
  • PDRDS-238 Make Linux license not dependent upon existence of eth0 and work with any interface name
  • PDRDS-239 Speed up Test Design library for processing Test Designs
  • PDRDS-252 Update installer to use latest version of Java 8
  • PDRDS-258 Upgrade teams-rds-be.sln to Visual Studio 2017
  • PDRDS-263 Update build script(s) to compile using Visual Studio 2017
  • PDRDS-267 Package Tomcat 7 compiled WAR in Linux distributions
  • PDRDS-268 Update installer to package Visual Studio 2017 redistributable
  • PDRDS-270 Add Boolean diagnostic option SHOW_SYMPTOMS_DURING_TRT_RESUME to database scripts
  • PDRDS-273 Implement zlib replacement
  • PDRDS-298 Update all dependencies to the latest version
  • PDRDS-299 Update build script to code sign binaries using SHA-256
  • PDRDS-307 Update RESTful web service documentation to include blurb on how to use examples
  • PDRDS-311 Update TEAMS-RDS Service Launcher to not rely on error code to determine if service stopped or started
  • PDRDS-324 Update installer to use JRE 1.8 update 161
  • PDRDS-337 Update installer to use latest version of Apache Tomcat 8.5
  • PDRDS-345 Update installer utilities to latest version of .NET and Visual Studio

  Epic

  • PDRDS-259 Upgrade the application to Visual Studio 2017
  • PDRDS-260 Update all third-party libraries to latest version

  Story

  • PDRDS-126 As a software administrator, I want ability to pull emails from Exchange without IMAP or POP
  • PDRDS-144 As a user, I want splash screen to show latest Windows version first
  • PDRDS-185 As a user, I want All option for Model Revision in Report Modeler Feedback page
  • PDRDS-186 As a user, I want Report Modeler Feedback page filter criteria remembered until I log out
  • PDRDS-193 As a product owner, I want Utilization Report exposed to Manager and Supervisor roles
  • PDRDS-202 As a user, I want ability to convert PackNGo jobs to other job types
  • PDRDS-213 Use the serial number sent by TEAMS-RT clients such as sagent or other SDK users and assign to systems in Managers screen
  • PDRDS-251 As a user, I want symptoms displayed when resuming guided troubleshooting session from TEAMS-RT session
  • PDRDS-285 As a user, I want ability to easily configure TEAMATE and TEAMS-RDS support pop-up content
  • PDRDS-289 As a user, I want to assign job on transfer if configured to do so
  • PDRDS-290 As an administrator, I want to enable/disable and re-order job notification target environments drop down
  • PDRDS-330 As an administrator, I want License ID displayed under Powered by RDS -> License Information
  • PDRDS-334 As a user, I want ability clean database upon installation of developer edition
  • PDRDS-346 As a user, I would like SQL Server 2017 Express installed
• TEAMATE Change Log

  Bug

  • PDTMATE-96 H2 database is not being removed during uninstallation
  • PDTMATE-113 MULTIMEDIA table pre-existing entries are not getting updated during Model Consolidation

  Task

  • PDTMATE-82 Update version number to 12.1.5
  • PDTMATE-105 Update teamate project to Visual Studio 2017
  • PDTMATE-106 Update build script(s) to compile using Visual Studio 2017
  • PDTMATE-107 Update installer to package Visual Studio 2017 redistributable
  • PDTMATE-111 Update build script to code sign binaries using SHA-256
  • PDTMATE-114 Update installer to use latest version of Java 8
  • PDTMATE-115 Update installer to use latest version of Apache Tomcat 8.5

  Story

  • PDTMATE-36 As a user, I want the software to uninstall itself upon reinstallation
  • PDTMATE-83 As a user, I want splash screen to show latest Windows version first
  • PDTMATE-89 As a user, I want the installer to reboot machine or log off user to set environment variables
  • PDTMATE-103 As a support agent, I would like logs saved to the file system
  • PDTMATE-112 As a user, I want multimedia served directly from the database without file caching
  • PDTMATE-119 As a user, I want TEAMATE release notes separated from TEAMS-RDS release notes

We are glad to announce the release of TEAMS 12.1.4!

Some features and bug fixes in this release include:

TEAMS-Designer

• Renamed ‘Design For Service Analysis’ menu items to ‘Serviceability Analysis’
• In configurable models, fixed the error “The system configuration(s) defined for the model is not valid” each time while performing the analyses.
• Multi-media references embedded in the library modules of the parent model, do not show up during off-line troubleshooting.

TEAMS-RDS

• Java Runtime Environment (JRE) bundled with TEAMS-RDS (and TEAMS-IDE) on Windows platforms is now upgraded to JRE 1.8
• User comments entered at each step of the troubleshooting screen are now shown under Session History tab
• ‘Task Assignment’ is renamed as ‘Case Assignment’
• ‘View Feedback’ page that modelers use to improve models, now honors Model Access Settings to show feedback for only the allowed models.
• The TEAMATE user’s role for troubleshooting is now synced from TEAMS-RDS as opposed to set in stone as ‘Field Technician’ in earlier versions
• Ability to hide/show TEAMATE Model configuration repository and Log Synchronization links from TEAMS-RDS
• TEAMS-RDS will automatically extract models to the repository that TEAMATE users connect, when a system is mapped to the model. Similarly TEAMS-RDS will delete the models from repository when no system is mapped, or when all the mapped systems are deleted. This eliminates the need for RDS administrator to extract the model in ‘Manual Synchronization’ page.
• New column is added in User Management screen to show user’s locations. If the user belongs to multiple locations, placing the mouse pointer on “…” will show all locations.
• Now soft and hard model expiration in TEAMS-RDS are in terms of number of days since TEAMATE last synchronized.
• Now email field is mandatory in ‘Add user’ screen, to facilitate emailing of jobs to Online/TEAMATE/PackNGo users.
• Search filter in Case Assignment: Default search filter has been changed to show only non-closed jobs.
• While assigning a case, in the Case Assignment screen, the screen selects the logged in user name under Technician Name for ease of job assignment to self.
• If the user belongs to multiple locations, selecting the location in the drop-down before troubleshooting the job, does not take effect and the job always belongs to first location.
• Unassigning a job, deletes the Case Id field in the ‘Case Assignment’ screen.
• TEAMATE job status sent during the start of the session stays Active even after the job is closed.
• ‘View diagnostic tree’ does not generate the tree in the primary language of the user who is troubleshooting.

TEAMATE

• User comments entered at each step of the troubleshooting screen are now shown under Session History tab.
• Now email field is mandatory for TEAMATE users as jobs can be emailed to the field users.
• Updated search index trigger when user initiates a guided troubleshooting session to account for configurations
• Fixed the Job report link that was disabled in TEAMATE for jobs sent from TEAMS-RDS

We are glad to announce the release of TEAMS 12.1.3

Some features and bug fixes in this release include:

TEAMS-Designer

• FMEA reports now honor the Filter by Technology exclusion.

Bug Fixes:

• Improved diagnostic tree strategy and probability computation when tests are unreliable
• FMEA Identifier specified in the module properties is used in FMECA reports, if given, instead of TEAMS generated ID.
• PackNGo view of the diagnostic tree does not work in Windows 8.1
• The Ambiguity Histogram in Design For Service HTML report does not show bars, and displays only numbers.

TEAMS-RDS

• RESTful API to send jobs to PackNGo : RESTful API was developed to facilitate machine to machine diagnosis. These APIs are useful for interface developers, where the remote equipment can send fault codes to TEAMS-RDS, and TEAMS-RDS needs to email a troubleshooting strategy to the appropriate engineer with PackNGo app on his mobile device. Machines can initiate the sessions by sending the status of symptoms of type ‘BIT/Error codes’ as pass or fail to TEAMS-RDS, and TEAMS-RDS can email the PackNGo strategy based on those initial error codes.
• Improved strategy and probability computation when tests are unreliable in TEAMATE troubleshooting.
• TEAMS-RDS is now supported with Tomcat 7.0

New features in PackNGo (PNG) 12.1.2

• Sample Troubleshooting Jobs: New users can get familiarized with the PackNGo app using a sample troubleshooting job.  After installing, the PNG app shows ‘Troubleshoot sample job’ button prominently on the welcome screen. Users can also troubleshoot sample job by selecting the selecting the menu item on the top right  hand corner.  PNG connects to TEAMS-RDS running on the QSI website to facilitate running this test job.
• Initiation of Jobs from TEAMS-RDS (Go Online): Users with proper credentials can initiate a job from PackNGo, by connecting to TEAMS-RDS using the ‘Go online’ menu item. They can then download the job payload to take it offline at any point during the troubleshooting by clicking the top right menu item ‘PackNGo’.
• Dispatch Center jobs: PackNGo now supports jobs sent by the Dispatch Center in TEAMS-RDS. Dispatchers can send a job with multiple matching symptoms and the mobile device user can select the right symptom in the field, and get the corresponding troubleshooting strategy from the server via HTTP/HTTP

01/15/2014:  A patch has been released to fix the following :

• The mime type which was preventing the old email clients on Android from opening the  payload.
• No job report will be emailed now for dispatched jobs where no steps were performed before the job was taken off-line (to PNG).

We are glad to announce the release of TEAMS 12.1.2

Some features and bug fixes in this release include:

TEAMS-Designer

•  TEAMATE analysis, and TEAMS-RT analysis can now be performed on configurable models by selecting different child configurations defined in the model.

Bug fixes:

• Default color for Test points is not remembered when creating a new Test point.
• TEAMS-RT analysis fails to connect to TEAMS-RDS if ‘http://’ is not specified in the URL.
• In TEAMS-Designer FMECA version, changing sensor modules to regular modules is not removing them from sensor lists on sensor tests.
• Other bug fixes…

TEAMS-RDS

• Job Initiation from PackNGo app:  Users of PackNGo app can initiate an online session with TEAMS-RDS and take the job offline by directly downloading the job on to their app.
• Ability to send TEAMS-RT jobs to PackNGo: TEAMS-RT session diagnosis can be now sent to PackNGo users for further off-line troubleshooting.
• Demo Mode in PackNGo app : Added a Demo feature in PackNGo app for new users to initiate a sample troubleshooting job.

We are glad to announce the release of TEAMS 12.1.1

Some features and bug fixes in this release include:

TEAMS-Designer

•  Re-designed the window for Create System Configuration
• Redesigned Toolbar buttons in the Tech Data tab of the Module and Test properties dialogs.
• Bug fix: TEAMS-designer crash when a module is being imported from another model on the disk.
• Other bug fixes…

TEAMS-RDS

• Dispatch Center: Dispatcher functionality to send multiple troubleshooting jobs to PackNGo users by selecting one or more matching symptoms for different systems
• Encryption/Decryption of jobs sent to PackNGo
• Ability to pass symptoms of type ‘BIT/Error codes’ in the symptom selection screen or via web service call, before the start of TEAMATE troubleshooting.
• Many more…

We are happy to announce the general availability of TEAMS 12.1.0. We strongly recommend all users of TEAMS 12.0.3 or earlier upgrade to this version.

Some features and bug fixes in this release include:

TEAMS-Designer

• Dockable toolbars with new toolbar icons
• Usage Finder feature: Users can search where a particular function, technology label, setup, resource, or a switch mode has been used in the model. Clicking on the search result takes the user to the right place in the model.
• Function Groups and Function Mapper GUI revamps
• Bug fixes and more…

TEAMS-RDS

• PackNGo now supports tests with test designs. It can now compute the test outcomes based on user inputs.
• PackNGo Session logs can now be synchronized with the TEAMS-RDS server via HTTP/HTTPS, in addition to via email.
• ‘Surface Mode’ versus ‘Airplane Mode’:PackNGo users can troubleshoot while being in Airplane Mode (Offline) after receiving the job from TEAMS-RDS.  However, if the user cannot perform certain tests or setups during the troubleshooting session, they can still complete the job by having the mobile device be in Surface Mode (Online), and PackNGo will automatically connect to TEAMS-RDS and get a revised troubleshooting strategy.
• Ability to edit Case ID any time during the troubleshooting session.
• ‘Task Assignment’ page enhancements, sorting jobs, navigation links to pages, and performance improvement to load the pages faster with the job filters.
• Many more…

TEAMATE

• Model entitlement based on the user groups integrated to TEAMATEs model consolidation page.

QSI is happy to announce the general availability of TEAMS 12.0.5. We strongly recommend all users of TEAMS 12.0.3 or earlier upgrade to this version.

Some features and bug fixes in this release include:

TEAMS-Designer

• Users can now generate usage report (or where used report) for Technology Labels, Hierarchy Labels, Test Labels, Resources, Setups, Functions, and User Roles.
• Fixed bugs related to usage of function groups
• Fixed memory problems with Testability Analysis with 8 or more cores.

TEAMS-RDS

• Fixed a bug where the reasoning engine gives preference to multi-outcome tests over two outcome tests
• Users with Supervisor role can now delete any non-active job
• Users with Supervisor role can reassign field jobs to another user
• The maximum model media size for PackNGo payloads can now be configured via a parameter

TEAMATE

• Model entitlement now works seamlessly with TEAMATE.  TEAMATE users can only consolidate models and troubleshoot systems that belong to their group(s) that gets assigned on the server.