Eclipse Pro Release Notes

v5.0.15.1273

Pro now requires Eclipse Classic to be at version 4.1.176 or newer.

New features:

  • Warnings appear on the Scheduler for jobs that are already past due, or will be per the current schedule.
  • RavenDb can now (optionally) be installed in “stand alone” mode. This means it runs at it’s own Windows service, which Pro then connects to. Installation instructions have been updated with details on how to do this.

Bug fixes:

  • The “Redirect to intranet url” feature toggle didn’t save. It does now.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.1189

New features:

  • Printing status view. Shows some basic system configuration of bundle tag printing.

Bug fixes:

  • Schedule summary computation did not handle the situation where a schedule did not yet exist. This would manifest as the schedule summary on the dashboard being out of date, and errors would show up in the Health view for the schedule summary services.

v5.0.15.1146

New features:

  • A history sync can be triggered via a button now available on the Health view.
  • [Experimental] a new “Webhooks” feature. A webhook allows Pro to post data about events to a customer-designated URL.
    • One event is currently supported, and that is to schedule updates.
  • Agent now supports a “Download Diagnostics Package” of its own.
  • The server “Download Diagnostic Package” function now has the computer name and current time embedded into the zip file name.

Bug fixes:

  • The ControllerSourcedBundleCompletionEvents service would occasionally change state to FatalError with the message “Object reference not set to an object” (as shown on the Health view). This is corrected.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.1121

New features:

  • Download Diagnostics Package button now available on the Health view. Clicking it launches a download of a .zip file containing all of the Server logs. We expect more helpful information to be added over time.
  • A new log file set has been created that contains information specific to the database activity. These logs have a …db… in the file name.

Bug fixes:

  • Agent could inadvertently add a “byte order mark” when saving the xlwin.ini file. This would prevent Classic from reading the file. This has been fixed.
  • Improvements to controller-sourced bundle completion detection. Alleviates an issue where production events were not being delivered to the completion calculator in a timely manner, often causing an extreme delay in the printing of bundle tags.
  • Typo fix that caused some Agent logs to have “Server” in their file name.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.1092

Bug fixes:

  • Material codes that ended with a ‘/’ would cause errors. This is corrected.
  • Scrap and delay codes can have an optional machine level ‘Group Number.’ The history import process now accounts for this.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.1082

New features:

  • Andons get panels for longest part, shortest part, and current bundle, per the current order.
  • Bundle tag view (under Integration) now allows a user to view and print bundle tags.
  • Andons get new panels for
    • Longest part
    • Shortest part
    • Current bundle
    • Order progress
    • Next order
    • Scheduled footage
    • Order level user fields
  • Server utility got a dbload command which loads the database, but does not refresh the indexes. This is a lower impact way to open a database for inspection than dupgrade is.
  • The Machine Dashboard includes the current lockout status of the controller. Requires XL version 4.58.00 or greater.
  • The single Machine Dashboard now includes some information about the controller configuration and software version.
  • [Experimental] Automatically redirect browser from localhost to a proper machine name url. Requires a setting in system preferences (RedirectFromLocalHost).
  • [Experimental] System health view now includes some “critical” alerts, with their full text.
  • [Experimental] System health view now includes some data synchronization state information and server uptime.
  • [Experimental] A preview of licensing. A default, and very permissive, license is generated at start up and applied. It gives access to every feature in Pro and all the active machines found in Classic. A License view displays the features and machines currently “licensed.”

Bug fixes:

  • Classic has limits on the number of items (900) and bundles (800) allowed on an order. Agent now watches for jobs that violate that, does not send them on to Server, and alerts about the situation.
  • The current order value in the dashboard did not always match what the controller was running.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.875

New features:

  • The update view now has a button for launching the upgrade via the UI.
  • Explorers now display the data as it streams. Previously it would wait for the entire data set to load before showing anything.
  • Shift History graph on the dashboard can now have units set to % or minutes.
  • Agent’s view now displays its Pro version number. This is helpful in situations where Agent is installed without a Server.
  • Express is now always on. (But machines still must be configured in Classic to use it.)
  • Install docs now include instructions on finding and installing pre-release and other custom builds.
  • Explorers now loads data incrementally.
  • Production records store punch pattern numbers in a more consistent manner.
  • Database maintenance activities are now run during the upgrade process.

Bug fixes:

  • Controller-sourced bundles would never get completed.
  • Bundles for recently viewed Orders would get displayed on the wrong order.
  • Sometimes the Pro server would hang on startup. The chances of this happening have been reduced.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.794

