Skip to main content
Release 162

Release date: February 14, 2025

D
Written by DeepStream Support
Updated over a week ago

👀 Make request bulletins visible from specific stages

We’ve updated request bulletins to be visible only to suppliers in specific stages, improving control and relevance of shared information.

  • Stage-Specific Visibility: Bulletins can now be restricted to suppliers in a specific stage or later stages.

  • New "Visible from stage…" Field: This internal-only field (visible only to buyers) determines when bulletins become accessible to suppliers.

  • Default to Stage 1: Existing bulletins will remain visible to all suppliers by default, ensuring full compatibility with current requests.

  • Notifications Aligned with Stages: Suppliers will receive bulletin notifications only when a bulletin is issued which they can view, or when they confirm progressing to a stage where a new bulletin is visible.

This change helps buyers manage sensitive information more effectively throughout the bidding process.

⬆️ Enhanced file upload experience in grid cells

  • Visual improvements for a cleaner and more consistent look across styles and states.

  • Currently applies to single-file uploads in document sections.

  • This update sets the foundation for broader use in upcoming contract improvements.

🐛 Bug fixes and small improvements

  • Optimisations to improve request processing speed and performance, particularly for large requests.

  • Fix for a small typo in the bulk file download “readme” file.

  • Fix to add a missing translation in the Excel line items bid file.

  • Fix to ensure that the correct bid total is shown where the final stage is an auction, rather than the bid total from the previous non-auction stage.

  • Fix for an issue where the currency was missing in the contract line items grid when imported from an RFx where the currency was revised. The supplier response will now display with the correct currency as expected.

  • Fix: Improved bid progress display to prevent occasional errors when rendering certain statuses.

  • Fix: Resolved an issue that caused some requests to fail due to incorrect request parameters.

  • Fix: Ensured all sections are correctly retrieved in evaluation pages, preventing errors during processing.

  • Fix: Corrected a missing translation in chat-related reports, ensuring all report fields are properly displayed.

  • Fixed an error in request lots report generation caused by bid-related queries for draft requests and templates, which should not contain bids.

  • Fixed an issue where incomplete templates caused errors in the system by removing the affected templates and requests.

  • Fixed an issue where removing a user twice from a request caused errors, by cleaning up redundant removal events.

Did this answer your question?