Release Notes – Ignition 7.9
These Release Notes apply to MES modules designed for Ignition 7.9
MES Platform 3 (Release Candidate)
+ 3.79 General: All MES Products
Change Type | Change Log | Rev |
Improvement | Responsiveness and turnaround times when performing schedule delays has been improved. Redundant delays are now avoided, schedules are now cached, and schedule delays now happen asynchronously. | SP3 |
Fixed | Corrected an error where analysis could return a message saying there are multiple unequal values, consider adding the datapoint to group by when the column is already in the group by. This was caused by hash collisions on unequal group values. | SP3 |
Fixed | Multiple groups in analysis filter by will no longer cause no results to be returned. | SP3 |
Fixed | Added hidden, deprecated, versions of createOperation and createSegment that accept a boolean ignoreVersion parameter for backwards compatibility on scripts from Platform 2.0. | SP3 |
Fixed | When artifacts are removed from the system.mes.purgeArtifacts method, changelog data for that artifact version is also removed. | SP2 |
Fixed | Live analysis for Reject Count on cells should no longer lose counts. | SP2 |
Fixed | Importing an Area object into a licensed site will no longer throw an exception about being unable to find the Site parent. | SP2 |
Fixed | Corrected inverted import/export labels in MES Equipment Manager. | SP2 |
Fixed | Corrected inverted import/export labels in the MES Equipment Manager. | RC2 |
Fixed | Corrected an issue where, when grouping by time interval and using the Line Standard Count or Line Target Count or the Variance version of either data point, values would be less than expected if that time interval contained a shift change or day change. | RC2 |
Fixed | Corrected an issue when grouping by time interval and using the Line Standard Count, Line Target Count, or Variance version of either data point, values would be less than expected if that time interval contained a shift change or day change. | RC1 |
Improved | Updated SSL certificate. | Full Release |
—— | Production module was renamed from Release Candidate 4 (“RC4” suffix) to Full Release (no suffix). No code changes. | |
Fixed | On a new install, assigning a database in MES Settings will now cause the module to finish starting up. | RC4 |
Fixed | Prevented a race condition between cached object complex property checks and cache clearing. | RC4 |
Fixed | Connected Enterprise servers can now send data between an Ignition 7 Gateway and an Ignition 8 Gateway over the Gateway Network. | RC4 |
Fixed | Remove unnecessary calls from the Client or Designer to the Gateway on the Schedule View and Work Order Table vision components. | RC4 |
Fixed | Fixed a bug where multi-day operations that run through multi-day breaks would be calculated to have too long of a duration for the production rate. | RC4 |
Fixed | Eliminated a possible deadlock situation when setting up Enterprise connections. | RC4 |
Fixed | Response Segments that come from a Request Segment that still has class references will be replaced with definition objects if the segment is automatically begun. | RC4 |
Fixed | Equipment Complex Properties will now sync throughout the Enterprise when they are deleted. | RC4 |
Fixed | Updated for new Ignition 8 logic that changed how signed-in users are detected. This will cause the correct user to be logged when changes are made instead of ‘Unknown’. | RC4 |
Improved | Added support for byte, short, and float tag types in the Analysis Engine. | RC4 |
Improved | Schedule View has better handling of dragging schedules and does not refresh, causing the currently dragging schedule to reappear on the view. Dropping a schedule now correctly displays a waiting cursor. | RC4 |
Added | Schedule View has two new properties that can be used to prevent or delay updates when Equipment State or Equipment Mode changes. ‘State Update Interval Seconds’ will throttle the component to update at most once every given seconds. ‘Disable Mode and State’ Removes the Mode icon and Running background highlighting and Mode or State changes will not cause the component to update. | RC4 |
Fixed | Enterprise Import/Export no longer checks all options on clicking the Export button. Uncheck all Response Objects and Request Objects by default. | RC3 |
Fixed | Remove a potential deadlock when an analysis is executing, a schedule is being delayed, and an object is being modified. | RC3 |
Fixed | Corrected an error from RC2 where editing existing additional factor values would have no effect. | RC3 |
Fixed | Corrected an issue where Downtime Reason could be calculated using the wrong reason when the downtime was attributed to different equipment at the time the reason was recorded. | RC3 |
Fixed | Changing the Key Cell should now notify Analysis about the change without having to edit the Cell or Cell Group object. | RC3 |
Fixed | Editing an Equipment Object after assigning a new shift will not cause erroneous writes to the MESEquipmentShiftValue table in the time span between when the new shift was assigned and the end of the newly-assigned shift. | RC3 |
Fixed | Prevent operations that were not ended from re-starting if the equipment running the operation was deleted. | RC3 |
Improved | Optimized analysis engine to improve performance on calculators with many dependencies and when calculating downtime with an Equipment State Class that has many possible States. | RC3 |
Fixed | Issue where concurrently-running operations on a line reschedule. Only Request Segments related to the primary Operation will reschedule. | RC2 |
Fixed | Issues with upstream Operations when scheduling downstream operations of a route. | RC2 |
Fixed | First row of analysis showed the analysis Start Date instead of the appropriate value, in the case when the value occurred before the analysis Start Date. The calculators with this issue resolved are: ShiftStartDateTimeCalculator, StateBeginTimeCalculator, LineStateEventBeginCalculator, EquipmentOperationBeginDateCalculator, and ModeBeginTimeCalculator. | RC2 |
Fixed | Line calculation issue with reject counter. | RC2 |
Fixed | Issue where custom calculators not created by scripts in a gateway startup. | RC2 |
Fixed | Additional Factors with the same names preview correctly using the analysis engine. | RC2 |
Fixed | Datetimes in Custom Property editor in MES Object Editor use Ignition date formatting, to be consistent with binding and component Custom Properties. | RC2 |
Fixed | Unicode character support in import/export of Equipment States. | RC2 |
Fixed | The MES Monitor component no longer relies on the Reporting Module. | RC2 |
Fixed | Issue where repeating Segments set to absolute only run once. | RC2 |
Fixed | Fixed Issue where using plural Tag Collector functions caused error to be thrown when using singular functions. | RC2 |
Fixed | Issue where equipmentStateOptions throws GatewayException with missing UUIDs. | RC2 |
Fixed | Issue with cycle time calculators throwing a NPE. | RC2 |
Fixed | Issue where analysis selector slide out panes only translate in designer, but not in client. | RC2 |
Fixed | Issue where overdue Operations query listed same Operation UUID twice. | RC2 |
Fixed | Getting shifts for day correctly returns all shifts that _start_ within that day. | RC2 |
Fixed | All schedules defer to Ignition’s timeline parsing, which can be visualized in the Schedule View at the bottom of the Schedule Management component. | RC2 |
Fixed | Shifts that cross midnight are now handled correctly. | RC2 |
Fixed | configureCell Extension Function has been added to work order components. | RC2 |
Fixed | All queries with MSSQL are now prepended with {{SET NOCOUNT OFF;}}. This prevents the only known way that JDBC returns -1 to a non-select query. | RC2 |
Fixed | Issue where analysis manager would not restart on redundancy switch. | RC2 |
Fixed | The ‘Before’ field of the changelog export now includes that entire day. | RC2 |
Fixed | By default, always export definition objects to prevent missing source objects. Added more options for limiting what object types are exported. | RC2 |
Fixed | Prevent a deadlock between the MESObjectManager and the MESTagManager when editing equipment. Prevent RPC calls or gateway scripts while the module is starting up by returning errors. Use system.mes.isProductionStarted() to check for ‘started’ state. | RC2 |
Fixed | Missing required tag collectors will be created when validating the equipment or before opening the Tag Collector view in the Equipment Manager. | RC2 |
Fixed | On an upgraded system, the counter and additional factor IDs will change to match the 2.0 IDs. | RC2 |
Fixed | Issue with filtering of State and Mode Duration calculators in Analysis Engine. | RC2 |
Fixed | Manifest and Manifest Classes can now be deleted via the MES Equipment Manager. | RC2 |
Fixed | When using an Oracle DB, Additional Factors analysis queries will no longer throw exceptions. | RC2 |
Fixed | MESObjectLink compareTo now respects transitivity. This could lead to uncommon errors when sorting MESObjectLinks. | RC2 |
Fixed | Removed subquery from Additional Factors and counter queries, to improve performance. | RC2 |
Fixed | During the Enterprise upgrade, the Lot Equipment Reference UUID will be updated to match the new UUID for the <any equipment> and <any supplemental equipment> Equipment Classes. | RC2 |
Fixed | Enterprise Export includes the current state for objects with no change history. | RC2 |
Fixed | Prevent possible SQL deadlock when deleting complex properties. | RC2 |
Fixed | executeImmediately no longer requires having the OEE Module installed. | RC2 |
Fixed | Issue where select top queries on MSSQL would grab all rows. | RC2 |
Fixed | Fixed locking order on reading from the schedule cache, to prevent deadlocking when simultaneous threads are reading and updating the schedule cache data. | RC2 |
Fixed | Improved behavior when pushing out modules from EAM. | RC2 |
Fixed | Export and apply current property values for complex properties. | RC2 |
Fixed | Cache MES Object Event Scripts to avoid unnecessary DB calls. | RC2 |
Fixed | In an Enterprise setting, if scripts are detected to have a different ArtifactRefUUID than the Enterprise, the ArtifactRefUUID will be updated to match the Enterprise and the Enterprise Artifact will be synced down. | RC2 |
Fixed | Change locking order when updating equipment in the Analysis Engine, to prevent conflicting with the Object Manager. | RC2 |
Fixed | Scheduled Operations crossing midnight twice causing issues in scheduling. | RC2 |
Fixed | Use parent object to determine sync servers in addition to child servers. | RC2 |
Fixed | Copy and paste on licensed equipment no longer throws an exception. Equipment must be licensed after pasting. | RC2 |
Fixed | Maintain existing behavior with 2.0 where updating non-existent tag value throws an exception rather than creating the value. Prevent duplicate Tag Collector values for the same timestamp. | RC2 |
Fixed | Attaching a site to an Enterprise will sync down all Operations with the synced equipment. | RC2 |
Fixed | Only ‘N’ prefix on user-entered columns in MSSQL. Columns such as UUID do not use the prefix. | RC2 |
Fixed | Blank Require Roles to Edit MES Scripts no longer causes exceptions. | RC2 |
Improved | Creation of a ‘Cleaning’ mode type. | RC2 |
Improved | Added back removed arg for system.mes.getAvailableReferenceOptions, to maintain backwards compatibility. Added a new field for useDerivedFromObject. | RC2 |
Improved | Reduce Enterprise sync logging from INFO to DEBUG, to prevent filling logs. | RC2 |
Improved | MES Work Order Filter get/setClosedBeginDate & get/setClosedEndDate operate as expected on closed date. Addition of get/setDueBeginDate and get/setDueEndDate methods to operate on a due date. | RC2 |
Improved | The Equipment Manager’s Equipment is now translated. If an item is about to be modified, it will revert back to its original text for ease of editing. When it is done being modified, it will perform a translation that only affects the GUI. | RC2 |
Improved | The various tables found in the Equipment Manager’s editors will now translate their cell contents and column names. The effect is cosmetic only, and does not affect the underlying data. | RC2 |
Improved | Minimum time between two sequential schedule items is one second instead of one minute. | RC2 |
Improved | Default Store Rate on new MES Counters is now 60 instead of 0. | RC2 |
Added | Logs have been improved for failed MES Object loading attempts that should help Support better identify them in the database. | RC2 |
Added | system.mes.invalidateTranslationCache() can now be called via Client Script to clear cached translations. | RC2 |
Added | Added a warning Dialog that informs user that it is difficult to un-sync Equipment linked to a Server in the Enterprise Network. Caution should be taken before committing (saving) Equipment. | RC2 |
+ 3.79 OEE Module
Change Type | Change Log | Rev |
Fixed | Calling system.mes.getTagCollectorLastTimeStamp will no longer effect the increase amount in Positive Change. | SP3 |
Fixed | Equipment Manager Counter Edit View now allows rollover values less than 32748. | SP3 |
Improved | The MES Equipment Manager’s Equipment is now translated. If an item is about to be modified, it will revert back to its original text for ease of editing. When it is done being modified, it will perform a translation that only affects the GUI. | RC2 |
Improved | The various editor sub-views within the MES Equipment Manager have also been updated to translate their visible GUI contents, as well as translate editable text that is not currently being modified. | RC2 |
Improved | The various tables found in the MES Equipment Manager’s editors will now translate their cell contents and column names. The effect is cosmetic only and does not affect the underlying data. | RC2 |
Improved | The OEE Downtime Table and its sub-views are now translated in a similar manner to the MES Equipment Manager. This means that the Editors will be translated, table cell and column contents will be translated, and editable text not currently undergoing modification will be translated. | RC2 |
Improved | The Bar and Pie Charts will now translate their titles, chart labels, and legend items. | RC2 |
Improved | The Bar Chart will now translate its axis labels. | RC2 |
Fixed | Issue with Key Reason cell calculator with disabled States under a Key Reason calculator. | RC2 |
Improved | The MES Equipment Manager’s Equipment is now translated. If an item is about to be modified, it will revert back to its original text for ease of editing. When it is done being modified, it will perform a translation that only affects the GUI. | RC2 |
Improved | The various editor sub-views within the MES Equipment Manager have also been updated to translate their visible GUI contents, as well as translate editable text that is not currently being modified. | RC2 |
Improved | The various tables found in the MES Equipment Manager’s editors will now translate their cell contents and column names. The effect is cosmetic only and does not affect the underlying data. | RC2 |
Improved | The OEE Downtime Table and its sub-views are now translated in a similar manner to the MES Equipment Manager. This means that the Editors will be translated, table cell and column contents will be translated, and editable text not currently undergoing modification will be translated. | RC2 |
Improved | The Bar and Pie Charts will now translate their titles, chart labels, and legend items. | RC2 |
Improved | The Bar Chart will now translate its axis labels. | RC2 |
Added | system.mes.invalidateTranslationCache() can now be called via Client Script, to clear cached translations. | RC2 |
—— | OEE Downtime module was renamed from Release Candidate 4 (“RC4” suffix) to Full Release (no suffix). No code changes. | FR |
Fixed | If a Neighbor-Priority Key is a Cell Group, and it is Blocked or Starved, it can now identify the cause if the blame belongs to one of its siblings (as opposed to its children). | RC4 |
Fixed | Corrected an error where States and State Classes created prior to the introduction of ‘Override Current Line Downtime’ would be treated as False instead of True. Treating the states as True provides the same behavior as prior to the introduction of this option. | RC4 |
Fixed | ‘Equipment Original State’ value source’s Postgres query’s syntax error has been resolved. | RC4 |
Fixed | Corrected an issue where splitting an event on a cell can cause downtime analysis to falsely attribute subsequent events to be rolled up to the cell the event was split from. | RC4 |
Fixed | Prevented a Stack Overflow from occurring, due to Starved and Blocked Cell Groups attempting to blame each other when a downtime reason is absent. | RC4 |
Fixed | Unplanned Downtime is now a trigger for Neighbor Priority. This corresponds with the documentation. | RC4 |
Fixed | Neighbor Priority Downtime events now carry the correct Equipment info to blame, as well as updated Timestamps. This prevents unwanted Roll-Up behaviors that were happening for certain edge-cases where States would flip back-and-forth often. | RC4 |
Fixed | The Neighbor Priority Downtime event is no longer one step behind. The last Downtime Event is no longer forcibly used as the current. | RC4 |
Added | Equipment Infeed Scale factors into OEE Quality Score. | RC4 |
Added | Added more control over OEE Time Chart State and Mode colors by accepting a Python method to determine the correct color. | RC4 |
Added | Added new Analysis Datapoints under Equipment/Line/Schedule/Entry that use Operation Schedules instead of Operations Responses. This requires includeFuture = True in Analysis Settings to analyze future operations. | RC4 |
Fixed | Resolved issue where downtime that occurred at the same time on multiple Cells were incorrectly being rolled up into a single event. | RC3 |
Fixed | Issue with key reason cell calculator with disabled states under a key reason calculator. | RC3 |
Fixed | Initial Cell Downtime Detection will no longer lock onto a cell that returns to a running state. This was caused by any surrounding blocked/starved cells (that have not recovered yet) forwarding fault to the initially-downed cell. | RC3 |
Fixed | Resolved a layout issue with the OEE Downtime Table where while using the grid view, the equipment or state boxes could be missing until a repaint. | RC3 |
Fixed | Fixed an issue where analysis would latch onto a more-recent line downtime event when using initialCell downtime detection mode when the line goes down and comes back up while a cell is currently down. | RC3 |
Fixed | Initial Cell compares cell order on the common parent, to account for nested Cells and Cell Groups. | RC3 |
Fixed | The Line Availability MES Tag will now show False during breaks in the schedule. | RC3 |
Fixed | When using Live Analysis that calculates OEE Reject from OEE Infeed – OEE Outfeed, the previously-cached OEE Reject value is discarded and re-calculated from the current OEE Infeed and OEE Outfeed values. | RC3 |
Added | Overloaded setDowntimeDetectionMode(string name) to Equipment objects. | RC3 |
Added | Added getDowntimeDetectionModeNames() to Equipment objects. | RC3 |
Fixed | Standard Rate for Hour is now entirely dependent on the coverage of the clock hour containing From Date by shift segments. For example, with an analysis row with From Date as 12:30, and assuming that the shift in question is 8:00-12:30, 12:45-16:30, the Standard Rate for Hour would be based on the 45 minutes of coverage within 12:00-13:00. | RC2 |
Fixed | Issue where End State time stamp listed same as State time stamp. | RC2 |
Fixed | Issue where running Operations Responses do not appear with function getOperationsResponses(). | RC2 |
Fixed | Downtime reasons coming from blocked/starved cell groups do not mark as unknown. | RC2 |
Fixed | Issue where disk cache from live analysis would keep filling up without deleting old live analyses. | RC2 |
Fixed | Prefixed strings with `N’` when interfacing with MSSQL to support Unicode encoding. Note that this will only be supported if the columns written to are an `NVARCHAR` variant (`VARCHAR` does not support Unicode). | RC2 |
Fixed | Splitting downtime event that started during changeover shows Start Time appropriately. | RC2 |
Fixed | Material unassigned from a line no longer appears in the Run Director component. | RC2 |
Fixed | Issue where reverted downtime event blocks note from displaying for original event. | RC2 |
Fixed | Issue where split events would cause display issues on OEE Time Chart. | RC2 |
Fixed | Issue where auto schedule by time completes after double the time. | RC2 |
Fixed | Tooltips no longer included colons. | RC2 |
Fixed | Issue where Operations would generally start one minute after scheduled. | RC2 |
Fixed | Issue where cycle count had offset of 2 instead of an offset of 0. | RC2 |
Fixed | Issue where scheduled item starting in the same minute the current Operation ends cannot start until the next minute. | RC2 |
Fixed | Issue where split event would split into more than two events with child cells and/or setting the line state directly. | RC2 |
Fixed | Issue where downtime events around the end of the run do not have an end date. | RC2 |
Fixed | OEE Downtime Detection Mode dropdown now properly selects the current value in the dropdown when opening the view. | RC2 |
Fixed | Prevent duplicate <Any *> classes from being created. | RC2 |
Fixed | Change Equipment on the OEE Downtime Table now uses the correct subpath in grid and list views. | RC2 |
Fixed | When analysis is checking for duplicate counts, it will now iterate through the smaller set. | RC2 |
Fixed | Rescheduling Operations to another line correctly changes the Operation to the new line on both routes and single operations. | RC2 |
Fixed | Live Analysis shift datapoints no longer go stale. | RC2 |
Fixed | Issue where material on Process Segment named ‘Material Out’ with same material and equipment as OEE Segment conflicts in the OEE Run Director. | RC2 |
Improved | MES Schedule View getToolTipText extension function now supports Ignition and production schedules. | RC2 |
Improved | Add “Override Current Line Downtime” state flag and functionality for key reason downtime detection methods. | RC2 |
Improved | The OEE Downtime Table and its sub-views are now translated in a similar method to the MES Equipment Manager. This means the Editors will be translated, table cell and column contents will be translated, and editable text not currently undergoing modification will be translated. | RC2 |
Improved | The Bar and Pie Charts will now translate their titles, chart labels, and legend items. | RC2 |
Improved | The Client Script function .getEquipmentStateOptions() has been given a performance update. Users should find that the scripting function’s turnaround time will be lower on average, and have a tighter standard deviation. | RC2 |
Improved | The Bar Chart will now translate its axis labels. | RC2 |
+ 3.79 Track & Trace Module
Change Type | Change Log | Rev |
—— | Track & Trace module was renamed from Release Candidate 4 (“RC4” suffix) to Full Release (no suffix). No code changes. | FR |
Fixed | system.mes.getLotList(filter) filters out duplicate MESObjects in the SQL query, preventing a situation where the returned number of objects was less than the set max results. | RC4 |
Fixed | Gateway scoped system.mes.executeSegmentImmediatly() has same return as client scope. | RC4 |
Improved | Significant performance improvement for system.mes.getLotInventoryByEquipment and Equipment WIP Inventory Binding when the number of lots at that equipment is large. | RC4 |
Improved | Added index on MESEquipment for MESEquipmentUUID and Name, as this showed a dramatic decrease in query execution time for queries made by system.mes.getLotList(filter). | RC4 |
Fixed | Zero Lot Threshold field in the MES Equipment Manager now allows decimals as it originally should have. Scripting is unaffected. | RC2 |
Fixed | Fixed errors in getAvailableRefenceOptions when adding and removing parent objects. | RC2 |
Fixed | Prevent circular dependency from causing stack overflow when loading associated equipment paths for a Segment that has a Material property, with lots being stored in Supplemental Equipment, that is a part of an Equipment Class. | RC2 |
Fixed | An Operation that specifies a specific Manifest rather than a Manifest Class will let that Manifest be chosen at run time. | RC2 |
Fixed | If a complex property is added then removed while still new, allow the match to be by name only. | RC2 |
Fixed | Resolved concurrency issues with trace queries. | RC2 |
Fixed | Get an Operations Definition from a Response Segment by going through the derived from Segment instead of Operations Response. | RC2 |
Fixed | Issue where material on Process Segment named ‘Material Out’ with same material and equipment as OEE segment conflicts in OEE Run Director. | RC2 |
Improved | Equipment Operation Scheduled Begin/End, Equipment Operation Original Begin/End, and Equipment Operation End analysis datapoints. | RC2 |
Improved | Added lot caching, to improve performance of finding available lots. | RC2 |
Improved | Supplemental Equipment has an equipment path editable through the MES Object Editor. Associated equipment and lot methods can take advantage of this new feature. | RC2 |
+ 3.79 Settings & Changeover
Change Type | Change Log | Rev |
Fixed | Removed a deprecated Recipe Change Log invalidation call that had the potential to deadlock the MES database. | RC2 |
Fixed | The Recipe Value columns have been incremented to size 1024 from 255. This is to support better backward compatibility with MES Platform 2.0. | RC2 |
Fixed | The Recipe Lists are now sorted alphabetically. | RC2 |
Fixed | Saving Recipe Values via components or scripting should no longer cause an MESItemRecipe version mismatch issue. | RC2 |
Fixed | Repaired issue where Default Equipment Recipes would randomly show a Sub-Recipe’s values. | RC1 |
Fixed | Repaired an issue where Sub-Recipes would be randomly deleted. | RC1 |
Fixed | Equipment Items no longer require a SubProductCode in order to read Recipe Values. | RC1 |
Fixed | The Recipe Change Log Viewer now automatically invalidates stale cached results. | RC1 |
Fixed | The Recipe Editor will now show Default Values if a Sub-Recipe is not found for Equipment using Sub-Product-Code-Masks. | RC1 |
Fixed | The constant stream of OPC Tag errors has been suppressed. | RC1 |
Fixed | The Recipe Variance Viewer’s Recipe name filters no longer empty out the analysis results. | RC1 |
Fixed | The Recipe Tree Editor will only show the Equipment Paths that it absolutely must. Valid Equipment must be selected and have at least 1 Default Recipe Value with a Tag bound to it. Alternatively, the Equipment must have a child that satisfies these conditions. | RC1 |
Fixed | The Recipe Name Filter has been repaired. | RC1 |
Fixed | Restored missing Recipe Change Log filter functions. | RC1 |
Fixed | Saving a Recipe without a parent no longer throws an Null Pointer Exception. A Parentless Recipe will now automatically be assigned as a child to the Recipe Root object. | RC1 |
Fixed | Equipment-Default and Parent-Recipe modes are now visibly differentiable in the Recipe Editor. | RC1 |
Fixed | Restored the Recipe Editor’s ability to show Area Values. | RC1 |
Fixed | The Recipe Editor’s Assigned-By values will now show the correct information if a default value is being inherited. | RC1 |
Fixed | The Recipe Editor’s Master Recipe hider has been restored. | RC1 |
Fixed | The ability to retrieve Default Values via script has been restored. | RC1 |
Fixed | The back-end will now automatically filter out Deleted Recipes and Item Recipes when performing various recipe-related tasks. | RC1 |
Fixed | The Default Recipe Value Editor will only save the actual value if the Tag-Path is dirty. Otherwise, it will continue using whatever the last set value was. | RC1 |
Fixed | Corrected poor error messaging when attempting to delete non-existent Recipes and Sub-Recipes. | RC1 |
Fixed | .changeRecipeGroup() and .changeRecipeState() now function correctly. | RC1 |
Fixed | .setLiveRecipeValue(), .getCurrentItemRecipe(), .isItemRecipeMonitoringEnabled(), .setItemRecipe() and .cancelItemRecipe() now function for Platform 3.0. | RC1 |
Fixed | Restored missing overloads for deprecated .getItemRecipeList() functions with .getEquipmentRecipeList(). | RC1 |
Fixed | Changes to Default Recipe Value Tag Paths will automatically transfer the updated Tag Meta Data to the Default Recipe Value. | RC1 |
Fixed | Deleting Equipment will now cause related Item Recipes to also be deleted. | RC1 |
Fixed | Renaming Equipment will now cause related Item Recipes to also be renamed. | RC1 |
Fixed | Default Recipe Values can now be inherited between Equipment Items. | RC1 |
Fixed | The Recipe 3.0 Recipe Editor will now properly show Default Value Inheritance, similar to the Equipment Editor. | RC1 |
Fixed | Uninstalling the Recipe module without a Gateway Restart will no longer prevent Equipment from being created/altered. | RC1 |
Fixed | Equipment can now perform Select Recipes command even if they are currently undergoing OEE operations. | RC1 |
Fixed | Recipe scripting functions will now return the names of their parent and child Recipes. | RC1 |
Fixed | Sub-Product-Code-Masks now influence Sub-Recipes when determining Recipe Default Values. | RC1 |
Fixed | Pasting Default Recipe Values will no longer cause ownership errors. They will now save and delete properly. | RC1 |
Fixed | Disabled Default Recipe Values in working memory no longer conflict with Delete-All command in the Default Recipe Value Editor. | RC1 |
Fixed | Tags no longer overwrite the Default Recipe Value name in the Edit View. | RC1 |
Fixed | Equipment listed in the Recipe Editor will now have the correct parent/child relationships. | RC1 |
Fixed | Recipe Set Point Value history now displays correctly in Analysis. | RC1 |
Fixed | Recipe Value Sort Orders are now used. | RC1 |
Fixed | Null Pointer Exception no longer thrown when editing Default Recipe Values for the first time on Equipment. | RC1 |
Fixed | Enterprises, Sites and Areas no longer require Recipe license checks. This is because they only supply Recipe meta-data and are unable to make functional use of Set-Point/Changeover software. | RC1 |
Fixed | Sub-Recipes will no longer appear in the Recipe Selector List. | RC1 |
Fixed | Sub-Recipes will no longer appear in the MES Object Editor’s Segment editors. | RC1 |
Fixed | Equipment Recipes are now identified by Equipment Name and Equipment UUID. | RC1 |
Fixed | The Recipe Editor will no longer overrides child Recipes that have already been overridden by the child. | RC1 |
Fixed | Locations, Storage Zones and Storage Units are now eligible for Recipe Selections. | RC1 |
Improved | The Recipe Change Log Viewer’s refreshing logic now executes on a separate thread for better performance. | RC1 |
Improved | Replaced a Recipe Scripting Function Null Pointer Exception with a more informative error message. | RC1 |
Improved | It is now easier to link MES-Equipment to MES-Recipes. | RC1 |
Improved | Modified the Recipe Selection Algorithm to improve performance. The MESRecipeSetPointComplexProperty has been removed. | RC1 |
Improved | Added Recipe Selection Monitoring. More precise Monitoring can be seen using Debug Mode. The MESRecipeVarianceManager may be further set to DEBUG level in the Gateway, to see even further-detailed timing. | RC1 |
Improved | ‘Sub-Recipe’ MESObjectTypes have now been implemented. | RC1 |
Improved | The Recipe List now populates much more quickly and will avoid overloading the MES Cache. | RC1 |
Improved | Saving, Selecting, and Canceling Equipment and Recipe objects now runs more efficiently. The Cache will no longer become overwhelmed by computationally-simple Recipe selections/cancellations. | RC1 |
Improved | A Row Limit has been added to the Recipe Change Log filters, to prevent accidental overuse of memory when querying large amounts of data. If the user does not provide a limit, the default value of 2000 is used. The Recipe Change Log Viewer and Recipe Change Log Filter both support this new feature. | RC1 |
Improved | The Administrator Role is no longer relied on as the default role. Recipe Security will automatically enforce a Tag’s Engineering Limits on all users. If a Value completely lacks security settings, any user may edit it until security is set. | RC1 |
Added | The Recipe Change Log Viewer now supports an ‘Auto Refresh’ property. If True, Recipe Change Events can trigger a refresh. | RC1 |
Added | The Default Recipe Value complex property (MESRecipeValueDefComplexProperty) can now accept a String for .setRecipeDataType(). | RC1 |
Added | The PMI Recipe Editor Designer component now displays a confirmation prompt when a user tries to delete a Recipe. | RC1 |
Added | Legacy Recipe OPC Tags have been reconstructed to support backwards compatibility. This will help reduce the minimum amount of changes required for users who wish to upgrade their older systems. | RC1 |
Added | When selecting a Recipe, its Set Points will be applied to the associated tags. | RC1 |
Added | Recipe Set Point Tag Changes (Recipe Variance) is now handled by the MES Tag Collectors. | RC1 |
Added | When Dropping a Tag into the Default Recipe Value Editor, the user may now opt to include the Tag’s folder path (or partial path) as part of the Default Value’s name. | RC1 |
Added | Sub Product Code masks can now be assigned to Equipment, via the Recipe Value Editor in the Equipment Manager. | RC1 |
Added | Recipe inheritance modes can be changed in the Recipe Value Editor in the Equipment Manager. The modes are the same as Recipe 2.0, featuring ‘Equipment Default’ and ‘Parent Recipe’ modes. | RC1 |
Added | Inherited Default Recipe Values can now be hidden in the Equipment Manager’s Recipe Value Editor. This can be done by unchecking the ‘Show Inherited Values’ checkbox, which will hide all values that have not been explicitly overridden. | RC1 |
Added | Recipe 2.0 Default Recipe Value .csv export files are compatible with Platform 3.0. | RC1 |
Added | Default Recipe Value editing is now available for Platform 3.0. | RC1 |
Added | Tags can now be dragged and dropped into the Default Recipe Value Editor. Multiple Tags may be dropped at one time. Warnings will be shown if entries with the same name are detected. | RC1 |
Added | Recipe Data Points have been added to Analysis. | RC1 |
Added | ‘Current Active Recipe Period’ has been added as a Live Analysis Time Period. | RC1 |
Added | Recipe 2.0 systems can now be upgraded to Platform 3.0 after an initial Enterprise migration is performed. | RC1 |
Added | Recipe Change Log data is now cached. Relevant Recipe Tag Collector changes will invalidate cache entries as necessary. Client and Gateway scripts have also been provided, so that users may manually invalidate the Recipe Change Log cache as well. | RC1 |
Added | The Recipe Editor Table is now functional in Platform 3.0. | RC1 |
Added | The Recipe Variance Viewer has now been refactored to continue working in Platform 3.0. | RC1 |
Added | The Default Recipe Value Editor now supports Tag Indirection. | RC1 |
Added | Default Recipe Values from Platform 2.0 can be imported into Platform 3.0. Doing so will convert all Value Calculation and Variance scripts into consolidated Platform 3.0 MES scripts. | RC1 |
Added | Recipe enabling and scaling is now handled by a new Platform 3.0 Tag Collector. | RC1 |
Added | system.recipe.getParentRecipe() has been implemented. It differs from the now-deprecated .getRecipeParent() in that it will throw an MESObjectNotFoundException if the named Recipe argument does not exist. | RC1 |
Added | system.recipe.getDescendantRecipes() has been implemented. It differs from the now-deprecated .getRecipeDescendants() in that it will throw an MESObjectNotFoundException if the named Recipe argument does not exist. | RC1 |
Added | Recipe Event handling scripts now exist as MES Scripts. Recipe Selection, Cancellation, Value Calculation, and Variance Evaluation Scripts can now be created and attached to Recipes and their values. | RC1 |
Added | Recipe Value Set Points may be optionally protected from being changed by certain users. A general value range can be assigned to the Tag, and additional limits can be added bases on Ignition Roles. | RC1 |
Added | When selecting or canceling Recipes, the respective Recipe Event scripts will fire. | RC1 |
Added | Recipe Value event scripts can be bound to individual Default Recipe Values with monitoring enabled. When a Recipe is selected, Request-Value scripts will fire for each Recipe Value. Likewise, Evaluate-Variance scripts will fire upon a Recipe Value Tag change (not on a variance!). | RC1 |
Added | Recipe items synchronize to servers based on what Production Equipment uses the recipe. Recipe vertical table data syncs up from children to the Enterprise. | RC1 |
Added | A warning dialog will be displayed if the user assigns a Default Recipe Value Name that is already in use. | RC1 |
Added | The Recipe Selector List no longer allows Enterprises, Sites or Areas to select Recipes. An Exception is now thrown. | RC1 |
Updated | The Recipe Module will now be known as the ‘Settings and Changeover’ Module. Back-end changes, such as the concept of Recipes and scripting function signatures will not be altered, to protect backwards compatibility. | RC1 |
Updated | The Recipe 3.0 Change Log has traded its ‘ChangeLogUUID’ column for the ‘CommitTimeAndSequence’ column in the main Platform 3.0 Change Log system. Likewise, the ‘ChangeSetUUID’ has been swapped out with the ‘ChangeSequenceNumber’ column. | RC1 |
+ 3.79 Document Management Module
Change Type | Change Log | Rev |
—— | Production module was renamed from Release Candidate 4 (“RC4” suffix) to Full Release (no suffix). No code changes. | FR |
Added | Addition of Document Management module. | RC2 |
Platform 2 (Stable)
+ 2.79 General: All MES Products
Change Type | Change Log | Rev |
Fixed | Corrected an error where analysis could return a message saying there are multiple unequal values, consider adding the datapoint to group by when the column is already in the group by. This was caused by hash collisions on unequal group values. | SP8 |
Fixed | Multiple groups in analysis filter by will no longer cause no results to be returned. | SP8 |
Fixed | Live analysis for Reject Count on cells no longer loses counts. | SP7 |
Improved | Updated SSL certificate. | SP7 |
Improved | Added internal caching of Ignition Schedules, to improve performance. Changes to existing Ignition Schedules can take up to 1 hour to be reflected in MES. Calling system.mes.invalidateCache() clears cache and forces reload of Ignition Schedule. | SP7 |
Added | Missing scripting function system.mes.getTagCollectorPastTimeStamp(equipmentPath, collectorType, key, lookBackCount, endDate) added to Gateway scope. | SP7 |
Fixed | Remove unnecessary calls from the Client or Designer to the Gateway on the Schedule View and Work Order Table Vision components. | SP5 |
Fixed | Work Order Table extension function onColumnsCreate no longer throws an exception when adding new columns. | SP5 |
Improved | Schedule View has better handling of dragging schedules and does not refresh causing the currently dragging schedule to reappear on the view. Dropping a schedule now correctly displays a waiting cursor. | SP5 |
Added | Schedule View has 2 new properties that can be used to prevent or delay updates when equipment state or mode changes: (1) “State Update Interval Seconds” will throttle the component to update at-most once every given seconds. (2) “Disable Mode and State” removes the Mode icon and Running background highlighting, and Mode or State changes will not cause the component to update. | SP5 |
Fixed | Positive Count Mode ignores any 0 to N transition. | SP4 |
Fixed | Fixed a bug where multi-day operations that run through multi-day breaks would be calculated to have too long of a duration for the production rate. | SP4 |
Fixed | Resolved an issue where while a machine is in an idle mode that does not include OEE, the state was incorrectly being calculated as Unplanned Downtime. | SP4 |
Fixed | Fixed locking order on reading from the schedule cache to prevent deadlocking when simultaneous threads are reading and updating the schedule cache data. | SP4 |
Fixed | Removed subquery from Additional Factors and counter queries, to improve performance. | SP4 |
Fixed | Errors during Legacy Imports are now handled more gracefully. The To-Date will no longer update, unless the import task is successful. | SP4 |
Fixed | A success message will no longer print if import fails. | SP4 |
Fixed | Reduce the number of network calls from Designer to the gateway when viewing the Production Model in the project browser tree. | SP4 |
Fixed | Issue where Rollover counter mode not respecting previously-edited counter values. | SP4 |
Improved | Import Phase and Step information is now displayed, to give users a better time estimate when watching the progress bars fill. | SP4 |
Improved | The ‘To Date’ seen on the Legacy Import Page is now visible, to make it easier to pick a reasonable ‘From Date’, as well as highlight date-range bugs/errors. | SP4 |
Improved | Error logs now contain more specific detail if something goes wrong during import. | SP4 |
Added | Added a hidden Analysis Setting called ‘Timeout Seconds’. This takes an integer value, allowing users to alter the auto-timeout from its default 60 seconds. A maximum of three concurrent 61+ second Analysis are permitted. | SP4 |
Added | The MES Legacy Import Page now contains a new option under Import OEE Run History. It is a checkbox that allows users to ignore importing values for Additional Factors that are do not have a definition. | SP4 |
Added | A Problematic Name Handler can now be selected on the Legacy Import Page. They are used to handle issues revolving around Platform 1.0 object names no longer being legal in Platform 2.0. | SP4 |
Fixed | Unicode character support in import/export of Equipment States. | SP3 |
Fixed | Issue where removeTagCollectorValues, updateTagCollectorValues, addTagCollectorValues function use later makes use of removeTagCollectorValue, updateTagCollectorValue, addTagCollectorValue respectively throw an error. | SP3 |
Fixed | Each text is translated based on current locale. Previously, most of these fields were preloaded with the translations of locales upon initialization, but did not account for change otherwise. Also, each tooltip text was built with StringBuilders, translating each attribute name with its colon, so I made a builder that translates those names without their colons. This can be easily applied to any other tooltip with localization issues. | SP3 |
Fixed | Issue where the Analysis Selector slide out panes only translate in Designer, but not in the Client. | SP3 |
Fixed | Shifts that cross midnight now yield the correct Shift State Date and Shift State Date Time. | SP3 |
Fixed | Getting shifts for the day now correctly returns all shifts that start within that day. | SP3 |
Fixed | Time segments correctly merge into shifts when they are close enough. | SP3 |
Fixed | The code now more accurately views time as a continuous construct. Midnight isn’t a special case that requires another method. | SP3 |
Fixed | All schedules defer to Ignition’s timeline parsing, which can be visualized in the schedule view at the bottom of the Schedule Management component. | SP3 |
Fixed | Shift End Date truncates to the midnight a week after the day for which shifts are being read. | SP3 |
Fixed | Issue where select top queries on MSSQL would grab all rows. | SP3 |
Fixed | Only ‘N’ prefix on user-entered columns in MSSQL. Columns such as UUID do not use the prefix. | SP3 |
Improved | Creation of a ‘Cleaning’ Mode type. | SP3 |
Fixed | Issue where Oracle timestamps were sensitive to locale. | SP2 |
Fixed | Issue where concurrently running operations on a line reschedule. Only request segments related to the primary operation will reschedule. | SP2 |
Fixed | Issues with upstream operations when scheduling downstream operations of a route. | SP2 |
Fixed | First row of analysis showed the analysis start date instead of the appropriate value in the case when the value occurred before the analysis start date. The calculators with this issue resolved are: ShiftStartDateTimeCalculator, StateBeginTimeCalculator, LineStateEventBeginCalculator, EquipmentOperationBeginDateCalculator, ModeBeginTimeCalculator. | SP2 |
Fixed | Line calculation issue with reject counter. | SP2 |
Fixed | Custom calculators can now be used within gateway startup scripts. | SP2 |
Fixed | Multiple Recipe Editor onCopy/onPaste behavior fixes and improvements. | SP2 |
Fixed | Additional factors with the same names preview correctly using the analysis engine. | SP2 |
Fixed | Datetimes in custom property editor in MES Object Editor use Ignition date formatting to be consistent with binding and component custom properties. | SP2 |
Fixed | Issue where repeating segments set to absolute only run once. | SP2 |
Fixed | Issue where equipmentStateOptions throws GatewayException with missing UUIDs. | SP2 |
Fixed | Issue with cycle time calculators throwing a NPE. | SP2 |
Fixed | Issue where overdue operations query listed same operation UUID twice. | SP2 |
Fixed | Extension script function has been added to Work Order Table. | SP2 |
Fixed | All queries with MSSQL are now prepended with {{SET NOCOUNT OFF;}}. This prevents the only known way that JDBC returns -1 to a non-select query. | SP2 |
Fixed | Issue where analysis manager would not restart on redundancy switch. | SP2 |
Fixed | Issue with filtering of State and Mode Duration calculators in Analysis Engine. | SP2 |
Improved | MES Work Order Filter get/setClosedBeginDate & get/setClosedEndDate operate as expected on closed date. Addition of get/setDueBeginDate and get/setDueEndDate methods to operate on a due date. | SP2 |
Improved | Internal index/schema management within factor and count tag collectors. | SP1 |
Improved | Improved concurrency of system.mes.searchMESObjects. | SP1 |
Improved | Translation performance when repeating the same performance. | SP1 |
Improved | Adding entries in the MES Value Editor gives the option to update following values. Scripting function addTagCollectorValue also has overloaded version with ‘updateFollowing’ flag. This only applies to MESEquipmentCountTagCollector and MESEquipmentCycleCountTagCollector. | SP1 |
Improved | Internal messaging from tag collectors to client components. | SP1 |
Improved | Ensured that “Save” button text is translated on MES Object Editor. | SP1 |
Fixed | After editing values in the MES Value Editor, tag collectors are still able to record the next change. | SP1 |
Fixed | Issue where resynchronized users could have the last name set as the first name. | SP1 |
Fixed | MES Work Order Table column settings on language change. | SP1 |
Fixed | getTagCollectorPreviousTimeStamp() function returns passed in timestamp if it exists instead of only returning previous timestamps. | SP1 |
Fixed | Irrelevant custom properties do not retrigger Analysis Controller. | SP1 |
Fixed | Issue where a deadlock could occur on Production Module startup. | SP1 |
Fixed | Issue where a deadlock could occur while indexing products on a line. | SP1 |
Fixed | Issues with internal schedule cache. | SP1 |
Fixed | Deadlock condition in AbstractMESObject.getPropertyValue. | SP1 |
Fixed | Available Begin/End Date reflect next upcoming shift in “Shift” tag folder. All other related shift columns reflect past shift. | SP1 |
Fixed | Issue where MES Counters with store rates other than 0 were storing values to wrong date. | SP1 |
Updated | Updated all module version numbers to 2.79.0. | SP1 |
—— | ———— Above this line, all modules are renamed to 2.79.x and release notes begin at SP1 ———————— | — |
Improved | Manually executing an operation that is scheduled at a past date will push it forward to the current date. If this happens, any overlapping operations will be pushed forward to the earliest available time slots. | SP13 |
Improved | Automatically executing schedules that do not execute on time will move forward to the current time. If this happens, any overlapping operations will be pushed forward to the earliest available time slots. | SP13 |
Added | New “User Scheduled Begin” and “User Scheduled End” columns to the MES Schedule Selector, which display the most recently begin and end times that were scheduled by the user (before any system delays). | SP13 |
Fixed | Issue where rescheduling an operations schedule could use the wrong scheduling method. | SP13 |
Fixed | When performing analysis, a dialog window warns users that they are missing an Equipment Path Filter-By expression. This warning will no longer prevent analysis results from being returned. | SP13 |
Fixed | Analysis cycle data was improperly nullified if the cycle’s time spanned multiple analysis dataset rows. Only partially included cycles found at the beginning and end of an analysis dataset will be nullified. | SP13 |
Fixed | Issue where schedule duration was not properly set by system.mes.scheduleOperations. | SP13 |
Fixed | Issue where schedule entries did not delay properly on Linux with MySQL. | SP13 |
Fixed | Issue where the downtime note calculator could throw an error for equipment that had no downtime notes. | SP13 |
Fixed | Issue where rescheduled operations could sometimes have the wrong duration. | SP13 |
Fixed | Issue where schedule entries would not show as delayed on the MES Schedule View. | SP13 |
Fixed | Issue where system.mes.workorder.getMESWorkOrders could return incorrect results for a piece of equipment in the presence of deleted operations. | SP13 |
Fixed | Issue where the schedule editor tab in the MES Schedule View’s editor panel would not open. | SP13 |
Fixed | Deadlock in the operations manager. | SP13 |
Fixed | Issues with certain complex property name size restrictions being too low. | SP13 |
Fixed | Issue where delayed schedules and routes would not be rescheduled properly. | SP13 |
Fixed | Prevent errors dragging and dropping schedules when using the right mouse button by only allowing drag and drop to work when holding the left mouse button. | SP13 |
Fixed | Split operations will now retain the duration that was assigned to them when they were part of a larger hierarchy in a route. | SP13 |
Fixed | Concurrent operations may be scheduled at any point after the BEGIN time of their preceding operation. | SP13 |
Fixed | Sequential operations may be scheduled at any point after the END time of their preceding operation. | SP13 |
Fixed | Rescheduling operations that have concurrent sub-operations (that run when the current one BEGINS) will automatically reschedule them to the current operation’s begin time. | SP13 |
Fixed | Rescheduling operations that have sequential sub-operations (that run when the current one ENDS) will automatically reschedule them to the current operation’s end time. | SP13 |
Fixed | Issue where threads for aborted operations were not cleaned up. | SP13 |
Fixed | the MESObjectSelector’s selected item will persist upon Window refreshes. This allows users to navigate between windows without losing their selection. This also allows other components with dependencies on the MESObjectSelector’s selection to stay up-t0-date. | SP13 |
Fixed | MES Request Segments will update their Begin and End Date times so that they match their Operation Request’s Begin and End Date times. | SP13 |
Fixed | Previously used data points within Group By and Order By will be removed when they are removed from the Data Points selection. | SP12 |
Fixed | Using the Production module without either OEE or Trace will no longer generate errors in the logs about counters and additional factor tables being undefined. | SP12 |
Fixed | system.mes.resetScheduleStatus() works without having to invalidate the cache. | SP12 |
Fixed | Operations Requests in a Route resize improperly after Drag and Drop Start Time Change. | SP12 |
Fixed | Warning about “MES datasource not available” will stop appearing after editing MES Settings or Database Connection settings to be valid. | SP12 |
Fixed | Issue where shift value was double-logged for shifts crossing midnight. | SP12 |
Fixed | Prevent an error saving when rescheduling an operation that is set to track progress by ‘Use Time’ and has both a scheduled duration and quantity. | SP12 |
Fixed | Slow analysis performance due to not using cache when all values are null. | SP12 |
Fixed | Issue where right-click menu stops functioning after copying something in the Production Model. | SP12 |
Fixed | Issue where copying copies of Production items created duplicate Production items. | SP12 |
Fixed | Issue where a NullPointerException was sometimes thrown in the analysis cache. | SP12 |
Improved | Added a Scheduled Begin Date and Scheduled End Date to OperationSchedule. These values are updated when a schedule is manually updated. The Original Begin Date and Original End Date will now stay the same from when the operation schedule was created. | SP12 |
Improved | Analysis that is run from a gateway context will now work regardless of security settings on the stored analysis. | SP12 |
Improved | Counter names may now exceed 50 characters (up to 255). | SP12 |
Improved | The MES Schedule Selector will now display the Original Begin Date and Original End Date for each Schedule Entry in addition to their Scheduled and Actual dates. Just as with any column, these new ‘Original Date’ columns may be optionally hidden. | SP12 |
Improved | The Tool Tips for Schedule Entries will now display Scheduled and Actual Dates. | SP12 |
Added | Work Order objects can now return their Material Lots, Personnel, and Supplemental Equipment. | SP12 |
Added | Assigning an Ignition Composite Schedule to an equipment now works correctly. | SP12 |
Added | Operations Response objects can now return their associated Material Lots, Personnel, and Supplemental Equipment. | SP12 |
Added | Scripting functions in the namespaces system.mes and system.mes.workorder have been added as an alternate means of using the new MES Work Order object functions. | SP12 |
Added | Added a field to the MES Settings in the gateway web page that allows users to define the amount of time between automatic MES Personnel synchronizations. Also added a checkbox to enable this functionality. | SP12 |
Added | Added new Shift Datapoints: Shift Start Date Time, Scheduled Shift, Scheduled Shift Start Date Time, Scheduled Shift End Date Time. | SP12 |
Added | Work Order objects can now return their associated Operations Request/Response segments. | SP12 |
Added | Operations Request objects can now return their associated Request Segments and Operations Response. | SP12 |
Added | Request Segment objects can now return their associated Response Segment. | SP12 |
Added | Operations Response objects can now return their associate Response Segments. | SP12 |
Improved | Added new addTagCollectorValue function that does not take a date parameter, for use when adding tag collector values at the current time. Additionally, added handling for desynced client/server times when adding tag collector values. | SP11 |
Improved | Performance of some checks performed during MES object save. | SP11 |
Fixed | Fixed errors when adding columns to existing tables when using PostgreSQL. | SP11 |
Fixed | Deleting an Additional Factor will remove it from the database. If an Equipment object is deleted, its Additional Factors will be deleted as well. | SP11 |
Fixed | Importing Additional Factors will preserve their original data types. References to their Tag Paths will also be preserved, even if the tag does not currently exist. | SP11 |
Fixed | Allow for database “string” fields to be defined as something other than VARCHAR(255). | SP11 |
Fixed | Typographical error in the description for the Line Downtime State Time Stamp analysis data point. | SP11 |
Fixed | Issue where mode and state duration did not always group properly in analysis. | SP11 |
Fixed | Issue where certain tag collectors could throw errors for certain tag collector functions, such as system.mes.removeTagCollectorValues(). | SP11 |
Fixed | Issue where some date fields on some objects (MESScheduleEntry, MESOperationsResponse, etc.) were returned as java.sql.Timestamp instead of java.util.Date. | SP11 |
Fixed | Issue where maintenance operations could not be copied and pasted. | SP11 |
Fixed | Error around Name column size could not be altered. | SP11 |
Fixed | Renamed “Date Format” in Analysis Selector settings to “Filter Comparison Date Format.” “Date Format” has been retained as a hidden legacy setting. | SP10 |
Fixed | Issue where scheduled runs ended 1 minute later than scheduled. | SP10 |
Fixed | Issue with deriving segments. | SP10 |
Fixed | Duration calculators are filterable in analysis. | SP10 |
Improved | Equipment manager logs issues with individual equipment, states, and modes and continues processing instead of failing out completely. | SP8 |
Improved | Added more information to the error message that appears when multiple equipment complex properties are added to a segment. | SP8 |
Improved | Equipment cache uses live cache for current equipment states. | SP8 |
Improved | Reuse existing database connection when handling object versioning. | SP8 |
Changed | MES Schedule View default behavior will only bring back schedule information for all equipment if there are less than 10 applicable equipment items. | SP8 |
Fixed | The system.mes.addTagCollectorValues, system.mes.updateTagCollectorValues, and system.mes.removeTagCollectorValues scripting functions now work with an Oracle database. | SP8 |
Fixed | The “Line Schedule Available Time” calculator now properly handles unknown modes. | SP8 |
Fixed | Issue where duration calculators (Mode, State, and Line State) did not produce correct values in Live Analysis. | SP8 |
Fixed | Typo in Production Settings property error message. | SP8 |
Improved | Equipment manager cache performance. | SP8 |
Fixed | The getTagCollectorValues() function now returns values sorted by timestamp for all database vendors. | SP8 |
Fixed | MES Schedule View performance has been drastically improved. | SP8 |
Fixed | Issue where equipment items with a path longer than 75 characters could not be assigned a material. | SP8 |
Improved | Analysis now works when grouping across multiple lines. | SP8 |
Fixed | Parallel cell detection’s minimum cell threshold now works correctly. | SP8 |
Fixed | Bug where the wrong intellisense documentation was displayed for the Schedule Delay event. | SP7 |
Improved | Removed unused MESPropertyList class and associated scripting methods. | SP7 |
Added | Disable Live Cache analysis setting to optionally prevent a live analysis entry from using the cache. This is useful if a Custom Period Tag is being used and the start time changes frequently. | SP7 |
Improved | Changed security on the execution of analysis in the gateway scope to support non-default Ignition authentication profiles. | SP7 |
Fixed | Issue starting a segment that has optional OUT materials that was generated through scripting. | SP6 |
Fixed | OEE mode values were not written correctly for Track & Trace operations. | SP6 |
Fixed | Counts for an MES counter would continue to accumulate from old tags even after the tag path was changed to a new tag. | SP6 |
Fixed | Bug that caused abnormally high query rates. | SP4 |
Improved | Localization for the Analysis Table. | SP4 |
Improved | Localization for MES Schedule Selector. | SP4 |
Improved | Localization for MES Schedule View. | SP4 |
Improved | Localization for MES Value Editor. | SP4 |
Fixed | Long live analysis execution time due to the cache not being used. | SP2 |
Fixed | Exception when Line Standard Count Variance data point was used in live analysis. | SP1 |
Fixed | Exception when Line Target Count Variance data point was used in live analysis. | SP1 |
Fixed | Exception when Delta Time Stamp data point was used in live analysis. | SP1 |
Fixed | Issue where Line Schedule Available data point was not returning the correct values. | SP1 |
Fixed | Overloaded the getComplexProperty(path) and getComplexPropertyByKind(path) methods on AbstractMESObject to accept the path parameter as a string so that they can be used in scripting. | RC2 |
Fixed | Prevented material classes that were created for OEE from being removed if they still have material definitions as children. | RC2 |
Improved | system.mes.exportMESObjects() script function to support providing a UUID with the object type. | RC2 |
Fixed | Roles containing invalid characters will no longer be displayed in the Permissions table within the General section of the MES Analysis Selector. | RC2 |
Improved | MES Counter Group naming and display in Analysis. | RC2 |
Fixed | Fix for cell counters under a cell group when performing a 1.0 to 2.0 legacy migration. * A group or parent cell should have counter values when imported as well as any child or nested parent in the group. * When displaying the counter values in MES value edit table, counter values should display along with any custom counters on the child level. | RC2 |
Fixed | Memory leak in MESOperationsSegment class. | RC2 |
Fixed | Efficiency of updating analysis with equipment, states, modes, and counters. | RC2 |
Fixed | Error creating schedule entries for OEE that have a long line and material names. | RC2 |
Fixed | Issue where the equipment count tag collector threw an exception with a misleading message. | RC2 |
Fixed | Issue where getComplexProperty(path) on MES Objects did not respect properties using extended naming. | RC2 |
Fixed | Autocompletion Window Does Not Match Documentation for system.mes.getTagCollectorLastTimeStamp() | RC2 |
Improved | Added confirmation for Operations Segment and Supplemental Equipment deletion in MES Object Editor. | RC2 |
Improved | Implemented updates to custom analysis value source and calculator functionality. | RC2 |
Added | Added feature to accept Historical Tag Values from the MQTT Engine and record in the MES tag collectors. | RC2 |
Improved | Added read-only property MES Object Editor component. | RC2 |
Improved | Text appearance on schedule blocks in MES Schedule View. | RC2 |
Improved | Functionality of MES Schedule View extension functions. | RC2 |
Improved | Cell order no longer lost on copy-paste of production model items. | RC2 |
+ 2.79 OEE Module
Change Type | Change Log | Rev |
Fixed | Joined operation schedule table to filter by “Active” state while querying for overdue operations. | SP8 |
Improved | Greatly improved performance of the OEE Reject Count Calculator. | SP6 |
Fixed | Corrected an error where States and State Classes created prior to the introduction of “Override Current Line Downtime” would be treated as False instead of True. Treating the states as True provides the same behavior as prior to the introduction of this option. | SP5 |
Fixed | Prevented a Stack Overflow from occurring due to Starved and Blocked Cell Groups attempting to blame each other when a downtime reason is absent. | SP4 |
Fixed | Decreasing counts in the Value Editor will now be reflected in Analysis without requiring a manual cache invalidation. | SP4 |
Fixed | Issue with key reason cell calculator with disabled states under a key reason calculator. | SP4 |
Fixed | Issue where End State Time Stamp listed same as State Time Stamp. | SP4 |
Fixed | When using Live Analysis that calculates OEE Reject from OEE Infeed – OEE Outfeed, the previously cached OEE Reject value is discarded and re-calculated from the current OEE Infeed and OEE Outfeed values. | SP4 |
Added | Rollover calculations with reject counts. | SP4 |
Added | Equipment Infeed Scale factors into OEE Quality Score. | SP4 |
Added | All data points specified have been added, with reference to scheduled operations, rather than responses from completed ones. This requires includeFuture = true in analysis settings to analyze future operations. | SP4 |
Fixed | Standard Rate for Hour is now entirely dependent on the coverage of the clock hour containing From Date by shift segments. For example, with an analysis row with From Date as 12:30, and assuming that the shift in question is 8:00-12:30, 12:45-16:30, the Standard Rate for Hour would be based on the 45 minutes of coverage within 12:00-13:00. | SP3 |
Fixed | Issue where running Operations Responses do not appear with function getOperationsResponses(). | SP3 |
Fixed | Issue where downtime events around the end of the run do not have an end date. | SP3 |
Improved | MES Schedule View getToolTipText extension function now supports Ignition and production schedules. | SP3 |
Fixed | Downtime reasons coming from blocked/starved cell groups do not mark as unknown. | SP2 |
Fixed | Issue where disk cache from live analysis would keep filling up without deleting old live analyses. | SP2 |
Fixed | Prefixed strings with `N’` when interfacing with MSSQL to support Unicode encoding. Note that this will only be supported if the columns written to are an `NVARCHAR` variant (`VARCHAR` does not support Unicode). | SP2 |
Fixed | Splitting downtime event that started during changeover shows start time appropriately. | SP2 |
Fixed | Material unassigned from a line no longer appears in the Run Director component. | SP2 |
Fixed | Issue where reverted downtime event blocks note from displaying for original event. | SP2 |
Fixed | Issue where split events would cause display issues on OEE Time Chart. | SP2 |
Fixed | Issue where auto schedule by time completes after double the time. | SP2 |
Fixed | Issue where operations would generally start one minute after scheduled. | SP2 |
Fixed | Issue where RelativeCycleCountCalculator was offset by 2 instead of having an offset of 0. | SP2 |
Fixed | Issue where scheduled item starting in the same minute the current operation ends cannot start until the next minute. | SP2 |
Fixed | Issue where split event would split into more than two events with child cells and/or setting the line state directly. | SP2 |
Fixed | Rescheduling operations to another line correctly changes the operation to the new line on both routes and single operations. | SP2 |
Fixed | Scheduled operations crossing midnight twice cause issues in scheduling. | SP2 |
Fixed | Clicking multiple operations/routes in the MES Schedule View does not change coloring of deselected operations. | SP2 |
Improved | Minimum time between two sequential schedule items is one second instead of one minute. | SP2 |
Improved | Add “override current line downtime” state flag and functionality for key reason downtime detection methods. | SP2 |
Added | MES Counter set for positive change mode will log a negative change message in the gateway log when the SQL tag decreases. | SP1 |
Added | Extra indices to the MESEquipmentStateValue table. | SP1 |
Improved | Added ‘Equipment List View Type’ setting on OEE Downtime Table component. | SP1 |
Improved | Added invalidation of the work order cache to system.mes.invalidateCache(). | SP1 |
Improved | Users can select the Idle Mode in addition to Changeover and Production modes in the OEE Material Manager. | SP1 |
Improved | Calculations of infeed/outfeed when infeed/outfeed missing. Uses calculations consistent with https://help.sepasoft.com/docs/display/MHD/Material+Production+Settings. | SP1 |
Improved | OEE Time Chart performance state loading times with large lines and large datasets. | SP1 |
Fixed | Performance issues with large number of states on the OEE Downtime Table drilldown. | SP1 |
Fixed | Issue where analysis drill down could throw a “duplicate filter expression” exception. | SP1 |
Fixed | Route operations not correctly sized when moving around other scheduled items. | SP1 |
Fixed | Relative paths for additional factors appear without having to use the full path. | SP1 |
Fixed | Infeed/Outfeed counters were assigned to the line generally instead of to cells when appropriate. | SP1 |
Fixed | Filtering on Line State Duration no longer returns wrong duration for state event. | SP1 |
Fixed | Line Target Count and Line Standard Count now add caps together appropriately on grouped analysis items. | SP1 |
Fixed | Filter issues with count grouping with equipment filters and Line State Duration. | SP1 |
Fixed | Issue where dragging work order may cause popup before proceeding with regular behavior. | SP1 |
Fixed | Issue where downtime note would display incorrectly after an edit in the OEE Downtime Table. | SP1 |
—— | ———— Above this line, module is renamed to 2.79.x and release notes begin at SP1 ———————— | — |
Improved | On a sorted OEE Downtime Table, if a row is selected, edited, and moved to a different row index, it will still remain selected. If the edited row disappears due to filtering, no rows will be selected. | SP13 |
Improved | Removed “Group By” option for some data points for which it was illogical to group on. | SP13 |
Added | New “Material Class Name Filter” property and “filterMaterials” extension function to the OEE Material Manager. | SP13 |
Fixed | Issue where analysis could sometimes fail while collecting OEE counts for a line if the line had child cells or cell groups which had been deleted. | SP13 |
Fixed | Issue where OEE Qualitiy could be incorrect at the line level when infeed, outfeed, and reject counts were coming from cell counters. | SP13 |
Fixed | On a sorted and/or filtered OEE Downtime Table, the correct row will be opened for editing when clicked on. | SP13 |
Fixed | The MES OEE Time Chart’s downtime display will reflect what is seen in the MES Property Value Editor. The MES OEE Time Chart will no longer get ‘stuck’ on the first event it sees if multiple events fire under a single second. | SP13 |
Fixed | Issue of line downtime notes not being retained over shifts in downtime table. | SP13 |
Fixed | Drag and drop will no longer work on the MES Schedule View if the schedule category does not match the Edit Category property. | SP13 |
Fixed | When performing analysis, a dialog window warns users that they are missing an Equipment Path Filter-By expression. This warning will no longer prevent analysis results from being returned. | SP13 |
Fixed | Analysis cycle data was improperly nullified if the cycle’s time spanned multiple analysis dataset rows. Only partially included cycles found at the beginning and end of an analysis dataset will be nullified. | SP13 |
Fixed | Copying and pasting Production Equipment in the Designer’s Production Model will now preserve cell-ordering and Cell-Group Starve/Block modes. | SP12 |
Fixed | Scheduled Work Orders that are scheduled by count will now resize when their counts are adjusted. Their progress percentages will also be updated both visually as a bar in the MESScheduleView component, and as a decimal entry in the MESScheduleSelector’s table. | SP12 |
Fixed | Active scheduled operations can no longer be dragged. | SP12 |
Fixed | Quickly dragging schedules will no longer cause an improper ProductionRPCHandler call error message. | SP12 |
Fixed | Disabled children cells under a Cell Group are now counted against the Minimum Cells Running Threshold. | SP12 |
Fixed | The Drill Down feature no longer confuses the current Drill Down state with the previous Drill Down on the first Drill Down attempt. | SP12 |
Fixed | Schedule View text now displays correctly on long runs. | SP12 |
Fixed | Corrected an issue where the reject count in the OEE Quality calculation would not increase when rejects went down. | SP12 |
Fixed | Internal fix preventing concurrent modification exception when using the MES Time Chart. | SP12 |
Fixed | MESScheduleEntry.getStateAsString() can now be called in the gateway scope. | SP12 |
Fixed | Values for Cycle Times would display in analysis for Date Ranges that did not encompass a cycle’s entire duration. Analysis rows that contain partial cycles will now have blank Cycle Time values. | SP12 |
Fixed | Custom analysis calculators CalculateRow and CalculateFinalRow now work with 5 or 6 arguments. | SP12 |
Fixed | Issue where Material Definitions in some situations could not be created in the material manager. | SP12 |
Fixed | Issue where the ‘Line State Event End’ and ‘Line State Duration’ data points did not always work correctly in Live Analysis. | SP12 |
Improved | Added a logger notifying the user of a count rollover, along with the sequence of counts that caused the rollover. | SP12 |
Improved | A new message can appear in analysis results. The message warns that the analysis may not perform efficiently if ‘Equipment Path’ is not contained in the Filter-By expression. | SP12 |
Added | DowntimeOriginalReason and DowntimeOriginalReasonCode to track original downtime state reasons. | SP11 |
Added | Loading bar dialog box if the amount of data would warrant taking longer than about 1.5 seconds. | SP11 |
Updated | UI, scripting, and importing to throw an error when zero is assigned to a downtime state. | SP11 |
Updated | Scripting and importing to throw an error when a negative integer is assigned to any state code. | SP11 |
Improved | The OEE Downtime Table component now has the ability to filter short stop events using the new property “Show Short Stops”. | SP11 |
Fixed | Configure block method should no longer be called when a slide out panel window is collapsing or expanding. | SP11 |
Fixed | Invalid states will no longer be available for selection when the current state is set for “SubState”. | SP11 |
Fixed | If all of a Cell Group’s children are all starved, the Cell Group will seek to blame an upstream cell that is causing its starvation. Likewise, if a Cell Group’s children are all blocked, the Cell Group will seek to blame a downstream cell that is causing the blockage. | SP11 |
Fixed | Analysis will no longer thrown an exception when the equipment mode is unknown and will log the relevant information. | SP11 |
Fixed | MES work order material name updated when a mes work order table material link is changed. | SP11 |
Fixed | Line Standard Count Variance incorrectly adding OEE Outfeed counts. | SP11 |
Fixed | Issue where filtering on Equipment Note in analysis could return incorrect results for other columns, e.g. Line State duration. | SP11 |
Fixed | Deadlock while unregistering shift monitor. | SP11 |
Fixed | ValueItem object to be the right type. | SP11 |
Added | Availability tags in the equipment Shift tags folder that reflect if the equipment is available based on the selected Ignition schedule. | SP10 |
Fixed | Issue where OEE run script function didn’t wait until complete causing multiple simultaneous runs. | SP10 |
Added | Logic to ignore keywords (AND, OR, LIKE, etc) between a pair of single quotes. Note that adding a single quote to a production item name will break filter. This quote in name issue is unrelated to the fix for this ticket. | SP10 |
Improved | Added ability to treat unknown states as unplanned downtime events in the OEE Downtime Table, OEE Time Chart, and analysis. | SP10 |
Fixed | The shift begin date in the shift folder not showing the current time instead of the shift start time. | SP10 |
Improved | Modules will gracefully recover if the database connection is lost and then re-established. | SP10 |
Fixed | The OEE Downtime Table will now save the user’s last-clicked Downtime Reason when they go to write a note. | SP9 |
Fixed | Issue where rolled-up downtime events had the wrong occurrence count and did not behave properly in the OEE Downtime Table when changing the downtime reason. | SP9 |
Fixed | Issue wherein progress on a scheduled operation or Work Order was incrementing incorrectly. | SP9 |
Fixed | Issue where splitting a downtime event more than once produced the incorrect begin and end dates for the split events in the downtime table and analysis. | SP9 |
Fixed | OEE operations now always reset the mode to IDLE when completing, regardless of the mode prior to completing (e.g. MAINTENANCE -> IDLE). | SP9 |
Added | Ability to get at the production model runner state through scripting using the system.mes.getProductionModelRunnerState() function. | SP8 |
Fixed | Issue where changes in the equipment state hierarchy could result in unknown states in analysis when the states actually still existed. | SP8 |
Fixed | Issue where downtime events could not be split more than once. | SP8 |
Fixed | Deadlock while unregistering shift monitor. | SP8 |
Fixed | Issue where a NullPointerException could be thrown during Parallel Cells downtime detection. | SP8 |
Fixed | Issue where Line Standard Count and Line Target Count values were not rounded properly, leading to incorrect values. | SP8 |
Fixed | Issue where disabling a line would remove production settings from any segments for the line. | SP8 |
Fixed | Issue where equipment items with a path longer than 75 characters could not be assigned a material. | SP8 |
Improved | Analysis now works when grouping across multiple lines. | SP8 |
Fixed | Parallel cell detection’s minimum cell threshold now works correctly. | SP8 |
Fixed | Grammatical error in intellisense for system.mes.getTagCollectorDeltaValue(). | SP7 |
Improved | Intellisense help for system.mes.getEquipmentStateOptions(). | SP7 |
Fixed | Issue preventing BLOCKED FOR UNKNOWN REASON or STARVED FOR UNKNOWN REASON from being overridden or split. | SP7 |
Added | Script functions for changing downtime reasons. | SP7 |
Fixed | Analysis MTBF calculations were incorrect. | SP6 |
Fixed | Nested equipment and material classes were not handled properly when running operations. | SP6 |
Fixed | A production module restart was required for the MES modules to pick up changes to Ignition® schedule entries. | SP6 |
Fixed | Line State Duration was not affected by grouping. (e.g. when comparing mode and state together in a single analysis query.) | SP6 |
Fixed | Errors in the Material Manager when disabling an equipment that has OEE material process segments associated. | SP6 |
Fixed | Equipment mode and state additions/modifications were not picked up properly until a production model save occurred. | SP6 |
Fixed | Cycle Time and related calculators did not produce the correct results. | SP6 |
Fixed | Splitting downtime events did not work with an Oracle database. | SP6 |
Fixed | Auto end production by scheduled time ending run prematurely. | SP5 |
Fixed | Last Line State Duration in a sequence of events always extends to the present. | SP5 |
Fixed | OEE Quality displays as 100% in analysis despite having reject counts. | SP5 |
Fixed | Elapsed Time varies, affecting Performance and OEE | SP5 |
Improved | Mode class validation in the Equipment and Material Managers. | SP4 |
Fixed | Fixed Time Chart component exception when equipment path is invalid. | SP4 |
Improved | Localization for OEE Run Director. | SP4 |
Improved | Changed Line State Duration to show a value using the current date and time for active downtime events while leaving the Line State Event End null. | SP4 |
Fixed | Issue of downtime event shows much longer duration that the begin and end times when a line is set for initial downtime detection with cell groups. | SP3 |
Fixed | Issue where OEE performance and overall OEE in live analysis are not correct based on the OEE Infeed and Infeed Standard Count values. | SP3 |
Fixed | Exception that was preventing deleting a scheduled request when multiple material references are defined. | SP2 |
Fixed | Not serializable exception associated with live analysis. | SP1 |
Fixed | Analysis “Line State Duration” and “Mode Duration” data points not working correctly and causing exceptions. | SP1 |
Fixed | Issue when rolling up events that cause multiple unequal values exception. | SP1 |
Fixed | Exception when “Line Schedule Available Time” or associated data point is added to analysis for a cell or cell group. “Line Schedule Available Time” is not applicable to cells or cell groups. | SP1 |
Added | Added historical and live analysis caching to analysis to improve the speed. | full |
Improved | Equipment State Changes in less than a second was not reflected properly. Instead of throwing an exception, changed tag collectors to overwrite the previous value if a tag changes within the same second. This does not apply to counters of shift tag collectors. | full |
Improved | Added read-only property MES Object Editor component. | RC2 |
Fixed | Schedule entries showing faulted when copied and pasted from schedule entries that had already been run. | RC2 |
Improved | Object naming validation and performance. | RC2 |
Fixed | Issue where deleting a cell or cell group under a line, or changing the name of a cell or cell group under a line, would break existing segments defined for the line. | RC2 |
Fixed | Issue when grouping by Shift Start Date analysis datapoint is not correct. | RC2 |
Fixed | Issue where cells within a line that have the same name didn’t track downtime correctly. | RC2 |
Fixed | Issue where material and production equipment name changes could break runs for existing segments. | RC2 |
Improved | Speed of analysis when determining initial cell downtime reason. | RC2 |
Fixed | Fixed Time Chart component exception when equipment path is invalid. | RC2 |
Fixed | Production Model unordered in OEE Equipment Manager. | RC2 |
Improved | Made improvements of how blocked or starved for unknown reason are handled with cell groups using initial or parallel downtime detection methods. | RC2 |
Improved | Speed of displaying downtime reasons options in both grid and tree view in the OEE Downtime Table component. | RC2 |
Fixed | Removed Retention Days MES settings on gateway page which is no longer used. | RC2 |
Improved | Module startup performance for gateways with a large quantity of Equipment States. | RC2 |
+ 2.79 Track & Trace Module
Change Type | Change Log | Rev |
Improved | Equipment Operation Scheduled Begin/End, Equipment Operation Original Begin/End, and Equipment Operation End analysis datapoints. | SP2 |
Improved | Supplemental equipment has an equipment path editable through the MES Object Editor. Associated equipment and lot methods can take advantage of this new feature. | SP2 |
—— | ———— Above this line, module is renamed to 2.79.x and release notes begin at SP1 ———————— | — |
Fixed | Configure block method should no longer be called when a slide out panel window is collapsing or expanding. | SP11 |
Fixed | If a material lot has more than one custom properties, fix allows to filter by however many available custom properties and return the corresponding lot filter results. | SP10 |
Fixed | OEE operations now always reset the mode to IDLE when completing, regardless of the mode prior to completing (e.g. MAINTENANCE -> IDLE). | SP9 |
Fixed | Issue where the segment.getAvailableMaterialLots() script function only returned lots for the currently set material instead of all material. | SP7 |
Improved | Localization for MES Operation Info. | SP4 |
Improved | Localization for MES Property Value Editor. | SP4 |
Improved | Localization for MES Supplemental Equipment Selector. | SP4 |
Fixed | Bug that prevented some objects from having – in their names. | RC2 |
Fixed | Incorrect descriptions for script functions. | RC2 |
Improved | Track and Trace execution speed. | RC2 |
+ 2.79 Settings & Changeover Module
Change Type | Change Log | Rev |
Fixed | Scaling is now accounted for when registering Recipe Tags for variance monitoring. | SP8 |
Fixed | Improper Recipe Tag subscription handling that generated multiple logs in the gateway. | SP4 |
Fixed | Recipe Tags that are slow to change values, especially OPC tags, now wait for their initial Recipe Values to set before listening is started. | SP4 |
Fixed | Issue where Recipe Changelog Viewer component would not load. | SP3 |
Fixed | Issues with horizontal clipping on recipe editor rows. | SP2 |
Fixed | Issue where “Select Production Items” sorts numbers in string using string compare instead of expected numerical compare for the number sections. | SP2 |
Fixed | Issue where material on process segment named ‘Material Out’ with same material and equipment as OEE segment conflicts in OEE Run Director. | SP2 |
Improved | Removal of tree, table value, and table header row height properties. These are determined automatically by the default font (affects tree), table value font, and table header font. | SP2 |
Fixed | Recipe name filter used for both Recipe/Last and Recipe/Date modes. | SP1 |
—— | ———— Above this line, module is renamed to 2.79.x and release notes begin at SP1 ———————— | — |
Fixed | Recipe variance production tag does not go high if the initial value is a blank string. | SP12 |
Fixed | Importing Recipe Values will overwrite existing ones. | SP12 |
Fixed | Issue where default recipe values do not retain value changes. | SP7 |
Improved | Localization for Recipe Selector Combo. | SP4 |
Fixed | Issue that doesn’t sort rows according to the sort order in the Multiple Recipe Editor Table component. | RC1 |
Fixed | Issue that the string value edit panel with read-only mode is closed immediately in the Recipe Editor Table component. | RC1 |
Fixed | Issue that put recipes at the master level if the recipes are not found in the system when they are imported in the Recipe Editor component. | RC1 |
Improved | Optimized the getStringValueOptions() extension function for displaying a drop-down list to the Recipe Editor, Recipe Editor Table, and Multiple Recipe Editor Table components. | RC1 |
Improved | Show all recipe values which have the same sort order in the Multiple Recipe Editor Table. | RC1 |
Added | Two scripting functions to get either a parent recipe name or a list of descendant recipe names of a given parent. | RC1 |
Improved | A scripting function that can be called to update a recipe value with most recent changes made to a tag in a given equipment path. The system.recipe.updateRecipeTagInfo() allows to include the item’s children too by taking a boolean that can be set to true if children should be included in the update. | RC1 |
Added | Prompt to include the recipe path in Recipe Value name. | RC1 |
Improved | Support the recipe name filter of comma separated values in the Multiple Recipe Editor Table component. | RC1 |
Improved | Don’t show any recipes if the ‘Recipe Name Filter’ property’s value is blank in Multiple Recipe Editor Table component. | RC1 |
Feature | Added the getStringValueOptions() extension function for displaying a drop-down list to the Recipe Editor, Recipe Editor Table, and Multiple Recipe Editor Table components. | RC1 |
Added | The ActiveRecipeState and ActiveRecipeGroup OPC tags. | RC1 |
Added | ‘Recipe Display Format’ property for displaying the recipe name, state, or group in the recipe title of the Recipe Editor, Recipe Editor Table, and Multiple Recipe Editor Table components. | RC1 |
Improved | Support drag & drop multiple selected recipe names from the Recipe Selector List or the Power Table components to the Multiple Recipe Editor Table component. | RC1 |
Added | Ability to freeze the first column to the Multiple Recipe Editor Table component. | RC1 |
Improved | Abilities to copy/paste a column in the Multiple Recipe Editor Table Table. | RC1 |
Improved | Abilities to import/export table data as currently contained in the Multiple Recipe Editor Table Table. | RC1 |
Improved | Record a log to the Recipe Changelog when importing/exporting a recipe. | RC1 |
+ 2.79 SPC Module
Change Type | Change Log | Rev |
Fixed | SPC Control Charts no longer require an SPC Controller or Selector on the same vision window. | SP8 |
Fixed | Cached definition samples that belong to disabled definitions are no longer included when evaluating signals. | SP8 |
Fixed | Prevent an error from happening when storing SPC Limits by Product Code. | SP4 |
Added | Location Sample List, Definition Attribute List, Definition Location List, Definition List, Recipe Changelog Viewer and Recipe Variance Viewer now have the following extension functions: getBackgroundAt, getForegroundAt, getDisplayTextAt. | SP4 |
Added | Production Bar Chart and Production Pie Chart now have a configureChart extension function. | SP4 |
Fixed | Previously, coercing the string value saved was dependent on the Client locale. Now it more accurate reflects the fact that the save is based on US locale, and only format it differently when outputting to a Client. | SP3 |
Fixed | Issue where SPC items would auto schedule every second instead of at the designated schedule time. | SP3 |
Fixed | Since we can now handle saving UTF-8 characters to the database with no difference in throughput, there was no need to escape HTML4 characters. This included characters with accents like è, which is why they were written to the database as their HTML equivalents. This marks a shift to reading/writing strings without an application layer encoding/decoding, which should eliminate any concerns about character encoding and increase throughput. | SP3 |
Fixed | Sample notes created when there are multiple attributes present (P, NP, C, U) shows notes for each attribute as well as the definition itself. | SP2 |
Fixed | Custom properties are now added when properties are initialized. Further investigation revealed several other components that exhibit the same bug; I fixed those as well. | SP2 |
Improved | SPC Auto schedule samples is no longer looking at samples that are set for manual. Previously it was looking at all samples and storing them in the cache. | SP2 |
Fixed | Prevent SPC intervals from evaluating sample definitions at locations the definition is not assigned to. | SP1 |
—— | ———— Above this line, module is renamed to 2.79.x and release notes begin at SP1 ———————— | — |
Fixed | Issue where the SPC functions setLocationProductCode() and cancelLocationProductCode() were not available in the gateway scope. | SP13 |
Fixed | SPC Interval Selector’s setSelectedInterval() now works. | SP12 |
Fixed | Tag collector entries with the same name cannot coexist even if in different locations. Now the system will append an integer in parens to keep names unique. | SP12 |
Fixed | Corrected copy/paste tag collector functionality. The newly-pasted entry now contains the original copied column values. | SP12 |
Added | getControlLimitValue() to get a limit value for a given limit name. | SP11 |
Fixed | Updated Default MR UCL Calculation script to provide a null check. | SP11 |
Fixed | Cannot calculate control limit via scripting. Failed with the message “Cannot find any sample data”. | SP11 |
Fixed | Using c Nelson Rule 1 along with non-conformity data type attribute to trigger a signal out of limit if sample data value is out of control. | SP11 |
Fixed | Which rows get displayed after Row Limit is applied. | SP11 |
Fixed | Issue where SPC Tag Collector Values could be recorded incorrectly depending on the locale. | SP11 |
Fixed | Stopped the Unknown Equipment Mode error logs from being recorded multiple times per execution. If there are multiple analysis executions reporting the same error, each will report the error once. | SP11 |
Fixed | Prevent a warning from displaying in the logs when using live analysis on new equipment with no run data. | SP11 |
Fixed | The system.quality.spc.saveStoredSPC scripting function is now accessible in scripting from both client and gateway scopes. | SP9 |
Fixed | SPC Attribute number format did not follow attribute format specified in Min/Max. | SP6 |
Improved | Localization for SPC Selector. | SP4 |
Improved | Localization for Sample Entry. | SP4 |
Improved | Localization for Definition Control Limit List. | SP4 |
Improved | Localization for Definition Signals List. | SP4 |
Improved | Localization for Interval Selector. | SP4 |
Improved | Localization for the following charts: XBar Range, Individual, Median, Xbar S, P, NP, C, U, Histogram, Pareto, Cp, Pp. | SP4 |
+ 2.79 Web Services Module
Change Type | Change Log | Rev |
Fixed | SOAP Consumer not respecting zero fraction digit restriction. | SP1 |
—— | ———— 2.79.1 above this line ———— | —— |
Fixed | Bug that caused leading zeros to be stripped off. | SP4 |
Fixed | Bug causing a flood of NTLM authentication warnings. | SP4 |
Fixed | Bug causing an error when using security features in SOAP consumers. | SP4 |
Fixed | Bug that caused WSDL files to be incorrectly parsed. | SP4 |
Fixed | Bug that caused only the first node of a complex field to be sent from a SOAP Consumer. | SP4 |
Fixed | An issue where toXML() was not working. | SP4 |
Fixed | Bug that caused SOAP schemas to be alphabetically sorted. | SP4 |
Fixed | Bug that caused WSDL reading errors to not be logged. | SP4 |
Fixed | Issue with parsing XML with embedded JSON. | SP4 |
Fixed | Status code always being set to 0 on WSVariable. | SP4 |
Added | Ability to override default Namespace in SOAP Response Body. | SP4 |
Added | Support for XML attributes in a RESTful Consumer. | SP4 |
Added | Error logs to catch statements in WSConsumer. | SP4 |
Added | ‘%20’ space escape option to RESTful Consumers. | SP4 |
Added | Expectation handling when generating REST Response object. | SP4 |
Fixed | Bug that caused SOAP schemas to be alphabetically sorted. | SP3 |
Fixed | Bug that caused WSDL reading errors to not be logged. | SP3 |
Fixed | Exception handling when generating REST response object. | SP3 |
Improved | Changed the encryption method used, to follow Ignition’s practices. As a result, the username and password of saved SAP Destinations will not be able to be decrypted, so you will have to re-enter both to use an SAP Destination. | SP3 |
Fixed | Issue where toXML() was not working. | SP2 |
Fixed | Issue where leading zeros are stripped off. | SP1 |
Fixed | Issue where a flood of NTLM authentication warnings occur. | SP1 |
Fixed | Issue causing an error when using security features in SOAP consumers. | SP1 |
Fixed | Issue where WSDL files are incorrectly parsed. | SP1 |
Fixed | Issue where only the first node of a complex field is sent from a SOAP consumer. | SP1 |
Improved | Added support for XML attributes in a RESTful consumer. | SP1 |
New Feature | ‘%20’ space escape option to RESTful consumers. | SP1 |
—— | ———— Above this line, module is renamed to 2.79.x and release notes begin at SP1 ———————— | — |
Improved | SOAP Providers can now be configured to not have input. | SP6 |
New Feature | Return custom SOAP Faults from SOAP Providers. | SP6 |
New Feature | Added HTTP Response headers to WS Variable. | SP6 |
New Feature | Added HTTP headers to SOAP endpoint script input. | SP6 |
New Feature | Added request data to SOAP and REST endpoint script input. | SP6 |
Fixed | SOAP Response no longer converts lists of size 1 to a non-list type. | SP6 |
Fixed | Lists being incorrectly passed into system.ws.runWebService . | SP6 |
Fixed | Web service REST consumer to accept special characters as a URL Query String item. | SP6 |
Fixed | SOAP input lists of size 1 being lost. | SP6 |
Fixed | SOAP script generation to include all values from SOAP configuration. | SP6 |
Fixed | Issue where operations in WSDL were generated with the HTTP port with “Redirect to SSL” selected when it should have been the HTTPS port. | SP5 |
Fixed | A bug that prevented system.ws.* scripts from working in the client. | SP4 |
Improved | Removed the dependency from the Vision module. | SP3 |
Fixed | Fixed a bug that SSL redirection doesn’t work with the HTTP POST method. | SP2 |
+ 2.79 Production Simulator Module
Change Type | Change Log | Rev |
Updated | Updated module certificate for Utility modules. | SP1 |
Platform 1 (Stable)
+ 1.9.5 General: All MES Products
Change Type | Change Log | Rev |
Improved | Added AUX DB connection logging. | SP7 |
Improved | Production model can indicate running before the module startup is complete. In rare cases, this can cause a thread deadlock. | Full |
Updated | Module signing certificate. | Full |
Validated | This release is compatible with Ignition 7.9.6. | Full |
+ 1.9.5 OEE Module
Change Type | Change Log | Rev |
Fixed | Production model stops processing and runs cannot be started or ended. | SP7 |
Fixed | Analysis downtime for TEEP Loading was not correct if multiple lines are in the analysis and not compared by Line. | SP4 |
Fixed | TEEP Loading not respecting date type compare by’s. Loading was always evaluated against the total time span. | SP2 |
Fixed | Analysis downtime minutes incorrect when compared by additional factor. | SP2 |
Fixed | Resumed run does not take into account the disabled reason code type when recording planned and unplanned times. | RC1 |
Fixed | Production model re-starts may generate unnecessary DB updates for downtime events. | RC1 |
+ 1.9.5 Track & Trace Module
Change Type | Change Log | Rev |
Fixed | Issue where nested equipment classes were not handled properly when running operations. | SP7 |
Improved | The equipmentWIP binding function efficiency improved. | SP1 and SP2 |
Improved | Track and Trace execution speed. | Full |
Fixed | Scripting function segmentExecuteImmediately() causes DB deadlocks and slow queries when many calls are made at the same time. | RC1 |
+ 1.9.5 Recipe Module
Change Type | Change Log | Rev |
Fixed | ChangeRecipeGroup() function was calling renameRecipe() in gateway scope. | SP7 |
Fixed | Issue where default recipe values do not retain value changes. | SP7 |
Fixed | Importing recipes does not update existing entries, only adds new ones. | RC1 |
+ 1.9.5 SPC Module
Change Type | Change Log | Rev |
Improved | SPC module efficiency parsing UUID’s. | SP7 |
Improved | SPC Auto schedule samples is no longer looking at samples that are set for manual. Previously it was looking at all samples and storing them in the cache. | SP7 |
Fixed | SPC Tag Collectors definition always updating to DB on module startup even though nothing has changed. | SP7 |
Improved | SPC module multiple thread usage to guard against excessive locking. | full |
Fixed | Sample Entry screen generates error in mobile client. | RC1 |
Fixed | SPC calcControlLimitValue() method does not allow calculating limits that are not related to default chart selection. | RC1 |
+ 1.9.5 Instrument Interface Module
Change Type | Change Log | Rev |
Fixed | File Path using “*” wildcard does not function in Unix (Ubuntu). | SP2 |
+ 1.9.5 Barcode Scanner Module
Change Type | Change Log | Rev |
Fixed | File Monitor does not indicate loading file generated an error. | RC1 |
MES Platform 1 (LTS)
+ 1.7.9 General: All MES Products
Change Type | Change Log |
Fixed | Issues when saving changes to production model multiple times in rapid succession. |
Fixed | Issue editing an MES Person object in the MES Object Editor component. The name which has a comma was not being accepted. This may have also occurred with script function. |
Improved | Production model items running on multiple threads. |
Improved | Speed of the slide over of the properties in the MES Object Editor component. |
+ 1.7.9 OEE Module
Change Type | Change Log |
Fixed | Resume run was not adding the sequence date to the prod additional factors table. |
Fixed | Null Pointer Exception showing when shutting down OEE Downtime module if the model is not running. |
+ 1.7.9 Recipe Module
Change Type | Change Log |
Improved | Changed size of value field in recipe value and sub recipe value table to 1024 from 255. Allows a larger string value data size. |
Added | Gateway scope now houses system.recipe.getRecipeValueSecurity and system.recipe.updateRecipeValueSecurity script funciton that were previously just in the client scope. |
Added | Script method system.recipe.getItemRecipeList() with “includeMasterRecipes” parameter. |
Improved | List changes to the changelog for child recipes when changing on the parent scope. |
Fixed | Bug that “User Filter” has no effect on the system.recipe.getChangeLogHistory() script and the “Recipe ChangeLog Viewer” component. |
Added | Support for importing/exporting multiple recipes. |
+ 1.7.9 Track & Trace Module
Change Type | Change Log |
Added | Check in track and trace create operation function to return error message when blank values are passed for operation name and equipment path. |
Added | Check in track and trace create segment function to return error message when blank values are passed for operation segment name. |
Fixed | Bug in track and trace when displaying sub lots in the trace graph. |
Fixed | Sublot Matched Text property so that it is used when displaying the sublot flag in the trace graph nodes. |
Fixed | Bug in Track and Trace where material lot objects were not being set to “Used”. |
Fixed | Bug in MES Material Selector component with optional material properties. |
Fixed | Issue where segment names that contain the _ character returned an error stating that the segment cannot run at the equipment. |
Fixed | Optional material reference for segments so that material lot object are not created if the quantity is zero. |
Improved | MES Lot Selector component to not show disabled material lots. This will also effect script functions to get material lots. |
Improved | How operations, segments and material lots are cleaned up after a segment or operation is aborted. |
Improved | Material lots that are active are not returned as options when selecting a lot for a segment. This change also effects script functions that return available lots. It also prevents selecting a material lot that is still active and begining, ending, updating or executing a segment. |
+ 1.7.9 SPC Module
Change Type | Change Log |
Fixed | Sample Entry component to not update the entry date time and taken date time properties if they are already set. This fixes the issue of the dates being changed from the original when editing existing samples. |
Fixed | Exception on Sample Entry component that was occurring when testing if samples are within limits. |
Fixed | Issue of the background color not reflecting the correct limit violation in the table of the control chart. This only applies for more than one upper limit or more than one lower limit being shown in the control chart. |
Added | system.quality.definition.getNewDefinitionSignal() script function to get an instance of a sample definition control limit. |
Added | system.quality.definition.getSignalNameList() script function to return the names of all SPC signals. |
Fixed | Bug adding and removing control limits and signals from sample definitions. |
Improved | SPC gateway script functions to work with or without the project name parameter. |
+ 1.7.9 Web Services Module
Change Type | Change Log |
Updated | Web services now use native Java implementation. Replaces SUDS implementation as the library was no longer being updated and had limitations. NOTE – Existing web services will need to be refreshed under the configuration and the project saved. |
Added | RESTful web services. |
+ 1.7.9 Instrument Interface Module
Change Type | Change Log | Rev |
No updates to feature. |
+ 1.7.9 Barcode Scanner Module
Change Type | Change Log | Rev |
No updates to feature. |
Business Connector
+ 3.79 Sepasoft Business Connector Module
Change Type | Change Log | Rev |
Fixed | Add element path to error message generated when generating REST response from an empty array. | SP2 |
Fixed | Bug reading complex objects as SOAP Action input. | SP2 |
Fixed | Alphabetical sorting of SAP BAPI options. | SP2 |
Fixed | Fixed bug that caused array item row deletion to fail. | Full Release |
Fixed | Fixed bug that prevented adding array elements to a child of an array element. | Full Release |
Fixed | Fixed input mapping bug cause by dataless mapping nodes being saved. | Full Release |
Fixed | Fixed BC parameter table displaying a maximum of 16 parameters. | Full Release |
Improved | Added better exception handling for BC Script block. | Full Release |
Added | Added default values to nodes of Complex Chart Parameters. | Full Release |
Added | Added Chart Parameter default values to auto-generated script. | Full Release |
Added | Added Named Query Action block to Business Connector. | Full Release |
Added | Added saved node pruning. | Full Release |
Added | Added creating and mapping parameters from input and output schema nodes of BC Actions. | Full Release |
Added | Added BC external modules and libraries version info in Designer. | Full Release |
Added | Added Plant Maintenance chart templates. | Full Release |
Fixed | Issue with exported enclosed charts not being found by the calling element. | Full Release |
Fixed | Issue with copy-pasting charts maintaining old UUID. | Full Release |
Fixed | Issue with templates creating the same UUID. | Full Release |
Fixed | Bug in Save MES Object Block. | Full Release |
Fixed | BAPI tree-caching bug. | Full Release |
Fixed | Issue with duplicated B2MML Material objects causing save error. | Full Release |
Fixed | Issue with Unicode characters out of allowed XML1.0 ranges causing BC charts to fail. | Full Release |
Fixed | Drop-down menu layout bug in BC. | Full Release |
Fixed | Issue that caused serialization errors if Ignition Designer was launched through the client launcher. | Full Release |
Fixed | Simple arrays defined on RESTAction didn’t have a type. | Full Release |
Fixed | Jython conversion issue in BC. | Full Release |
Fixed | 1-to-n mapping bug. | Full Release |
Fixed | 1-to-n unmapping bug. | Full Release |
Fixed | Handling missing mapped nodes. | Full Release |
Fixed | Bug that blocked the aggregator source from being an array. | Full Release |
Fixed | Mapping from an iterated simple array node. | Full Release |
Fixed | Issue that made the BC, WS and SAP modules depend on the Vision module. | Full Release |
Fixed | “format” field for Work Order Due Date. | Full Release |
Fixed | Parameter table column sizes. | Full Release |
Fixed | Parameter renaming bug. | Full Release |
Improved | Replaced the bind to a tag/set fixed value buttons with ‘add an array element buttons’. The bind to a tag/set fixed value buttons to the pop up menu. | Full Release |
Improved | Changed default debug log setting to OFF. | Full Release |
Added | Support for Work Orders to Business Connector. | Full Release |
Added | Work Order to B2MML OperationSchedule (MESWorkOrder objects can now be passed to/from charts as parameters). | Full Release |
Added | Input/output property to BC Chart Parameters. | Full Release |
Added | Support for non-default date formats in the mapper. | Full Release |
Added | Improvements in B2MML Parsing. | Full Release |
Added | Automatic parameter path refactoring. | Full Release |
Added | Added table titles to BC Mapper. | Full Release |
Added | Scrolling to Business Connector palette view. | Full Release |
Added | Added a “Remove Schema” button to each root row of a schema. | Full Release |
Removed | The “Remove Schema” button from above the tables. | Full Release |
Added | Functionality to only expand rows that have mapping, functions, or bindings. | RC4 |
Added | Calendar selector UI for Date parameters. | RC4 |
Updated | Function editor buttons. | RC4 |
Fixed | Can’t have two grandchildren with the same name in one parameter bug. | RC4 |
Fixed | Passing xml output of one action to the next. | RC4 |
None | No changes to module in release | RC3 |
Fixed | Caching issue with iterator path. | RC2 |
Fixed | Exception block now allows name and description editing. | RC2 |
Fixed | BC Chart date parameters format corrected. | RC2 |
Fixed | Aggregator supports indexed rows. | RC2 |
+ 3.79 Interface for SAP ERP Module
Change Type | Change Log | Rev |
Fixed | Fixed bug that created duplicated I4SAP roots. | Full Release |
Fixed | Fixed bug that showed new BC folders not italic. | Full Release |
Improved | Added support for load-balanced architecture in I4SAP. | Full Release |
Fixed | Select button being disabled. | Full Release |
Improved | I4SAP templates. | Full Release |
Improved | Changed encryption method to match Ignition’s method. As a result, the Username and Password of saved SAP Destinations cannot be decrypted, so users must re-enter both to use an SAP Destination. | Full Release |
Added | “Test Connection” button to SAP Destination. | Full Release |
Added | SAP Destination test now reminds users to save modified Destinations. | Full Release |
None | No changes to module in release | RC4 |
Fixed | Error messages now log the correct module name | RC3 |
Fixed | SAP Destination can now be created without Production Module | RC3 |
Fixed | SAP Destination UI now correctly saves edits. | RC2 |
Fixed | SAP Blocks support indexed rows. | RC2 |
Added | SAP templates added to BC. | RC2 |
Updated | JCo BAPI action loads the BAPI tree asynchronously. | RC2 |
+ 3.79 Web Services Module
Change Type | Change Log | Rev |
Fixed | Add element path to error message generated when generating REST response from an empty array. | SP2 |
Fixed | Bug reading complex objects as SOAP Action input. | SP2 |
Fixed | SOAP Consumer not respecting zero fraction digit restriction. | SP1 |
Fixed | Fixed REST Configuration screen infinite-growing bug. | Full Release |
Fixed | Fixed bug that caused SOAP Configuration refresh to re-encrypt encrypted password. | Full Release |
Improved | Added focusing password field in SOAP/REST configuration empties password field. | Full Release |
Fixed | Bug that caused leading zeros to be stripped off. | Full Release |
Fixed | Bug causing a flood of NTLM authentication warnings. | Full Release |
Fixed | Bug causing an error when using security features in SOAP consumers. | Full Release |
Fixed | Bug that caused WSDL files to be incorrectly parsed. | Full Release |
Fixed | Bug that caused only the first node of a complex field to be sent from a SOAP Consumer. | Full Release |
Fixed | An issue where toXML() was not working. | Full Release |
Fixed | Bug that caused SOAP schemas to be alphabetically sorted. | Full Release |
Fixed | Bug that caused WSDL reading errors to not be logged. | Full Release |
Fixed | Issue with parsing XML with embedded JSON. | Full Release |
Fixed | Status code always being set to 0 on WSVariable. | Full Release |
Added | Ability to override default Namespace in SOAP Response Body. | Full Release |
Added | Support for XML attributes in a RESTful Consumer. | Full Release |
Added | Error logs to catch statements in WSConsumer. | Full Release |
Added | ‘%20’ space escape option to RESTful Consumers. | Full Release |
Added | Expectation handling when generating REST Response object. | Full Release |
Added | ‘%20’ space escape option to RESTful consumers. | RC4 |
Added | Support for XML attributes in a RESTful consumer. | RC4 |
Fixed | Bug causing leading zeros to be stripped off. | RC4 |
Fixed | Bug causing a flood of NTLM authentication warnings. | RC4 |
Fixed | Bug causing an error when using security features in SOAP consumers. | RC4 |
Fixed | Bug causing WSDL files to be incorrectly parsed. | RC4 |
Fixed | Bug causing only the first node of a complex field to be sent from a SOAP consumer. | RC4 |
None | No changes to module in release | RC3 |
Fixed | Fixes from Web Services version 2.9.6 SP6. | RC2 |
Utilities
+ 2.79 Instrument Interface Module
Change Type | Change Log | Rev |
Updated | Updated module certificate for Utility modules. | SP1 |
+ 2.79 Barcode Scanner Module
Change Type | Change Log | Rev |
Updated | Updated module certificate for Utility modules. | SP1 |