2024 Updates

Links to update-specific information are below:

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.

December 18, 2024

This update includes new features and planned channel updates.

New features

The new functionalities are described below:

1. Enhanced navigation features

Breadcrumbs have been added to every page in PDX, the admin tool, and Enhanced content. This feature, located below the page title, shows your current location and provides an option to return to the previous screen.

Along with adding breadcrumbs, we have also updated the page titles in PDX to reflect the user's current location. This enhancement provides a better overview and understanding of your position within the application.

Finally, we have enabled keyboard navigation in the menu header of the product view, allowing you to use the Tab, ESC, and Enter keys to navigate.

2. Submission log capabilities extended

We have enhanced the submission log with an option to download the HTTP output submit JSON file. By selecting 'Download submitted data' from the action dropdown, you can download the JSON file to your PC. This update improves transparency and helps you understand why a submission marked as successful might have failed.

3. Text editor changed to Quill

We have switched our rich content editor from CKEditor to Quill. This change primarily affects email layouts used as output receivers within configured channels. Existing email output receivers will not be impacted, but new ones will see some visual changes without major alterations.

4. New navigational button created

We have implemented a new navigational button in the configured channel management section of PDX. This button functions as a redirect, sending you to the channel you are working on when clicked. This change provides an easy way to make changes to a channel and then move directly into that channel.

5. Internal retention period updated

We have updated PDX to reflect our internal retention period of 90 days. Going forward, you may only select a maximum retention period of 90 days within the PDX application.

6. Digital Catalog – Data monitoring and Request Log

The PDX application now includes two new beta pages that display product information for retailers and partners using the Digital Catalog API. These pages are available to customers using the Digital Catalog. Note that filtering and sorting features are not included in this release but will be added later.

Previously, manufacturers had no visibility into the product data pulled from the Digital Catalog. The new pages provide transparency, showing what information partners and retailers have accessed.

Users with the 'Client Admin' role or the 'Digital Catalog API Monitoring' permission can view these pages.

Data monitoring

The Data Monitoring page provides an overview of the number of products your partners and retailers have pulled from the catalogs they can access.

Important: Important: The first time the page is opened, the 'Products delivered / total' column may show 0/0 products, even if you have submitted products to your catalogs. To see accurate numbers, products must be resubmitted, as the counter only tracks data submitted after these new pages were introduced.

The page includes the following columns:

  • Channel name: The name of the channel providing product information to your catalog. A channel can contain multiple catalogs.

  • Catalog name: The catalog containing the product information.

  • Partner name: The organization invited to pull information from the catalog.

  • Products delivered / total: The first number indicates how many products the partner has pulled from the catalog using the Digital API. This number updates if the digital catalog user exports products. The second number shows the total products in the catalog. These numbers update each time a partner pulls new information or when a manufacturer updates the catalog with new or updated products.

Request log

The Request log is a page that lists all the requests that has been made by partners. The following information is available for each request:

  • Time: Data and time of request

  • Catalog name: the name of the catalog partners made a request towards

  • Partner Name

  • Status Code: the status code provided in the response

  • Request type: that type of request – POST or GET

  • Request path

  • Received products count: the number of products that the request resulted in

  • Received assets count: number of assets that was a part of the response

  • Response time in milliseconds

  • Details: displays the entire body of the request

  • Request ID

Bug fixes

This section is reserved for error corrections of general interest. This update contains no bug fixes of that type.

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

  • Brandbank have performed an Ad-Hoc update to all EU channel markets. As a result, the following fields were added to the Brandbank UK, IE, PL, HU, CZ, SK, BE and NL channels on December 6, 2024:

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

Future update preview

While we're continually working on enhancing the software, there are no specific features to announce in this release. Stay tuned for future updates.

Next update

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

December 2, 2024

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

New features

The new functionalities are described below:

1. Languages added to PDX UI

Ten additional languages have been added to the PDX UI with this release. The new languages are located within the same area as the five original languages: they can be found in the 'Your Profile' section within the Profile and account settings.

Within this section, it is now possible to select from the following additional languages using the drop-down selector under general settings.

  1. Dutch

  2. Italian

  3. Portuguese

  4. Czech

  5. Hungarian

  6. Slovak

  7. Finnish

  8. Thai

  9. Korean

  10. Chinese

Note: The Czech and Chinese translations have been checked and translated by a human. The other eight translations were done by AI and are marked with an indicator symbol. As human translations are completed for these languages, the AI indicator symbol will be removed.

2. Digital Catalog design reversion

In the last update, we introduced a new design for the Digital Catalog. In this release, we are reverting to the previous design. After gathering feedback, we found that the recent changes did not align with our intended user experience and strategy for a modern digital catalog platform.

To ensure optimal functionality and satisfaction, we have restored the earlier design. The previous design has been fully reinstated, and all core functionalities remain unchanged.

Next Steps: We are actively working to address the identified issues and plan to reintroduce an improved design in a future release. We appreciate your understanding and patience during this process.

The screenshot below provides a current example of the reversion to the original design.

Bug fixes

The following bug fix is described below:

  Description

A communication defect in the PDX Retailer Onboarding Channels to STEP has been fixed. Previously, some submissions could fail with a generic message: 'STEP import failed! Submit action to channel failed.' Now, more of these errors will produce specific error messages, execution reports, and submitted data, which can be downloaded from the PDX Submission Log UI. This update allows troubleshooting directly from the PDX UI, eliminating the need to contact the retailer.

Planned channel updates

The planned channel update are listed below:

1WorldSync channel updates

The 1WorldSync Channels have been updated to the IM 8.54 (GDSN 3.1.29) version. The update took place on these dates:

• 1WorldSync Preprod: November 12, 2024

• 1WorldSync: November 18, 2024

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 were updated to match the Brandbank Release 15 on November 18, 2024.

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 Onboarding improvements for the vendor portal, enabling the possibility of single product creation

  • New download feature for JSON files associated with their HTTP output submissions.

Note: Future update deliveries are subject to change.

Next update

The next update to PDX is scheduled for December 18, 2024.

November 6, 2024

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

New features

The new functionalities are described below:

Important: The 'Adjustments to Attribute value inheritance in Channel Groups' new feature is relevant only to users of Channel Groups.

1. Adjustments to Attribute value inheritance in Channel Groups

Channel Groups and channel hierarchy levels

On the PDX platform, some channels manage data at multiple levels, typically referred to as 'Markets' and/or 'Receivers.' Examples of these channels include the 1WorldSync channel, Brandbank channels, certain Retailer Onboarding channels, and any Configured Channel with multiple receivers.

These kinds of channels are referred to as Channel Groups.

These channel groups can be identified by a hierarchy level selector in the Channel UI, which allows you to navigate between different data levels. For example, the 1WorldSync channel features two sublevels: Markets and Receivers.

The example below is from a Configured Channel with two Receivers.

In a channel group, product attribute values may vary across zero, one, or two dimensions, depending on the channel’s specific setup:

Global Attributes: Some attributes, like Item ID, Product Type, or Unique Manufacturer Identifier, are global, meaning their values remain the same across both languages and hierarchy levels. These attributes are marked with a 'G' in the mapping screen and can only be mapped at the global level in a channel group.

Language-Specific Attributes: Some attributes, such as Product Descriptions, may vary by language. These attributes also appear with a 'G' in the mapping screen and can only be mapped at the global level. Language-specific values are obtained through language mappings or manual edits.

Channel Group Attributes: Some attributes may vary by hierarchy level (e.g., market or receiver), such as Warranty Information or Hazard Class, which can depend on legal or country-specific requirements. These attributes are marked with 'G,' 'M' (for Market), and/or 'R' (for Receiver) in the mapping screen and can be mapped at both the global level and at market and/or receiver levels.

Language and Hierarchy-Level Attributes: Some attributes may vary by both language and hierarchy level. These are also marked with 'G,' 'M,' and/or 'R' in the mapping screen and can be mapped at the global level as well as at market and/or receiver levels. Language-specific values are obtained through language mappings.

The exact setup of these attributes depends on the individual channel. Below are examples from the 1WorldSync channel.

Changes introduced in this update

As part of this PDX update, we are refining the UI to better display these attributes and making a minor change to how manual edits are inherited across levels. Our goal is to provide users with a consistent and enhanced view of data variations by language and levels within channel groups.

Additionally, these improvements are expected to reduce the need for mappings and manual edits when managing channel data. This functionality has already been enabled for some customers in certain PDX environments as part of a gradual rollout and early testing.

Commitment to consistency

Previously, it was possible to generate inconsistent attribute values for a Global attribute across different levels due to mismatched master data and mappings. This issue has now been resolved.

Additionally, in Configured Channels, there was a defect where mapping different languages to the same channel language across multiple receivers could result in data inconsistencies. For example, if 'en' was the channel language, mapping 'en-us' from master data to 'en' in a US receiver and 'en-uk' to 'en' in a UK receiver would cause the submitted data to vary depending on whether the submission was made from the global or receiver level.

This defect has also been fixed. Now, submitted data will remain consistent, allowing users to submit to multiple receivers at once from the global level or use scheduled submissions without issues.

Attributes become read-only at lower levels

Currently, attributes whose values cannot vary by language are displayed as read-only in all languages that are not the Default language. Examples are below.

The same approach will now be applied to attributes whose values cannot vary by level.

Previously, attributes that were not allowed to vary at certain levels still appeared as editable (read-write) at lower levels. For example, if GTIN is a global attribute, it will still show as editable at the market level.

If a user modified an attribute at this level, a notification would appear, explaining that the change would impact additional levels beyond the one selected.

This behavior is changed with this release. Attributes that cannot vary at a specific level will be read-only in the channel UI at this level. Below is an example of the changed behavior.

If a user then attempts to edit such a value a new toast message with the text 'This attribute can't be edited on Market level. Switch to Global level to edit.' will appear.

Inheritance of manual edits

For attributes that can vary by level, any manual edits made at a higher level were previously overridden by explicit mappings at a lower level. With this release, this behavior will change: a manual edit made at a higher level will now become the value at all lower levels. However, manual edits at a lower level will still override those made at a higher level.

In the example below, different Delivery data is mapped at both the Global and Market levels using two different mappings.

However, one manual edit on Global can now adjust the Global as well as all the Market values as in the example below.

This allows a user to quickly alter multiple market and/or receiver-specific values with a single manual edit, rather than making manual edits for each market and/or receiver individually. However, a manual edit at a lower level will still override a manual edit made at a higher level.

2. Expansion of HTTP status messages in product history

To improve transparency in our PDX HTTP messages, we've added more information to responses with a Status Code 200 (OK). Moving forward, the response body text will also be included.

The purpose of this enhancement is to help identify reasons for failures that may still occur with a 200 status code. By including the response body, users can now see details like 'User not found' or 'No products sent' to better understand why a request marked as successful may not have completed as expected.

3. New footer for Channel and list counts

A new footer has been added to all list views and the Channel Management page in PDX. This footer provides an overview of the total number of items in a list and shows the number of selected items versus the total items in the list.

With the addition of the footer on the Channel Management page, users now have a clear view of the number of Configured and Direct Channels available within PDX.

4. New Digital Catalog design

We’re excited to announce a fresh new look for our Digital Catalog application! The updated design mirrors the PDX application, featuring a left-side menu for easy navigation. Users can now access their catalog by clicking on the ‘Catalogs’ option in this menu.

Opening a catalog provides the same features as before, including product search, Gallery View or List View options, language selection, export functions, and category filtering.

In the ‘Management’ section, users can now manage ‘Users’ and create API Keys. Previously, these features were accessed via the user icon in the upper right corner.

This design update is part of our ongoing effort to enhance usability and introduce new features to the Digital Catalog.

Bug fixes

This section is reserved for error corrections of general interest. This update contains no bug fixes of that type.

Planned channel updates

The planned channel update are listed below:

1WorldSync channel updates

The next 1WorldSync Channel update to the IM 8.54 (GDSN 3.1.29) 1WorldSync release is scheduled for November 2024.

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.54 (GDSN 3.1.29) release, the target dates are below:

• 1WorldSync Preprod: November 8, 2024

• 1WorldSync: November 16, 2024

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 15 on November 18, 2024.

Future update preview

Future updates should include the following:

Additional languages added to PDX UI

We are currently working on adding more languages to the PDX UI. In the future, we will be preparing several additional languages, allowing users to localize their UI. Our goal is to expand the existing language options by adding ten more languages to PDX. More details will be upcoming.

Enhanced visibility for required attributes

To enhance user experience and minimize submission errors, we are developing a feature to clearly highlight mandatory attributes. At present, users might miss required fields, resulting in incomplete submissions.

Note: Future update deliveries are subject to change.

Next update

The next update to PDX is scheduled for December 2, 2024.

October 16, 2024

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

New features

The new functionalities are described below:

PDX UI now supports multiple languages

In this release, we're adding several new languages to PDX, allowing users to switch the UI between different languages. With this update, PDX will be available in English, Spanish, French, German, Danish, and Polish. By default, the UI will be set to match your browser's language.

To change the language, simply go to your profile settings, navigate to the General settings section, and find the 'Preferred language' drop-down. From there, select your desired language, and the entire UI will switch to it.

We're also preparing to support even more languages in the future.

Updates to Channels management page

As part of the ongoing redesign of the PDX Channels management page, we are introducing two new features. First, we are adding a new toolbar that retains the same functions as the old Channels Management interface, ensuring consistency with other areas of PDX.

Second, we are implementing a new filter function, making it easier to find specific configured channels.

New value transformation

The new value transformation, 'Remove duplicate values/rows from multivalue,' allows users to eliminate duplicate values in a multivalue attribute. But why do duplicates occur? Some customers create multivalue fields in channels by joining several single-value master attributes using the 'Add attribute to multivalue' transformation, which can sometimes result in duplicates.

