Current release notes.
GENERAL
- Translation
Additional terms have been added for English, Vietnamese and French, and some existing translations have been improved. - DB size optimization
For installations where many declarations are used or need to be persisted in the database, optimized handling of the required storage space has been implemented. This results in less storage space being required and a slower rate at which the space requirement increases. - Audit
The existing audit functionality has been expanded to include the following areas: dosing orders, station assignment, transport orders, strategies. - Watch values
The actual data of the system values (watch values) are now persisted separately from the dosing order. This allows dosing orders that have already been partially processed to be modified without causing unwanted manipulation of previously recorded actual data. - Recipe optimization – inactive scales
Individual scales can now be marked as inactive for recipe optimization. This allows for quick responses if, for example, a scale is defective – without having to change the basic configuration. - Customer-specific tolerances
Customer-specific tolerances can now be maintained. These tolerances can then be used when creating an order, provided a customer is specified. - Soehnle 3010
The scale driver for the Soehnle 3010 now supports operation in either grams or kilograms. - Splitting of the modules Systemserver and Move-RT
The two backend modules, System Server and Move-RT, can now be executed multiple times (divided into tasks) under certain conditions and with appropriate configuration. - Logging of failed logins
Failed login attempts represent security-relevant events and are now recorded. - New scale Mettler IND400
A new scale Mettler IND400 is supported now.
MANAGER
- Print jobs
There is now a new view for print jobs that are processed in the background by the system (_ew_print). Reprinting with modified parameters is also possible here. - Blacklist declaration printing
For printing with DevExpress, the printers installed on the application server are loaded and displayed to the operator. To restrict the printer selection in the manager to those printers that should be available to the operator, a blacklist option is created in the system configuration. Printers selected here are then ignored at declaration printing. - Process recipe in order
With the appropriate setting, the process recipe can now also be edited when processing an order. - Indicator booking user right
In order to perform an indicator booking from inventory (details), a corresponding right is now required.
SYSTEMSERVER
- Recipe transfer
Recipe variants are now also processed at recipe transfer. - Rotation of dosing priorities
It is now possible to cyclically rotate the dosing priority within a defined time interval, so that with multiple silos for one component, each silo is used regularly.
ESACOM
- Labeling of open containers
After the last dose of an entire order, a raw material label can now be printed automatically if configured accordingly.
LOGISTIC
- Source storage location
The source storage location is now also displayed to the operator if the transport order consists of a single LE.
RUNTIME 8 FE
- PLC reset user right
A dedicated user right is now required to initiate a PLC reset. - Occupancy check - target selection
When selecting a target, the user is now informed about any existing occupancy. The user action is recorded in the operator log.
GENERAL
- Logging - character set
The UTF8 character set is now explicitly used for logging. - Minebea-Intec scales
The correct decimal separator is now used according to the system settings. - PLC communication – date values
In certain cases, a date value transmitted by the PLC could be incorrect. - Logging - security
When handling certain infrastructure-related error events, it was possible that a password might be logged in plain text. - HBM AED scale
An error at taring was fixed.
MANAGER
- Inventory
Some minor improvements were made. - Component consumption
The sorting did not work correctly. - Dosing recipe - tolerances
Tolerances could not be changed when editing a dosing recipe. - Acceptance pieces
When saving the delivery details, the external order number was not transferred. - Copy transport strategy
A bug that occurred when copying a transport strategy has been fixed. - Analysis truck loading
The calculation of the displayed values may have been incorrect in certain cases. Also further columns can be displayed now. - Picking order
When a picking order is completed, an operator log entry is now made and an automatic order picking status change is only made if the process is not already completed. When a new picking entry is created, an operator log entry is also made. - Declaration printout
The export path was incorrect in the print preview. - Operator log Runtime 8 FE
Operator log entries from Runtime 8 FE were not displayed. - Booking of LE
Before booking an LE manually, it must be checked whether the LE is already booked in at another storage location. - Oder planning
If the release is removed, the batch status must not be reset to open. The setting "Already dosed orders may be processed" is now also considered in order planning. - Contract management
The monthly report showed different data in the contracts compared to invoice control. The calculation has been corrected. - Goods receipt
Automatic label printing at checkout is only performed if the corresponding setting is enabled. - Edit production recipe
An error could occur when editing a production recipe with user-defined column settings. - Language switching
When switching the user-specific language, it could happen that some terms were not translated without restarting the module. - Column settings
It was possible to create a custom column setting without a label.
ESACOM
- Assigned orders
The "released" flag was not considered for assigned orders. - Article scan in SC view
With active source LE management, an article scan in the SC view must not cause dosing to start, since the source LHM was never scanned.
RUNTIME 8 FE
- Format settings
The format settings were fixed (date and number format). - Login
A problem with the standard login process has been fixed.
SYSTEMSERVER
- Batch tracking
In a specific case, an SQL error could occur.
MFM
- Indicator strategy
A possible parent LE is now considered when checking for already created transport jobs.
GENERAL
- Translation
Additional terms have been added for English, Vietnamese und Hungarian, and some existing translations have been improved.
MANAGER
- Multi selection
To process multiple entries more efficiently, it is now possible to select several entries at once for specific actions in many central views (delete, confirm, ...). - Activate process
If no real truck is available when activating a process, the "flatbed" truck type can now be used. Furthermore, a delivery note label can now be printed automatically, if configured accordingly. - Line swap
In the case of a line swap, the scale assignment of the components is now checked in detail. - Order planning – contamination violation
Previously, orders could still be released after a security prompt in case of a contamination violation. From now on, this is only possible if the user has the necessary user right. - Single Sign on (LDAP)
Now it is possible to use the LDAP-authenticated user from the operating system for the ESAweight Manager log on. - Edit customer
There is now a filter option for assigned articles. - Color code in order planning
A color code can be stored in the finished goods master data. This can be displayed as a column, represented by a symbol, in order planning. - Cross references
To enable more efficient data handling, further cross-references have been added, allowing operators to directly access details from certain views without having to navigate manually.
SYSTEMSERVER
- Target feedback
The target feedback can now also be configured to perform an article assignment also.
ESAPRINT
- Retention time
The retention time for cleaning up old print jobs can now be configured.
ESAPRESS
- Idle during startup
In mode “startup”, the Idle button can now be enabled by PLC.
RUNTIME 8 BE
- Dosing priority sequence
A dosing sequence can now be configured across multiple scales. This allows the source silo sequence of one scale to be applied to all others.
RUNTIME 8 FE
- Security prompt at job start
Optionally, a security prompt can be activated at job start now.
TRADE
- New scale: Frank AWF510
The scale Frank AWF510 can now also be used.
GENERAL
- Performance
Several structural improvements were made, which slightly reduced the loading times of some forms. - Security
Mechanisms that process database connection information are used when a module starts. Security has been improved here so that a potential attacker who has already gained access to a system cannot intercept any further connection data. - Audit
Some improvements were made. - Completion of dosing orders with semi-finished products
Generally, when a dosing order is completed, the expiration date is calculated based on the shelf life specified for the finished product. However, in the case of semi-finished products, unexpected results could occur (finished product vs. component). Therefore, the component's value is now used here, and the schema check now also checks whether there are any semi-finished products with conflicting values set. - Export: Excel
A cryptic error could occur during Excel export in grid views. - Material availability
When checking material availability, the calculation could be incorrect if negative stock levels and different units were present in the target data.
ESACOM
- External batch code verification
Translation did not work in this view.
ESAPRESS
- Rest position
The rest position was not taken from the PLC.
MANAGER
- Target selection
An internal variable could use more memory than necessary at repeated usage. - Contract management - report
The inspection text was not printed. - Schema check – user logon
The schema check did not correctly account for a case of invalid database structure, where a specific unexpected structure prevented user authentication. - Inventory
The validations during saving were not checked in every relevant case. - Edit workspace
The sorting of ‚Available modules‘ was not correct. - Declaration preview
A problem with previewing reports containing declarations has been fixed. - Sorting filters
Lists of available item and stock filters are now sorted alphabetically. - Analysis loading pieces
At the dialog for declaration printing, the last selection of the form to be printed was not preselected, unlike the same process at orders loading. - Create purchase order
When manually creating a purchase order, it was possible that the wrong client was selected. - Order volume check
If the volume exceeds the order target, it can still be saved after a security prompt, now. - Analysis loading
The option to display null sets was incorrectly referred to as alternative source with null sets. - Performance: stock movements
By optimizing a database query, the performance at displaying stock movements was improved. - Performance: analysis dosing orders
By optimizing a database query, the performance at displaying dosing orders was improved. - Edit dosing order
Only finished products with a valid recipe will be displayed now. Furthermore, some targeted performance improvements were made. - Operator log entry at PW-change
When a password is changed, an operator log entry is now always made, so that unwanted changes can be traced.
MFM
- Route clearance
In a specific case, it was not checked whether another TO was already heading to the same storage location. - Error handling
If a (justified) booking error occurred, it was possible that the route or position would still be completed. In another case, it was possible that a database incident resulted in continuing with an invalid TO-id.
RUNTIME 8 BE
- Alternate silo change
A previously resolved issue has been ported from EW9, and a minor issue related to tolerance exceedance has been resolved.
SYSTEMSERVER
- Memory Leak
When transmitting instructions to the PLC, an unnecessary increase in memory consumption could occur.
TRADE
- Send weight to PLC
The default offset was not correct for sending a specific weight value to PLC, if no specific offset was configured. - Picking loading
The loading date was not processed correctly. - Goods receipt: Weighing report
The item information was not retrieved. - Weighing
Previously, the weighing time was taken directly from the scale. To prevent incorrect data due to scale issues, the database time is used now.
General
- Translation
Additional terms have been added for English and Hungarian, and some existing translations have been improved. - Vietnamese
ESAweight modules can now also be operated in Vietnamese. - Login – last user
The last login on a specific system is now saved so that it can be suggested for the next login. - Navigation
The criteria for navigation are now configurable.
Manager
- Automatic email dispatch of system messages
After proper configuration and availability of a given mail server, certain system messages can be sent automatically via email. - Inventory: Information
It is now possible to apply information to all inventories of a specific batch code. - Bulk loading: editable truck license plate
The truck license plate can now also be changed even after the loading process has already started. - Release notes
The link to the release notes leads to the English version for all languages except German (previously only German) now.
- Automatic updating
In views with continuous automatic updates, it could happen—due to security mechanisms or the influence of third-party software—that updates were no longer possible. This situation is now handled more robustly, and the user is informed if necessary. In addition, an issue was resolved where automatic updating could stop even without external influence.
- Relocation analysis (RT)
Performance has been improved.
- Mass changes – LE actions
Additional possible actions have been implemented for mass changes of selected LEs.
- Source/target selection
Performance has been improved.
SYSTEMSERVER
- Station communication
Several improvements have been made. Among other things, units are now taken into account, and scale handling as well as logging have been improved.
MFM
- Production container strategy
A performance improvement has been implemented.
- Production scales strategy
Now it is possible to configure a restriction of the LEs for the line.
ESACOM
- Mobile dosing
The existing scale connection now supports 2 weighing platforms.
- Performance
Targeted improvements in performance and handling have been implemented.
- Target container verification
When scanning target containers, it is now possible to check whether the correct target container is being used.
- Scale verification
A guided scale verification prompt can now be triggered either after a defined time interval or based on expiration-related criteria. The recorded verification data is persisted.
RUNTIME 8 FE
- Column widths
The configured column widths are now persisted and therefore remain after a module restart.
- User ID transfer
The user ID is now also transferred to the PLC when starting or confirming.
LOGISTIC
- Loading – instructions
It is now possible to display instructions at the start and end of a process.
General
- Automatic dosing – storage occupancy
When checking storage occupancy during automatic dosing, only components that are not yet completed can be checked. Confirmed components must not be included.
Manager
- Acceptance (loose)
Printing/emailing a contract reported “Report not found.” In addition, possible user column definitions were not considered in sorting, and an existing supplier batch code was not displayed in the correct column. - System messages
The “Update” button was disabled. - Component traceability evaluation
When using a date filter, the time was not handled correctly.
- Production order analysis
The current contamination group was not used. Instead, the one from legacy functionality was taken. - Edit production order
Data of already dosed batches must not be overwritten. This could occur if an order had already been released, partial dosing data was available, and the release was revoked later. - Dosing recipes
In the dosing recipes overview, date columns were not always sorted correctly. - Goods acceptance
When a new target was specified at the end of the process, it could occur that it was not persisted. - Reports
An issue with handling floating-point values when preparing data for order-related reports has been fixed. In addition, the dosing orders report could not be executed. - Edit relocation order (RT)
The throughput was always overwritten by the area, even if a throughput had already been specified. - Bagging orders analysis
For finished goods postings, the item number was displayed with decimal places. -
Test and archive systems
The notice for marking a test or archive system was no longer displayed in the user interface. - Print preview
Targeted improvements have been made. - Empty message
When an empty message is issued, an entry is now also recorded in the operator log. - Route planning
An error could occur when deleting a route if the corresponding loading was being edited. - Edit component
When the dialog was docked, some buttons could appear at the wrong position. - Loading
When moving picking positions, it must be considered whether the picking is already part of a loading process. Only pickings that do not yet have an active loading are now displayed as possible move targets.
SYSTEMSERVER
- Export
In some standard exports, the version numbers in file names or error messages were incorrect. - Declaration printing
The handling of date formats was incorrect when non-German format settings were used on the operating system. - Inventory as of
The QS ID was not displayed. - Sorting of date values
In some tabular views, sorting by date was not correct.
ESACOM
- Batch code assignment
An issue with batch code assignment has been resolved. - Source LE
When using source LEs, there was no handling for the case where no source LHM was available in the affected storage location.
MFM
- Production scales strategy
The calculation of quantities/volumes for SKs did not correctly account for included SKs. - Route optimization for transport orders
During route optimization of order-related transport orders, the component’s packaging was not correctly considered. - Minimum stock strategy
During internal processing, records without a defined minimum stock were also considered. This could lead to incorrect behavior in certain cases. - Automatic start
If a station was locked, subsequent issues could occur with equivalent stations.
ESAPRESS
- Target change
When a target is changed, the cell is now also updated with the corresponding occupation.
General
- Translation
Additional terms have been added for the English and Hungarian languages, and some existing translations have also been improved. - Scale Dini Argeo
The already supported Dini Argeo scale can now also be connected via TCP/IP. - New strategy type: Manual production scales
This new transport order strategy works similarly to the already known production scales strategy. Based on the scales defined in the strategy calculation and the configured storage locations, the route is built in sequence according to the scales involved in the order. At the ESAcom stations that are reached, dosing is carried out targeting the respective LEs. - New storage location setting: LE requirement
There is a new storage location setting that ensures only LEs can be posted. Any posting to such a storage location without a LE will result in a posting error. - Packing orders
Several adjustments have been made to order creation: If no LHM type is configured, the selection will be hidden. If only one packaging option is available, the packaging station and line will be preselected. If no packaging is available for an item, the packaging display must be cleared.
Manager
- Cross references
To enable more efficient data handling, several cross-references have been added, allowing operators to directly access details from certain views without having to navigate manually. - Multi-Select
To enable more efficient data handling, it is now possible to select multiple entries and perform a batch action in the following views: Dosing orders, Stock (details). - Create packaging orders
Packaging orders can now be created based on loading positions - Edit components
In the scale assignment it is now possible to select whether the stations should also be displayed.
MFM
- Automatic start for non-PSS scales
There is a new configuration setting that allows the automatic start for non-PSS scales to be disabled.
Runtime 8 FE
- Target check
At starting an order, it is now possible to verify whether a production target has been selected and if the item allocation is as expected. This helps to prevent unwanted mixing due to operator errors.
System server
- Batch tracking
The actual quantity for dosing order components is now additionally determined and displayed in the manager.
General
- Loss posting
Loss postings can only be triggered once the actual posting has been completed, as triggering them earlier could lead to incorrect inventory levels. - Posting via DLL
An internal function could trigger an error when called via a DLL in relation to loading equipment in a specific case. - Repeat posting
A SQL error could occur in a specific case when repeating a posting. - Posting overlaps
When overlaps are received, the original posting timestamp of the batch code must be incremented, otherwise sorting issues may occur.
Manager
- Receiving target
An issue with the preselection of the receiving target has been resolved. - Password renewal
An issue with password renewal— which can be enforced based on individual user settings or user templates—has been resolved. - Batch tracking
An issue with the display of data has been resolved. - Configuration
A change of the default user of the “Move Runtime” module was not persisted. - Stock transfer order RT: Preselect area for new orders
An issue related to “Preselect area for new orders” has been resolved. - Loading (pieces)
Setting the operation status is now only possible if it is not already "Finished." - Packing parameters
The "Edit packing parameters" dialog has been revised. - Truck selection
When saving a truck selection, a SQL error could be triggered in a specific case. - Picking – Instruction assignment
A SQL error could be triggered when removing an instruction assignment during picking. - Packing orders
The "Update" button was disabled. - Copy component
When copying a component, the assigned packaging was not carried over. - Analysis
Several improvements have been made to various analyses. - Order planning: confirmation
When confirming individual items, the current container of the item is now suggested. - Goods acceptance – Print preview
An internal error could cause a display issue in the goods acceptance print preview. - Dosing orders
When using recipe variants, it could occur that the line filter did not function correctly. - Stock (totals)
It could occur that an incorrect value for the total was displayed when no stock was available. - Refresh view
If a view remained open for an extended period, it could happen that it could not be updated anymore. - Analysis: Packing orders
The calculation of the number of containers was incorrect. - Acceptance orders
Filter settings were not persisted.
ESAcom
- Remaining quantity
When transferring a remaining quantity to another scale, an item could be transferred multiple times. - Hang
If no release bit for "Release subcode" was configured, stability issues could occur as the system waited for a non-existent release. - Negative weighing
An issue with negative weighing has been resolved.
Runtime 8 BE
- Alternative silo switching
In the case of substitute items, it could occur that the wrong storage location or associated parameters were used.
Runtime 8 FE
- Display update
The display update should only take place after the login has been completed.
LogistiC
- Target scan
An incorrect and unnecessary call for barcode parsing at scanning a target has been removed. - Stock – Source storage location
When displaying the stock of a source storage location, LEs that are already used in transport orders (TOs) should not be considered.
MFM
- Route optimization
If optimization failed for transport type MFM, it could happen that the route was still posted. Furthermore, a posting error is now triggered if all entries of a component have been removed because no valid quantity could be found. - Stock coverage
An issue in the calculation has been fixed.
General
- Database Access
The database access protocol has been updated. This allows for better interaction with current technologies and improved access times. Furthermore, it now enables the option to ensure a state-of-the-art encryption of communication between ESA software and database systems. - Interfaces
The Protection of access information used by system interfaces, as well as authentication-related data, has been improved. - Root Directory
The root directory has been restructured to allow for easier and more granular access control. - Default User
In all standard modules, either a user must be logged in or a default user must be configured. Backend modules must run with a dedicated user. This increases both security and the quality of generated data.
Manager
- Modernization of the User Interface
To further simplify daily operations in the ESAweight Manager, we have carried out a comprehensive update of the development tools and can now offer the ESAweight Manager as a multi-view system. This concept provides improved support for multi-monitor setups. Additionally, we took the opportunity to enhance the visual appearance of the Manager. - Standardization of Filter Options
The previously available filtering options have been standardized, revised, and expanded. - Inventory Details – Flat View
To improve clarity, the “Inventory Details” view is now displayed with a flatter hierarchy. - Stack as of - Performance
Thanks to a revision of the calculation algorithm, larger data volumes can now be processed more quickly here. - Parallel Opening of Master Data
While master data is being edited, it is locked from being edited by another user in parallel. However, the affected data can still be viewed in read-only mode.
More information needed?
Information about older software versions are available upon request.
Ansprechpartner wählen
ESA Elektronische Steuerungs- und Automatisierungs Ges.m.b.H
Fabian Atzenhofer
Sales
