General Enhancements and Changes

Summary

The following enhancements and changes have been made as part of the 2025.3 update:

  • The existing Javadoc 'html' link has been updated to display the 'All Classes and Interfaces' page directly (instead of the package overview page) for faster navigation to specific class documentation. Refer to the Technical Documentation, available at [system]/sdk or accessible from the Start Page.

  • The GraphQL API now supports filtering objects based on their last modification date, enabling more precise data queries. The new revisedObjectLastEdited condition uses ISO date-time values with standard comparison operators (such as >, <, and =) to search object revision timestamps. Developers can now retrieve recently modified objects, identify objects that have not been updated since a specific date, or locate objects modified within a specified number of recent minutes. Refer to the GraphQL API links in the Technical Documentation, available at [system]/sdk or accessible from the Start Page.

  • The log level for business conditions that prevent approval, for example, during bulk updates, has been reclassified to improve log clarity. This reduces unnecessary clutter in the standard log view while maintaining full stack trace visibility at the fine level. This enhancement helps administrators focus on critical issues by filtering routine business condition failures. For more information, refer to the Logs topic in the Administration Portal documentation.

  • Web UI password editing for STEP authenticated users no longer requires updating a configuration property when adding the User Password component to User Details screens. This enhancement reduces administrative overhead and accelerates Web UI deployment. For details, refer to the Changing a User Password topic in the System Setup documentation.

  • The background process (BGP) storage functionality has been enhanced to improve execution and performance. Intermediate BGP files are now accessible only through APIs, or by downloading them directly via STEP. For more information on how to download BGP files from STEP, refer to the Managing BGP Data topic in the System Setup documentation.

  • To improve storage availability, SaaS environments now enforce a 30 day limit on the retention of integration and background process files. It is advised that customers retrieve and archive files that need to be kept for longer.

  • Performance has been improved for Cassandra multitenancy.

  • Support for the use of publishing business conditions in Elasticsearch configurations has been deprecated. Existing configurations that use business conditions will continue to function as expected. If a customer is already using this functionality, the creation of new configurations using business conditions will continue to be available to them.

  • Sufficiency Scores are now supported by Elasticsearch for use in the Instrument search screen.

The following enhancements and changes to the Self-Service UI (SSUI) are documented in the SaaS Self-Service 'User guide':

  • The 'SFTP access control' section of the 'User guide' now includes steps to create a public / private key pair using ssh-keygen.

  • The new 'Modular Services' page allows developers to deploy extension services for use in STEP. Refer to the New Modular Service Platform update note for details.

  • The new 'Security events' tab for environments provides visibility into changes made to Users and Groups, including metadata, privilege modifications, log in attempts, log out attempts, and failed authentication attempts.

  • The 'Environments details' page now supports configuration of the 'Welcome text' that is displayed on the Login Screen for STEP Authenticated users, as well as the option to display or hide the 'Forgot password' link.

  • The 'Update preview sandbox' feature is now generally available and has been extended to also allow Pre-Production environments to be selected as source. Including a database copy is now optional and is available depending on the size and characteristics of the source environment.

  • IP addresses for inbound / outbound communication to STEP services for all regions have been updated. Customers using IP whitelisting must add the new IPs prior to the next Stibo Systems SaaS platform maintenance window on November 2nd, 2025. Failure to do so may cause inability to access the STEP services. Refer to the 'STEP IP access control list' section of the 'User guide' for details.

These enhancements and changes are also included in the 2025.3 update and are described in the Details section that follows:

Details

Persistent filters in Web UI

Users filtering data in most Web UI tables (e.g., Task Lists and search result screens) can now expect the applied filters to persist after navigating away from the table. When a filter is applied to a Task List, for example, and users change the view or context, navigate to another object, switch to another Task List, or even log out, the filter will still be applied for that user when they return to the Task List. Previously, the filters would not persist, requiring users to re-apply them each time, which proved needlessly time-intensive. With this improvement, all contributors to a workflow will find the experience of filtering their data in Web UI tables to be more reliable, improving the general efficiency of using filters. As an added help to users, the filter icon displays as blue when a filter is applied. Providing this clear visual gives users an immediate view as to whether the table data being displayed is filtered.

It should be noted that the 'Enable filtering' setting should be activated in the designer to make use of these improvements.

For more information on filtering in the Web UI, refer to the Node List Component topic in the Web User Interfaces documentation.

Explore further by clicking the video below. If it does not play as expected or you want to watch more videos, you can explore all our Product Updates videos on YouTube or within our Product Updates page on our corporate website.

JavaScript business rules, reflection, and public APIs

Reflection is now blocked for JavaScript business rules, as announced in the 2023.3, 2025.1, and 2025.2 Update Guides. The scheduled 'Reflection Usage in Business Rules' healthcheck (defined in the Healthcheck Test Index topic in the Performance Analysis documentation) identifies business rules that use reflection and reports them with the text 'Attempted to call reflection API...' in the step.0.log.

Developers should rewrite business rules that use reflection to use publicly available methods, which are secure and performance-optimized for long-term stability and compliance. The Scripting API now provides new public methods for:

  • Attributes

  • Lists of values

  • Print

  • Workflows

For more information, refer to the Javadoc link under the Scripting API section of the Technical Documentation, available at [system]/sdk or accessible from the Start Page.

Retailers can provide feedback to suppliers on enhanced content in STEP

Retailers can now enable and configure enhanced content status updates, allowing them to review new or updated enhanced content submitted in STEP by suppliers. Retailers have the flexibility to accept or reject content, and in cases of rejection, provide a message to guide suppliers in making necessary corrections. This feedback, including content status and rejection reasons, is communicated back to suppliers through enhanced content. To ensure quality and consistency, enhanced content will only publish content that has been accepted by the retailer to consumers browsing the retailer’s product detail pages (PDPs). The enhanced content feedback loop operates independently from the product feedback loop, and suppliers can continue to update enhanced content, notify retailers, and request additional reviews. During this process, previously approved enhanced content may remain live on the e-commerce site while new content is under review. For more information, refer to the Enhanced Content Tab topic in the Solution Enablement documentation.