Previously, users could remove duplicates by applying the 'Regular expression' transformation, but this method was often complex and didn’t always deliver the desired results.

With this new transformation, duplicates are removed without altering the order of the values. The first occurrence of a value will remain, while any duplicates that follow will be removed. This transformation is case sensitive.

Extension to existing transformation

The 'Replace value' transformation has been enhanced with a new feature that ensures all occurrences of a value can now be replaced, not just the first one.

Previously, the transformation only replaced the first occurrence of the value, which wasn’t well-documented or clearly indicated in the UI. Now, a new checkbox has been added that allows you to replace all instances of a value, rather than just the first. This transformation is case sensitive.

By default, this new functionality is turned off to maintain backward compatibility.

Bug fixes

The following bug fixes are described below:

  Description

As part of this update, we have resolved an issue in our Brandbank channels where language-specific attributes were previously always submitted in English. This error has been corrected, and now language-specific values can be successfully submitted.
Another error in the Brandbank channel has also been fixed: Previously if the same Subscription code was being used at Market and at a Receiver level, some submissions would fail with an error in the payload generation. This error has now been fixed.
In the 1WorldSync channel, a cache refreshing issue caused new submissions for newly added IP GLNs to not receive any status updates in the PDX UI, making them appear ‘stuck.’ This issue has now been resolved.

Planned channel updates

The planned channel updates are listed below:

1WorldSync channel updates

The next 1WorldSync Channel update to the IM 8.54 (GDSN 3.1.29) 1WorldSync release is scheduled for November 2024. As the release of IM 8.54 (GDSN 3.1.29) approaches, we will provide specific dates for the channel update.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 15 on November 18, 2024.

Future update preview

Important: The following information applies only to users of Channels Groups.

Future updates should include the following:

Adjustments to Attribute value inheritance in Channel Groups

Channel Groups and channel hierarchy levels

On the PDX platform, some channels manage data at multiple levels, typically referred to as 'Markets' and/or 'Receivers.' Examples of these channels include the 1WorldSync channel, Brandbank channels, certain Retailer Onboarding channels, and any Configured Channel with multiple receivers.

These kinds of channels are referred to as Channel Groups.

These channel groups can be identified by a hierarchy level selector in the Channel UI, which allows you to navigate between different data levels. For example, the 1WorldSync channel features two sublevels: Markets and Receivers.

The example below is from a Configured Channel with two Receivers.

In a channel group, product attribute values may vary across zero, one, or two dimensions, depending on the channel’s specific setup:

Global Attributes: Some attributes, like Item ID, Product Type, or Unique Manufacturer Identifier, are global, meaning their values remain the same across both languages and hierarchy levels. These attributes are marked with a 'G' in the mapping screen and can only be mapped at the global level in a channel group.

Language-Specific Attributes: Some attributes, such as Product Descriptions, may vary by language. These attributes also appear with a 'G' in the mapping screen and can only be mapped at the global level. Language-specific values are obtained through language mappings or manual edits.

Channel Group Attributes: Some attributes may vary by hierarchy level (e.g., market or receiver), such as Warranty Information or Hazard Class, which can depend on legal or country-specific requirements. These attributes are marked with 'G,' 'M' (for Market), and/or 'R' (for Receiver) in the mapping screen and can be mapped at both the global level and at market and/or receiver levels.

Language and Hierarchy-Level Attributes: Some attributes may vary by both language and hierarchy level. These are also marked with 'G,' 'M,' and/or 'R' in the mapping screen and can be mapped at the global level as well as at market and/or receiver levels. Language-specific values are obtained through language mappings.

The exact setup of these attributes depends on the individual channel. Below are examples from the 1WorldSync channel.

Upcoming changes

In the next PDX update, we are refining how the UI displays attributes and making a small adjustment to how manual edits are inherited across levels. The goal is to provide users with a clearer, more consistent view of which data can vary by language and at which levels.

An additional benefit of these improvements is that channel data can be managed with fewer mappings and fewer manual edits.

For some customers in certain PDX environments, this functionality has already been enabled as part of a gradual roll out and early testing.

Commitment to consistency

Previously, it was possible to generate inconsistent attribute values for a Global attribute across different levels due to mismatched master data and mappings. This issue has now been resolved.

Additionally, in Configured Channels, there was a defect where mapping different languages to the same channel language across multiple receivers could result in data inconsistencies. For example, if 'en' was the channel language, mapping 'en-us' from master data to 'en' in a US receiver and 'en-uk' to 'en' in a UK receiver would cause the submitted data to vary depending on whether the submission was made from the global or receiver level.

This defect has also been fixed. Now, submitted data will remain consistent, allowing users to submit to multiple receivers at once from the global level or use scheduled submissions without issues.

Attributes become read-only at lower levels

Currently, attributes whose values cannot vary by language are displayed as read-only in all languages that are not the Default language. Examples are below.

The same approach will now be applied to attributes whose values cannot vary by level.

Previously, attributes that were not allowed to vary at certain levels still appeared as editable (read-write) at lower levels. For example, if GTIN was a global attribute, it would still show as editable at the market level.

If a user modified an attribute at this level, a notification would appear, explaining that the change would impact additional levels beyond the one selected.

This behavior will change with the next release. Attributes that cannot vary at a specific level will be read-only in the channel UI at this level. Below is an example of the changed behavior.

If a user then attempts to edit such a value a new toast message with the text 'This attribute can't be edited on Market level. Switch to Global level to edit.' will appear.

Inheritance of manual edits

For attributes that can vary by level, any manual edits made at a higher level were previously overridden by explicit mappings at a lower level. With the next release, this behavior will change: a manual edit made at a higher level will now become the value at all lower levels. However, manual edits at a lower level will still override those made at a higher level.

In the example below, different Delivery data is mapped at both the Global and Market levels using two different mappings.

However, one manual edit on Global can now adjust the Global as well as all the Market values as in the example below.

This allows a user to quickly alter multiple market and/or receiver-specific values with a single manual edit, rather than making manual edits for each market and/or receiver individually. However, a manual edit at a lower level will still override a manual edit made at a higher level.

Note: Future update deliveries are subject to change.

Next update

The next update to PDX is scheduled for November 6, 2024.

PDX planned maintenance

Scheduled maintenance will be performed on the Stibo PDX platform Sunday, October 27, 2024, from 12:00 CET (noon) to 14:00 CET (6:00 AM – 8:00 AM EST).

During this time, the PDX service will be temporarily unavailable.

If you have any questions or concerns, please feel free to contact Stibo Systems Support at https://service.stibosystems.com.

September 11, 2024

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

New features

The following new functionality is described below:

Extension to value transformation

A new checkbox has been added to the Value Transformation 'Lookup table.' This checkbox ensures that 'key' values are transformed or replaced only once.

Sometimes, a value needs to be transformed when it appears both as a 'Key' and a 'Value'. For example, in line 2, the number '24' should replace the key number '2.' In line 3, '24' also exists as a key value and should be replaced by '0.75.' Similarly, in line 5, the key value '730' should be transformed to '24.'

