Share

Fixed issues in Upchain 22.1

Overview

This article describes fixes provided in the Upchain 22.1 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

  • *The names of customized task types may contain multiple spaces between characters. Upchain no longer excludes these extra spaces. Task types’ names are listed exactly as they are saved.
  • *Advanced Search, in the CAD Plugin and Upchain Web, no longer sporadically returns empty search results.
  • Using Insert after performing a search no longer returns a more-recent version of an item if its status is Obsolete.

API

  • The POST /api/bom/v1/file_version/{fileVersionId}/write-properties endpoint writes file properties for phantom items when the includeCustomAttributes field is set to true instead of returning a 500-http error code.
  • In the POST /api/bom/v1/file_version/{fileVersionId}/custom_properties_status endpoint, the hasCustomProperties field accepts toggling between true and false values and not just setting false to true.
  • *The POST /api/project/v1/projects endpoint creates a project as expected instead of returning a 500-http error code.
  • *The POST /api/supplier/v1/parts endpoint adds or updates a part’s currency code when currencyCode is provided in the request body.
  • *The response for GET /api/user/v1/locked_objects no longer excludes locked phantom objects when includePhantoms is set to true.
  • *If there are multiple entries for the GET /api/user/v2/users/{username} endpoint, all entries are returned in the response instead of a 500-http error code.
  • *The GET /bom/v1/part_version/{partversionId}/revisions endpoint returns only eBOM revisions of the specified part and not mBOMs.
  • *The POST /api/item/v1/item-version/{ItemVersionID}/generate-translations endpoint no longer returns a 400-http error code stating that the file name is invalid when item version Ids and not file names were a part of the request.
  • *The POST /api/bom/v1/file-versions endpoint no longer returns a 409-http error code when uploading original files to a tenant.

BOM

  • *Exceeding the 256 character limit for an item’s revision note does not generate a 500-http error code.
  • *The PDF translations generated as a part of a CR workflow are now listed, as expected, under item details pane > Documents tab > Translations section.
  • *Special characters are not stripped from item names when saving the item in Upchain.
  • *Clicking Download in the bulk-export email no longer triggers a 401-http error message.
  • *Optimized performance prevents seeing a blank screen in some instances when a CN fails.
  • *When viewing a model in the 3D Viewer, the ‘Hide’ option in the right-click menu successfully hides the highlighted part or component. Prior to this change, the part/component could only be hidden by checking the box corresponding to the part/component that was required to be hidden.
  • *An item’s attributes such as eBOM notes, spare flag, quantity, etc. can no longer be modified if the item’s parent is released.
  • *When reusing a saved search ‘Projekt’ type is no longer automatically reset to ‘Artikelversion’. This issue only occurred when running Upchain Web in German.
  • *Cost information for an eBOM is saved, as expected, after modifying this information.
  • *Clicking on the preview of a CAD model opens the model in the 3D Viewer and no longer returns an error message.
  • *Changing the quantity of an item that is a part of a project with an effective date in the future does not generate a 500-http error code.
  • *Upchain no longer prevents published PDFs from being checked out.
  • *When exporting documents, Upchain no longer omits the document number from the document’s title. This effectively prevents related issues when checking the document back into Upchain such as updating the document’s version number.
  • STEP translations no longer show an assembly as randomly placed parts but reflect the model created in Solidworks.
  • The non-descript 500-http error code is replaced with a new error message that identifies the duplicate end-item that you are trying to paste in a project.
  • Downloaded PDF and DWG translations correspond with the released version of the item. Older versions of the PDF and DWG translations are no longer downloaded.
  • When an imported drawing is a DWG file, clicking on the drawing icon drawing icon opens the item details pane as expected.
  • When the item has an imported drawing, that is in an accepted file format such as PDF, the drawing icon drawing icon is active and no longer remains in an inactive state.
  • *Bulk-export emails were reported as missing. On investigation it was determined that this occurs when a requested item's document was not available on the vault. After the fix, emails are received as expected; the ZIP file can be downloaded from the provided link; and if any documents are not available on the vault, these are listed in a separate PDF attached to the bulk-export email.

