Release Notes for Insight 13.3.0

New Features & Enhancements

Business Intelligence

  • The 'Dashboard Components' form is now available in the browser-based client.
    583201

Catalog Setup

  • It is now possible to assign multiple Value Sets for the same Price Rule to a Price List.
    When evaluating Value Set values, only one result value is selected per Price Rule, i.e. the first result in asccending sorting by Sequence and then Rank.
    This ensures that only one Value Set value is selected as the result per Price Rule.
    Image
    593469

Core

  • Descriptions of attribute list values can now be translated, e.g. for use in reports.
    567808

Integrations

  • The new action 'Winstore: Synchronize remnants created in Winstore' allows to import Remnants created in Winstore to Insight.
    567787

Inventory

  • The new Action Maintain Nettable Indicator, run from the Warehouse Container Inquiry form, allows users to set or clear the Nettable flag for the selected warehouse containers.
    For more information, see Using the Warehouse Container Inquiry Form in Purchasing and Inventory.
    The new Action Maintain Nettable Indicator for Warehouse Location, run from the Location Inquiry form, sets or clears the Nettable flag for the selected location(s). If Recursive Update is selected when the Action is run, the flag is also set for the warehouse containers stored there.
    For more information, see Using the Location Inquiry Form in Purchasing and Inventory.
    567593

Machining

  • Added new system-action 'Winstore: Send Material Items to Winstore' that can be run from the Items form, where the user can select the Items (Boards) to be created in the Winstore board library.
    567764
  • The 'Prevent Edge Blowout' function in GenPost has been improved to work on both open contours and closed pockets.
    567769
  • GenPost functionality has been added to allow a second tool to be used for the cleaning function, which is different from the main cleaning tool due to tool rotation requirements.
    567798
  • The NestLib optimizer now respects individual edge trims set on material boards.
    566935

Purchasing

  • The length of the Purchase Order Line Description (polDescription) has been increased to match the Item Description (itmDescription) length of 100 characters.
    566463
  • Specifying the Vendor for new Purchase Orders is now facilitated by a lookup combo-box with type-ahead feature.
    566971

Sales

  • Added new additional filter for Shipment selection to system-action 'Create Invoices from Invoiceable Entries'.
    594346
  • Added new option 'Prorate' for line charges and header amounts to system-action 'Create Invoiceable Entries for Shipment'.
    597509
  • Added new action parameter 'Order Type Codes' to system-action 'Create Invoiceable Entries for Order', which allows to define Order Type Codes in which Invoiceables are created also for Order Lines without an Instance (BOM).
    This function can be used, for example, for credit note orders where lines have been copied from the original order that do not require a BOM in the credit note.
    Multiple Order Type Codes can be specified separated with a pipe symbol '|'.
    597524
  • When adding Sales Order Relationships, the user and time are now logged for improved traceability.
    567862
  • The width of the product quantity input field in the desktop-based Sales Orders form has been increased to display up to 6-digit quantities.
    567568
  • The Sales Order Management module and related forms are now available in the browser client.
    New available forms:
    • Sales Orders
    • Invoices
    • Buying Groups
    • Customers
    • Contacts
    • Sales Order Types
    Some features are not yet available and will be added in a future release, such as: Commission calculation, Order Styles, Feature Sets, user-based customer restrictions, on-the-fly one-time use address creation, replacement parts selection/processing.
     
    Note: In order to use 2 and 3-way exclusions in the web form Sales Orders, the exclusion matrix defined on the Catalog Version needs to be converted to Feature Option Constraint Matrices. If this step is not done, no options will be marked as excluded.
    • On the Catalog Versions form select the Catalog in the grid you wish to convert.
    • Run the System Action 'Create Feature Option Exclusion Matrices'.
      • This action has the option of converting all exclusions, or you can target a specific exclusion.
      • Only supports running against a single catalog at a time.
    The desktop Sales Order logic still uses the original Exclusion Matrix logic.
    The current Exclusion Matrix tab is still to be used to make changes.
    Any changes made post action execution will require rerunning the action again to merge the changes to the matrices.
    There is no interface to maintain these new matrices directly. Eventually the current catalog version Exclusion Matrix tab will be used to maintain the new data and it will be used in both web and desktop version.
    602951

