2025 Updates

Links to update-specific information are below:

April 2, 2025

The update will include new features, error corrections, planned channel updates, and future update preview.

New Features

The new functionality is described below:

1. Preview Feature: Multi and Variety Pack Support

A preview feature, currently available only on PDX Preprod, is designed to provide support for Multi and Variety Packs in the Brandbank Channel.

As part of our ongoing implementation to support multi and variety packs in the Brandbank channels, the Brandbank UK channel on the PDX Preprod environment has been updated with a new Parts Composite attribute:

The new attribute ensures that each row in the Parts Composite contains product data linked to individual parts.Currently, this attribute is visible in the UI but will be ignored during submissions.

This partial implementation is intended to gather feedback on the Parts Composite structure from selected customers. It marks the first step toward full support for multi-packs and variety packs in Brandbank channels. Future updates will be reflected in the release notes as progress continues.

2. New Channel Marketplace for PDX Direct Channels

As part of this release, we are introducing a new Channel Marketplace. This marketplace provides a centralized view of all existing direct channels within PDX, allowing you to explore and connect with them easily.

Previously, direct channels were located on the Channel Management page, but they have now been moved to this dedicated marketplace for improved accessibility.

The new Channel Marketplace offers a clearer overview of available direct channels in PDX and makes it easier to highlight newly added channels of interest.

The Channel Marketplace introduced in this release is the first iteration, and we plan to enhance it further by adding new features in future updates.

3. Improvements to AI Mapping

As part of a recent update, we have improved our AI mappings model to provide more accurate and precise suggestions compared to the previous version.

4. Update to Invitation Flows

  • Supplier Invitation for Onboarding Customers

In the PDX Onboarding solution, new suppliers are invited from STEP, and an email is sent to the supplier. In the current solution, an invitation email is sent with a link that will take the user to a 'Log in' screen, which also contains a 'Create account' link. When a new supplier is invited to start using PDX, the supplier must click on 'Create account' for creating a PDX account. However, this process may be confusing for users, as in the example below.

This flow has been changed because PDX can determine if this user already has a PDX account. If the invited user has no PDX account, the user will no longer be directed to the 'Log in' or 'Create account' screen but will instead be directed to the 'Create account' page, as in the image below.

  • Digital Catalog

The change to the invitation flow has also been applied to invitations that are used for Digital Catalog. When a user is invited to a Digital Catalog, PDX can determine if this user already has a Digital Catalog account or not. If user has no Digital Catalog account, then the user will no longer be directed 'Log in' screen with 'Create account' link in upper right corner. The user will instead be taken directly to the 'Create account' page as in the example below.

Error Corrections of General Interest

The following error corrections are described below:

  Description

1WorldSync status update: 'Received by 1WS. Pending 1WS response'

In the 1WorldSync channel, submitted products will generate the following entry in the product history after 1WorldSync has picked up the submitted product and begun internal processing on the 1WorldSync side: 'Received by 1WS. Pending 1WS response.'

Previously, this update event could lead to unwanted status updates on the PDX side.

In the example below an Accepted product has been returned to the Submitted state:

The unwanted status update issue has been corrected. Henceforth, 'Received by 1WS. Pending 1WS response' updates will no longer lead to product status updates. For example, in the scenario depicted in the above image, the Product status will remain accepted.

Bug in Composite Output Conditions at Receiver Level

If a conditional output condition was made in a composite at receiver level in a channel, and the condition removed all the rows in the composite, then PDX interpreted it as if the composite has no value, and it would it inherits its value from the channel root / group level.

This behavior has been fixed so the composite on receiver level will stay empty if an output condition removes all rows in the composite.

Planned Channel Updates

The planned channel updates are listed below:

1WorldSync channel updates

The next 1WorldSync Channel update to the IM 8.61 (GDSN 3.1.31) 1WorldSync release is scheduled for May 2025.

Depending on when the Participant Dictionary is released and the size of the update, the update will typically be reflected in the 1WorldSync Channels in PDX 1-2 weeks after the update in the 1WorldSync environments.

