MindGEST Last Features
Several improvements to the “Last Lattice Tool”
Better lattice controls and more intuitive UI to manipulate and deform the Last.
To find these new optimizations, navigate to: Last>Modify>By Lattice Grid
UI/UX Enhancements
Possibility to change the order of the columns
New option to change the columns order, to give a better view to the operator when checking the tables.
Add shortcuts for forward and backward on mouse buttons and F5 for refresh
Ability to use mouse keys to go forward and backward inside the tabs, and also use F5 to refresh the pages removing the obligation of use the options for it.
Status bar on lists with summarized information and visualization options
On the bottom we have a small status bar where we can see the total of entries and how many are selected. Also three visualization shortcuts to expand, collapse or expand to the level of the selected entry.
Enable search on all visible list fields
When searching all the tables where the data is displayed should appear in the list.
PDM Core/Explorer Improvements
Progress bar for “long operations” when exporting reports
Exporting CSV and Excel files will generate a progress bar that becomes particularly evident during "lengthy operations". This feature assists the operator in recognizing that the software is actively engaged in a task.
Allow filtering by remnants on collecting job (Assignment)
Possibility to filter while choosing the materials for the collecting job on the assignment tab, allowing to choose the remnants.
Optimize Cut orders deletion
The process of removing or eliminating cut orders has been refined and improved for efficiency and effectiveness.
Possible to create another nesting job when cutting
Previously we had to change the state of the cut order in order to do another nesting job for the remaining parts or deviation parts, now is possible without having to change it.
Data integration Center improvements
Export Data Integration Center task logs
Possibility to export logs information to a CSV or excel file.
Optimize table loading for large datasets
Tables with thousands of entries were optimized to show.
Data Integration Center task logs should contain all needed information for an operator to take actions
Some extra information was added to the logs in order to the operator to extract the most efficient report possible:
- Detailed error message,
- Warning message will appear on log when task is deactivated,
- Uniformization of business entity names, for example: Source material for Material, Cut job for Cut Order, etc.
- License verification,
- List of conditions to disable the task.
Default value for time range when enabling scheduling should be full day
Default period for the task to be runned when trigger is set to schedule is automatically set to 24h.
Warn which model files where not correctly imported
Warning message on logs if a model is not assigned to the cut order while importing and trying to import a cut order with a model that doesn`t exist on the database.
Conflict resolution option for Import Model action
New feature that allows the user to choose what to do in case of a conflict while importing a model with the same name.
- Ignore – It will not import the file again giving a warning message that there is nothing to save,
- Replace existing model – Replace the existing model by the new one being imported,
- Rename repeated model – Repeated models will be renamed when imported,
- Update model, replace existing parts – Existing models will be updated and parts that were already there will be replaced,
- Update model, rename repeated parts – Like the previous option the existing models will be updated and repeated parts are renamed.
Material Estimation Improvements
Improved readability of part thumbnails
Part thumbnails are displayed with all the information from the drawings like punches, notches, quality areas for better recognition of parts.
Load old projects with a large database (missing data)
On a substantial database, the platform will now display all the accessible projects within MindCost. Previously, there was a limitation in place that restricted searches to the initial 1000 models. This restriction was implemented to minimize the loading time.