Overview

This article describes fixes provided in the Upchain 21.3 major service update.

In between major service updates, Upchain deploys weekly, minor updates to address any critical issues reported by our customers. This article includes details of the changes introduced in the weekly updates, denoted by an asterisk (*).

Administration

• Flashing grey error messages are replaced with static red messages that are displayed when the Tenant Admin exceeds maximum permitted character length for fields in the ‘Attributes’ sub-panel, accessed when viewing a selected task type from Administration > Business processes > Task types.

Advanced Search

• Advanced Search on Upchain Web now provides better and faster search results both in general and specifically when one of the following filter combinations are applied:
  • Item Version + Project
  • Item Version + Manufacturer; and
  • Item Version + Project + Manufacturer.

BOM

• *The items shown in the ‘Where Used’ tab in the Genealogy section were not clickable. The items are now clickable to allow users to navigate directly to the item without needing to search.
• *Suppressed files are also downloaded when the assembly is downloaded from Upchain Web. This behavior is now consistent with how an assembly with a suppressed item is downloaded from the CAD Plugin.
• *There was a discrepancy between the capitalization of certain item attributes shown in the CAD plugin, Web, and Advanced Searches. This has been fixed so that, even when the tenant property item.attribute.uppercase is set to true, the values taken from their picklists for Material, Shape, Finish, and Heat Treatment will always match exactly how it was input.
• *Users were unable to download CAD files from items in the Web application.

Business Processes

• *Users may assign a Quality Assurance (QA) task to a supplier. Upchain no longer prompts ‘User with licence: FREE cannot be assigned to an activity.’ when attempting to assign a QA task to a supplier.
• Users may assign another Team Member to the role of ‘Responsible Designer’ when viewing a CR’s details on the ‘Business processes’ page, instead of a blank drop-down.
• *Change Notices were not displaying all electrical items within an electrical package if they existed in more than one kitting location, and the Effective Date filter was being used.
• *When checking for missing attributes, the System Decision Primitive was not correctly identifying when purchased part attributes were missing.
• *The Filter by Selected Components option was expanding the full tree on a Change Notice rather than displaying selected components on the CN.

CAD Plugin

• Check-ins are successfully performed for an assembly with an eBOM-only item in non-active configuration. The check-in is no longer blocked by an error message.
• Translations are not created for a CAD model’s drawing when only the CAD model is checked out and checked back in.
• The Generic CAD Plugin no longer generates the following error: ‘One or more errors occurred’ when a freshly released item is re-opened in the Generic CAD Plugin.
• Refreshing the ProjectBOM, in the SolidWorks CAD Plugin, for items that do not have one or more of these properties ‘ConfigurationName’, ‘HasDrawing’ or ‘LockList’ no longer generates an error and refreshes.
• *Catia 2016 no longer stalls when a newly created drawing is left open while refreshing the cBOM.
• Suppliers are now included in the drop-down options for the ‘Assignee’ field when creating a task in the CAD Plugin.
• Users were unable to release a new revision of an item if the item numbering rule switched from double character/digit revisions to single character/digit revisions.
• Custom item attributes set to Read the value from the CAD file were not populating during a save or check in.
• The Stale cBOM Report would not generate for certain items because of an issue trying to generate thumbnails. Thumbnail generation has now been removed from the report.
• Users were unable to release a new revision of an item if the item numbering rule switched from double character/digit revisions to single character/digit revisions.
• *There was some performance degradation in checking in large assemblies that has been improved.
• *Users were able to make changes to NX files that were not checked out to them because the plugin was setting the incorrect read/write lock on the file.
• *When users refreshed the cBOM view and encountered validation errors on old file versions within a read only assembly, Upchain would prompt users to save the read-only assembly. The prompt to save no longer appears and the latest file versions are downloaded as expected.
• *When the Effective Date filter was selected in the Download window, the cBOM was not being displayed.
• *The Download window was indicating that a newer file version existed, but the latest version was actually obsolete. Obsolete items are now ignored.
• *Custom item attributes that were set to WRITE were not being updated in the CAD files during a save or check in.
• *Cloning an item in the CAD plugin would reset all of the out-of-the-box eBOM attributes (ie. Spare, PC/WP, MRT, C of C, Apvl, and Reference Only).
• *The Material selected in the CAD plugin was only updating the material in the default SolidWorks configuration and none of the other configurations. SolidWorks configurations were not enabled and so it was expected that the material would be applied to all configurations.
• *Performance issues related to refreshing the cBOM in the SolidWorks CAD Plugin are resolved.
• *Custom properties set to WRITE were not being updated in the CAD files if the attributes were changed in Web.
• *With SolidWorks configurations enabled, registering a drawing to a part with configurations was creating a new version of the part with the drawing’s name.
• *The plugin was not retrieving the latest versions of an open assembly that had been released in the Web in the meantime.
• *When revising a released component, the link to the drawing was being lost.