New features:

  • Reclaimed Scrap was added to the Production Summary report.

Bug fixes:

  • The Agent service would sometimes cause a “cannot update the cursor” error.
  • Controller-sourced bundles would cause an exception if the order was modified at the controller.

Known problems:

  • For bundle tag printing, a default printer must be specified in Windows. This does not need to be a printer that is used for bundle tag printing.

v5.0.15.756

Pro now requires a minimum Classic version of 4.1.174.

New features:

  • An “experimental” mode shows unreleased features. Experimental features will have a beaker-shaped icon. Experimental mode can be enabled via a checkbox in System Preferences.
  • A new “System Health” view is available in experimental mode. This shows the current state of Pro’s internal tasks. This may be helpful to Support as an occasional shortcut before reviewing log files.
  • A previously run export operation can be repeated manually. Trigger this via a button in the Export channel view of Integration.
  • The global search now includes controller serial numbers.

Machine Dashboards:

  • A “Shift History” chart has been added to the machine dashboards. This shows a graph of runtime broken out by shift. This is an experimental feature.
  • A bug fix where a machine’s current run state was not always displaying correctly.

Production Summary:

  • The help text displayed on hover has been fleshed out.
  • The “duration” setting, when set to day, week, or month, is now saved. It will be remembered between user sessions on the same machine.
  • Production Summary report itself is enabled via the experimental features checkbox.

Reports: Explorers:

  • All Explorers now have a “reset” button that resets all individual dimension filters that are enabled.
  • The Punched facet was being incorrectly calculated. It is now correct on all Explorers that display it.

Bug fixes: 

  • A handful of logged messages have been demoted to Warning status (instead of Error).

v5.0.15.635

Bug fixes:

  • Agent was including tables besides history in its precalculations. This is corrected.
  • Agent now more gracefully handles Classic having a lock on a history file.
  • Coil loaded event detection may have been producing many duplicates. This is corrected.
  • Reduced logging in a few cases where it was excessive.

Known issues:

  • Windows Server 2012 R2 specifically has known issues involving performance problems that have been observed exclusively on this OS. It should be avoided.

v5.0.15.617

New features:

  • An alert is shown when Classic has duplicate PCODEs on a machine. This can happen due to a bug in Classic importing.
    • To fix the problem and remove the alert, find and delete the duplicate record in Classic.
  • Order detail view now includes “Id” (for bundle id) as a column on the bundles table.
  • Inactive machines no longer appear on the performance configuration view.

Bug fixes:

  • Improvements to startup performance when there are many production history shifts to synchronize.
  • Jobs lists on the Scheduler view would not scroll.

Known issues:

  • Windows Server 2012 R2 specifically has known issues involving performance problems that have been observed exclusively on this OS. It should be avoided.

v5.0.15.552

New features: 

  • “Device” (aka Machine App) features – An initial implementation of features to support Pro integration on non-length-based production machines.
    • Machine App builds are embedded into the Pro Server.
    • Machine App launch URL, under Settings (enabled via feature flag machineapp).
    • Connected devices appear in the Dashboard, with some basic metrics.
  • Upgraded database. Database is now using RavenDb version 3.5.8.
  • Bundle tag printing view. A new view has been added to show configuration and current status of bundle printing. Enabled via feature flag printing.

Bug fixes:

  • The time since last state change on a machine’s dashboard would get stale on occasion and opening another browser window would then show a correct result. This has been fixed and now updates as expected.

Known issues:

  • Windows Server 2012 R2 specifically has known issues involving performance problems that have been observed exclusively on this OS. It should be avoided.

v5.0.15.387

Bug fixes:

  • Unable to schedule a downtime that started at midnight.
  • Various other reliability fixes to mitigate problems detected in the field.

Known issues:

  • Windows Server 2012 R2 specifically has known issues involving performance problems that have been observed exclusively on this OS. It should be avoided.

v5.0.15.294

New features:

  • Late Warehouse tasks now add an alert.
  • Jobs that have an undefined pattern name now get an alert on the Schedule and Order Details views.
  • When calculating a schedule and Pro determines there is not enough coil inventory, it creates “phantom” coils of 5000 ft. length to fill in. These phantom coils are designated on the schedule with a stripe pattern.
  • Logs now include operating system version, logged at startup, on both Server and Agent.

Bug fixes:

  • Reject coils from Agent that have \ character in the coil id. This avoids a Server side exception.