Initially, the transformation would replace 2 with 24, 24 with 0.75, and 730 with 24. However, because the system performs recursive transformations, in the second transformation, '24' in lines 2 and 5 would be transformed to '0.75'. An example is below:

Note that when using the 'Replace only once' feature, a user would get the expected outcome:

Planned channel updates

1WorldSync channel updates

  • The 1WorldSync Preprod Channel and the 1WorldSync Channel have been updated to match the IM 8.51 (GDSN 3.1.28) 1WorldSync release

  • The next 1WorldSync Channel update to the IM 8.54 (GDSN 3.1.29) 1WorldSync release is scheduled for November 2024.

Brandbank channels update

  • The Brandbank channels in PDX are expected to be updated to match the Brandbank Release 14 on September 11, 2024. As part of this update, the two fields Structured Nutrition US (256) and Structured Nutrition EU (257) will be updated as follows:

    • The list of valid values for Nutrition Group, Amount Unit, and Amount Qualifier will be updated to reflect market specific Brandbank requirements.

    • For example, Kilocalories (kcal) will no longer be a valid Amount Unit in Structured Nutrition US (256) but will remain a valid Amount Unit in Structured Nutrition EU (257).

  • The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 15 on November 18, 2024.

Future update preview

Future updates should include the following:

  • AI mapping assistance: We are currently testing a new feature for the mappings screen within PDX. This feature leverages AI to help users complete mappings more quickly. The AI can suggest mappings based on attribute names and provide a list of recommended mappings. More details about this functionality will be available soon.

    Below is a test example of AI mapping suggestions. Up to five suggested mappings will be presented to the user, with each including the AI’s confidence score.

Below is a test example of the preview suggestions screen, with the option to map all mappings using the AI suggestions. The suggested mappings are the AI’s top confidence score suggested mappings.

Note: Future update deliveries are subject to change.

 

August 14, 2024

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

New features

The following new functionalities are described below:

Toolbar redesign

The toolbar on the channel screens has been redesigned. This new design provides a better overview of the functionalities to the user as well better navigation, improving the user experience. All previously existing features will continue to be available.

Searchable attributes settings expanded

The settings for which attributes appear in the search list, originally introduced in the May 1, 2024, update, have been expanded. Channel admins can now select attributes related to specific categories, not just those linked to the root category. This change also applies to the searchable attributes settings in Direct Channels.

Update to labels

Labels and ‘Info’ Sections in 'Application Features' under 'User Management' have been updated. The names of certain permissions have been updated. For example, 'Master Data' is now 'Master data (edit), and 'Channel setup' has been renamed 'Channel Management,' among other changes. Additionally, the descriptions in the information boxes for these permissions have been revised. It's important to note that there have been no changes to the access these permissions provide, and no new permissions have been added.

Planned channel updates

1WorldSync channel updates

The IM 8.51 (GDSN 3.1.28) 1WorldSync release is currently in test. The 1WorldSync Preprod Channel should be updated to match the IM 8.51 (GDSN 3.1.28) release on August 9, 2024.

The corresponding 1WorldSync Channel update is scheduled to happen August 17, 2024.

Brandbank channels update

The Brandbank channels in PDX are expected to be updated to match the Brandbank Release 14 on September 11, 2024.

As part of this update, the two fields Structured Nutrition US (256) and Structured Nutrition EU (257) will be updated as follows:

  • The list of valid values for Nutrition Group, Amount Unit, and Amount Qualifier will be updated to reflect market specific Brandbank requirements.

  • For example, Kilocalories (kcal) will no longer be a valid Amount Unit in Structured Nutrition US (256) but will remain a valid Amount Unit in Structured Nutrition EU (257).

Future update preview

Future updates should include the following:

  • AI mapping assistance: A new feature for the mappings screen within PDX is currently in test. The new feature will be using AI to help users in perform mappings faster. The AI can suggest mappings based on attribute names and provide a list of suggested mappings to use. More information about the new functionality will be available soon.

Note: Future update deliveries are subject to change.

July 30, 2024

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

New features

The following new functionalities are described below:

New import flow introduced

In the latest update, the import process within PDX has been streamlined for simplicity. While the fundamental components and stages of the import process are unchanged, the user interface has been improved. Navigation now displays horizontally instead of vertically, with all steps conveniently integrated within the import wizard interface—eliminating the need for a separate window for the mapping step.

Additionally, there have been modifications to the default settings. Users are now required to manually activate the Auto assignment feature, which contrasts with the previous setting where it was enabled automatically.

The objective of these changes is to offer a more user-friendly and intuitive import experience.

Updated instructions are available for the Import Data Screen.

Amazon pre-validation added

Users with any Amazon market channel can now perform a pre-validation action to confirm that a product will meet all downstream validations by Amazon prior to submitting the product. This aims to reduce the number of submission attempts required to get a product accepted by Amazon, especially in cases where teams want to ensure products are valid before setting them live on Amazon.

New configured channel output options added

New output options for sending product data in Configured Channels have been added to email and HTTP output types.

New email options:

  • Specify sender name to be shown in email to recipient

  • A direct link to the submitted file(s) replaces the current link to a download splash page. This direct link will remain valid for up to seven days, or until it expires based on the receiver's link expiration setting.

New HTTP options:

For HTTP output receivers, users can now use the PATCH method in addition to the existing POST and PUT methods supported previously.

Improved PDX route hierarchy

improvements have been made to the PDX route hierarchy, which is moving away from a mostly flat structure to a channel and area specific structure. Note that saved bookmarks and links might become invalid after the update.

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

The next 1WorldSync Channel update for the IM 8.51 (GDSN 3.1.28) release is scheduled for August 17, 2024.

The date for the corresponding 1WorldSync Preprod Channel is scheduled for August 9, 2024.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 14 on August 19, 2024.

Future update preview

The August 14, 2024, update should include the following:

  • Toolbar redesign: a redesign of the toolbar is expected to be delivered soon. Current features will still be available within the new design, but it has been updated for improved ease of use.

  • Searchable attributes settings expanded: The settings for which attributes appear in the search list, originally introduced in the May 1, 2024, update, will be expanded to include attributes related to categories.

Note: Future update deliveries are subject to change.

July 3, 2024

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

New features

The following new functionalities are described below:

Process overview added

A new Process overview has been added to PDX, which provides the user with an overview of many of the processes that are running in PDX.

The Process overview's purpose is to provide better visibility into the processing of many time-consuming operations and provide the user with a status on different processes, such as import, add to channel actions, mappings, and preparation of submissions.

The Process overview can answer questions such as the following:

  • Did the system acknowledge my request?

  • Has the job I started been completed?

  • When can I expect my job to be completed?

  • How much time went by before my job was picked up for processing?

  • How much time was spent processing my job?

  • Which other jobs have been queued up?

Users can also see information about the following:

  • When a large process has begun

  • When a large process has completed

  • Provide a overview for historical long-running processes

  • User can see metadata on the processes