Main dashboard

• *The following generic description ’<user’s name> changed, description, name, priority on ’ listed under the Activity Stream section on the main dashboard is replaced now with a more descriptive message. For example, when a project’s priority is changed, the description now reads as, ‘<user’s name> changed priority on ’.

Manufacturers API

• When creating a manufacturer’s location using the following endpoint POST /api/v2/manufacturers/{manufacturerId}/locations, the correct values are recorded for the ‘primary’ field. The ‘primary’ field is set to ‘true’ when the location is a primary location, and set to ‘false’ when the location is not a primary location.
• When creating a manufacturer’s location using the following endpoint PUT /api/v2/manufacturers/{manufacturerId}/locations/{locationId}, the correct values are recorded for the primary field. The primary field is set to true when the location is a primary location, and set to false when the location is not a primary location.
• When creating a manufacturer’s point-of-contact, using the following endpoint POST /api/v2/manufacturers/{manufacturerId}/locations/{locationsId}/contact, the endpoint correctly records the information related to the contact: name, city, state, zip, and country instead of Null.
• When editing a manufacturer's point-of-contact, using the following endpoint PUT /api/v2/manufacturers/{manufacturerId}/locations/{locationsId}/contact/{contactId}, the endpoint correctly records the information related to name, city, state, zip, and country instead of `Null’.
• When creating a manufacturer’s point-of-contact using the following endpoint, POST /api/v2/manufacturers/{manufacturerId}/locations/{locationId}/contacts, the endpoint correctly records the primary field as true when the location is a primary location, and records false when the location is not a primary location.
• When editing a manufacturer's point-of-contact using the endpoint, PUT /api/v2/manufacturers/{manufacturerId}/locations/{locationId}/contacts/{contactId}, the endpoint correctly records the primary field as true when the location is a primary location, and records false when the location is not a primary location.
• The following endpoints do not return a previously recorded primaryContact in the header when subsequently, this information had been deleted:
  • GET:/api/v2/manufacturers/{manufacturerId}/locations/{locationId}, and
  • PUT:/api/v2/manufacturers/{manufacturerId}/locations/{locationId}/contacts/{contactId}

Project management

• Tasks created using the () button after searching for a parent activity in Quick Search are now successfully added under the Project overview section on the ‘Project management’ page.
• Only tasks associated with an active project are listed for Tenant Admins to reassign on behalf of Out-of-Office (OOO) or former Upchain-users.
• *Projects could not be reopened after being closed or archived if the user who closed the project is a Tenant Administrator.

Project settings

• Editing a project name no longer generates an error if the project name exceeds 80 characters in length. If the project name exceeds this limit the excessive characters are automatically cut-off when displayed in Upchain.
• A project’s description (up to 1000 characters in length) is fully displayed on the top section of the ‘Project settings’ and ‘Documents’ pages in Upchain Web. The user may use the newly-introduced scrollbar to see the full text.

Reports

• BOM Reports generated for an item are retitled as '<Item#_ItemName_BOM_Report-YYYYMMDD-HHMM>.xlsx' instead of '<Project#_ProjectName_Report-YYYYMMDD-HHMM>.xlsx'. Upchain for Office
• Upchain for Office does not stall when a user, who does not belong to any project on the tenant, attempts to create a task. Now Upchain prevents users, who are unassigned to any project, from creating a task with an error message.