Known issues:

  • Windows Server 2012 R2 specifically has known issues involving performance problems that have been observed exclusively on this OS. It should be avoided.

v5.0.15.75

Bug fixes:

  • An oversight in the database upgrade meant Performance Standards view would be empty for some customers that had been upgraded (vs fresh install). This is corrected.
  • Sometimes Classic sends machine status events (not to be confused with production events) that are unreadable. Agent no longer considers these an error and instead logs the bad data with a warning.

v5.0.15.1

New features:

  • New api method (/api/machine/{id}/production) for retrieving raw production events for a machine.
  • The metrics to display in the “large” machine dashboard view is now configurable. The “mini” view has been configurable since the beginning.

Bug fixes:

  • Improvements to production record synching in an effort to reduce the incidence of Foxpro lock errors.

Known issues:

  • Pro Agent may give errors about minimum Classic version requirements, even after Classic has been updated to the new minimum (v4.1.166). The solution is to rebuild indexes.

v5.0.14.804

New features:

  •  Added Production Summary Report – Preview (use feature flag reports. production-summary to enable it).
  • Start syncing shape/pattern data with the Server. Precursor to a forthcoming alert.
  • Coil selection policy is now configurable, via a sorted list of preferred locations (via manual db edit. Sorry, no config ui yet).
  • Support a new “Bin” location category (expanding the existing categories Warehouse, Dock, Truck, Staging Bay, and Machine).
  • Host computer name is now included in the logs at start up.
  • Coil types (Materials), Coils, and Orders lists now all support column selection.

Bug fixes:

  • Prevent Agent config corruption, seen in production, by validating some inputs better.
  • Resolve issue where schedule would not do an initial calculation at start up. It always waited for a run state change.

v5.014.751

Bug fixes:

  • Scheduler ui performance tweak.
  • Realtime production even processing – fix excessive errors caused by bad preprocessing.
  • Fixed a situation where Alerts service held a reference to the database, after the database had been shutdown.

v5.0.14.622

New features:

  • Performance configuration view is now live for customers.

v5.0.14.593

Bug fixes:

  • Would often see errors like “can’t deserialize LongestItemLengthIn” on orders in history where the job detail had been purged. This is fixed.

v5.0.14.522

Bug fixes:

  • Server service now asks for extra time to start up.
  • Scheduler was duplicating jobs, if a job was also on the machine.

v5.0.14.506

New features:

Machine Performance Configuration View

  • Users can set planning values for configuration changeovers. These values are used when predicting the schedule.

Performance Improvements

  • Web clients now get less realtime information updates, by default. Instead they only get updates on information they’ve specifically subscribed to.
  • Improvements to how we detect when it’s time to recompute a machine’s schedule, such that we compute it far less redundantly.

Integrations with External Systems

  • An initial implementation of importing orders from an ERP system.
  • An initial implementation of importing coils from a flat file.
  • An initial implementation of coil validation through an ERP system.
  • An initial implementation of notifying an external system with Eclipse events like order import result and bundle completion.
  • Added an integrations status page that shows
    • Status of each import attempt.
      • Shows overall success or failure.
      • Shows errors on individual records that could not be imported. For example, due to bad data.
    • Read-only view of the configuration of import channels.

Bundle Tag Printing

  • Customizable bundle tag templates.

Rebundling

  • A basic rebundling algorithm is supported.
  • Initially, can only be invoked as part of an order import (in other words, can not yet be executed against arbitrary orders).

Scheduler

  • Available jobs now has more grouping (column) options. The color, gauge, and width of the material and the length of the longest part in the order are all choices.

Bug fixes:

  • Scheduling
    • Downtime entry did not validate all fields correctly, and allowed downtimes to be created that did not correspond to any machine.
    • On the “Scheduled Jobs” side of the Scheduler, all jobs had the same start time. Now each job has it’s own projected start time.
  • Divide by zero error that has been lurking for two years. Caught in the wild by a review of customer log files.
  • Startup takes a long time when a diagnostics.sqlite file exists.

v5.0.14.276

New features:

  • Added more schedule summary details to dashboard.
    • Scheduled footage
    • Footage at the machine
    • Schedule completion date
  • Diagnostics
    • Server and Agent send their text logs (NLog) to the diagnostics ingress.
    • Agent sends comm logging to diagnostics ingress, when Express is enabled.

Bug fixes:

  • Applied a vendor supplied database hotfix for AlreadyClosedException.