The Process overview has three tabs corresponding to process statuses: ‘Queue,’ ‘Active,’ and ‘Completed.’ Users can access information about 16 different processes used in PDX. Additionally, users can view the status of processes initiated by themselves or other team members. Processes initiated by PDX will be labeled as ‘System’ in the ‘Created by’ column.

The ‘Queue’ tab displays information about processes awaiting pickup. The overview includes details such as ID, Process type, Channels (with relevant channel names displayed), creator, and creation timestamp.

In the ‘Actions’ column, users can cancel processes. Only processes in the ‘Queue’ or ‘Active’ status can be canceled. Regular users can cancel processes they initiated. Client Admins have broader cancellation privileges: they can cancel their own processes, processes initiated by teammates, and even processes initiated by the ‘System.’

In the ‘Active’ tab, users can see information about ID, Process type, information about channel and receivers, Created by, Created at, Started at and, Estimated time to complete. In the ‘Actions’ column, users can select and cancel active processes.

In the ‘Completed’ tab, users can view information as in the other tabs. This tab includes a status column: processes that are done have a ‘Completed’ status, canceled processes display as ‘Canceled,’ and failed processes show as ‘Failed.’ The completion time is also provided.

Note: In this version of the Process overview, the ‘Channels’ column only displays receiver names if the user first selects receivers and then initiates a submission. If the user is in the channel and selects ‘Submit’ before choosing receivers, the channel name will also be displayed.

Some processes are triggered only if they involve more than 100 products. For example:

  • The ‘Add to channel’ process in Master Data and from a channel is triggered when it involves more than 100 products.

  • The ‘Update Product Attributes (CH)’ process is triggered when more than 200 products are selected.

Note that the ‘Prepare submission data’ process in the 1WorldSync Channel and Brandbank Channels is not displayed in the Process overview because these channels’ submission processes are not ‘workflow’ enabled in PDX.

Permissions to view processes in the Process overview include the following:

  • Information about ‘Import’ processes can be viewed by all users.

  • If an ‘import to channel’ is performed, a user needs access to the specific channel to see the import process in the overview.

Improved accessibility and usability

The application’s accessibility and usability by enabling keyboard navigation in the sidebar menu. Additionally, users can now close pop-up dialogs using the ‘ESC’ key.

Mapping details updated display

In order to better utilize AI in the PDX application, a clean-up of the displayed mapping details section within the mapping screen has been performed. Below is an example of how the mapping screen looked previously:

Users will now be able to find an updated version with more details within each of the new panel sections and subsections. It should now provide the user with a better overview of the mapped data, as well as the option of closing the mapping details side-screen. Below is an example of the updated version:

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

The next 1WorldSync Channel update for the IM 8.51 (GDSN 3.1.28) release is scheduled for August 17, 2024.

The date for the corresponding 1WorldSync Preprod Channel is scheduled for August 9, 2024.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 14 on August 19, 2024.

Future update preview

The July 30, 2024, update should include the following:

  • New data import flow: a new data import flow is being developed for PDX. These changes simplify the flow by splitting the existing import flow into multiple flows based on the uploaded file type.

  • Toolbar redesign: a redesign of the toolbar is expected to be delivered soon. Current features will still be available within the new design, but it has been updated for improved ease of use.

  • Improved PDX route hierarchy: improvements are being made to the PDX route hierarchy, which is moving away from a mostly flat structure to a channel and area specific structure. Note that saved bookmarks and links might become invalid after the update.

Note: Future update deliveries are subject to change.

June 12, 2024

This update includes planned channel updates and a future update preview.

Planned channel updates

The planned channel updates are described below:

1WorldSync channel updates

1WorldSync Channel update

The next 1WorldSync Channel update (GDSN 3.1.28) is scheduled for August 17, 2024.

The date for the corresponding 1WorldSync Preprod Channel update will be announced in these release notes as soon as 1WorldSync have published their release schedule.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 14 on August 19th, 2024.

Future update preview

The June 30, 2024, update should include the following:

  • Visual changes to import flow

Note: Future update deliveries are subject to change.

May 22, 2024

This update includes new features, error corrections, planned channel updates, and a future update preview.

New features

The following new functionalities are described below:

Composite output conditions enabled

'Composite Output conditions' can now be applied to mappings beyond those between a master data composite and channel composite. Additionally, you can use 'Output conditions' on channel attributes such as assets, strings, dates, and integers if they are mapped to a composite sub-attribute in Master Data.

In the example below, 'Composite output conditions' are available for a channel asset attribute that is mapped to a composite sub-attribute in Master Data.

In the example below, the user is creating a mapping between a channel asset attribute named 'Asset #2' and a Master data composite sub-attribute named 'l1_asset.'

If a user does a mapping to a single valued attribute, it is recommended to set the Index value to 0.

If the definition of 'Output conditions' yields only one match, then the value at Index 0 (the first value) ensures that this single match will be mapped. Index 0 corresponds to the first row in a row selection, and Index 1 corresponds to the second row, and so forth.

If the user sets the Index to 3 and the Output Conditions yield only one match, no asset will be mapped because the one match corresponds to an Index value of 0.

Below is an example of a 'Composite Output condition' in a channel named 'Composites.' The asset attribute ‘Asset # 2’ is mapped to an asset sub-attribute (L1_Asset) in Master data. Since it is mapped to a composite sub-attribute, it could contain multiple assets. The 'Output condition' states that only assets where the sub-attribute 'l1_string' is equal to 'Top' will be mapped to the attribute in the channel.

In this case, only the asset where 'L1_String' is equal to 'Top' will be mapped. As in the example below from Master data, it will then be the asset in row 3 that will be mapped to asset attribute in the channel.

Important: ‘Composite Output Conditions’ can only be used on sub-attributes that are defined at first level in a composite. Sub-attributes that are created on nested composites cannot be used in composite output conditions.

Prefix search enabled

Previously, a user performing a search in Digital assets would have to enter the full name of the asset to obtain a result in the search. Now, the search feature is extended so it is possible to search for assets using a prefix search.

A user will need to enter a minimum of three characters in order to perform the prefix search. The prefix search is only performed on the first word in the name of the file.

Error correction

The error correction is described below:

  Description

Previously, a user could edit the values in the column 'Name' in a channel. However, this edit would also affect the value in Master data even though the user did not have access to write / edit data in Master data. With this release, values in the 'Name' column are now read-only on the channel level and can only be edited in Master data.

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

As mentioned in the previous release notes, on May 18, 2024, the 1WorldSync Channel was updated to the IM 8.48 / GDSN 3.1.27 release. This is the same date 1WorldSync performed the IM 8.48 / GDSN 3.1.27 update in their environment.

Important: As this release will contain new, deleted, and renamed attributes, users of the 1WorldSync Channel may have to map or remap attributes.

Note: This release also introduces changes to the GPC, including deleted codes. Products belonging to a deleted category code will, after the update, fall into the root category of the 1WorldSync Channel. The proper way to address this will typically include updating category codes in the source systems and adjusting auto categorization rules in PDX.