Business Processes

  • *When a requirements workflow has a task, Start Workflow in the task’s details pane moves the workflow along instead of keeping the workflow static.
  • *Change Notices (CNs) are no longer missing from the Previously Viewed field’s drop-down list.
  • *When viewing the details of a CN-in-progress (in the Workflow actions workflow actions tab tab), tasks and decisions are included in the details.
  • *For projects with an Effective date in the future, a CN workflow no longer automatically requisitions a reference-only item. Investigation Requests (IRs) can be successfully generated from the 3D Viewer when:
    • The opened document is attached to an item in Upchain using the Import feature; and
    • *Viewing CAD models with Upchain documents attached.
  • *Deselect All Released works regardless of whether the option is selected before or after the CN workflow is selected.
  • *When a project has Effective date configured, and the selected CN workflow has the System primitive configured as Compare with Latest eBOM type, then the items that have revisions of the item in another assembly do not compose the requisition request.
  • An apostrophe in an CN's description no longer triggers an error that prevents the CN from being saved.
  • When the end of a CR workflow includes a task primitive with Create CN enabled, the Create CN button is no longer shown as inactive throughout the CR workflow but remains hidden until the workflow reaches the task primitive that has Create CN enabled.
  • Show orphaned button is no longer hidden when a CN workflow is completed or canceled.
  • After investigations into the cause for CNs being caught in a gridlock when multiple team members attempted to approve a task, the cause was identified as being related to missing messages from the Java Message Service (JMS). As a part of the resolution, the system will attempt to resend the JMS message up to three times in order to progress the CN workflow, and if the CN workflow still fails to progress then an error message is displayed. You will then need to contact Support to cancel the CN before resending the assembly through the CN workflow.
  • *When child items, belonging to electrical packages, are put through a CN workflow, the child items are no longer incorrectly listed as orphaned items.

CAD Plugin

  • Upchain no longer creates a new version of a Toolbox part when it goes through a Change Request (CR). This change effectively resolves failing CRs for assemblies with Toolbox parts.
  • As expected, check in fails when duplicate item numbers are manually entered in the BOM wizard. A new error message identifies the items with duplicate numbers and you can restart the BOM wizard to correct the duplicate entries.
  • *Checking in a parent assembly with child items that are checked out by another team member no longer removes the read-only status for the checked out child items. This issue occurred only in the SolidWorks CAD Plugin.
  • *When viewing an item’s details in the CAD Plugin, after selecting a project, an item’s currency and cost always reflect the project-division’s currency settings and not the user-division’s currency settings. This removes any discrepancy when viewing the item’s cost in the CAD Plugin and Upchain Web.

    Note: If a project is not selected then the item’s currency reflects the user-division’s currency.
  • *Upchain CAD Plugin for SolidWorks does not stall SolidWorks when an open item’s configurations are changed and then the item is checked out using the plugin.
  • *For released child-items, with a direct parent in development, the ‘CofC’, ‘MTR’, ‘Approval’, ‘PC/WP’ and ‘Notes’ attributes can now be edited.
  • Multiple users on a single machine are no longer blocked from accessing the Upchain CAD Plugin for Inventor as long as they are logged on with their own credentials.
  • An assembly, created in Inventor, that has a duplicated item used both at the parent-level and again within a sub-assembly is correctly checked in. The checked-in assembly will include the duplicated item both at the parent-level as well as at the sub-assembly level. Upchain no longer creates the assembly with just the item at the parent-level.
  • An assembly created in Inventor that contains a combination of parts and sub-assemblies no longer generates an error when creating an item from Item View item view icon.
  • When the item description is updated or entered, the item description is also updated in Upchain Web and not just in the Solidworks PLM_ItemDescription attribute.
  • *Upchain no longer tries to upload a removed, suppressed file in an assembly on check in.
  • Upchain no longer allows an item to be changed to a virtual item type from the CAD Plugin.
  • When a suppressed item is replaced the suppressed icon is no longer absent for the replacement item.
  • *Solidworks does not stall when opening a drawing in the Upchain CAD Plugin 21.4.6 for SolidWorks.
  • *Improved speed when switching between the cBOM, eBOM, and Project BOM views in the CAD Plugin.
  • *Upchain CAD Plugin for NX no longer prompts an error message that SolidWorks is not connected.
  • After opening an assembly (that is imported to Upchain by another user) directly from the home folder, editing one of its child items sets a checkmark only against the child item. The top assembly item is no longer automatically selected.
  • *Those using the CAD Plugin 21.4.4 with Inventor 2022.2 are no longer required to authenticate using the Generic Plugin.
  • *The CAD files for obsolete items can be downloaded from the CAD Plugin. Upchain no longer prompts an error message.
  • *SolidWorks’ toolbox parts are saved to Upchain using the item numbering rule for purchased items and not the numbering rule for mechanical parts.
  • When opening a CAD model from My Workspace > FAVORITE OBJECTS, the view automatically switches from My Workspace to cBOM and no longer remains on My Workspace > FAVORITE OBJECTS.
  • The hotspot for icons is expanded so that the tooltip for the icon displays when the cursor is anywhere on the icon and not just on a specific spot.
  • When the parent assembly is open in PTC Creo 7.0 while registering a new sub-assembly, Upchain CAD Plugin no longer automatically closes the sub-assembly after check in.
  • Upchain CAD Plugin for Creo no longer requires users to manually copy and paste renamed and re-referenced CAD files to the home folder. Now the plugin does this automatically.
  • The clone function now works as expected:
    • All parts and sub-assemblies under the item against which the clone operation was performed are all cloned; and
    • The cloned parts and assemblies are set to unregistered.

      Prior to this change, only the topmost assembly was cloned and the cloned parts and assemblies were indiscriminately set to registered and unregistered.
  • Upchain sets a file to read-only when multiple team members have the same item open after downloading the same assembly. Upchain alerts the team member with the read-only item that the item is in use by another team member so that they know that the changes will be overwritten when the other team member checks in their changes.

    Note: For the read-only text to display next to the file name this feature is dependent on the CAD software in use.
  • Upchain no longer sets a file to read-only after a team member downloads the latest version of an item. This is relevant when multiple team members download the same assembly and could possibly attempt to work out of the same file.
  • In the Upchain CAD Plugin for Inventor, checking in changes to an individual part that also belongs to an assembly increments the version number for both the part and the assembly and not just the part’s version number.
  • In Upchain, when an item's attributes contain the sharp S, German character ß, Upchain no longer replaces ß with SS on check in.
  • When changes to an item or assembly are saved in Solidworks, the preview, item details, doc tab, etc. are no longer hidden in the CAD Plugin.
  • An incomplete attempt to import a drawing for an item from the CAD Plugin no longer creates a database record of the drawing. This effectively prevents errors from occurring when the item is put through a Change Request (CR) and the CR expects the item to have a drawing as a result of the database record.
  • When using Clear in the CAD Plugin > My Workspace > My Locked Objects, locks on phantom files are also cleared.
  • In the NX CAD Plugin, custom properties mapped to write are updated to the file on checkout regardless of how the enable.configurations.solidworks tenant property is configured.

