Обзор нововведений

Altium Concord Pro 4.1

Released: 26 January 2022 - Version: 4.1.3 (build 3)
Released: 21 December 2021 - Version: 4.1.2 (build 4)
Released: 22 November 2021 - Version: 4.1.1 (build 6)

Release Notes for Altium Concord Pro 4.1

This release is a minor stabilization update that sees further beneficial enhancements to Altium Concord Pro and its related technologies. In addition, numerous fixes have been made to resolve issues raised by customers through the AltiumLive Community.

Support for Aras PLM

This Altium Concord Pro release sees the introduction of component synchronization support for the popular Aras Innovator^® PLM system. As with other PLM systems supported by Concord Pro, the Aras connectivity integration enables bidirectional component parameter data exchange during synchronization events.

The Aras PLM integration is set up and validated by adding a new enterprise system instance through the Admin – Component Sync page of Concord Pro's browser interface. Commented base configuration and publishing XML files for the Aras PLM are provided in the downloadable Configuration file samples. These are available when creating the new connectivity instance, and can be edited and then uploaded to configure the enterprise system's connectivity with Concord Pro.

► See Connecting to Your Enterprise System for more information.

A connectivity instance for data exchange with the Aras PLM system is configured from the server's Component Sync page.

Support for Bidirectional Part Choices Data Synchronization

The exchange of component Part Choices data between Altium Concord Pro and a connected enterprise system (such as a PLM installation) can now be configured for either direction. While the enterprise system was set as the source of part choice data in previous releases, this Concord Pro update also allows Part Choices to propagate (be pushed) to the connected enterprise system. This is a directionally exclusive arrangement, where the part choice data can be configured to transfer in either direction, but not both.

Part Choices data transfer is specified in the configuration schema applied to the server's PLM instance (Admin – Component Sync) as an XML configuration file, which can be based on the provided sample files. The schema allows for specific Part Choices attribute parameter mapping for most supported PLM systems, and Approved Manufacturing List (AML) relationships for Aras and Arena PLM systems.

In the XML configuration file, part choices parameter attribute mapping for propagation to the enterprise (PLM) side is added as a component ToPLM entry is the following format:

<PartChoices>
  <ToPlm sync="true">
    <MfrMappings>
      <MfrMapping>
        <MfrName>PartChoiceManufacturer1</MfrName>
        <MfrPartNumber>PartChoiceNumber1</MfrPartNumber>
      </MfrMapping>
    </MfrMappings>
  </ToPlm>
</PartChoices>

When supporting part choice data that is native to the target PLM system it is sufficient to add a global ToPLM entry definition, which will enable the transfer of all part choice data:

<PartChoices>
  <ToPlm sync="true" />
</PartChoices>

Support for Change History and Rejection Comments

CoDesigner, in conjunction with your Concord Pro Workspace, now displays the full history of accepted and rejected changes, along with any comments the engineer has entered if a change is rejected. The history of changes is shown in CoDesigner's panel, making the interaction between the electrical and mechanical engineers more transparent. As soon as changes are applied/rejected on one side the engineer on the other side is notified, and any rejection comments are displayed.

Change history makes it easy for the engineers on both sides to be aware of each other's responses to the changes being made.