Services

  • The 'Service Order Scheduling' form in the browser-client now supports scheduling a single job that spans multiple days without being split into multiple tasks.
    Use the system setting inSight.ServiceOrders.SchedulingSplitTask to control this:
    • 0 (New method) = The scheduled task will not be split into multiple tasks when it needs to span multiple days.
    • 1 (Default original method) = The scheduled task will be split into multiple tasks when it needs to span multiple days.
    This will allow a scheduling user to move a multi-day spanning task as a single entity instead of having to adjust multiple individual tasks if changes are needed after the initial scheduling. 
    576093

Shop Floor

  • The AutoDesk Viewer checkpoint frame (TframAutoDeskViewer) has been removed due to compatibility reasons.
    570963
  • The 'Work Orders' form is now available in the browser-based client, allowing users to view information about Work Orders, also known as Containers.
    567281

System Admin

  • The 'Users' form is now available in the browser-based client.
    583215
  • The 'Application Log' form is now available in the browser-based client.
    583206

System Setup

  • When adding or modifying Addresses, the user and time are now logged for improved traceability.
    567825

UI/UX

  • The concept of Pushover Grids has been revised and in some places replaced by simpler operating concepts.
    • If there are only a few data to choose from, they are now displayed in a table where you can assign the data by simply ticking a checkbox.
      Example: Business Intelligence > Charts > User Groups:
      Image
    • If there are many records to choose from, clicking the Add button will open a popup dialog where one or more records can be selected and added accordingly.
      Example: System Administration > Users > Settings:
      Image
    582978
  • Clicking an attachment preview image in the browser-based client now opens a full-screen view of the attachment.
    567749

Workflow

  • File monitors can now automatically archive source files, i.e. move them to an archive folder.
    If an archive directory is specified, the file is moved there instead of being deleted.
    The function can be enabled in the configuration dialog:
    Image
    566233

Issues Resolved

BOM Processing

  • If HB copy is enabled and Nucleus processing is used, all lines that found a match for copy were failing with 'An object or column name is missing or empty' error
    592380
  • The wrong procurement method was used if an MTS item added to the top level item via Item Family criteria match
    581275
  • Incorrect BOM results were experienced when using Item Component Persisted Property formulas, which override Item Persisted properties
    600857
  • System Action 501 - 'Reprocess Order Line BOM' was showing incorrect Parameter listing in red
    591827

Business Intelligence

  • Dashboard level parameters were not cascading to individual Dashboard components in a Dashboard layout
    600184

Catalog Setup

  • In the IDM Catalog form there were several issues with data not displaying correctly, as well as a performance issue when using the Exclusions tab
    590139
  • If columns in Catalog Versions > Exclusion matrix were re-ordered by a user, multi-selecting values to exclude were not being set reliably
    603612
  • The IDM Catalog form became unresponsive when adding a new catalog
    589806
  • Invalid value for field 'optionDefaultValue' error was occurring when using Product Identity with non-numeric feature option value
    599714
  • In the Features form, a type mismatch error in occurred in the formula syntax check when creating 2 Features in a row
    598741
  • A 'Deferred prepare could not be completed' error would occur in the Features form if you have selected a Feature and click on the Options grid > Where Used tab
    592097
  • Duplicate exclusions existed when exporting IDM Catalogs.
    572148

Core

  • The Update Matching Core Address feature was not working correctly
    594918
  • Access violation occurred when opening forms with <FindRelated/> elements implemented with database form customizations 
    574826
  • Value Selector form in Lookup Matrix Value Sets would not display selected view after switching between Value Sets
    591664
  • After upgrade to 13.2, Data Event defined for Sales Orders were no longer working due to a database schema change
    593859
  • Errors were occurring when trying to delete Notes of certain origins like Sales Orders, Sales Order Lines, and Organizations
    594175
  • System Action 134 - 'Update Sales Order Line Status by Prod Order' contained incorrect logic to determine if the supplied Sales Order Line Status valid was valid
    593853
  • When using a Monitor to copy a 2020 Design .kit file to a different directory before processing it, the .kit file the blob to file action type corrupted the .kit file. 
    601915
  • Insight Web drop down list attributes contained no items after changing constant data language.
    573066

Engineering Setup

  • Edge Angle field was missing from the Item export/import infrastructure
    582610
  • Edge information was missing for Items with greater than 20 edges
    601889
  • Machine Sequences with machine output were not displayed in Order Line Instances form
    583004
  • In the Items form, it was not possible to add a material definition for the Item on the Materials/Edges tab
    598611
  • 'Is Editable' field was not set for persisted criteria properties if you had an item from Construct which had an item family with a template item
    600256

