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 (*).

APIs

• When adding a part to Upchain using the POST: /api/BOM/v2/items endpoint, the part’s cost is recorded as the value entered for the estimated cost field in the request body. Note: Update a part’s cost by providing the modified cost in the estimatedCost field using the POST: /api/BOM/v1/part_edit endpoint.
• *The POST: api/BOM/v1/lock/{itemVersionId}/actions/release-item-lock endpoint could only remove EDIT locks. Now the endpoint removes both EDIT and CHECKOUT locks.

BOM

• *In the BOM > eBOM table, edits to an eBOM’s attributes such as, ‘Spare’, ‘Ref Only’, etc. are saved as expected.

• *SolidWorks’ custom properties are updated along with common and custom attributes whenever an item is created, checked in, checked out, edited, or saved.

• When adding a part to Upchain using the POST: /api/BOM/v2/items endpoint, the part’s cost is recorded as the value entered for the estimatedCost field in the request body.

• *In the Bulk export window, the drawings () column has a checkbox for root items so drawings for root items may be included in the export.

• */api/BOM/v3/file-versions/{fileVersionId}/children-bulk endpoint no longer returns the following 400 HTTP error: ‘Children items list contains duplicate item IDs.’ if the response contains a unique value when considering both the fileVersionId and configurationName fields.

• *In Upchain Web, when a user initiates a download from the BOM page the user is notified that their download is being prepared.

  

  The notification effectively prevents the user from clicking the Download button repeatedly - a common use case when downloading large assemblies.

• *When a child-item is added multiple times to a single Change Request (CR), because it belongs to multiple parent-child relationships, and then if one instance of the child-item is removed from the CR then the structural lock is still displayed for the remaining instances of the child-item in the CR, as expected.

• *Cloned copies of items registered from the CAD Plugin for Inventor no longer display a 90-degree skewed preview of the model when the original item has a Default Design View and a Level of Design (LOD) with a suppressed part.

• **Descriptions for Change Requests, Change Notices, and Investigation Requests provided in Chinese and Japanese display correctly, both in Upchain Web and the CAD Plugins.

• *The Locked Objects section for a project’s Design dashboard was missing the list of locked objects (including check out locks).

Business Processes

• When a project had an Effective Date set, eBOM attributes were not being carried to a Change Notice, meaning users were not able to view this information when reviewing the Change Notice.
• *When a project had an Effective Date set, the System Decision primitive in Change Notice workflows would not follow the correct logic if an item was included in the CN because of the Effective Date.

CAD Importer

• CAD Importer is no longer caught in a cBOM loop when importing a CAD assembly created in Inventor.

CAD Plugin

• *Users are no longer blocked from downloading large assemblies due to an expired access token. Upchain automatically refreshes the access token after the first unauthorized request.
• *Checked out items are restricted from being sent to a Change Request (CR) from the CAD Plugin. This behavior is consistent with how locked items are restricted from being sent to a CR from Upchain Web.
• *Save/check in is not blocked for an item after associating a second drawing with it.
• *When viewing the drawing of a model, the CAD Plugin does not prompt the user to select a version of a drawing when there is only one version.
• *PLM_FileVersion property correctly tracks the item’s latest version number after performing a check in or save operation. This effectively prevents users from getting stuck in an endless validation loop due to a mismatch between the version number assigned to the item and the version number recorded for PLM_FileVersion.
• *Upchain optimized accepting authorization requests from the SolidWorks CAD Plugin to resolve instances of users being unable to launch the plugin.
• *Item’s cost is correctly updated to Upchain Web when modified from the CAD Plugin, provided the user has selected the item’s associated project. Otherwise, the updated cost is applicable only to the user who modified the cost.
• *In order to prevent users from modifying the structure of a parent-item that is a part of a CR workflow in-progress, Upchain prompts an error message to inform the user that a check in is currently not allowed.
• The buttons to add a folder or document are disabled to prevent users from adding documents or folders to a project’s document-category when a released or pending-release item is selected.
• When viewing the description of an assignment, the label is fully readable and letters are not cut-off.
• When a user has multiple CAD models open in Inventor, the cBOM view correctly displays the last refreshed inactive CAD file in a dull grey. When the user clicks the refresh button the cBOM view is updated with the currently active CAD design.
• PDFs of Inventor CAD-model drawings contained a cut-off page and a blank page. Now PDF versions of DWG files have a standard 3 pages:
  • The first page contains all of the views from the DWG file, and
  • The subsequent pages contain the model’s common and custom properties.
• The Documents button () is no longer disabled if an assignment already has documents associated with it.
• Cloning a configuration item with drawings no longer causes Upchain for AutoCAD to freeze.
• When viewing AutoCAD drawings with external references in the Generic Plugin the full structure is reflected in the cBOM view and not just the parent item.
• Users are alerted if an eBOM loop occurs for a root only check in.
• In the CAD Plugin for Inventor, when filename.pattern is configured the drawing associated with an item no longer defaults to its original name when the drawing is loaded and the cBOM is refreshed.
• *Locked objects are now consistently listed under My Workspace > My Locked Objects section in the CAD Plugin just as they are listed under Project Dashboard > My Locked Objects in Upchain Web.

Documents

• *Upchain no longer applies the default document numbering rule if a document folder contains a document that is a part of a workflow in progress. Upchain always applies the selected document numbering rule (whether custom or default) when adding new documents to a folder, without exception.
• Upchain now prompts an error message when team members attempt to check out a published, project document.
• Documents added to a custom specification folder, may still be found in the folder after the associated item is released.

Projects

• Tenant Administrators are no longer blocked from editing a project’s settings when the project is in a ‘Draft’ state.
• The /api/workflow/v1/projects/{projectId}/actions/start endpoint first validates whether the authenticated user is the creator of the project (identified by {projectId}) or is a Tenant Administrator. If this validation fails, then a 403 HTTP response is returned.

Reports

• *When an item’s ‘Spare’ property is set to ‘unknown’, the BOM Report records a hyphen (‘-’) to represent ‘unknown’ instead of ‘No’.
• *When a project is configured with an effective date, the generated BOM Report no longer records ‘0’ in the quantity column. The item’s quantity, as recorded when the ‘As Saved’ filter is applied to the eBOM table, is recorded.

Search

• The Advanced Search feature’s search results no longer list ‘UG’ in the ‘CAD type’ column for PNG-type translation files. This column is left blank for PNG-type translation files.

Suppliers

• *Suppliers may successfully view 3D models in the supplier portal.

Users

• *Users may now be removed from a project with a workflow-in-progress that requires that user’s role - provided there is someone else on the team with the same role. If you are attempting to remove the only team member with the role that is required for the workflow to progress, then Upchain prompts the following new error message: “The role is currently being used in a workflow. If you want to remove this user, please assign a different user to this role first.”

Workflows

• Task workflows, configured with a ‘decision’ primitive, require comments from the assignee when the ‘Approved Comment Required’ and ‘Reject Comment Required’ attributes are checked. Prior to this fix, when the assignee’s decision is to reject the task, the workflow always required a comment; and when the assignee’s decision is to accept the task, the workflow never required a comment - irrespective of how the ‘Approved Comment Required’ and ‘Reject Comment Required’ attributes were configured.