For the IM 8.61 (GDSN 3.1.31) release, we currently plan to update the 1WorldSync channels on these dates:

  • 1WorldSync Preprod:

    • The initial update is currently in QA and is expected to be released no later than April 4, 2025.

    • A second update is expected by the end of April 2025.

  • 1WorldSync:

    • May 24, 2025

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 17 on May 26, 2025.

Future Update Preview

Future updates should include the following:

  • New Channel Overview & Details Page

Note: Future update deliveries are subject to change.

Next Update

The next update to PDX is scheduled for April 28, 2025.

March 20, 2025

The update will include new features, error corrections, planned channel updates, and future update preview.

New Features

The new functionality is described below:

1. Tradesolution Channel: Reusing GTINs Across Packaging Hierarchies

The PDX Syndication solution includes support for the Norwegian data pool Tradesolution.

Products are submitted to Tradesolution's EPD platform as Packaging Hierarchies that consist of several products / GTINs.

In the Tradesolution channel, the packaging level types are referred to as ‘Topp’ (pallet), ‘Mellom’ (case and/or pack) and ‘Basis’ (each).

Previously, it was not possible for Packaging Hierarchies in the PDX Tradesolution channel to share products. This meant that a single Basis could not be submitted as part of multiple Packaging Hierarchies, and GTINs would be duplicated in EPD.

A feature to share products has been implemented, and Basis units can now be shared between Packaging Hierarchies. This enhancement allows for a single Basis unit to be created and maintained across various packaging configurations., e.g., as a standalone product and in a mixed configuration.

Below is an example of a Basis GTIN being used in two mixed products:

The functionality also supports cases where there are usages of a GTIN that does not originate from PDX, i.e., an old GTIN originally created directly in the Tradesolution EPD UI is being used in a new product submitted from PDX.

The lifecyle of products in Tradesolutions EPD platform means that products must pass through ‘draft’ and ‘published’

  • When a GTIN is reused in a new Packaging Hierarchy, the new product will be created as a draft in phase 2.

  • When a GTIN is reused in a new Packaging Hierarchy, all messages received by Tradesolution will be displayed on the product's history page and will be prepended with the Draft ID or EPD number that the message originates from. An example is below.

The current implementation is limited to the reuse of Basis units.

The functionality has been in customer pilot test and has now been released to all users of the Tradesolution channel.

2. Language-specific Attribute Filters Disabled

The support for attribute filters is currently limited across languages in PDX.

Master Data

In Master data, the attribute filters 'Empty' and 'Not Empty' can be used to filter attributes to only show those attributes that either have content or do not have any content.

Currently, this filter only works correctly in the English (en) language.

In order to reduce the risk of confusion, the two filters have been disabled for all other languages in the master data area.

Channels with Multiple Languages

In channels, the following three attribute filters can be used to filter down to only show the attributes that either have errors, have content, or do not have any content: 'Errors,' 'Empty,' and 'Not Empty.'

Currently, these filters are only available in the Default language of the channel. In order to reduce confusion and to avoid misleading users, the three filters have been disabled in other languages in the channel UI.

The default language can differ across channels and channel groups (markets / receivers). This also means that the Default language can be a language other than English — hence the filters will be enabled and work as expected in other languages, depending on channel and channel hierarchy level. An example of this behavior is below.

Note: This is a temporary change. Once the support for attribute filters is extended to cover multiple languages, these limitations to the filtering selection will be removed.

3. Validation on Asset Upload

PDX now includes robust asset validation during the upload process. Previously, the system had minimal format verification, allowing nearly any file type to be uploaded. With this enhancement, PDX automatically checks each file format and skips unsupported files, preventing them from being uploaded.

The following file formats are currently supported for upload to PDX.

  • Photos: .tga, .pbm, .jpg, .jpeg, .svg, .gif, .webp, .bmp, .png, .avif, .tiff

  • Videos: .wmv, .avi, .mov, .mpeg, .m4v, .mp4

  • Audio: .wav, .mp3

  • Documents: .xlsx, .xlsm, .xls, .xml, .indd, .pptx, .docx, .ppt, .pdf, .doc, .xsl, .csv, .txt, .html, .xhtml, .rtf

  • Compressed: .rar, .zip, .bz2

  • Design: .psd, .sldprt