Inventory

  • Inventory Receipt Transaction dates were not being set correctly to the Purchase Receipt date
    592030
  • In Inventory Transactions, the dropdown values for  Lot Number returns several rows for the same lot if it was stored on several Inventory locations
    597470

Machining

  • Block nesting algorithm with vertical orientation option set produced poor optimization output.
    565994
  • In GenPost, the ContourToPocket function doesn't handle non top/bottom contours correctly when using XML processing
    588423
  • GenPost was displaying wrong dropdown values for the Routing Entry and Exit list when language was set to Portuguese
    599946
  • GenPost was sometimes placing the labels off of the item for certain label sizes
    597324
  • Create Panel Optimization Batch action was not updating Work Orders to the specified Status Value
    599370
  • When GenPost flips parts based on thru-machining, the Z value was incorrect
    598605
  • Some Panel Optimization Batch Actions were incorrectly setting the action return code to 2 instead of 0 when successful
    599672
  • GenPost was not rotating the label according to the part orientation in the optimization pattern
    595423
  • In Panel Optimization, incorrect Y dimension positions were being set for some items in formation patterns
    590047

Purchasing

  • Status list for Purchase Order Line Receipts was incorrectly retrieving the available status values from the Items status values
    587119
  • When processing Order Item Receipts for Outsourced Operations, the Operation Routing Status override was not being used
    598347
  • In the Purchase Demand form, the icon which used to be used to generate Purchase Orders was changed, which caused confusion
    591460
  • Imported Purchase Orders remained in a locked state after import
    602547

Sales

  • If there was no customer default for Sales Channel, there was no way to select a valid Sales Channel in the Sales Order form
    583365
  • When configuring Order Lines in the Sales Order form, configurator logic using Constraint Matrices were causing error 62153 'Constraint Violation in Matrix' in certain conditions
    590786
  • Access Violation was happening in Customers form, Relationships tab when creating new entry for Role 'Represented By' if Organization selection is used
    586874
  • Order level Price Rules based on buying group were not being calculated  
    586603
  • Sales order price rules could be incorrectly omitted if they were based on CustomerGroup code.
    570661
  • Slow performance was experienced in Sales Order Inquiry due to unnecessary retrieval of Time Tracking data, even though user was not actively viewing it
    598717
  • Status Change in the Projects form switched to the Sales Order origin if the Sales Order form was left open
    590226
  • Sales Orders form Costing tab was showing cost values for the entire Project that the Sales Order was assigned to
    587007
  • It was not possible to use Attribute values as search criteria in the Bids form
    598210
  • Export Sales Order Line BOM To XML action failed if there was a configured item in the BOM and include As Processed was selected
    589666
  • Performance was poor in the Sales Channel form, Customer tab
    589598
  • In the Projects form, Task sequences were unexpectedly changed when making changes to the task structure
    598308
  • Poor performance was experienced in the Exclusions tab of the Organizations form when viewing Buying Group data
    592346
  • The Market field was not available to be changed in the Bids form
    581157
  • The Styles grid in the Sales Order form was continuing to validate Features even after they were deleted
    592590
  • Buying Group was not displayed in Sales Order from even when the Buying Group was saved correctly for the Sales Order
    591194
  • The Customer Group Code and Sales Channel Code fields were not included in Sales Order Import form
    594177

Scheduling

  • Stop  information was not displayed in the Shipment Inquiry form
    586582
  • Error occurred in MTO Inventory form if search criteria Commodity Group or Persisted Properties were used
    587060

Services

  • Scheduling large Service Order Jobs with split enabled was only scheduling the first time interval instead of splitting it over multiple periods
    595284

Shop Floor

  • In the Manual Containers shop floor component, grid views would revert to the default view after a scan was performed
    582943
  • Error was encountered when using the Form Action icons to launch actions in the Shipment Loading shop floor frame
    590238
  • In Shop Floor screens, the Validate Container Scan process was not taking Operation Routing Status override into consideration
    595212

System Admin

  • Copying an Email Generation Action did not copy the HTML Message content
    582678
  • It was not possible to remove unused Attribute list values from an Attribute
    581227

Workflow

  • In Status Workbench, the view was annoyingly re-adjusting after creating new Statuses or changing status value of Statuses
    588225
Was this article helpful?
0 out of 0 found this helpful