Month: October 2018

FTMaintenance Service Request v3.1.5 Release Notes

Posted: 10/17/2018

Solutions

  • Corrected an issue that delivered multiple email notifications for the Approved status to recipients when service requests were submitted while in Direct Mode.
  • Corrected an issue that prevented large lists of equipment from being displayed all at once on the Equipment Visibility configuration page.
  • Corrected an issue that caused errors when excluding equipment from a large list of equipment.
  • Corrected an issue that caused errors when excluding equipment too quickly.
  • Corrected an issue that prevented an image from being hidden on the Login page.
  • Corrected an issue that caused errors when interacting with large amounts of data for extended periods of time.

FTVersionTrak v1.9.3 Release Notes

Posted: 10/5/2018

Solutions

  • Connection
    • A single verification is required when declining to update Repositories created by previous releases of FTVersionTrak.
  • Files System Operations
    • Root directories can be set as Working Directories for folders.
    • Each Repository folder and subfolder can be assigned unique working directories.
  • Repository Options
    • Folder history is now retained after the Activity Log is purged.
    • Activity Log entries can be purged, and the number of days to keep log entries can be adjusted without causing deletion errors.
    • When configured, users must enter a comment when checking in files.
    • The Comment field in the label dialog is resizable.
  • Repository Security
    • When configured, a signature is required when revising Repository group owners.

 

  • Scheduled Tasks
    • Successfully executed Scheduled Tasks are reported correctly.
    • When configured, Scheduled Tasks that detect no differences between the current PLC program and its most recent file in the Repository will email appropriate message.
  • Version Control Operations
    • Electronic signatures are accepted when checking out folders.
    • Electronic signatures are not required when viewing unedited comments.
    • Dialog that confirms deleted or destroyed files closes automatically.
    • A warning dialog appears when checking out a file that will be copied over an edited working copy.

FTVersionTrak for APT v1.9.3 Release Notes

Posted: 10/5/2018

Solutions

  • Connection
    • A single verification is required when declining to update Repositories created by previous releases of FTVersionTrak.
  • Files System Operations
    • Root directories can be set as Working Directories for folders.
    • Each Repository folder and subfolder can be assigned unique working directories.
  • Integration with FTSolution
    • New files added to a Solution remain are not automatically checked out after they are checked in.
    • New files can be bound to a Solution into folders that were originally empty.
    • Multiple performance improvements were made to responsiveness of the FTVersionTrak toolbar, and when binding Solutions to Repositories.
    • The correct number of files is reported in the Repository Properties.
    • Items that are deleted but not destroyed cannot be renamed.
    • Checked out files are automatically checked in when binding a Solution to another Repository.
    • Read/Write status is restored to files in Solutions that are unbound from Repositories.
    • New files now can be directly added to Repositories and checked in.
      Repositories can be configured to require entry of Folder Comments when any new folders are added.
    • Properties can be viewed when comparing Projects.
    • Checking in files to a Solution that was deleted from its Repository restores the Solution to the Repository.
    • Check Out Comments can be displayed for any item, including Solutions, Projects, and Units.
    • The Refresh feature in FTVersionTrak correctly displays recently added Solutions from FTSolution for APT.
    • Repository Properties window properly closes.
    • Required Comment field message wording is clarified.
    • When configured, signatures are required for Properties and Comments only when they are edited.
    • Solutions must be rebounded to or unbounded from its Repository if the Solution was deleted from its Repository it was open in FTSolution.
    • The file status of checked-in Subroutines is now set to “Current”.
  • Repository Options
    • Folder history is now retained after the Activity Log is purged.
    • Activity Log entries can be purged, and the number of days to keep log entries can be adjusted without causing deletion errors.
    • When configured, users must enter a comment when checking in files.
    • The Comment field in the label dialog is resizable.
  • Repository Security
    • When configured, a signature is required when revising Repository group owners.
  • Scheduled Tasks
    • Successfully executed Scheduled Tasks are reported correctly.
    • When configured, Scheduled Tasks that detect no differences between the current PLC program and its most recent file in the Repository will email appropriate message.
  • Version Control Operations
    • Electronic signatures are accepted when checking out folders.
    • Electronic signatures are not required when viewing unedited comments.
    • Dialog that confirms deleted or destroyed files closes automatically.
    • A warning dialog appears when checking out a file that will be copied over an edited working copy.