For more information on the content of the IM 8.48 / GDSN 3.1.27 release, please refer to the 1WorldSync main page for IM 8.48 / GDSN 3.1.27 release: https://community.1worldsync.com/t5/Are-You-Ready-for-Large-Release/ct-p/LargeRelease2024 (login required).

1WorldSync CIC message improvements

This release also includes support for two new CIC fields that will now be displayed on CIC product history entries in PDX:

  • Creator Name

  • Creator GLN

The below image is an example of these fields.

Brandbank channels update

As mentioned in the previous release notes, on May 20, 2024, the Brandbank channels in PDX were updated to match the Brandbank Release 13.

For more information on the content of the Brandbank Release 13 release please look at Brandbank's Data Model Release Notes: https://nielsenbrandbank.freshdesk.com/en/support/solutions/folders/75000016412 (login required).

Brandbank Structured Nutrition US improvements

As part of this update, the 'Structured Nutrition US' attribute in the Brandbank US channel has been updated with new options for Nutrition Group (the 'Per Reference' Column) and Amount Unit (e.g., the 'Cups' Unit of Measure).

Below are examples of the usage of the new options:

Future update preview

The June 12, 2024, update should include the following:

  • Multilanguage products data can be exported from channel to Excel file.

  • Multilanguage products data can be re-imported from Excel file into the channel.

Note: Future update deliveries are subject to change.

 

May 1, 2024

This update includes new features, error corrections, planned channel updates, and a future update preview.

New features

The following new functionality is described below:

Ability to set attributes as searchable

Users with access to ‘Direct Channels’ in Channel Management now have the possibility to set up searchable attributes in a direct channel.

On the General tab and in the section ‘Searchable channel attributes,’ the user can define which attributes should be displayed in the filters where attributes are used.

The below window will open when a user clicks 'Set searchable attributes.' Attributes can be activated when clicked in the left-side window. Attributes displayed on the right side are activated. Order of attributes can also be defined by clicking on the two lines and moving the attribute up or down.

Attributes with a keylock cannot be removed as they are part of a channel's data standard.

The definition and order of the attributes will be shown in the filter ‘Product attributes’ in list view and grid view.

In this first version of ‘Set searchable attributes’ only attributes that are linked to the channels root category can be set. Attributes that only exist in one or more categories will not be available. Attribute types like composites and assets cannot be added to a search filter.

Ability to set grid view as default

A new user preference has been added to 'Your profile' settings. The 'Show grid as default view' setting allows a user to set the grid view as the default view for channels and master data in order to immediately start working in the preferred mode.

New filtering ability for last updated date for products

A new product filter available in list and grid views allows to filter by products updated within a specific date range to more easily find the relevant products to edit / submit.

In channels users can filter by both 'Updated in channel' and 'Updated in Master Data' date ranges, and users can filter by the 'Updated in Master Data' date range in master data.

Ability to skip 'bearer token' in HTTP delivery

Previously, if a user chose 'Send request to get bearer token' in HTTP delivery, the 'Bearer' prefix was automatically added to the token received.

A user can now select 'Skip Bearer prefix in header' with the following description: 'This will allow you to send token in Authorization header without Bearer prefix.' This checkbox is placed below the 'Token name' input field in the Authentication section of an HTTP delivery method configuration.

With this option, a user can input different prefixes and send them together with the token.

Error corrections

Error corrections are described below:

  Description

For PDX channels that take advantage of the Channel Hierarchy functionality (e.g., Markets in 1Worldsync and Subscription Codes in the Brandbank channels), the PDX Application previously made it possible to define Category Rules for each channel level in a Channel Hierarchy.

As products can only belong to one category per channel, allowing distinct category rules for various sub-channels was illogical. Since these rules were ineffective, such an option could lead to confusion.

Therefore, this option has been removed from the application, and Category Rules can now only be configured at the Global level and no longer at lower levels in a Channel Hierarchy.

See the screenshots below from the 1Worldsync channel at Global level and the 1Worldsync channel at the US market level that illustrate the different options:

The digital asset search has been changed. Users must now enter the full asset name, asset ID, or origin.

Originally, anything a user entered into the search field was turned into a wildcard search. The wildcard search feature was disabled due to instances where search durations surpassed the browser’s timeout limit, leading to a 'no assets found' message even though a user was searching for items that do exist.

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

As mentioned in the previous release notes, the 1WorldSync Preprod environment has been updated to the coming large IM 8.48 / GDSN 3.1.27 release.

As part of this PDX release the PDX 1WorldSync preprod Channel has now also been updated to the IM 8.48/GDSN 3.1.27 version.

The future 1WorldSync Channel updates will now be the following:

  • The 1WorldSync preprod Channel will be updated as 1WorldSync post new updates.

  • On May 18, 2024, the 1WorldSync Channel will be updated to the IM 8.48 / GDSN 3.1.27 release (this update will include updates from IM 8.46 and IM 8.47). This is the same date 1WorldSync will perform the IM 8.48 / GDSN 3.1.27 update in their environment.

  • No separate updates for IM 8.46 or IM 8.47 will be made in the 1WorldSync Channel.

Important: As this release will contain new, deleted, and renamed attributes, users of the 1WorldSync Channel may have to map or remap attributes.

Note: This release also introduces changes to the GPC, including deleted codes. Products belonging to a deleted category code will, after the update, fall into the root category of the 1WorldSync Channel. The proper way to address this will typically include updating category codes in the source systems and adjusting auto categorization rules in PDX.

For more information on the content of the IM 8.48 / GDSN 3.1.27 release, please refer to the 1WorldSync main page for IM 8.48 / GDSN 3.1.27 release: https://community.1worldsync.com/t5/Are-You-Ready-for-Large-Release/ct-p/LargeRelease2024 (login required).

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 13 on May 20, 2024.

Future update preview

The June 12, 2024, update should include the following:

  • Multilanguage products data can be exported from channel to Excel file.

  • Multilanguage products data can be reimported from Excel file into the channel.

Note: Future update deliveries are subject to change.

April 10, 2024

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

New features

The following new functionality is described below:

Consolidated templates option added

Originally referred to as 'Support All-Products-In-One Template Output in Configured Channels' in the update preview, this new consolidated templates option has been added for spreadsheet templates in Output Configuration of configured channels. This option allows users to submit all products across categories from a Configured Channel into a single output template. The option will not split products into output files by category, meaning receivers won’t have to look through many different spreadsheets when they receive the submission to get all data. This is mutually exclusive to the 'Output category template' option.

Asynchronous download of product data to Excel file

Downloading the data from both Master Data and Channels is now asynchronous, with no limit on the number of products that can be exported. Longer download times for large export files might occur.

When the user starts downloading, the following message will display: 'Your download has started. We will notify you once it is ready.'

Once the product file is ready for download, another notification will display, which will contain the download link:

Changes to Auto-Categorization and Manually-Added Product Behavior

