Sumday Product Release Update
🚀 Sumday Product Release
We're thrilled to unveil a host of improvements in our latest release, designed to elevate your carbon accounting experience and make your workflow even more seamless. Here's a glimpse of what's new:
🎉 Carbon Ledger Improvements
- Click Anywhere Convenience: Effortlessly select or unselect transactions in the Carbon Ledger with a simple click, eliminating the hassle of hunting for tiny checkboxes.
- Smart Transaction Search: Easily locate specific transactions with our enhanced search functionality, allowing you to explore and filter transactions based on any non-editable column – be it text or amount and bulk select.
- Efficient Handling of Transactions: Enjoy the capability to manage a larger volume of transactions seamlessly, thanks to updates in the Carbon Ledger that improve data handling.
📈 Assessment Updates
- Full Cradle-to-Grave Assessment Functionality: We've introduced the Processing of Sold Products and Use of Sold Products categories to the downstream emissions section, meaning that all downstream categories can now be included in assessments prepared in Sumday.
- Enhanced Finalisation Handling: Experience improved finalisation processes with proactive warnings when an unavailable emission source is detected, ensuring the credibility of your assessments.
🌐 Usability Enhancements and ⚙️ Performance Boosts
- Informative Tooltips: Dive into a more guided experience with tooltips strategically placed throughout the product. Many of these tooltips provide quick links to our help page, ensuring you're always in the know.
- Speedy Responses: Various improvements have been implemented to optimise response times and reduce loading durations across different areas of the product, ensuring a swift and responsive user experience.
🛠️ Technical Enhancements and 🐞 Bug Fixes
- Bugs Squashed: We've addressed and fixed various bugs, including one which allowed some downstream categories to be selectable from the carbon ledger, some which caused screens not to refresh when they should have, and one where huge numbers could be entered which generated some calculation errors.
