Recent Releases


Asset Publisher

Back Release 6.2.1 (27.02.2020)


02/27/2020 - CDX Release 6.2.1 with further enhancements


CDX Release 6.2.1 (rollout March 25, 2020) focuses on the following enhancements:

New and Improved Functionality

  • Russian Application Language
    CDX now supports Russian language for the application ¿ data language of course remains English and extended characters such as Cyrillic or Chinese are not accepted for data fields.
  • Integration of Analysis in Tree-Search
    When executing an individual analysis against a specific datasheet, or a Where-Used-Analysis for a specific substance in a company¿s asset of MDSs, search results can now be used for the MDS tree search. In individual analysis this means that double clicking a found substance will open up the MDS tree view and start a tree search for the substance. In Where-Used-Analysis, this means double clicking a found MDS will open up the MDS and then start a tree search for the substance in scope of the Where-Used-Analysis.
  • Adaptations to Regulation Compliance Handling (Confirmations only required on MDS level incl. referenced MDSs)
    We significantly reduced the number of confirmations required for a given MDS. These are now only visible and editable at the top-node level, and displayed only for the first reference level. Also, plausibility checks will only consider top-node and first reference level.
  • Regulation Complied Value on Non-Compliance
    Whenever an MDS has confirmations that are adverse to actual compliance issues, the user is notified upon trying to release and may choose to set confirmations according to findings, or override. For example, if a user has chosen to state ¿Compliant to RoHS¿, but the MDS contains exemptions no longer valid, they will be informed about this discrepancy and asked whether to keep the ¿Compliant¿ flag or override to ¿Non-Compliant¿. As there is much legacy data reported, CDX does not enforce this behavior.
  • Deactivating MDSs
    Manufacturers and recipients can now deactivate (make obsolete) MDSs, so that this can not be further used for references. These MDSs can no longer be found when searching for reference, and they will raise warnings / errors when referenced in not yet released MDSs. Within the scope of released MDSs they remain valid data. If a manufacturer deactivates an MDS, this will become ¿cancelled by sender¿ at the recipient. If a recipient deactivates, the MDS will remain active for the manufacturer and all other recipients. For situations where accepted MDSs need to be obsoleted by the manufacturer, a new version is still the go-to.
  • Attachments to MDS Requests
    To provide additional information with an MDS request, users can now add attachments and a short information to an MDS request. Up to 5 documents can be uploaded, and the allowed file formats are the same as for an MDS attachment. 
  • Adaptations to IPC 1752 / 1754 to Meet IPC Requirements
    Several adaptations have been made to our IPC 1752 and 1754 export / import capabilities. This led to an extended re-certification of CDX as IPC 1752 solution for classes A,C,D, including support for complex products. We¿re also looking forward to becoming certified IPC 1754 provider.
  • Supplier Codes Added as Search Options to Inbox and Outbox
    Inbox and Outbox search now honors all supplier codes associated with an MDS and provides the option of using these as search parameters.
  • Send E-Mail from CDX to Service Desk including Attachments and Contextual Information
    In order to ease issue reporting, users can now send E-Mails to the Help Desk directly using the Help menu. These E-Mails include contextual information (which screen the issue was raised) and the option to attach screenshots as well.
  • Adapt Where-Used-Analysis (WUA) to Consider Thresholds of Regulations
    When doing a Where-Used-Analysis against regulations, CDX now only reports those datasheets that have above-threshold substances contained. This is a notable feature introduction, as now the results of the Where-Used-Analysis can be used for various investigations on actual compliance.
  • Safe Use Instructions in Regulations
    Regulations can be marked as ¿Requires Safe Use Instruction¿. Whenever an MDS has that regulation in scope and contains regulated substances above threshold, at least one document of type ¿Safe Use Instruction¿ has to be attached to the MDS, else a warning is raised.
  • MDS Explorer has been renamed to CDX QCM (Queue and Collection Manager) in order to reflect on upcoming changes to its functionality.

Notable Fixes

  • Regulatory rule checks considering worst case (max values still in ranges)
  • When doing a compliance check, CDX now always uses the max value for substance ranges in order to reflect on worst case assumption for compliance
  • Various fixes to sorting and display of %-values in MDS regulation details
  • Deleting released company specific regulations does now lead to usage of previous released version
  • Check against historical version of regulation now honors the substance group configuration at the given time
  • While regulations themselves are immutable after release, they may refer to substance groups (i.e. ¿Lead and its compounds¿). These groups are dynamic and content may change over time. It is therefore essential to record the state of the substance group once an MDS is released or accepted.
  • Performance Improvements

CDX Web Services:

The CDX Web Services is enhanced to support the above mentioned changes regarding ¿Deactivating MDSs¿.