Previously, products manually added to a channel were permanent: the products must be manually removed and then re-added using rules in order to allow rules to remove them again. Now, the behavior allows rules to remove manually added products from a channel:

  • A product manually added to a channel that matches existing rules will be treated as if added by rules when the rules are run.

  • A product manually added to a channel that originally matched the rules will be removed if it no longer matches the rules.

  • A product manually added to a channel that never matched the rules will not be removed, even if there is no current match.

Ultimately, a manually added product first has to match the rules and then not match those rules before the product is removed by rules – otherwise, it will remain in the channel until removed manually.

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

Previous release notes announced the next update to be made to the 1WorldSync Channels in PDX would be IM 8.46.

1WorldSync now has decided to update its 1WorldSync Preprod environment to the coming large GDSN 3.1.27 release. PDX has decided to follow a similar approach in order to give users of the 1WorldSync Channel in PDX time to test the new GDSN 3.1.27 release and prepare the needed changes. Therefore, the future 1WorldSync Channel updates will now be the following:

1WorldSync Preprod Channel update

  • The 1WorldSync preprod Channel will be updated to the version in the 1WorldSync Preprod environment (currently this is IM 8.48 / GDSN 3.1.27 and IM 8.46) once PDX development and testing has been completed.

  • The 1WorldSync Preprod Channel will be updated as 1WorldSync post new updates.

    • Currently 1WorldSync plans to add IM 8.47 to the Preprod environment April 12, 2024, but other updates may be made available.

1WorldSync Channel update

  • On May 18, 2024, the 1WorldSync Channel will be updated to the IM 8.48 / GDSN 3.1.27 release (this update will include updates from IM 8.46 and IM 8.47). This is the same date 1WorldSync will perform the IM 8.48 / GDSN 3.1.27 update in its environment.

  • No separate updates for IM 8.46 or IM 8.47 will be made in the 1WorldSync Channel.

Important: As this release will contain new, deleted, and renamed attributes, users of the 1WorldSync Channel may have to map or remap attributes.

Note: This release also introduces changes to the GPC, including deleted codes. Products belonging to a deleted category code will, after the update, fall into the root category of the 1WorldSync Channel. The proper way to address this will typically include updating category codes in the source systems and adjusting auto categorization rules in PDX.

For more information on the content of the IM 8.48 / GDSN 3.1.27 release, refer to the 1WorldSync main page for IM 8.48 / GDSN 3.1.27 release: https://community.1worldsync.com/t5/Are-You-Ready-for-Large-Release/ct-p/LargeRelease2024 (login required).

Brandbank channels update

The Brandbank channels in PDX are scheduled for a May 20, 2024, update to match the Brandbank Release 13.

Future update preview

The May 1, 2024, update should include the following:

  • User preference setting to 'Show grid as default view'

  • Filtering products by last updated date range in channels and in master data

  • Skipping 'Bearer' prefix for token in the HTTP delivery method in Configured Channels

  • Multilanguage products data can be exported from channel to Excel file

  • Multilanguage products data can be exported from channel to Excel file

  • New 'Process log' that will display processes initiated by a user or external submission, such as imports, submissions, updates, and more.

Note: Future update deliveries are subject to change.

March 20, 2024

This update includes a new feature, planned channel updates, and a future update preview.

New feature

The following new functionality is described below:

Variables added to email template

Additional variables are now available in the email templates for Configured Channels. These additional submission variables, which can be added to a configured channel's output configuration, can increase the amount of information available to the receivers.

The following variables have been added to the template:

  • Submission comment

  • Submission date / time

  • Link expiry days

All currently available variables are now also listed in the tooltip message for the email content section:

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

1WorldSync Channel update (IM 8.46)

The next 1WorldSync update (IM 8.46) is scheduled for March 15, 2024, in the 1WorldSync Preprod environment and March 23, 2024, in the 1WorldSync production environment.

Note: After 1WorldSync has released the corresponding Participant Dictionary and the PDX team has tested the resulting updates, the corresponding channels will be updated in the PDX environments. The update will typically be reflected in the 1WorldSync Channels in PDX one to two weeks after the update in the 1WorldSync environments, depending on the release of the Participant Dictionary and the size of the update.

Brandbank channels update

The Brandbank channels in PDX are scheduled for a May 20, 2024, update to match the Brandbank Release 13.

Future update preview

The April 10, 2024, update should include the following:

  • Asynchronous export of product data to Excel file from Master Data

  • Asynchronous export of product data to Excel file from Channels

  • Support All-Products-In-One Template Output in Configured Channels

Note: Future update deliveries are subject to change.

March 4, 2024

This update includes a new feature, planned channel updates, and a future update preview.

New feature

The following new functionality is described below:

CSV templates supported

CSV templates are now supported along with Excel templates in the Configured Channels output configuration template library.

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

1WorldSync scheduled maintenance

1WorldSync has announced a maintenance window on the production systems on Saturday March 9, 2024, from 9:00 am to 1:00 pm ET. Several 1WorldSync components are affected and temporarily taken down by 1WorldSync.

This impacts the 1WorldSync Channel in PDX:

  • The message exchange between PDX and 1WorldSync will be interrupted and message queues may build up while the 1WorldSync Batch processing is down.

  • During the announced time period and for a for few hours afterward, users of the 1WorldSync channel in PDX can expect to experience delays in message sent to 1WorldSync and messages arriving from 1WorldSync.

The PDX team will monitor the connection.

See the 1WorldSync announcement for additional details. A login is required.

1WorldSync Channel update (IM 8.45 + GDSN Release 3.1.26)

  • The 1WorldSync Channel update (IM 8.45 + GDSN Release 3.1.26) was performed in the 1WorldSync Preprod Channel February 27, 2024.

  • “The 1WorldSync update (IM 8.45 + GDSN Release 3.1.26) of the 1WorldSync Channel is included in the current update March 4, 2024.

Upcoming 1WorldSync channel update (IM 8.46)

  • 1WorldSync channel update (IM 8.46) is scheduled for the 1WorldSync Preprod channel on March 15, 2024.

  • 1WorldSync channel update (IM 8.46) is scheduled for the 1WorldSync Production channel on March 23, 2024.

Note: After 1WorldSync has released the corresponding Participant Dictionary and the PDX team has tested the resulting updates, the corresponding channels will be updated in the PDX environments. The update will typically be reflected in the 1WorldSync Channels in PDX one to two weeks after the update in the 1WorldSync environments, depending on the release of the Participant Dictionary and the size of the update.

Brandbank channels update

As part of the current update of March 4, 2024, the Brandbank channels in PDX are updated to match the Brandbank Release 12.

Future update preview

The March 20, 2024, update should include the following:

  • Additional variables available in the email templates for Configured Channel

    • {{submission_comment}}

    • {{submission_datetime}}

    • {{link_expiry_days}}

Note: Future update deliveries are subject to change.

February 12, 2024

This release includes new features and planned channel updates.

New features

The following new functionalities are described below:

New account settings view

A new account settings view is now available for all users under the user icon. Client admin users will have a Profile and account settings view option, and regular users will have a Profile settings view option.