Project Management

  • Project Activation task is now available for reassignment from Administration > Users > {team member’s full name} > Job details > Reassign tasks. Prior to this change it was not possible to re-assign the project activation task to another team member. The Activate Project button was available only to the individual specified in the Assignee field of the related Project workflow.
  • Creating a project management task with a time constraint no longer generates an invalid, PUT-method error.
  • *Quick search no longer returns an error message instead of the search results. This error is restricted to Upchain 21.4.2.
  • *Users with a Participant license and a Viewer role are no longer restricted from using Quick Search to find released items and items in development.

Upchain for Office

  • When searching for documents, Upchain for Office displays a search-in-progress indicator instead of a blank page.
  • When inserting the details of an eBOM item into a spreadsheet, the item number’s leading 0s are no longer removed. The item number is saved to the spreadsheet exactly as it is stored in Upchain.
  • When Upchain for Office is first launched in Word, Excel, or PowerPoint, only the Sign-In and Toggle Pane options are active. Import Into Project and Mark-up are no longer active until sign-in to a tenant is complete.
  • When an item is linked within a document and the document is a part of the project, you can find the document in Upchain Web in the following places:
    • Item’s details pane under Documents > Linked documents.
    • Documents page > General documents category.

      Upchain no longer lists the document by itself, directly under the Document folders.

Users

  • *User’s last log in and login history are no longer missing from the user’s information recorded in Administration > Users.
  • *An apostrophe in a user’s name, such as O’Brien, no longer generates an error when accepting their invite to join Upchain.`

Workflows

  • *User Command is removed for the Stop primitive since this field is not required to configure this primitive.
  • *The quorum decision primitive no longer stalls a workflow’s progress when the decision task is reassigned to a team member who was not one of the original decision-makers assigned to the task.
  • *Creating a workflow from XML data, that includes custom attributes, no longer generates an error as long as the custom attributes are recognized by the tenant.
  • A workflow is no longer created when using the import function if the XML data includes categories that belong to another tenant.
Parent page: New features and fixed issues in Upchain 22.X

Was this information helpful?