Error Corrections of General Interest

The following error corrections are described below:

  Description

Improved Handling of Composite Sub-attributes

We have fixed a defect in the 1WorldSync channel related to composite sub-attributes that are language and receiver specific.

Previously, receiver specific values could end up on the market level when submitted to 1WorldSync.

Support for Multivalued Memo fields in Brandbank Channels

We have fixed a defect in the handling of multivalued Memo fields in the Brandbank channels.

Previously, during submission to Brandbank, values in multivalued Memo fields would be mixed with additional characters such as square brackets [ ] and double quotes " ".

This defect has now been fixed:

  • Square brackets and double quotes are no longer added.

  • Multiple values will now be properly separated by a newline upon submission, ensuring correct delivery to Brandbank.

Asset Validation Error Correction

A recent enhancement to assist in asset file type conversion introduced a validation error stating ‘Grid validation errors. Asset Max Heights’ and ‘Grid validation errors. Asset Max Width’. The error occurred in configured channels under the following condition: if the asset attribute had restrictions for height and width combined with no ‘Asset extension’ (JPEG, PNG or GIF) selection. Additionally, if a user then changed an extension to ‘Any format,’ the error would still occur. The bug has now been fixed so asset attributes again can have requirements to width and height, even if no asset extension / file type is selected.

Copy-paste Error in Grid View Corrected

An error in grid view blocked users from copying selected values in cells and pasting those values to other cells. This occurred both in Master Data and channels. This bug has now been fixed, so users again can copy-paste in grid view.

Planned Channel Updates

The planned channel updates are listed below:

1WorldSync channel updates

The next 1WorldSync Channel update to the IM 8.61 (GDSN 3.1.31) 1WorldSync release is scheduled for May 2025.

Depending on when the Participant Dictionary is released and the size of the update, the update will typically be reflected in the 1WorldSync Channels in PDX 1-2 weeks after the update in the 1WorldSync environments.

For the IM 8.61 (GDSN 3.1.31) release, the current plan is to update the 1WorldSync channels on these dates:

  • 1WorldSync Preprod: End of March 2025 with a second update by end of April 2025

  • 1WorldSync: May 24, 2025.

Brandbank channels update

The Brandbank channels in PDX were updated to match the Brandbank Release 16 on February 24, 2025.

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 17 on May 26, 2025.

Future Update Preview

Future updates should include the following:

  • New PDX Channel Marketplace with the option to see and connect to all available Direct Channels

  • Sorting and filtering in ‘Digital Catalog – Data Monitoring and Request Log’ pages

  • Improved invitation flow for suppliers invited to use PDX Onboarding.

Note: Future update deliveries are subject to change.

Next Update

The next update to PDX is scheduled for April 2, 2025.

February 19, 2025

This update includes new features and planned channel updates.

New Features

The new functionality is described below:

1. Automatic asset file type conversion

PDX now supports automatic conversion of asset file types. This feature addresses the need for users in PDX to be able to work with various file types, while still meeting the specific file format requirements of downstream syndication partners or retailers.

With this enhancement, PDX will automatically convert uploaded asset files to the required output format during product submission.

Previously, users would receive an error if the uploaded image file type did not match the attribute requirements (e.g., uploading a TIFF when a PNG is needed). Now, the PDX system will convert the image to the correct format upon submission, eliminating these errors.

The following image types can be converted: JPEG, PNG, WebP, GIF, AVIF, TIFF, and SVG images.

If channel administrator has defined in ‘Asset extensions’ on the attribute that more than one type of image is allowed on the attribute, such as PNG and JPEG, the images will then be converted to PNG. If multiple selections have been made, images will convert following the below priority:

  1. PNG

  2. JPG

  3. GIF

The same behavior has also been implemented in PDX Direct channels.

If a user uploads images with transparent backgrounds (like TIFF or PNG), but the attribute only allows JPEG images, the transparent backgrounds will be converted to white.

This enhancement is supported in Configured Channels where Channel administrators can configure the required file types for their channels. If a specific file type is selected, all uploaded assets for that attribute will be converted to the specified format during submission.