FTSolution for APT v2.0.1 Release Notes

Posted: 10/5/2018

Solutions

  • Compile Report
    • Fixed incorrectly reported count of Y addresses used as CR (when none was used) in summary of memory requirements of Compile Report.
  • Configuration Editor
    • Fixed incorrect errors displayed in the Configuration Editor regarding non-Retentive and Retentive Reserved Locations. The errors now display the correct non-Retentive and Retentive Reserved Locations allowed ranges.
  • Cross Reference
    • Search for references to all symbols (“*”) no longer results in crash in a large program.
    • Cross Reference no longer displays the full local file path of the project file containing the reference. The project relative path will now be displayed.
  • Declaration Editor
    • Previously, renaming a Declaration file and adding a Declaration would cause “The operation could not be completed. The parameter is incorrect.” error on the save of the Declaration file. Once the file was reopened, the added Declaration wouldn’t be in the file, and a Declaration with the same name could not be re-added. This release corrects this behavior such that renaming a Declaration file followed by adding a declaration and saving the renamed file will complete without error and without the added declaration going missing.
  • Full Compile
    • Subroutine recursive calls exceeding 4 levels deep is no longer allowed, consistent with APT. If recursive calls deeper than 4 levels is detected, the (incremental or full) compilation will fail with an error message.
    • User is no longer required to have at least one reserved location from non-retentive C addresses in order to set user-assigned address for Boolean for Retentive C.
    • User will no longer get Potential PCS\PLC Mismatch warning whenever compiling a program with a user-assigned tagged Declaration unless the address of the PCS Tag has changed from the last compile.
  • Incremental Compile
    • When the program was downloaded incrementally after it had been compiled incrementally more than once since the last download, the order of the downloaded commands required the PLC switch between Edit and Run multiple times. Incremental download commands generated by an Incremental Compile are now optimized to avoid multiple PLC transitions from Run to Edit and Edit to Run.
    • Incremental Compile no longer fails when a unit is renamed.
    • Incremental compile validation will no longer fail with error “Conflict between Y and CRs: unable to do an incremental compile” when Y addresses have not been allocated as CR addresses.
  • Incremental Download
    • Fixed “Unknown network error (Cannot Display Network)” when downloading to the 505 simulator.
  •  Report
    • Download Reports now include Communication Type (TCP/IP address or COM port number) information.
    • When generating multiple Cross Reference reports from the same open Cross Reference window, Cross Reference report files were added under the Miscellaneous Files solution folder, instead of adding those files under the project’s Report folder. This release fixes this behavior by adding Cross Reference report files under the projects Report folder.
    • Fixed an error of Boolean type shown in Address-to-Symbol and Symbol-to-Address reports shown as Bool, as well as Boolean. It will show as Bool from now on.
    • The user was not given the option to provide a different filename for a report after being alerted that a file with the same name exists and they decline overriding the existing file. This release fixes this behavior by keeping the Select Report(s) To Generate dialog open, to allow the user to provide a different report filename.
  • Solutions Management
    • Commands for Compile, Download, Debug and Exit Debug were only available if a Project node or Compile node was selected in Solution Explorer. These commands are now available regardless of which project node is selected.
    • Compiler-generated file, CompiledPCSTags, is no longer shown on the solution tree.
  • Version Control Integration
    • Check In of a Declaration table file no longer results in Check Out of a Solution file.
    • Adding an I/O symbol in the I/O Module Editor required the user to manually Check Out the I/O Symbols file. This release adds support to automatically check out and update the I/O Symbols file when adding an I/O symbol in I/O Module Editor.
    • Changes to Process Groups required the user to manually check out the Process Groups file. This release adds support to automatically check out the Process Groups file whenever Process Groups are edited.
    • Changes to communication setup required the user to manually check out the Communication Setup file. This release adds support to automatically check out the Communication Setup file whenever this file edited.
    • Changes to the Object File Report required the user to manually Check Out the Object File Report. This release adds support to automatically check out the Object File Report upon making changes to it by the compiler.
    • Changes to the Download Report required the user to manually Check Out the Download Report. Changes to the Cross Reference Report required the user to manually Check Out the Cross Reference Report. This release adds support to automatically check out the Download Report Report and/or the Cross Reference Report upon making changes to either file.