If a user clicks on the applicable new settings view, a new sidebar will appear in the tool. Both user levels will have the 'Your profile' option. This option provides settings such as resetting the password (formerly placed under the user icon), preferred language, and user level feature settings.and client admin users will also have an expandable 'Account' option.

Client admin users will also see an expandable menu for Account options.

  1. General: provides general information about the account as well as settings previously available under Configuration -> Feature settings.

  2. Team management: was previously available under the user icon as 'Manage team.'

  3. API keys: provides option to add and delete API keys.

  4. Master data configuration: previously available under Configuration -> Master settings.

Feature toggles cleanup

Some feature toggles have been deprecated and removed. The remaining feature toggles have been divided into Customer controlled and Stibo controlled. Customer controlled settings are available in the 'Your profile' or 'General' settings tabs. Stibo controlled settings are owned and managed by Stibo Systems Professional Services and are moved to a separate administration application.

Customer controlled: settings that can be enabled or disabled by clients

  • User preferences

    • Set on user level

    • Currently include 'Show category dashboard'

  • Client settings

    • Set on client level and should all affect all users of a given client

    • Available only to client admins in Account -> General settings screen

    • Currently include 'Lockdown mode'

Stibo controlled: settings available only to Stibo employees

  • Client settings

    • Set on client level and should all affect all users of a given client

    • Set individually for each customer

    • Include the following

      • Enable product limits

      • Use websockets for fetching import feed

      • Allow retrieving products from channels that allow retrieval

      • Use simple presubmit validation

      • Enable vendor portal

  • Test features

    • Temporary features to be used by testers and/or beta testers

    • Will be set to on by default and removed upon successful testing completion

    • Currently include the following

      • Enable process log

      • Enable new toolbar

The table below provides a list of all previously available feature toggles and their current state:

New grid view

The 'Render Families Separately' flag is now turned on for all users and removed from feature settings. This new view should provide improved performance for viewing families. Now, whenever the channel supports families and there are families to be displayed, the grid will be divided into three tabs:

  • Regular products

  • Family products

  • Variant products

Planned channel updates

The planned channel update are described below:

1WorldSync channel updates

1WorldSync Channel update (IM 8.44)

  • The 1WorldSync Channel update (IM 8.44) was performed in the 1WorldSync Preprod Channel on January 29, 2024.

  • The 1WorldSync update (IM 8.44) was performed in the 1WorldSync Channel on February 6, 2024.

1WorldSync public certificate rotation

As part of its yearly rotation of certificates, 1WordSync is replacing its public AS2 certificates.

PDX will update the 1WorldSync public certificates on the PDX AS2 systems during the AS2 outage windows announced by 1WordSync:

  • 1WorldSync Preprod channel – PDX switch completed February 2, 2024.

  • 1WorldSync Production channel – PDX switch completion scheduled for February 16, 2024.

See the 1WorldSync announcement for additional details on the maintenance windows.

No actions are required by users of the 1WorldSync channel in PDX, and PDX will be operational during 1WorldSync's maintenance window. However, during the 1WorldSync maintenance window, 1WorldSync will not pick up new messages, which means that submissions from PDX to 1WorldSync during this maintenance window might be delayed.

Upcoming 1WorldSync channel update (IM 8.45 + GDSN Release 3.1.26)

  • 1WorldSync channel update (IM 8.45 + GDSN Release 3.1.26) is scheduled for the 1WorldSync Preprod channel on February 16, 2024.

  • 1WorldSync channel update (IM 8.45 + GDSN Release 3.1.26) is scheduled for the 1WorldSync Production channel on February 24, 2024.

Note: After 1WorldSync has released the corresponding Participant Dictionary and the PDX team has tested the resulting updates, the corresponding channels will be updated in the PDX environments. The update will typically be reflected in the 1WorldSync Channels in PDX one to two weeks after the update in the 1WorldSync environments, depending on the release of the Participant Dictionary and the size of the update.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 12 on February 24, 2024.

January 15, 2024

This update includes planned channel updates.

Planned channel updates

The planned channel update are described below:

1WorldSync channel update

The next 1WorldSync Channel update (IM 8.44) is scheduled for January 19, 2024, in the 1WorldSync Preprod Channel and January 24, 2024, in the 1WorldSync Channel.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 12 on February 24, 2024.

January 3, 2024

This release includes new features and planned channel updates.

New features

The following new functionalities are described below:

Channel attribute locking

In the grid view in Master data and on channel level, a user can now define which attributes should be locked. Each user can define an individual view for the master data and channels accessible to that user.

In the feature ‘Attribute filters,’ the user can select attributes to lock by performing a search and selecting the specific attribute.

In the example below, the user has chosen ‘Name,’ ‘External product status,’ and ‘Product description’ to be locked.

These three attributes columns are now locked when the user scrolls on the horizontal navigation bar. Attributes on the left side of the gray thin line are the locked ones. The attributes ‘ID’ and ‘Status’ are always shown and cannot be unlocked.

Unpublish products from a digital catalog

It is now possible to unpublish / remove products in a digital catalog. The user of PDX can now select the feature ‘Unpublish’ under the FAB icon. It is only possible to unpublish products from a Digital Catalog.

The icon for ‘Unpublish’ will only be shown in channels where a digital catalog has been created. The ability to ‘Unpublish’ is related to the a user's permissions. A user must have the permission ‘Submit to channel’ in order to unpublish products.

It is only possible to unpublish products that have status ‘Submitted’ or ‘Accepted.’ When a product has been unpublished, it will change status back to ‘Ready’ or ‘In-Progress,’ depending on the state of the product.

Unpublishing products on a global level in a channel

To unpublish products from a digital catalog, the user must first select which products should be removed. When a user unpublishes products on a global level in a channel, the user will be shown all the digital catalogs that exist in that channel. In the example below, the channel contains three digital catalogs. A user can select to unpublish products from some or all digital catalogs in the channel.

When user has selected the products and then selects ‘Unpublish,’ the below screen will appear. In the example below, the user has selected to unpublish products only from the digital catalog ‘My Digital Catalog.’

Unpublishing products on a receiver level in a channel

If user wants to unpublish products on ‘Receivers’ level, the selected receiver will be shown in the window, and the user can select ‘Unpublish.’

Removing products from a channel

If user removes products from a channel, the products will also automatically be removed from the channel’s digital catalogs.

Deleting product information in master data

If user deletes a product in Master Data, the product will also be deleted in the channels and the corresponding digital catalogs.

Show composite attributes in a digital catalog

It is now possible to show composite attributes in the digital catalog. Composite attributes will be shown on the product details page. If a composite contains multiple levels, it is possible for the user to navigate to a specific level by clicking on the links inside the composite. The link will take the user to the next level of the composite.

Planned channel updates

The planned channel update are described below:

1WorldSync channel update

The next 1WorldSync Channel update (IM 8.44) is scheduled for January 19, 2024, in the 1WorldSync Preprod Channel and January 24, 2024, in the 1WorldSync Channel.

Brandbank channels update

The Brandbank channels in PDX are scheduled to be updated to match the Brandbank Release 12 on February 24, 2024.