The image below is an example of a channel administrator setting an asset attribute to accept only PNG images. Any assets uploaded or mapped to this attribute will be converted to PNG format upon submission.

This enhancement is also supported in PDX Direct channels and PDX Onboarding channels that have file type requirements defined, with the exception of the Nielsen Brandbank channels.

If no file type requirements are set, no conversion will occur.

Planned Channel Updates

The planned channel updates are listed below:

1WorldSync channel updates

The 1WorldSync release schedule has been made public. The PDX team is currently reviewing the release schedule and release content. Consequently, the content and date for the next update to the 1WorldSync Channels in PDX are currently unknown.

Any updates to this information will be made available well in advance of the next update via these release notes.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match Brandbank Release 16 on February 24, 2025. Brandbank’s release notes for this update are available on the Brandbank Knowledge base site: https://nielsenbrandbank.freshdesk.com/en/support/solutions/folders/75000017682.

Future Update Preview

While we're continually working on enhancing the software, there are no specific upcoming features to announce in this release. Keep an eye out for future previews.

Note: Future update deliveries are subject to change.

Next Update

The next update to PDX is scheduled for March 17, 2025.

February 5, 2025

This update includes new features, bug fixes, planned channel updates, and future update preview.

New features

The new functionalities are described below:

1. PDX system status

PDX is now integrated into Stibo Systems SaaS Status Page. With this update, PDX users can access important notifications about system performance, unexpected downtime, or scheduled maintenance. To access the status information directly from within PDX, navigate to the Help Center and select 'System Status.'

This link will direct you to the SaaS Status Page, where you can view current and historical service statuses.

You can also subscribe on the page to stay updated and receive automated email notifications and follow-ups about system events.

Users do not need to login to check the PDX System Status page. It can also be accessed directly via this link: https://statushub.mdm.stibosystems.com. For further information about system status, visit the Support Services page.

2. Language-specific icon in mappings screen

A visual indicator for attributes that are language specific has been introduced in the mapping screen. The new icon gives an overview of the different types of mappings you are working with.

Bug fixes

The following bug fix is described below:

  Description

Improvements have been made to how data fetching functions within the grid view. This error correction enhances the scroll experience in PDX's grid view. Previously, stopping at certain points while scrolling could cause incomplete loading, moving you to a different spot and requiring you to return to your original position. This update resolves that issue, ensuring a smoother scrolling experience.

The 'Multiple' family status has been reintroduced. Previously when two or more products in a family had a different PDX status, the status displayed in views where only one row is shown per family would display 'Multiple.' An error occurred in this kind of view, where only one row is shown per family. Instead of displaying 'Multiple,' the status of the first product in the family would be shown. This error has now been fixed so if two or more products in a family have a different PDX status, the display will once more display 'Multiple.' The image below is an example of a below ‘Multiple’ display because the three products in the family have different statuses.

Planned channel updates

The planned channel update are listed below:

1WorldSync channel updates

The 1WorldSync release schedule has just been made public.

Please note that depending on when the Participant Dictionary is released and the size of the update, the update will typically be reflected in the 1WorldSync Channels in PDX 1-2 weeks after the update in the 1WorldSync environments.

The next update to the 1WorldSync Channels is expected to happen in February 2025.

1WorldSync AS2 Security Certificate update for production and pre-production systems

1WorldSync have also announced planned updates to their AS2 connection:

  • On February 7, 2025, 1WorldSync will activate new digital certificates for Pre-Production systems. This includes some changes to the Inbound IP Address.

  • On February 21, 2025, 1WorldSync will activate new digital certificates for Production systems.

This is a recurring maintenance task that 1WorldSync performs once every year.

With regards to the connection between the 1WorldSync channels in PDX and the 1WorldSync environment, the PDX team will perform the steps necessary to accommodate these changes on behalf of all users of the 1WorldSync channels. These steps will be completed within the time frames required by 1WorldSync.

For more information on the details on the 1WorldSync announcement please see this link (login required).

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match Brandbank Release 16 on February 24, 2025.

Future update preview

Future updates should include the following:

PDX will support automatic conversion of asset file types during product submission, ensuring uploaded images meet downstream format requirements and eliminating errors.

Note: Future update deliveries are subject to change.

Next update

The next update to PDX is scheduled for February 19, 2025.

January 13, 2025

This update includes new features, bug fixes, planned channel updates, and future update preview.

New features

The new functionalities are described below:

1. AI-assisted mappings available for Amazon and configured channels

With this release, our new AI-assisted mapping feature is now available to both Amazon and all configured channels. Admin users can enable AI mapping suggestions via a new toggle in Account > General settings.

Once this feature is enabled, AI suggestions will appear in the channel mappings screen for Amazon and configured channels. The screen will display an AI symbol and a confidence score for each suggestion. The AI will prioritize the highest confidence score items at the top of the screen to help you find relevant mapping suggestions.

Additionally, a new feature allows you to view all mapping suggestions within the mapping screen. The 'Preview AI Suggestions' feature displays a list of all AI-generated suggestions.

This feature allows you to select all or some of the suggestions and apply them all at the same time.

After applying the new suggestion, an icon will be added to the mapping to indicate that it has been mapped using the AI.

2. Update to URL presigner for configured channels

We have updated our URL presigner for configured channels within PDX. Previously, submission link expiry dates could only be extended up to seven days. With this update, they can now be set for up to 90 days.

Bug fixes

The following bug fix is described below:

  Description

As part of a support case related to the handling of the Manufacturers Address field in the Brandbank channels, two new value transformations have been added.

  • Append newline

  • Replace value with newline

They can be useful when mapping content to fields (e.g., Brandbank's Memo type fields) that support the newline character.

These new transformations enable the creation of output that includes newline characters.

  • Append newline: This transformation adds a newline character to the end of the current text.

  • Replace value with newline: This transformation will replace a configured text string, e.g. '<br>', with the newline character.

The choice of value transformation depends on the structure of the master data. With the value transformations above, the following actions are possible:

  1. Combine multiple attributes in Master data into one channel attribute where the master data values become separated by newline characters in the channel.

    • In the example below, a channel attribute is mapped to the master data attribute: 'Address line 1.' Then, two additional master data attributes are appended: 'Address line 2' and 'Address line 3.' A newline character is then inserted within the three master data attributes, using the Append newline value transformation.

    • The option 'Append newline. Use checkbox to avoid empty lines' can be used to ensure that two consecutive newlines (i.e., an empty line) will not be output. The empty line could occur if, for example, Address line 2 was empty for some products, but it will be prevented by the 'Avoid duplicate newlines' option.

  2. Transform one attribute in Master data with newline indicators into one channel attribute where the newline indicators in master data are turned into newline characters in the channel.

    • In the example below, a channel attribute is mapped to master data attribute 'Full Address,' and all instances of '<br>' are replaced by a newline character using the 'Replace Value with newline value' transformation.

    • The option 'Avoid empty lines' ensures that two consecutive newlines (i.e., a blank line) will not be output.

The PDX UI will not display the newline characters. Although they are present, they will not be visible in the fields. They will be visible in the Excel sheet created if the product is exported from the channel:

If the transformations referenced above are used, the fields will, when sent to the data recipient, contain newline characters. Examples of XML and JSON formatted output are below:

These value transformations should only be used if output containing newline characters is supported by the data recipient. In many cases, data recipients will ignore or automatically convert newline characters.

Additional option for 'Replace' value transformations

As part of the support task above, another value transformation has been extended: 'Replace' now has a new option: Ignore case. If selected, the search field will match any combination of upper / lower case. As a result, replacing a word like 'yes' will match any of 'yes,', 'Yes', 'YES', 'yeS,' etc., if this option is used.

For more information on value transformations, refer to the Value Transformations for Attributes topic.

Planned channel updates

The planned channel update are listed below:

1WorldSync channel updates

The upcoming 1WorldSync release schedule has not been made public yet, but the next updates to the 1WorldSync channels are expected to happen in February 2025.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match Brandbank Release 16 on February 24, 2025.

Future update preview

Future updates should include the following:

  • Alphabetically sorted options

Note: Future update deliveries are subject to change.

Next update

The next update to PDX is scheduled for January 29, 2025.