04 October 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.2.11 | Automatic update |
Web app | 3.2.11 | Automatic update |
Mobile iOS app (Beta) | 3.2.11 | Automatic update |
Mobile Android app (Beta) | 3.2.11 | Automatic update |
Middleware | 3.2.11 | Automatic update |
APIs and Integrations | 3.2.11 | Automatic update |
Category | Product Update | Charity | Donor | Foodbank | Reference |
Mobile Apps | Charity users using the Foodboard on the Flutter app can now successfully accept offers, resolving the issue that prevented them from accepting offers. | ✔ | C3-7170 | ||
Notifications | There was an issue where users were receiving duplicate notifications from the Donor. This issue has been fixed, and now only one text per donation is sent. | ✔ | C3-6997 | ||
Mobile Apps | There was an issue on the mobile app where when Donors creating an offer with a Custom Transfer Window and added a primary charity branch—the offer was getting stuck in the “received” status. This is now fixed. | ✔ | ✔ | C3-7123 | |
Foodiverse Web | As a FoodNet Admin or Member Manager, charities without a future start date will no longer appear on the schedule until they accept the invite. | ✔ | C3-7010 | ||
Foodiverse Web | As a Foodnet admin, the issue with different behavior when adding Third Party Assignment charities to a donor schedule, specifically for 3PC branches, has been addressed. | ✔ | C3-7050 | ||
Reporting | Users can now see the total kg donated and the sum of listed kg for each branch are the same. | ✔ | C3-7169 | ||
DevOps | The “no parent element found” and other warnings seen in the dev tool console when adding and removing Temporary Calendar Closure dates on the Manage Network Members page have been cleared. | C3-6966 | |||
Backend/APIs | The list of Kenyan counties and branches has been updated based on the provided sheet from FBK, and the database now reflects correct KE locations. | ✔ | C3-7042 | ||
Reporting | We removed the “Impact Report” from the web app dashboard as it was causing minor performance issues and we received feedback from users that it wasn’t adding value for them. | C3-6903 | |||
Foodiverse Web | As a FoodNet admin, charity branches can no longer be added to the Third Party Assignment of a 3PC unless they belong to the same charity organization as the 3PC. | ✔ | C3-6984 | ||
Notifications | We have added a warning message to the charity temporary calendar on the mobile app to alert charity branches to the fact that if they close themselves temporarily today, this may have a negative impact on their compliance KPI. | ✔ | C3-6997 | ||
Mobile Apps | Users can now remove all temporary closures in the future by clicking the “Select All” checkbox on the mobile app. | C3-6998 | |||
Foodiverse Web, Mobile Apps | We have updated the tooltips for food bank admins and charity branches using the mobile app to view temporary closures up to 12 months into the past. We have updated the charity temporary calendar user interface on the web app so that it’s easier to read. | ✔ | ✔ | C3-7000, C3-7001, C3-7020 | |
Reporting | Foodiverse users can now view Scheduling reports with pagination enabled for frontend data. | ✔ | C3-7154 | ||
Reporting | Foodnet users can now run the schedule report for only 7 days to retrieve data quickly on the frontend and the backend. | ✔ | C3-7212, C3-7213 | ||
Backend/APIs | We have added a new setting if Foodnet recipient branch members. Now Food Net admins can set a max. capacity limit to recipient branches in Membership Administration for the purposes of Automated split donations only. | ✔ | ✔ | C3-6856 | |
Foodiverse Web | As a Foodiverse user, scheduling reports are now available directly in Foodiverse, eliminating the need to use scripts and saving time. | ✔ | C3-6860 | ||
Backend/APIs | We have implemented a way for Foodiverse to have a way of prioritizing the order in which branches will receive an auto-split donation on a Donor schedule. The priority will be based on the order in which recipient branches are added and saved to a Donor Schedule. | ✔ | ✔ | ✔ | C3-6871 |
Foodiverse Web | As a Foodiverse user, the ability to download the schedule report has been enabled, allowing for easier data analysis. | ✔ | C3-6876 | ||
Reporting, Backend/APIs | We have implemented a new check which enables Foodiverse to check if all Charities on a Donor schedule have a maximum volume capacity set. If they do, the donation will automatically split between those charities. Users can now process split donations automatically based on Charity recipients Maximum Volume Capacity settings. | ✔ | C3-6915, C3-6916 | ||
Backend/APIs | Foodiverse can now successfully split donations automatically between Charities on Donor schedules where the charity branches each have their maximum capacity settings set. This was to automate the testing of the auto-split feature end to end. | ✔ | ✔ | C3-6923, C3-6928 | |
Foodiverse Web | Foodiverse users can download the schedule report from the backend for data analysis. | ✔ | C3-6930 | ||
Reporting | Foodiverse users can now download the schedule report from the backend for data analysis. | ✔ | C3-7003 | ||
Mobile Apps | Donor users on the Flutter app can now add donation collection notes for the person collecting, ensuring they have the relevant information to find the correct contact and transfer the donation. Charity users accepting offers on the Flutter app can now add delivery notes for the collector branch address. Donor and Foodbank users on Flutter can now see the added donation collection notes on the Live Donation details and Donation details in Donation History. | ✔ | ✔ | ✔ | C3-7005, C3-7006, C3-7007 |
Mobile Apps | Charity branch users, 3PC, 3PL, and Foodbank users on Flutter can now see both donor-added collection notes and recipient charity-added delivery notes on the Live Donation details and Recent Offers. | ✔ | ✔ | ✔ | C3-7008 |
DevOps | A feature flag for Donor Collection notes and Charity Delivery notes has been created for the Flutter mobile app, allowing the feature to be enabled or disabled in Foodiverse environments. | ✔ | ✔ | C3-7011 | |
Backend/APIs | We have added a new recipient branch type that Charity Org admins can create called “3PL branches.” These branches will be used to onboard a 3PL provider as an app user of Foodiverse. 3PL branches cannot accept food donations but will be assigned to collect food donations from the donor and deliver them to the charity that accepted the offer. | ✔ | C3-7017 | ||
Backend/APIs | We have added a new transfer window type for donor schedules. Now Foodbank admin can add a 3PL branch in their Food Net to a 3PL schedule type so that when the donor posts, a 3PL branch knows to collect food from the Donor branch and deliver it to the charity branch that accepted the offer during that scheduled collection window time. | ✔ | ✔ | C3-7022 | |
Foodiverse Web | The Foodiverse web app for Donors and Foodbanks now includes a clear and intuitive schedule view that highlights when 3PL transfer windows are scheduled. This ensures Donors are aware of when to expect a 3PL driver at their branch during the specified Collection Window time. | ✔ | ✔ | C3-7065 | |
Foodiverse Web | We have ensured that 3PL branch types cannot be added to standard schedule types or to Delegated Collector schedule types. This is in case a 3PL branch is accidentally added by mistake. 3PL branches cannot donate or accept offers so they should not be added to these schedule types to avoid potential system or process errors. | ✔ | ✔ | C3-7071 |
30 August 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.2.9 | Automatic update |
Web app | 3.2.9 | Automatic update |
Mobile iOS app (Beta) | 3.2.9 | Automatic update |
Mobile Android app (Beta) | 3.2.9 | Automatic update |
Middleware | 3.2.9 | Automatic update |
APIs and Integrations | 3.2.9 | Automatic update |
Category | Foodiverse Update | Charity | Donor | Foodbank | Reference |
Backend/APIs | When creating a Collection Window, the UUID is now correctly returned by the database instead of the ID. | ✓ | C3-3332 | ||
Foodiverse Web App | Food Net Admins, Users, and Member Managers will no longer see charities on the schedule before their designated start date when scheduled with a future start date. | ✓ | ✓ | ✓ | C3-5434 |
Mobile Apps | Mobile users of FV on Android devices will no longer see a ‘compatibility’ warning message about the APK not being compatible with the latest version of Android. | ✓ | ✓ | ✓ | C3-6470 |
Foodiverse Web App | For offers accepted on the Foodboard in the Slovakian market ONLY, some donations that were accepted by charities were being duplicated in the ‘offers history’. This has now been resolved. | ✓ | ✓ | C3-6489 | |
Foodiverse Web App | Web app users will no longer experience changes in donation times after entering daylight savings. | ✓ | ✓ | ✓ | C3-6494 |
Foodiverse Web App | When web app users update their address, the geo coordinates now automatically regenerate to reflect the new address. | ✓ | ✓ | ✓ | C3-6616 |
Foodiverse Web App | There were instances of incorrect Km distances calculated between Donor branches and their Donations offered to Charities on the Foodboard. This has been fixed so that now the correct distances are calculated and Offers are presented depending on the geofilter distance selected by the Charity. | ✓ | ✓ | ✓ | C3-6641 |
Foodiverse Web App | 3PC users can no longer accept offers for themselves on the FV web app without needing to assign a charity. This is the expected functionality | ✓ | ✓ | ✓ | C3-6687 |
Mobile Apps | There was an issue on the flutter mobile app where the Donor Posted At time was being replaced with the Charity accepted at time. This has been fixed and the times displayed on the donation details page are correct. | ✓ | ✓ | ✓ | C3-6694 |
Mobile Apps | Charity users on the mobile app will now see the correct offer type for transferred Foodboard offers in their recent offers. | ✓ | ✓ | C3-6751 | |
Mobile Apps | Charity mobile app users can now successfully cancel out of the E-sign process without any issues. | ✓ | C3-6752 | ||
Notifications | Slovakian Foodbank admins using the Managed Closed Dates feature will now see the Temporary Closure email working as intended. | ✓ | C3-6761 | ||
Foodiverse Web App | Charity users on the Foodboard will now see the Foodboard counter update correctly after refreshing when using a non-MRT account. | ✓ | ✓ | C3-6773 | |
Foodiverse Web App | Foodbanks and charities using the Foodboard can now scroll up and down the list smoothly. | ✓ | ✓ | C3-6789 | |
Mobile Apps | App users can now load any image without issues. | ✓ | ✓ | ✓ | C3-6790 |
Foodiverse Web App | Foodbanks and charities using the app can now access the Foodboard page without encountering any issues. | ✓ | ✓ | C3-6791 | |
Foodiverse Web App | Donors making donations will no longer see duplicates when checking the donation details page. | ✓ | ✓ | C3-6942 | |
Foodiverse Web App | There was an issue discovered on the Donation Details of previous historic donations where the food items donated were displaying as their Food Classification labels. This has been fixed so that now users can revert back to previous donations and view the correct Food Category labels. | ✓ | ✓ | C3-6947 | |
Mobile Apps | We have improved the Geofilter and Foodboard Counter on the Charity dashboard so that now the count of foodboard offers will update when users change branch and radius in the geofilter settings. When they return to the dashboard and press reload, the count will update based on what was selected in the Geofilter settings. | ✓ | ✓ | C3-6462 | |
Mobile Apps | The donation record on Flutter Web has been improved, allowing the table UI to be used effectively for PLD Visibility. | ✓ | ✓ | ✓ | C3-6472 |
Backend/APIs | Donor organizations can now configure the autoselect behavior at a donor branch level, specifically for TW’s. | ✓ | ✓ | C3-6488 | |
Foodiverse Web App | The functionalities on the View Member Schedules page have been updated to match those on the Manage Network Members page. | ✓ | ✓ | C3-6578 | |
Foodiverse Web App | The registration form on FV Beta for new organizations onboarding from Kenya now includes the correct region, county, and ward details when Kenya is selected. | ✓ | ✓ | ✓ | C3-6606 |
Mobile Apps | We have made an improvement to the Donation Wizard on the mobile app. If Donors select to post a donation in the same Donation Window that they have already posted in – now they will not see conflicting warning messages. | ✓ | ✓ | C3-6645 | |
Mobile Apps | We have improved a grammatical error on the web app that was displayed on the pop up for marking donations transferred. | ✓ | ✓ | C3-6652 | |
Foodiverse Web App | FV organizations from Kenya can now choose the correct form dropdowns when editing their organization address in Org settings on FV Beta. | ✓ | ✓ | ✓ | C3-6673 |
Foodiverse Web App | FV organizations from Kenya can now choose the correct form dropdowns when editing or adding branches in branch settings on FV Beta. | ✓ | ✓ | ✓ | C3-6674 |
Foodiverse Web App | The interdependency between pagination and search functionality on the My FoodBank Network → View Member Schedules page has been improved. | ✓ | ✓ | ✓ | C3-6686 |
Reporting | We have fixed a small issue relating to downloadable reports for the Charity KPI Report. There was a incorrectly named column heading which has now been improved. | ✓ | ✓ | C3-6716 | |
Foodiverse Web App | User Personas used for EU markets have been improved to better represent our International Market customers, as requested by the UX designer. | ✓ | ✓ | ✓ | C3-6725 |
Foodiverse Web App | Donors can no longer add a charity branch that has been marked temporarily closed to a Custom Transfer Window when creating a donation. | ✓ | ✓ | C3-6727 | |
Mobile Apps | We have made an improvement to the Dashboard donation details screen and the Donations History screen for Delegated Collector users. These users need to be able to see both the Donor and Charity addresses in order to collect and deliver food donations. This has been added to the relevant donation details screens for the 3PC user. | ✓ | C3-6750 | ||
Foodiverse Web App | Food net admins & member managers can now temporarily substitute a primary charity where the original primary charity is going to be temporarily closed. This can be done in the manage member schedules section of the app by inviting a substitute primary charity for the period of time that the original primary charity will be temporarily closed. Please note that the food net admin or member manager will also need to invite the original primary charity back to the slot for the day that they are due to reopen. | ✓ | C3-6758 | ||
Mobile Apps | Charity Org Admins now have the ability to temporarily mark a charity branch as ‘closed’ for a set period of time in the mobile app. As a result, if a charity is unavailable to collect food for a set period, this can be reflected in the Foodiverse system. This has three main benefits:If the charity is temporarily closed/unavailable, they won’t receive donation offers. In fact, if they are scheduled as a primary collector, the new donation will be offered straight away to the waitlist and foodboard. If the charity is temporarily closed/unavailable, their response compliance will not be negatively impacted. The charity will be automatically marked as ‘open’ again once the set period has passed so that charities no longer have to request food net admins to pause their membership | ✓ | ✓ | C3-6776 | |
Foodiverse Web App | Charity branches that are temporarily closed can now accept future invitations that apply to the days they are currently marked as closed. This ensures that when the branch re-opens, the schedule will already be accepted and in place. | ✓ | ✓ | C3-6788 | |
Foodiverse Web App | We have made an improvement to the collection window invitations. Before, when a notification to accept an invitation appeared on the dashboard, the user would be brought to their schedule page and would need to click on the orange status before being able to accept/reject the invitation. Now, the pop-up modal will automatically appear after the schedule page has loaded, saving users the need to click the orange status. | ✓ | ✓ | ✓ | C3-6800 |
Mobile Apps | Charity organization admins using the mobile app can now view upcoming closures up to four months in advance, highlighted in purple | ✓ | ✓ | C3-6803 | |
Foodiverse Web App | As a part of Splitting Donations, we have made an improvement to the Donation Category Table on the web app that displays to Donors and Foodbanks. Now when a donation is split between Charities, the Donor and Foodbank can see a clear breakdown of what the quantity of split items were, which categories and which charities accepted the food. This is where the Brach impact for Donor and Charity reporting is sent from. | ✓ | ✓ | C3-6804 | |
Mobile Apps | As a part of Splitting Donations, we have made an improvement to the Donation Category Table on the mobile application that displays to Donors and Foodbanks. Now when a donation is split between Charities, the Donor and Foodbank can see a clear breakdown of what the quantity of split items were, which categories and which charities accepted the food. | ✓ | ✓ | C3-6814 | |
Foodiverse Web App | The issue where the “Done” button was impeding on the calendar space in the temporary calendar pop-up within Angular has been fixed. | ✓ | ✓ | ✓ | C3-6820 |
Foodiverse Web App | The incorrect word for Sunday on schedules for Slovakian users has been corrected from “sinko” to “Nedeľa.” | ✓ | ✓ | ✓ | C3-6825 |
Foodiverse Web App | Food net admins and users can now see red calendar icons on the Mon-Sun days that a donor is closed in the Manage Network Members > Dropdown schedule, allowing for quick identification of temporary closures. | ✓ | C3-6830 | ||
Devops | Foodnet admins can now invite only two charities as Primary using the ‘primary charity slot invitation’ function, enabling the temporary assignment of a ‘substitute’ primary and the original primary. | ✓ | C3-6837 | ||
Notifications | We have improved the Donor’s Collection Window pop up where Food Bank Admins can edit or add new Collection Windows for Charities on the Donor’s Schedule. Previously the maximum number if recipients could be set to 5. We have increased this to 10 for the purposes of splitting donations to multiple recipients. | ✓ | ✓ | C3-6906 | |
Mobile Apps | We have added a hyperlink to the knowledge hub on the email that food bank coordinators receive when they are made aware of a charity temporary closure. The URL is https://foodiverse.scrollhelp.site/foodiverse/ | ✓ | C3-6912 | ||
Foodiverse Web App | We have updated the mobile message that appears to charities when they delete an upcoming temporary closure. | ✓ | C3-6913 | ||
Foodiverse Web App | N/A | C3-6983 | |||
Devops | The Auto-Split feature flag has been applied to all Front End occurrences of Auto-Split features, ensuring consistency across the application. | ✓ | ✓ | ✓ | C3-7032 |
Mobile Apps | Indonesian translation feedback has been added to the Angular and Flutter apps, providing Foodiverse with the correct context for translations. | ✓ | ✓ | ✓ | C3-6418 |
Mobile Apps | The front-end push notifications setting has been feature flagged for all users on the Flutter app. | ✓ | ✓ | ✓ | C3-6478 |
Mobile Apps | Charity users on the Flutter app now have a setting that opens their device notification settings, allowing them to enable push notifications from Foodiverse. | ✓ | C3-6479 | ||
Mobile Apps | Donor users on the Flutter app now have a setting that opens their device notification settings, enabling them to receive push notifications from Foodiverse. | ✓ | C3-6480 | ||
Mobile Apps | Foodbank users on the Flutter app now have a setting that opens their device notification settings, enabling them to receive push notifications from Foodiverse. | ✓ | C3-6481 | ||
Foodiverse Web App | The Vue component that allows food net admins to mark a charity as temporarily closed in ‘Manage Members’ has been successfully embedded in the Angular web app. | ✓ | C3-6544 | ||
Mobile Apps | Charity users on the mobile app can now see that their charity branch is temporarily closed on the schedule page, providing a quick reminder of temporary closures that might affect their volunteers, drivers, or collectors for the week. | ✓ | C3-6565 | ||
Foodiverse Web App | Food Net Admins now have the ability to temporarily mark a charity member as ‘closed’ for a set period of time so that, if a charity is unavailable to collect food for a set period, this can be reflected in the system. This has three main benefits: If the charity is temporarily closed/unavailable, they won’t receive donation offers. In fact, if they are scheduled as a primary collector, the new donation will be offered straight away to the waitlist and foodboard. If the charity is temporarily closed/unavailable, their response compliance will not be negatively impacted. The charity will be automatically marked as ‘open’ again once the set period has passed so that food net admins do not need to remember to ‘unpause’ the memberships as they need to currently. | ✓ | C3-6571 | ||
Mobile Apps | Charity Org Admins now have the ability to temporarily mark a charity branch as ‘closed’ for a set period of time in the mobile app. As a result, if a charity is unavailable to collect food for a set period, this can be reflected in the Foodiverse system. This has three main benefits: If the charity is temporarily closed/unavailable, they won’t receive donation offers. In fact, if they are scheduled as a primary collector, the new donation will be offered straight away to the waitlist and foodboard. If the charity is temporarily closed/unavailable, their response compliance will not be negatively impacted. The charity will be automatically marked as ‘open’ again once the set period has passed so that charities no longer have to request food net admins to pause their membership | ✓ | C3-6573 | ||
Foodiverse Web App | An automated feature test has been built to verify the ability to temporarily close charities via the Angular -> Vue component. | ✓ | C3-6583 | ||
Mobile Apps | An automated feature test has been built to ensure the ability to temporarily close charities on the Flutter app is functioning correctly. | ✓ | C3-6584 | ||
Foodiverse Web App | An automated feature test has been created to test the effective schedule logic when a temporary charity closure is in place. | ✓ | C3-6585 | ||
Notifications | An automated feature test has been developed to check that an email is sent to both the charity organization admin and the food net organization admin when a temporary closure has been assigned to a charity branch. | ✓ | C3-6586 | ||
Foodiverse Web App | An automated test has been built to verify the ability to substitute a primary charity during a ‘temp closure’ using the invitation feature. | ✓ | C3-6598 | ||
Reporting | Food bank and donor organization admins can now view and edit the ‘Donor KPI Summary’ report page in Vue.JS. | ✓ | ✓ | C3-6633 | |
Foodiverse Web App | In the Foodiverse web app, Food bank coordinators can now quickly see if a charity member has a temporary closure planned for the present week. It will be highlighted by a red calendar icon and can be viewed by navigating to ‘Manage Network Members’ > Searching for the Charity schedule you wish to view > Clicking on the dropdown beside the charity’s name to view their schedule for the week | ✓ | ✓ | C3-6701 | |
Foodiverse Web App | Not Applicable | ✓ | C3-6702 | ||
Mobile Apps | Charity admins and branch users using the mobile app can now view past temporary closures up to 12 months ago in the Schedules > Manage Closed Dates > Calendar view, allowing for a quick reminder of closures that occurred in the past. | ✓ | C3-6704 | ||
Backend/APIs | The schedule endpoint payload has been extended to ensure that Tesco’s integration won’t be affected by the planned improvements. | ✓ | C3-6708 | ||
Foodiverse Web App | The changes made to the temporary calendar pop-up have been successfully embedded into Angular. | ✓ | C3-6709 | ||
Foodiverse Web App | Foodbanks using the Angular app now receive a pending action on their web app dashboard when a donation is quarantined, which directs them to the Flutter mobile app to split the donation. | ✓ | C3-6722 | ||
Mobile Apps | Foodbanks using the Flutter app now receive a new pending action on their mobile dashboard when a donation is quarantined, allowing them to Split, Release, or Decline the donation. | ✓ | C3-6723 | ||
Notifications | Foodbanks using the Flutter app now receive a push notification when a donation is quarantined, directing them to their Flutter dashboard. | ✓ | C3-6724 | ||
Mobile Apps | The Flutter UI front end has been built as the foundation for the manual splitting workflow. | ✓ | ✓ | C3-6731 | |
Mobile Apps | Foodiverse has a new feature on the mobile application for Food Net Administrators! Now admins will be able to split a large donation between charities on the Donor schedule if the Donation exceeds the Food Net threshold setting. This is a early iteration of a new feature and will only be available to certain trial customers. | ✓ | ✓ | C3-6732 | |
Backend/APIs | ✓ | C3-6733 | |||
Mobile Apps | We have added a new section on the mobile app that will only display to Foodnet admins when there is a Large Donation Holding for them to action. Donor, Charity and 3PC branch users will not see this new section since it is for administrative tasks only to be completed by a Foodnet administrator. | ✓ | C3-6737 | ||
Devops | A backend feature flag has been created for the splitting donations feature, allowing developers to enable or disable the manual Splitting Donations feature across different Foodiverse environments. | ✓ | C3-6738 | ||
Foodiverse Web App | Not Applicable | ✓ | ✓ | C3-6744 | |
Mobile Apps | We have improved the mobile application to have up to date and contextual Indonesian language translations for Indonesian speaking users on Foodiverse. | ✓ | ✓ | ✓ | C3-6748 |
Foodiverse Web App | When a donation is quarantined, Foodbanks using the Angular app now receive a pending action on their web app dashboard that directs them to the Flutter mobile app to split the donation. | ✓ | ✓ | ✓ | C3-6753 |
Mobile Apps | We have added an improvement to the way that Foodbank admins can split a donation manually using the mobile app. Now admins can tap on a button that splits the donation categories evenly between the charities. | ✓ | C3-6763 | ||
Foodiverse Web App | An automated feature test has been built to verify the dashboard pending action that appears when a large donation is quarantined on the Angular web app. | ✓ | C3-6784 | ||
Mobile Apps | An automated feature test has been created for quarantined large donations on the Flutter mobile app. | ✓ | C3-6785 | ||
Mobile Apps | An automated feature test has been developed to test the manual splitting of a donation on the Flutter app and the submission of the split offers to Foodiverse. | ✓ | C3-6786 | ||
Mobile Apps | A key part to delivering a new feature to enable Foodbank admins to Split Donations on Foodiverse required a new change to be made to how a single donation can be split by food category and food classification into multiple new offers and offered to several charities while preserving how Charities can Accept/Decline offers and Donors can mark donations Transferred. This task was to build and apply the mechanism to the Foodbank Admins action to split a donation. | ✓ | ✓ | C3-6809 | |
Foodiverse Web App | We have added increased visibility to split donations and offers for all Foodiverse users on the web application and on the mobile application. Now whenever a donation has been split into smaller parts and offered to multiple charities – the Foodbank users, Donors and Charities will be able to see that their donation or offer was “Split“. | ✓ | ✓ | C3-6810 | |
Reporting | An automated feature test has been built to verify that the Donations History Food category tables update as expected when split offers are marked as transferred on the backend. | ✓ | ✓ | ✓ | C3-6817 |
Mobile Apps | An automated feature test has been developed to ensure that the Donations History Food category tables update correctly when split offers are marked as transferred on the Flutter app. | ✓ | ✓ | C3-6818 | |
Backend/APIs | A backend feature flag has been created for the charity branch capacity setting, allowing developers to enable or disable the automated Split Donations feature on Foodiverse environments. | ✓ | C3-6852 | ||
Backend/APIs | Foodbanks can have their recipient member’s Total Max. Capacity saved in the Foodviverse database for the purposes of auto-split donations. | ✓ | ✓ | C3-6857 | |
Backend/APIs | An endpoint has been created that allows for the splitting of large donations into new offers, enabling multiple offers to be sent to multiple charities. | ✓ | ✓ | C3-6858 | |
Devops | A backend feature flag has been added for the temporary calendar feature, allowing developers to enable or disable this feature on Foodiverse environments. | ✓ | C3-6877 | ||
Backend/APIs | We have added an info tooltip to explain how auto-split donations are based on the priority order in which Charity recipient branches are added to the Transfer Window on a Donor schedule. This only applies to auto-split donations. | ✓ | ✓ | C3-6901 | |
Backend/APIs | A new endpoint has been created that returns the defined Schedule information, providing developers with the necessary data to manage and interact with schedules efficiently. | ✓ | ✓ | ✓ | C3-6907 |
Backend/APIs | Large Donations that breach the Food Net threshold will be held until either the Food Bank Admin splits, releases or declines the donation – Or until the Accept By Time has been reached. Once the accept by time has passed, the donation will be cancelled and can be seen in Donations History. | ✓ | ✓ | ✓ | C3-6911 |
Backend/APIs | The query for the schedule report endpoint that returns the defined Schedule information has been optimized to prevent timeouts, ensuring faster and more reliable performance. | ✓ | ✓ | ✓ | C3-7013 |
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | ✓ | ✓ | C3-6881 |
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6882 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6884 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6885 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6886 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6887 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6888 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6889 | ||
Reporting | In order to ensure that Split donations are reported correctly with accuracy on FV, we have doubled down on the testing of FV so that any issues are reported prior to feature release. | ✓ | C3-6890 | ||
Mobile Apps | An investigation has been conducted into how Flutter interacts with the native features of device notification settings across different operating systems. | ✓ | ✓ | ✓ | C3-6477 |
Notifications | The most cost-efficient phone number for sending SMS notifications to Kenya has been verified for configuring SMS donation notifications. | ✓ | ✓ | ✓ | C3-6664 |
17 July 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.2.5 | No changes required |
Web app | 3.2.5 | No changes required |
Mobile iOS app (Beta) | 3.2.7 | Automatic update |
Mobile Android app (Beta) | 3.2.7 | Automatic update |
Middleware | 3.2.5 | No changes required |
APIs and Integrations | 3.2.5 | No changes required |
Category | Foodiverse Update | Charity | Donor | Foodbank | Reference |
Mobile App | Mobile users of Foodiverse (FV) on Android devices will no longer receive ‘compatibility’ warning messages indicating that the app is not compatible with the latest version of Android. | ✓ | ✓ | ✓ | C3-6470 |
Mobile App | Foodbank and charity users can now access the Foodboard page without any issues. | ✓ | ✓ | C3-6791 | |
Mobile App | App users can now load any image without problems. | ✓ | ✓ | ✓ | C3-6790 |
Mobile App | Donor users on the Flutter app will no longer see the ‘posting time’ on the live donation page change to the <accepted at> time when a charity accepts the offer. | ✓ | C3-6694 | ||
Mobile App | The feature flag has been enabled for the mobile app. | ✓ | ✓ | ✓ | C3-6719 |
Mobile App/Foodiverse | We have made an improvement to the Donation Wizard on the mobile app. If Donors select to post a donation in the same Donation Window that they have already posted in – now they will not see conflicting warning messages. | ✓ | C3-6645 | ||
Mobile App/Foodiverse Web App | There were instances of incorrect Km distances calculated between Donor branches and their Donations offered to Charities on the Foodboard. This has been fixed so that now the correct distances are calculated and Offers are presented depending on the geofilter distance selected by the Charity. | ✓ | ✓ | C3-6641 | |
Mobile App/Foodiverse Web App | The donation record on Flutter Web has been improved, allowing the table UI to be used for PLD Visibility. | ✓ | ✓ | ✓ | C3-6472 |
Mobile App/Foodiverse Web App | We have improved the Geofilter and Foodboard Counter on the Charity dashboard so that now the count of foodboard offers will update when users change branch and radius in the geofilter settings. When they return to the dashboard and press reload, the count will update based on what was selected in the Geofilter settings. | ✓ | C3-6462 C3-6773 | ||
Mobile App/Foodiverse Web App | 3PC users can now accept an offer for themselves when logging into the Foodiverse (FV) web app without needing to assign a charity. | ✓ | C3-6687 | ||
Mobile App/Foodiverse Web App | Foodboard Charity users will no longer see duplicate quantities offered/accepted in ‘Offers History’ when a donation is accepted via the Foodboard. | ✓ | C3-6489 | ||
Mobile Apps (BETA release only) | Charity Org Admins now have the ability to temporarily mark a charity branch as ‘closed’ for a set period of time in the mobile app. As a result, if a charity is unavailable to collect food for a set period, this can be reflected in the Foodiverse system. This has three main benefits: 1. If the charity is temporarily closed/unavailable, they won’t receive donation offers. In fact, if they are scheduled as a primary collector, the new donation will be offered straight away to the waitlist and foodboard. 2. If the charity is temporarily closed/unavailable, their response compliance will not be negatively impacted. 3. The charity will be automatically marked as ‘open’ again once the set period has passed so that charities no longer have to request food net admins to pause their membership | ✓ | C3-6573 | ||
Mobile Apps (BETA release only) | Food Net Admins now have the ability to temporarily mark a charity member as ‘closed’ for a set period of time so that, if a charity is unavailable to collect food for a set period, this can be reflected in the system. This has three main benefits: 1. If the charity is temporarily closed/unavailable, they won’t receive donation offers. In fact, if they are scheduled as a primary collector, the new donation will be offered straight away to the waitlist and foodboard. 2. If the charity is temporarily closed/unavailable, their response compliance will not be negatively impacted. 3. The charity will be automatically marked as ‘open’ again once the set period has passed so that food net admins do not need to remember to ‘unpause’ the memberships as they need to currently. | ✓ | C3-6571 | ||
Mobile Apps (BETA release only) | Charity org admins using the mobile app can now mark a charity branch temporarily closed for set dates in the future using a date range picker. | ✓ | C3-6776 | ||
Mobile Apps | 3PC branch users on the Flutter App can now see both the donor and charity branch addresses after assigning and accepting a donation to a charity. | ✓ | ✓ | C3-6750 | |
Mobile Apps | The ‘PLDVisible’ feature flag label has been applied to every location on the Flutter app where the ‘View Products’ buttons are located. | ✓ | ✓ | ✓ | C3-6735 |
Mobile Apps | The Indonesian Translations Feedback has been added to the Flutter apps to ensure Foodiverse has the correct context for translations. | ✓ | ✓ | ✓ | C3-6748 |
Mobile Apps (BETA release only) | An automated feature test for the ability to close charities temporarily on the Flutter app has been built. | ✓ | C3-6584 | ||
Mobile Apps | The Indonesian Translations Feedback has been added to both the Angular and Flutter apps to ensure Foodiverse has the correct context for translations. | ✓ | C3-6418 | ||
Mobile Apps/Notifications | We have added a setting to the Foodiverse mobile app so that now users can enable important push notification updates on their mobile devices that are received from Foodiverse. | ✓ | C3-6481 C3-6480 C3-6479 | ||
Mobile Apps/Notifications | The front end push notification settings on Flutter have been feature flagged for all users. | ✓ | ✓ | ✓ | C3-6478 |
05 June 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.2.5 | Automatic update |
Web app | 3.2.5 | Automatic update |
Mobile iOS app | 3.2.5 | Automatic update |
Mobile Android app | 3.2.5 | Automatic update |
Middleware | 3.2.5 | No changes required |
APIs and Integrations | 3.2.5 | No changes required |
Category | Foodiverse Update | Charity | Donor | Foodbank | Reference |
Bug Fix | There was an issue where a small number of Primary Charities weren’t receiving their offers. Now this is fixed and these Charities receive offers as expected. | ✓ | C3-6075 | ||
Backend/APIs | Audit logs have been created for the Networks_categories table, allowing FoodNet Admins to track changes to the CO2e/meals calculations. | ✓ | C3-4442 | ||
Backend/APIs | The SQL equivalent for the GPS precalc backfilling task has been implemented. | ✓ | ✓ | C3-6341 | |
Backend/APIs | Rate limiting has been applied to the PDF generation endpoint. | ✓ | ✓ | ✓ | C3-5133 |
Backend/APIs | A TST command has been created to automate the backfilling of donations for the IE data backfilling process. | ✓ | ✓ | ✓ | C3-6012 |
Backend/APIs | An automated end-to-end feature test for scheduling a Third Party Collector has been created an runs successfully. | ✓ | ✓ | C3-6419 | |
Backend/APIs | An automated feature test for the delegated collector donation process has been created. | ✓ | ✓ | C3-6420 | |
Foodiverse Web App | We have fixed an issue where Foodnet admins were able to see Donation data that related to members of their Foodnet that were not in an active state at the time. | ✓ | C3-5498 | ||
Foodiverse Web App | For Foodiverse users navigating the Offers History and Donations pages, the system now displays a warning if the selected date range exceeds 90 days. | ✓ | ✓ | ✓ | C3-6605 |
Foodiverse Web App | Translations for Featured/Other FoodNets have been added. | ✓ | ✓ | ✓ | C3-4976 |
Foodiverse Web App | Missing CZ, SK, and IN translations on the Offers History, Donations, and Reports pages for all users have been improved. | ✓ | ✓ | ✓ | C3-6458 |
Foodiverse Web App | Missing CZ and IN translations in the user view dropdown have been improved. | ✓ | ✓ | ✓ | C3-6532 |
Foodiverse Web App | Feature flagging on the Vue migration project has been improved, allowing ready-migrated pages to be released in production. | ✓ | ✓ | ✓ | C3-6576 |
Foodiverse Web App | The ‘Edit Branches’ component has been converted from Angular to Vue.js. | ✓ | ✓ | ✓ | C3-5909 |
Foodiverse Web App | The ‘View Users’ component has been converted from Angular to Vue.js. | ✓ | ✓ | ✓ | C3-5920 |
Foodiverse Web App | The ‘Add New User’ and ‘Edit User’ components have been converted from Angular to Vue.js. | ✓ | ✓ | ✓ | C3-5926 |
Foodiverse Web App | The Angular version of the viewable and filterable ‘Donor Impact Summary’ has been replaced with the Vue.JS component. | ✓ | C3-6003 | ||
Foodiverse Web App | We have a new feature where third parties (e.g. volunteers or delivery drivers) can be scheduled to collect food on behalf of charities by food bank coordinators. | ✓ | ✓ | C3-6347 | |
Foodiverse Web App | Food net admins must select the 3PC transfer window type in order for a delegated collector schedule to be created. Therefore, they won’t be able to assign a 3PC branch to a standard primary or waitlist schedule for ‘Collection’ or ‘Delivery’ windows at this time. | ✓ | C3-6378 | ||
Foodiverse Web App | To ensure that Charities have visibility of donations that were accepted by a Third Party Collector on their behalf; we have added a new section to the Charity dashboard called “Awaiting Delivery“ with the details of the donation and who is delivering it so that Foodiverse helps to manage the Charities expectations. | ✓ | ✓ | C3-6385 | |
Foodiverse Web App | We have made an improvement to the Collection Window scheduling pop up modal so that now Donor and Charity Food Classifications will be displayed in order to assist the Foodbank Admin during the scheduling process. Food bank coordinators can now make better informed decisions when scheduling charity branches to donors. | ✓ | C3-6390 | ||
Foodiverse Web App | Food Net admins can now temporarily close charity members via a pop-up modal in the ‘Manage Members’ section of the Vue app. | ✓ | C3-6543 | ||
Foodiverse Web App | A fix for the caching of Vue components in Angular has been implemented. | ✓ | ✓ | ✓ | C3-6662 |
Mobile Apps | In the Flutter app, charities will now see a notice if another charity has already accepted the offer, preventing errors. | ✓ | C3-6350 | ||
Mobile Apps | Engineers have fixed an issue on the Foodboard for Charities using the mobile application. Some Charities were not able to see offers that they should be able to see. This is now fixed and the Foodboard functions as expected on the mobile app. | ✓ | C3-6473 | ||
Mobile Apps | For charity users on the Flutter App, the number displayed on the foodboard offers counter now updates in real time with each page reload, without needing to sign out and back in. | ✓ | ✓ | ✓ | C3-6600 |
Mobile Apps | On the Flutter App, charity users can now view their completed donation records without encountering any grey screens. | ✓ | ✓ | ✓ | C3-6611 |
Mobile Apps | This was a Bugfix on the Donation Details of offers in the Recent Offers section for Charities. When users tapped on the “View Products“ button they were presented with a grey screen. This is now fixed and users can see the Product Level Detail of offers on the mobile app in Recent Offers. | ✓ | ✓ | ✓ | C3-6653 |
Mobile Apps | 3PC charities now only see one card when they accept a donation. | ✓ | ✓ | ✓ | C3-6670 |
Mobile Apps | 3PC Flutter app users no longer see duplicate cards or long grey screens when accepting an offer without assigning a recipient charity. | ✓ | ✓ | ✓ | C3-6672 |
Mobile Apps | Donor users/admins on the Flutter app now see the blue notification ‘we are waiting for a charity to accept your donation’ at the correct location on the Live donation page. | ✓ | ✓ | C3-6679 | |
Mobile Apps | The Donation Details screen in the Flutter app now includes all the missing data points that were available on the Angular web app. | ✓ | C3-6106 | ||
Mobile Apps | Indonesian users on the Flutter app can now see the days of the week fully translated on the schedule pages, with shorter versions used when necessary. | ✓ | ✓ | ✓ | C3-6514 |
Mobile Apps | SK, IN, and CZ users on the Flutter mobile app now see their selected translations on the Live Donation page. | ✓ | ✓ | ✓ | C3-6541 |
Mobile Apps | The Live Donation Details screen in the Flutter app now includes all the missing data points that were available on the Angular web app. | ✓ | ✓ | ✓ | C3-6603 |
Mobile Apps | 3PC users now see the donation transfer type when they accept a donation from a donor. | ✓ | ✓ | C3-6669 | |
Mobile Apps | The backend functionality has been built to allow 3PC branch users to see offers on their mobile dashboard and assign a charity to them before accepting the donation. | ✓ | ✓ | C3-6371 | |
Mobile Apps | Third Party Collectors will see an appropriate error message if they try to accept a donation that has already been accepted or rejected by another associated user of the branch. | ✓ | ✓ | C3-6382 | |
Mobile Apps | To ensure that Donors have visibility of donations that were accepted by a Third Party Collector on behalf of the charity on the schedule; we have added updated offer card dashboard with the details of the donation and a contact number so that the charity can contact the Volunteer delivering if required. | ✓ | ✓ | ✓ | C3-6386 |
Mobile Apps | In order to ensure that Donors & Foodbanks have visibility of who has accepted a donation offer in their Donations History on the mobile app – we have added an “Accepted by“ data point to the Donations History which the donor will see when they tap on the Donations History card. This means that Donors will have a visible record that their donation was accepted by a Third Party Collector or a Charity and that the Donation went to the Primary Charity that the offer was accepted for. | ✓ | ✓ | C3-6391 | |
Mobile Apps | In order to ensure that Charities have visibility of who has accepted a donation offer in their Recent Offers History on the mobile app – we have added an “Accepted by“ data point to the offer details in Recent Offers History that the Charity will see when they tap on the related offer card. This means that Charities will have a visible record that their donation was accepted by a Third Party Collector or that the they the Charity branch accepted the Donation themselves. | ✓ | C3-6392 | ||
Mobile Apps | The PLD visibility “View Products” button for all donations on the Flutter app is now feature-flagged for all users. | ✓ | ✓ | ✓ | C3-6449 |
Mobile Apps | We have made an improvement to the Product Detail that Charities and Foodbanks can see in their Recent Offers on the mobile application. Now users can see a full breakdown of what was offered in donations that have been transferred or not transferred. | ✓ | ✓ | C3-6450 | |
Mobile Apps | We have made an improvement to the Product Details that Charities and Foodbanks can see on a Donation that they have been offered on the mobile application. This allows Charities to see the details of the food they have been offered before they decide to Accept or Reject a donation. | ✓ | ✓ | C3-6452 | |
Mobile Apps | We have made an improvement to the Product Details that Donors and Foodbanks can see on a Donation that they have posted using the mobile application. This allows them to see the details of the food they have just posted when it has been accepted before marking it transferred. | ✓ | ✓ | C3-6456 | |
Mobile Apps | We have made an improvement to the Product Detail that Donors and Foodbanks can see in their Donations History on the mobile application. Now users can see a full breakdown of what food was donated in historical donations. | ✓ | ✓ | C3-6457 | |
Mobile Apps | The back-end functionality has been implemented to mark organization branches as temporarily closed, enabling Flutter developers to implement this feature in the Flutter app. | ✓ | ✓ | ✓ | C3-6545 |
Mobile Apps | It is now possible for specific Foodbank Volunteer users to Accept donations on behalf of a charity (or charities) in order so that the Foodbank Volunteer user can accept, collect and deliver a donation directly to a charity branch. | ✓ | ✓ | C3-6562 | |
Mobile Apps | It is now possible for specific Foodbank Volunteer users to Accept donations on behalf of a charity (or charities) in order so that the Foodbank Volunteer user can accept, collect and deliver a donation directly to a charity branch. | ✓ | ✓ | C3-6604 | |
Mobile Apps | 3PC branch users are not able to interact with waitlist or foodboard offers at this stage of the project. Additionally, 3PC branches cannot see historical donations. | ✓ | ✓ | ✓ | C3-6627 |
Notifications | Donors receiving push notifications after a charity accepts their donation are no longer brought to a blank grey screen when they click on it. | ✓ | C3-6680 | ||
Notifications | As a part of the new Delegated Collector improvements, if there are no Charity branches on the Third Party Collector’s schedule then they will see an informative message suggesting to get in touch with the Foodbank admin to assign some Charity branches to the schedule. | ✓ | ✓ | C3-6380 | |
Notifications | If a charity branch has been marked temporarily closed by a charity user or a food net admin, the food net admin will be made aware via email. | ✓ | ✓ | C3-6560 | |
Notifications | If a charity branch has been marked temporarily closed by a charity user or a food net admin, the charity org admin will be made aware via email | ✓ | C3-6561 | ||
Reporting | When FoodNet Admins download a week’s historic Donor KPI report, it now correctly shows the Scheduled Donation Window details. | ✓ | C3-6107 | ||
Reporting | Food bank and donor org admins can now view and filter the ‘Donor Impact Summary’ report page in Vue.JS. | ✓ | ✓ | C3-5896 | |
Reporting | Food bank and donor org admins can now view and edit the ‘Donor Impact Details’ report page in Vue.JS. | ✓ | ✓ | C3-5897 | |
Reporting | Food bank and charity org admins can now view and edit the ‘Charity Impact Details’ report page in Vue.JS (Part One). | ✓ | ✓ | C3-5898 | |
Reporting | Food bank and donor org admins can now view and edit the ‘Donor KPI Summary’ report page in Vue.JS. | ✓ | ✓ | C3-5902 | |
Reporting | In order to ensure that Donors and Foodbanks have visibility of who has accepted a donation offer, we have added an “Accepted by“ data point to the Donation History. This means that both Donor and Foodbank admin know that a donation was accepted by a Third Party and the Donation went to a Primary Charity that was on the schedule. | ✓ | ✓ | C3-6387 | |
Reporting | In order to ensure that Charities and Foodbanks have visibility of who has accepted a donation offer, in addition to Donor visibility – we have added an “Accepted by“ data point to the Offers History on the web app. This means that both Charities and Foodbank admins know that a donation was accepted by a Third Party and the Donation went to the Primary Charity that the offer was accepted for. | ✓ | ✓ | C3-6388 | |
Reporting | In order to ensure that Charities have reporting visibility with Third Party Assigned donations we have updated the Charity KPI report so that the report will include Third Party Collected donations in the Total Donations, KGs, Co2 and meals equivalent. Charities will also see the number of Third Party Collected donations that were marked transferred in the table breakdown of the KPI report. | ✓ | C3-6397 | ||
Reporting | In order to ensure that Foodbanks have oversight reporting visibility with Third Party Assigned donations we have updated the Foodbank Charity KPI report so that the report will include Third Party Collected donations. | ✓ | C3-6413 |
24 April 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.2.2 | Automatic update |
Web app | 3.2.2 | Automatic update |
Mobile iOS app | 3.2.2 | Automatic update |
Mobile Android app | 3.2.2 | Automatic update |
Middleware | 3.2.2 | No changes required |
APIs and Integrations | 3.2.2 | No changes required |
Category | Foodiverse Update | Charity | Donor | Foodbank | Reference |
Backend/API | Donors using our APIs will no longer receive a 200 HTTP response when sending cPLD to Foodiverse with invalid weight data; instead, they will receive an accurate failure error message. | ✓ | C3-5424 | ||
Backend/API | The auto-select API logic now supports passing the branch_official_id, enhancing functionality and ensuring the use of accurate branch identification. | ✓ | ✓ | ✓ | C3-6286 |
Backend/API | The issue causing blank pages when handling branches without categories during donation creation has been resolved, providing a more seamless user experience. | ✓ | ✓ | ✓ | C3-6310 |
Backend/API | The issue causing incorrect display of product quantities on the Donate page during donation creation has been resolved, ensuring accurate representation. | ✓ | C3-6322 | ||
Backend/API | The geo-filter feature’s back-end distance calculation has been optimised, making it easier to locate nearby resources. | ✓ | ✓ | ✓ | C3-6336 |
Backend/API | Donor organizations now have control over how donations are allocated from their branches, enhancing customization options. | ✓ | C3-6401 | ||
DevOps | An automated feature test for the VIP Window has been successfully developed, preventing the need to include this feature in MRT requirements. | ✓ | ✓ | ✓ | C3-6232 |
DevOps | cPLD job performance has been improved, resulting in faster processing times and enhanced efficiency. | ✓ | ✓ | ✓ | C3-6289 |
DevOps | Geo-location results for donors near Charity users are now accurate when using the store locator map or geofilter, resolving previous inaccuracies. | ✓ | ✓ | C3-6290 | |
DevOps | Code has been refactored to skip jobs if the donation response does not exist, improving efficiency and resource management. | ✓ | ✓ | ✓ | C3-6330 |
Foodiverse | We have made improvements to the user permissions for assigned user roles. | ✓ | ✓ | ✓ | C3-5855 |
Foodiverse | Rectangular format logos for Foodiverse users are now correctly displayed on the ‘join foodbank network’ screen, despite changes in container size. | ✓ | ✓ | ✓ | C3-6152 |
Foodiverse | Donor Org admins, that have integrated with Foodiverse’s donation API, can now configure their autoselect behavior on for maximum collection windows; donation window cut-off; and transfer window cut-off by navigating to Manage Branches and clicking ‘Edit Branch’. Please note that this is not yet applicable to donors without a donation API integration. | ✓ | C3-6288 | ||
Mobile Apps | The Offers History Flutter screen on mobile has been improved to ensure Charity & Foodbank users have similar information as what can be seen on the web app. | ✓ | ✓ | C3-6099 | |
Mobile Apps | We have added a new visual placeholder to the Donor’s dashboard on the mobile application. Now when Donors post a donation, a message will appear on the dashboard thanking them for posting a donation. | ✓ | C3-6176; C3-6183 | ||
Mobile Apps | Flutter code has been refactored to improve load performance on the mobile app screens. | ✓ | ✓ | ✓ | C3-6189 |
Mobile Apps | We have made offline app improvements so that all users will be able to use recently cached information on the Foodiverse app when their device is not connected to the internet. | ✓ | ✓ | ✓ | C3-6192 |
Mobile Apps | We have made an improvement to the donation posting process on the mobile app. Now Donors will be able to post in the same Donation Window more than once. This is to allow for the fact that in some cases there may be additional food that could be offered to the collecting charity and the Donor may prefer one collection rather than two or more. There is an appropriate warning message that displays to donors that will try to post this way. | ✓ | ✓ | C3-6200 | |
Mobile Apps | Testing for the internet connectivity banner and cached screens on Flutter has been automated, ensuring smoother testing processes. | ✓ | ✓ | ✓ | C3-6212 |
Mobile Apps | Testing that Donors can post multiple times in a Donation Window on the mobile app has been automated, ensuring smoother testing processes. | ✓ | C3-6213 | ||
Mobile Apps | Calls to the summary endpoint have been optimized for Donors using the Dashboard on the mobile app, resulting in improved performance. | ✓ | C3-6303 | ||
Mobile Apps | Improvements have been made to how the ‘reload’ button works on the mobile dashboard, resulting in improved performance. | ✓ | ✓ | ✓ | C3-6321 |
Mobile Apps | The app no longer crashes when users try to view schedules, ensuring a smoother user experience. | ✓ | ✓ | ✓ | C3-6469 |
Mobile Apps | Indonesian translations for the days of the week have been updated across both web and mobile platforms. | ✓ | ✓ | ✓ | C3-6476 |
Notifications | Response time on the Dashboard for Donors/Charities has been improved, eliminating loader display times of over a minute. | ✓ | ✓ | C3-6311 | |
Notifications | Improvements have been made to the mobile Dashboard, resulting in faster and smoother loading times. | ✓ | ✓ | ✓ | C3-6312 |
Reporting | The sorting issue with the Donor Impact Report label has been resolved, and it now filters as intended. | ✓ | C3-5964 |
20 March 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.2.1 | Automatic update |
Web app | 3.2.1 | Automatic update |
Mobile iOS app | 3.2.1 | Automatic update |
Mobile Android app | 3.2.1 | Automatic update |
Middleware | 3.2.1 | No changes required |
APIs and Integrations | 3.2.1 | No changes required |
Category | Foodiverse Update | Charity | Donor | Foodbank | Reference |
Foodiverse Translations | We made an improvement to elements on certain pages of the web app that became misaligned when the user language was changed to Indonesian. | ✓ | ✓ | ✓ | C3-6080 |
Foodiverse Translations | We fixed a UI issue that was appearing when the app user language was changed to Indonesian. | ✓ | ✓ | ✓ | C3-6085 |
Knowledge Base | We have updated the user guides in the Knowledge Hub for the recent changes to the default naming of the first branch created with a Foodiverse account. | ✓ | ✓ | ✓ | C3-6093 |
Mobile Apps | During the donation process on the mobile app, there was a limit to the number of characters that Donors could input in the quantity field. This has been removed and we have added improved error validation for when minimum and maximum donation weights have been breached to include UI feedback for users. | ✓ | ✓ | C3-5948 | |
Mobile Apps | We made an improvement to the Waitlist and Foodboard counters on the dashboard of the mobile app which tells Charity users if there are additional food offers available to them. Now each time the app is closed and reopened; the counters will update automatically to check if there are additional offers. | ✓ | ✓ | C3-6081 | |
Mobile Apps | We improved the donation process on the mobile app when Donors add product details. Now the values added will sum and give the user a running total in Kg. | ✓ | ✓ | C3-6173 | |
Mobile Apps | In an effort to improve the mobile app performance, we have made a slight change to the reload icon that reloads the screen. The reload button can only be pressed every 3 seconds. This improvement across all users will help with the speed of the mobile application. | ✓ | ✓ | ✓ | C3-6184 |
Mobile Apps | In an effort to improve how the mobile app handles loading of new pages – we have fixed the flickering issues that were previously occurring on page load while improving page performance. | ✓ | ✓ | ✓ | C3-6186 C3-6187 C3-6188 C3-6211 |
Mobile Apps | We have added a new feature which informs users when their device is not connected to the internet. A banner will display to the user when the user is disconnected and when they are reconnected again. | ✓ | ✓ | ✓ | C3-6191 C3-6193 |
Mobile Apps | We have improved the mobile app so that the Offers History, Donations History and Dashboard pending actions are cached. This means if your device is disconnected from the internet, the most recent app updates can still be interacted with. | ✓ | ✓ | ✓ | C3-6194 |
Mobile Apps | We fixed some issues that were happening on the Foodboard in regards to the GeoFilter feature where Charities were not able to see all of the offers in the selected location radius. | ✓ | ✓ | C3-6235 C3-6236 C3-6335 | |
Mobile Apps | We have added the Geofilter feature to the Beta Foodiverse application for trials. | ✓ | ✓ | C3-6274 | |
Performance Improvements | After the latest Foodiverse release on Feb 7th 2024, our system experienced some performance issues based on how our mobile app was interacting with one of our system’s APIs. This resulted in some of our integrated customers receiving 429 and 524 error messages. The API has now been optimised which should resolve this issue. | ✓ | ✓ | ✓ | C3-6277 |
System Performance | There was an improvement made to the donation creation code so that the performance of the Donation API maintains optimal system performance for Foodiverse when bulk donations are created. | ✓ | C3-4849 | ||
Testing Improvements | Engineers have made improvements to automated testing in an effort to reduce the amount of time required for manual testing before a new Production release. | ✓ | ✓ | ✓ | C3-6114 C3-6115 C3-6116 C3-6117 |
Web app | There was an improvement made to the orientation of how logos are displayed on the web app. | ✓ | ✓ | ✓ | C3-5764 |
Web App | As a part of Foodiverse trials in Kenya, there were some location additions added to the registration form for the BETA platform. | ✓ | ✓ | ✓ | C3-5807 |
Web App | The Manage Member Schedule page on the Web Application has been improved so that Foodbank Admins can filter and view all of the member schedules in their Food Net. This makes it easier for Food Nets to check schedules and removes the need to click into every member’s schedule settings. | ✓ | C3-5968 | ||
Web App | We have improved the Branch settings so that Foodiverse admins can add and edit their branch GPS coordinates. | ✓ | ✓ | ✓ | C3-6022 |
Web App | The team fixed an issue where the donation status filter was not working correctly. Data is now returned correctly when setting the order by a selected filter. | ✓ | ✓ | C3-6095 | |
Web App | We have made an improvement to the Add new user and Edit existing user form process flow. Now all phone numbers for individual users will be an optional instead of a requirement. | ✓ | ✓ | ✓ | C3-6096 |
Web App | We have improved all user input form fields on the web app so that now users can clearly see what input fields are required before pressing submit. | ✓ | ✓ | ✓ | C3-6098 |
Web App | We have improved the donation creation process on the flutter mobile app so that when the Donation volume is higher (or lower) than the Branch settings are set to, that an informative error message will also take custom units of measurements for an Org into account. | C3-6112 | |||
Web App | We fixed an issue on the Donations page where the search bar filter would not search for Donation UUID, Offer ID or the Reference. This now works as expected. | ✓ | ✓ | C3-6155 | |
Web App | We have enabled Donor organisations to be able to add and edit VIP window’s for their Donations. When this feature is enabled, it provides Donor orgs with the flexibility to set a custom VIP window time frame for all of the donor branches in their organisation which allows customization options for offering a Donation to Primary Charities for the selected timeframe. | ✓ | ✓ | C3-6196 C3-6199 C3-6201 C3-6202 C3-6203 C3-6283 | |
Web App | We made an improvement to Donors that try to post without an active membership status. If a donor tries to use a schedule when they don’t have an active membership (e.g. paused), the donor will see an error message and will not be able to continue with the donation. | ✓ | ✓ | C3-6209 | |
Web App | We fixed a reporting issue where the report labels were not being applied and searched correctly. This now works as expected. | ✓ | ✓ | ✓ | C3-6260 |
Web App | Foodiverse admin users can now search the donations page and Offers History page at an organisation level as well as at a granular branch level by selecting the appropriate radio button with the search box | ✓ | ✓ | ✓ | C3-6271 C3-6272 |
Web App | There was an issue where Donors were not able to retrieve Foodboard donations in their Donations History. This has been fixed. | ✓ | ✓ | C3-6273 | |
Web app, Mobile App | We fixed an issue on Foodiverse where some branch locations were displaying incorrect geolocation coordinates. | ✓ | ✓ | ✓ | C3-5584 |
Web app, Mobile App | As a part of a Foodiverse framework improvement; we have made the mobile authentication pages desktop responsive. | ✓ | ✓ | ✓ | C3-5921 C3-5925 C3-6014 C3-6027 |
Web App, Mobile App | We have added minimum and maximum Kg weight settings to the Branch Settings in the FV web app so that Donors can have more control of the quantity of their Donation Postings. This setting does not have to be changed, it can be left at the default settings (Min: 0 Kg and max: 100 Kg). Changing this setting will apply the minimum and maximum donation weight to the mobile application only. The Web application will not be affected. | ✓ | ✓ | C3-6038 C3-6039 C3-6110 C3-6305 C3-6225 C3-6175 | |
Web App, Mobile App | We made an improvement to the naming of the first branch that is created automatically when a Foodiverse account is created. The words “Default Branch” appeared on Reports, Offers History and the Donations page. Now an asterisk will appear after the branch name in order for users to know that that is the first branch created on their Foodiverse account. | ✓ | ✓ | ✓ | C3-6091 |
31st January 2024 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.17 | Automatic update |
Web app | 3.1.17 | Automatic update |
Mobile iOS app | 3.1.17 | Automatic update |
Mobile Android app | 3.1.17 | Automatic update |
Middleware | 3.1.17 | No changes required |
APIs and Integrations | 3.1.17 | No changes required |
Category | Foodiverse Update | Charity | Donor | Foodbank | Reference |
Beta Web App | We have improved the Foodiverse Beta platform registration as a part of our pilot programs for Kenya and Indonesia so that users in these regions can join Foodiverse. | ✓ | ✓ | ✓ | C3-5727 |
Donation Process | An issue was arising in certain scenarios where a VIP Window and the Accept By time were clashing when the two happened to overlap. This has been fixed so that if the VIP window is a longer period than the time between the offer and Accept By Time, the VIP window is skipped. | ✓ | ✓ | C3-5388, C3-5942 | |
Middleware | We had cases with an automated integration where some data uploaded contained invalid characters which was causing issues with a number of donation postings. This has been fixed so that data like this is simply skipped over so that the food donation is still read by Foodiverse and posts successfully. | ✓ | C3-5844 | ||
Middleware | We made an improvement to how the Middleware targets available Donation Windows when a Donation file is uploaded. | ✓ | C3-5905 | ||
Middleware | We fixed an issue with an automated integration where food items uploaded to Foodiverse with a weight of less than 0.001kg were the cause of a donation to not be created. Even though this happened rarely – it is still a loss of food to be saved and goes against our mission. This now works as expected. | ✓ | C3-5666 | ||
Mobile App | As a part of improvements to the mobile app and Charity UI improvements we have made sure that all mobile screens have a scrollbar as needed. | ✓ | ✓ | ✓ | C3-5320 |
Mobile App | We have improved the button UI for when Donors mark Donations transferred. Now the buttons use icons so that they have universal meaning. | ✓ | ✓ | C3-5439 | |
Mobile App | We have made an improvement to the language used in the Flutter mobile app. We have replaced ‘Offers History’ with ‘Recent Offers’ anywhere it was mentioned on the app. This is more intuitive and representative of what the user expects to see. | ✓ | ✓ | C3-5448 | |
Mobile App | We have improved the Profile section UI of the mobile application. We’ve now made it possible to edit your personal user information such as Name & phone number directly from the mobile app whereas before this was only possible from the Desktop web app. | ✓ | ✓ | ✓ | C3-5481 |
Mobile App | We have made an improvement to the language used in the Flutter mobile app. | ✓ | ✓ | C3-5482 | |
Mobile App | We have improved the Schedule page of the mobile app so that Food Banks that are operating as a Donor or Charity recipient have UI indicators of the type of action required a scheduled item in the upcoming days or week. | ✓ | ✓ | C3-5513 | |
Mobile App | We made improvements to the web app so that Organisation logos if added to the web app, will also display on the mobile app Donation cards for Donors, Charities and Food Banks. | ✓ | ✓ | ✓ | C3-5533 |
Mobile App | We improved the Schedule on the mobile app so that Donors/Food Banks with no scheduled donation windows can still see if they have an upcoming transfer window where they are expected to post to the foodboard. | ✓ | ✓ | C3-5623 | |
Mobile App | With the new Geo-filter feature, we have added functionality where Foodiverse will calculate the distance to the branch offering Food to the Charities branch address so that the Charity user knows how far the Offer Collection is from their branch address before accepting the donation. This will show up to 100 Km from the branch address of the Charity | ✓ | ✓ | C3-5642 | |
Mobile App | We have implemented a Geo-locational filter on the Foodboard of the mobile app. Now Charities and Food Banks will be able to filter based on distance to their branch address. | ✓ | ✓ | C3-5643 | |
Mobile App | We fixed a front end error on the UI of the mobile app where the Schedule was not loading correctly in some instances. ‘No Branch Selected’ would appear for a few seconds until the schedule loaded. This is now working as expected. | ✓ | ✓ | ✓ | C3-5728 |
Mobile App | We have improved the Charity dashboard to have a section called ‘Updates’ where primary Charities will see important Donor updates relating to their transfers. | ✓ | C3-5772 | ||
Mobile App | We have added an improved Geo-Filter UI to enhance how users can interact with the GeoFilter feature | ✓ | ✓ | C3-5833 | |
Mobile App | We fixed an issue on the Charity mobile app dashboard where the ‘No Availability’ status was displaying incorrectly. | ✓ | C3-5851 | ||
Mobile App | We fixed an issue where Donors that had no scheduled Charities were not seeing donations posted feedback on their dashboard when they posted a donation. Now they see the expected ‘Thank you for posting’ feedback that Donors are meant to see. | ✓ | ✓ | C3-5871 | |
Mobile App | We have improved the UI of the Waitlist offer cards for all users on the mobile app. | ✓ | ✓ | ✓ | C3-5906 |
Mobile App | We have improved the UI of the Foodboard offer cards for all users on the mobile app. | ✓ | ✓ | ✓ | C3-5907 |
Mobile App | We have added Indonesian language to the FV app for Indonesian native speakers as a part of our pilot programme to Indonesia. | ✓ | ✓ | ✓ | C3-6018 |
Mobile App | During the new addition of the Geo-filter on the Foodboard, we fixed a bug where the KM and Miles conversion was not taking the distance shown on offer cards into account. Now these units of distance change when the unit is switched in settings. | ✓ | ✓ | C3-6061 | |
Mobile App | We have confirmed the security relating to when eSign is used to ensure that the signatures of Donors and Charities are protected as per industry cyber security standards. | ✓ | ✓ | ✓ | C3-5914 |
Notifications | We removed an unnecessary email that was sent to Donors to reduce the number of emails sent. | ✓ | C3-5908 | ||
Onboarding Process | We fixed a bug on the Registration page that happened when the time zone was changed. It would reset the address settings of that the user had just entered. This now works as expected again. | ✓ | ✓ | ✓ | C3-6010 |
Reports | We fixed a specific issue for a Foodbank Admin account where they couldn’t load specific Charity data because of a technical issue. The report loads as expected now. | ✓ | C3-5730 | ||
Web App | We have improved the Web app Date Range Pickers so that if you set a range and then search again or change page – the same date ranges that you picked will persist from page to page. | ✓ | ✓ | ✓ | C3-5485 |
Web App | We have improved the Web app number of page results shown so that when users select a number of results to see, this selection will be the same from page to page. | ✓ | ✓ | ✓ | C3-5486 |
Web App | We have improved the Offers History page to have additional Donor and Charity filters allowing users to find information using additional search criteria available to them. | ✓ | ✓ | C3-5489, C3-5487 | |
Web App | On Foodiverse, when selecting a date range for a Donor Branch with the Temporary Calendar feature – the user was unable to select tomorrow’s date. The expected behaviour is that it will only allow a selection from tomorrow. This has been fixed. | ✓ | ✓ | C3-5494 | |
Web App | We have added additional columns of information about Offers on the Offers History page for Charities and Food Banks to improve workflow. | ✓ | ✓ | C3-5507 | |
Web App | We have improved the Donations page to have additional Donor and Charity filters allowing users to find information using additional search criteria available to them. | ✓ | ✓ | C3-5568, C3-5569 | |
Web app | We improved the UI of the search filters for the Offers History page | ✓ | ✓ | C3-5638 | |
Web app | We improved the UI of the search filters for the Donations page | ✓ | ✓ | C3-5639 | |
Web App | With the new Geo-filter, it was important to add a user preference of Km or Miles as a selection. This can be done in the Branch settings. | ✓ | ✓ | C3-5645 | |
Web App | We have improved the searchability of the Offers History page on the web app for Food Bank users so that search criteria filters and data is returned as expected. | ✓ | ✓ | C3-5865, C3-5887 | |
Web app | We have made the Offers History page far more similar to the Donations page. Now Charities will be able to see the same level of donation information that Donors and Food Banks can. | ✓ | ✓ | C3-5888 | |
Web App | When adding a phone number to user information on Foodiverse, it was possible to use a phone number that was already in use for another phone number. This is fixed so that the phone number must be unique. | ✓ | ✓ | ✓ | C3-5916 |
Web App | We made a change to how data is searched on the Offers History page. Now only the Offer ID, Reference ID and UUID of a donation can be searched using the normal search bar. All new other searches like Branch name, ID, User, Phone number and address should be searched for the Donor or Charity dropdown filters. | ✓ | ✓ | C3-5927 | |
Web App | We have improved the process for adding new users to a Foodiverse account. Now, admins will not need to provide a phone number when adding a new user unless the new user will be an Org admin. This is to help improve adding new users where all the user’s details may not be known at the time of inviting them to Foodiverse. | ✓ | ✓ | ✓ | C3-5965 |
Web App | We have improved the Add New User page for Org admins. Now, all the required steps to add a new user/edit an existing user and assign branch permissions will be on the same page. | ✓ | ✓ | ✓ | C3-5966 |
Web App | We have added an improvement to the way that admins can assign branch permissions to new users. Now there is a master toggle switch to apply all branch permissions to the new user which will save admins time. Previously, admins had to assign permissions branch by branch. | ✓ | ✓ | ✓ | C3-5967 |
Web App | When we improved the search filters for Offers History and the Donations page, we needed to fix an issue where the filters didn’t always work in unity together. Now they do so that data with a relationship between a Donor and Charity can be searched for. | ✓ | ✓ | ✓ | C3-5977 |
Web App | We have streamlined how admins can create new branches or edit existing branches. Previously this was a tabbed section whereas now it is a one page form with stepped sections for the admin to add new branch details to. | ✓ | ✓ | ✓ | C3-5986 |
Web App | We have added Indonesian language to the FV app for Indonesian native speakers as a part of our pilot programme to Indonesia. | ✓ | ✓ | ✓ | C3-6019 |
Web App | We added informative tool tips to the updated search filters on the Offers History and Donations page so that users are informed what they can search for and in which search filters they can do so. | ✓ | ✓ | ✓ | C3-6064 |
Web App, Mobile App | In some cases we found that a Charity or Food Bank acting as a Charity recipient weren’t able to accept an offer on the Foodboard. We investigated the issue and implemented a fix. | ✓ | ✓ | C3-6013 |
11 October 2023 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.13 | Automatic update |
Web app | 3.1.13 | Automatic update |
Mobile iOS app | 3.1.13 | Automatic update |
Mobile Android app | 3.1.13 | Automatic update |
Middleware | 3.1.13 | No changes required |
APIs and Integrations | 3.1.13 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
Donation Process | We remedied an issue that was occurring with a Donor integration that was causing NoPostings to be posted because of invalid products that were automatically uploaded to Foodiverse. | ✓ | C3-5081 | ||
Donation Process | There was a fixed bug in the Foodiverse platform where some Charities were able to accept offers from Donors when the respective time to accept by had already passed. This issue only affected some specific users. | ✓ | C3-5471 | ||
Donation Process | We fixed an error that some users were experiencing where the Donation Record was not displaying the timestamp, donation, category and product information correctly. | ✓ | ✓ | ✓ | C3-5626 |
Donation Process | New Feature – File Transfer Service: We have built a new integration that allows customers to send us donation data via an integration. Some BETA customers will be testing this in the coming weeks | ✓ | ✓ | ✓ | N/A |
Mobile | We made an improvement on Offer cards where the total Kg of the offer shows to the user | ✓ | ✓ | ✓ | C3-5357 |
Mobile | We implemented a UX improvement for time and dates that are now standardised across the mobile app | ✓ | ✓ | ✓ | C3-5358 |
Mobile | We have improved the Offer design that shows to Charities before they accept or decline an offer as a part of mobile UI and UX improvements. | ✓ | ✓ | C3-5321 | |
Mobile | We have added a new section to the mobile dashboard for Charities and Food Banks that have accepted an offer named “To Be Collected“. In this section, the offers that have been accepted will appear here and inform the user of their Collection Window time, the address for collection and give the option to leave feedback on the Donation. | ✓ | ✓ | C3-5322 | |
Mobile | We have made a new ‘Offer’ card design that will be shown to Charities & Food Bank users of the Foodiverse mobile app. This new Offer card will appear under ‘My Primary Offers’. | ✓ | ✓ | C3-5326, C3-5601 | |
Mobile | We have improved the Donor’s scheduled donation call to action and design for Donors and Food Banks in order to improve the donation flow between Donors and Charities. | ✓ | ✓ | C3-5327 | |
Mobile | We have added an improved UI and UX aesthetic to the mobile app. Now all users of the mobile app will be able to see the logo image from who has offered a Donation and who has accepted a Donation. In this way, Charities can see the Donor’s logo on their offers and Donors can see the Charity logo on their accepted donations. The logo can be set and changed on the Foodiverse Web App in Profile settings | ✓ | ✓ | ✓ | C3-5355 |
Mobile | We have updated the branch dropdown selector in all areas of the app. Any Organisation account that has just 1 branch set up on their account they no longer see the branch dropdown selector. If an Organisation has more than 1 branch account then they will see it as normal and be able to toggle between branches if they have the user permissions to do so. | ✓ | ✓ | ✓ | C3-5381 |
Mobile | We have improved the mobile app Schedule screen so that all mobile users can have a greater schedule view for the week of Donations and Offers ahead with calendar UI. This allows users to filter their weekly schedule so that they can view one, many or all of the week ahead. A ‘dot’ on a calendar day implies that there is a donation to post or an offer to expect on that day. | ✓ | ✓ | ✓ | C3-5382 |
Mobile | We have improved the Donation and Offer Schedules that appear on the Schedule screen for all users. Now users can see the branch name that is Collecting or Offering their scheduled donation as well as the Collection time window for that Donation. | ✓ | ✓ | ✓ | C3-5383, C3-5514 |
Mobile | We have made an improvement to the language used in the Flutter mobile app. We have replaced ‘Offers History’ with ‘Recent Offers’ anywhere it was mentioned on the app. This is more intuitive and representative of what the user expects to see. | ✓ | ✓ | C3-5448 | |
Mobile | As a part of the Mobile UI and UX improvements, we have added a Waitlist Offers counter to the dashboard that tells Charities how many Waitlist offers are available to them before tapping on the card – removing the need to go and check if there are any waitlist offers available to them. | ✓ | ✓ | C3-5323 | |
Mobile | To add to the counter design; we have added a Foodboard Offers counter that informs Charities how many Foodboard offers in their Foodnet are available to them before tapping on the card – removing the need to go and check if there are any foodboard offers available to them. When users tap on the card, they may need to edit the advanced filters to display additional offers. | ✓ | ✓ | C3-5324 | |
Mobile | We have added a Primary Offers counter card that informs Charities how many Primary Offers have been accepted by their branch so far that day – out of a total amount of offers available to that branch. This UX improvement is a step taken to inform the branch user that there are more scheduled Primary offers available to them that they could accept for their Charity. | ✓ | ✓ | C3-5325 | |
Reports | We have fixed a small bug in Foodnet reports where unrelated data was showing in downloaded reports. | ✓ | C3-5391 | ||
Web App | There was a bug that some users were experiencing where they were unable to view offers with the offer status ‘Accepted by Other’. This has been fixed and now performs as expected. | ✓ | ✓ | C3-5443 | |
Knowledge Base | We have updated the user guides in the Knowledge Hub for the recent changes where users create an account in Foodiverse. | ✓ | ✓ | ✓ | C3-4890, C3-4891, C3-5079, C3-5013, C3-5034, C3-5048, C3-5203, C3-5281 |
Knowledge Base | We have updated the user guide for how to Add a new user to my Org/branch in the Knowledge Hub in line with the recent onboarding improvements. | ✓ | ✓ | ✓ | C3-4890, C3-4891, C3-5079, C3-5013, C3-5034, C3-5048, C3-5203, C3-5281 |
Knowledge Base | We have updated the user guide for how to apply to a Foodnet | ✓ | ✓ | ✓ | C3-4901, C3-4902, C3-4917, C3-4917 |
Knowledge Base | We have updated the user guide for how to set branch food classifications. | ✓ | ✓ | ✓ | C3-5241 |
Knowledge Base | We have updated the user guide for how to invite members to a Food Network. | ✓ | ✓ | ✓ | C3-4952, C3-4917, C3-5039 |
Knowledge Base | We have updated the user guide for how to approve an application to a Food Network. | ✓ | ✓ | ✓ | C3-4903 |
Knowledge Base | We have updated the Donor mobile guide in the Knowledge Hub to reflect the new Mobile UI improvements | ✓ | ✓ | ✓ | C3-5297, C3-5357, C3-5358, C3-5292, C3-5293, C3-4899, C3-5327, C3-5355, C3-5311, C3-5321, C3-5321, C3-5322, C3-5326, C3-5323, C3-5324, C3-5325, C3-5439, C3-5532 |
Knowledge Base | We have updated the Charity mobile guide in the Knowledge Hub to reflect the new Mobile UI improvements | ✓ | ✓ | ✓ | |
Knowledge Base | The Food Category Report user guide was updated to reflect some changes in images and wording. | ✓ | ✓ | ✓ | N/A |
Knowledge Base | We added a new section to the Knowledge Hub to explain a new in app notification feature that all mobile users will experience to help guide the Donation process. | ✓ | ✓ | ✓ | C3-5304, C3-5389, C3-5601 |
Knowledge Base | We have updated the Reports Glossary to inform the difference between Total Donations in reporting and Total Transferred in reporting. | ✓ | ✓ | ✓ | N/A |
30 August 2023 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.9.2 | Automatic update |
Web app | 3.1.9.2 | Automatic update |
Mobile iOS app | 3.1.9.2 | Automatic update |
Mobile Android app | 3.1.9.2 | Automatic update |
Middleware | 3.1.9.2 | No changes required |
APIs and Integrations | 3.1.9.2 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
Mobile App | We have improved the Mobile app loading screen so that now the Foodiverse logo displays when a user first opens the app. | ✓ | ✓ | ✓ | C3-5299 |
Mobile App | We have added a new mobile message pop up to the mobile app that shows from the bottom of the screen instead of taking over the entire screen. This allows users to acknowledge important app information relating to Offers and Donations while still being able to interact with the screen. | ✓ | ✓ | ✓ | C3-5304 |
Mobile App | Mobile app users can now find the Foodiverse T&Cs in My Profile > Settings & Privacy | ✓ | ✓ | ✓ | C3-5171 |
Web App | We have made improvements to the user permissions for assigned user roles. | ✓ | ✓ | ✓ | C3-5296 |
Web App | We improved the tabbed navigation naming in the Foodbank Manage Membership Section of the Web App | ✓ | C3-5022 | ||
Food Net Membership | We have fixed an automated mail recipient error where a FoodBank invites an Org to join their FoodNet. Previously these accepted or declined invite emails were going to the member organisation. We have fixed this so that these emails go to the FoodBank Organisation. | ✓ | ✓ | ✓ | C3-5178 |
Food Net Membership | We’ve made an improvement to the ‘Join a Food Net’ user experience. A loading message will now appear to users to alert them the system is working to retrieve the relevant branches that are eligible to apply as a member of the food net in question. | ✓ | ✓ | ✓ | C3-4649 |
Registration Process | We have improved the welcome email that newly onboarded users receive if they have registered on Foodiverse via a custom link given to them by a Foodbank. Now the welcome the email no longer instructs the user to join a foodnet and this is because the user in this case will be automatically added to the Foodbank’s foodnet to be approved by the Foodbank admin. | ✓ | ✓ | C3-5237 | |
Email Notifications | We have made design improvements to the emails that users receive from Foodiverse. | ✓ | ✓ | ✓ | C3-5033 |
Donation Process | When making a Donation, we have made it possible to select the previous day’s Donation Window when a Donation is create within 12 hours of the previous day’s Donation Window | ✓ | ✓ | C3-5099 | |
Reporting | We have made user views in reporting more intuitive and removed confusion for Foodbank Admins. | ✓ | C3-5035 | ||
Reporting | We made an improvement to report filters where Foodbank Admins and Users were not able to view their own Charity and Donor org information in the generated report results. Previously they could only see their Foodnet member results. We have fixed this so that now they can see both. | ✓ | ✓ | ✓ | C3-5171 |
14 June 2023 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.4 | Automatic update |
Web app | 3.1.4 | Automatic update |
Mobile iOS app | 3.1.4 | Automatic update |
Mobile Android app | 3.1.4 | Automatic update |
Middleware | 3.1.4 | No changes required |
APIs and Integrations | 3.1.4 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
Mobile App | There was a bug on the Flutter mobile app where the Active Donations panel was not refreshing automatically after a Donor user created a Donation. The prompt “Can you Donate today?” was still appearing. this has been fixed and now when the donation is created, that prompt disappears. | ✓ | ✓ | C3-5066 | |
Mobile App | We have added consistency of information on Live Donation screens. A tooltip will now show to inform the Donor that Foodiverse is waiting for a Charity to accept their Donation. The Offer Time, Charity name & address and their accepted categories have also been merged into one card instead of two. | ✓ | ✓ | ✓ | C3-5053 |
Mobile App | There was a bug on the Flutter mobile app where users could change to their desired language – but if they wanted to switch back to English they were unable to do so. This has been fixed. | ✓ | ✓ | ✓ | C3-5065 |
Web App | There was a bug on Foodiverse where some users could see backend commands for language settings on the frontend. This has been fixed. | ✓ | ✓ | ✓ | C3-5067 |
Extra PLD & Breached PLD Offers | In Foodiverse, when you see donation data described as Extra, that means that the Donor gave the charity additional food than what they had estimated in their original donation offer. When you see donation data described as Breached, that means that the donor gave the charity food that they are not approved in Foodiverse to accept. There was an issue happening when a Donor sent ‘Extra’ or ‘Breached’ category product level details items. Foodiverse was adding the estimated kilograms to the categories table for these items. We have fixed this bug so now when a donor sends additional or breached, only the actual kilograms appear on the Categories table for these items | ✓ | ✓ | ✓ | C3-4566 |
Food Net Membership Approval | We have made some improvements to the ‘Membership Administration’ section of the platform so that Food Net Admins can approve or reject new membership applications faster than before. | ✓ | ✓ | ✓ | C3-4903 |
Food Net Membership Automation | We have made it possible to automate the ‘membership activation’ step of the user and organisation onboarding process. The configuration is available in the Food Net Settings. | ✓ | ✓ | ✓ | C3-4952 |
Registration Process | The registration page has been made more readable by becoming one form column instead of two. Each section heading has been updated to be more indicative of what information is required from a registering user. Lastly, the form now only requires one mobile contact number whereas before; two were required. These updates should allow for a smoother registration process. | ✓ | ✓ | ✓ | C3-5048 |
Registration Form | We improved the error validation on the Foodiverse registration form. Now when a user enters a phone number that is already used on the platform, the user will be shown the error so that they know they need to input a number that hasn’t already been used. | ✓ | ✓ | ✓ | C3-5203 |
Onboarding Process | We have developed a new link that Food Net Admins can share with members wishing to join Foodiverse that will allow them to register and automatically send their Foodnet application for review once they are registered, eliminating the need to log in and ‘join the food net’. There is a Donor link and a Charity link. New members will not have to choose their Organisation type if they use this link. Once the new member becomes actived on Foodiverse, the Foodbank will receive a request to join their Foodnet. | ✓ | ✓ | ✓ | C3-4902C3-4917 |
Onboarding Process | We have streamlined the email notifications for the onboarding process of joining Foodiverse as a Donor and as a Charity. New Organisations and new users will receive less emails than previously in an effort to onboard users faster and with ease. | ✓ | ✓ | ✓ | C3-5039 |
Onboarding Process | We have updated the email content in the first 9 emails that new Foodiverse Organisations receive during the onboarding process. | ✓ | ✓ | ✓ | C3-5034 |
Platform Security | We added an increased security to user account activation where all Foodiverse users now have a 24 hour timeline to be able to activate an account, password or password reset via email. This gives users enough time to activate accounts and reset their password while ensuring that we maintain platform security. | ✓ | ✓ | ✓ | C3-5079 |
SMS Notifications | We have updated the default SMS settings for when a user adds a new branch to their existing organisation. The setting is now defaulted to ‘Never Send SMS’, | ✓ | ✓ | ✓ | C3-4821 |
30 April 2023 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.2 | Automatic update |
Web app | 3.1.2 | Automatic update |
Mobile iOS app | 3.1.2 | Automatic update |
Mobile Android app | 3.1.2 | Automatic update |
Middleware | 3.1.2 | No changes required |
APIs and Integrations | 3.1.2 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
Donation Record | The donation record will now be exportable as a PDF on the web app. Food Banks and Donors can do this by clicking on the ‘Donation Record’ button on the ‘Donations’ page and clicking the export button. Charities can do this by clicking on the ‘Donation Record’ button on the ‘Offers History’ page and clicking the export button. | ✓ | ✓ | ✓ | C3-4350; C3-5050 |
Food Net Membership | We fixed a bug that was mainly affecting the ‘Membership Approval’ section of the platform whereby the titles of the clickable buttons were not showing correctly. | ✓ | C3-5036 | ||
Food Net Membership | When an Org Admin wishes to add a new branch to their organisation, they can now join a ‘featured’ food net at the same time. Featured food nets are food nets that FoodCloud has verified to be active food nets. The data in the ‘Status’ column will be fixed in a future release but will not disrupt the new feature’s functionality. | ✓ | ✓ | ✓ | C3-4901; C3-4996 |
Knowledge Hub | The Charity Mobile User Guide has been updated to include instructions on how to:- Click through to a map to see where the donor is based once a donation has been accepted- Set your language preferences- Filter by date in ‘Offers History’ The Donor Mobile User Guide has been updated to include:- Updated screenshots on how to add products to a donation offer- Instructions on how to set your language preferences | ✓ | ✓ | ✓ | C3-4962 |
Mobile App | Donors preparing donations on the mobile app will notice a new button that, when toggled from right to left, will allow them to post a ‘no availability’ notification to charities. This is to increase the intuitiveness of the app and maximise the possibility of food donations. | ✓ | C3-4968 | ||
Mobile App | We have improved the experience for donors using the mobile app who wish to let charities know that they do not have any food available to donate. From now on, when they select ‘No food available on the ‘prepare donation’ screen, they will receive a popup notification asking if they are sure they would like to post this and then thanking them for letting us know. This will replace a confusing notification telling them that their donation was successful. | ✓ | C3-5012 | ||
Mobile App | Donors entering product-level detail (PLD) at the point of donation will now receive a validation error if they try to input non-numeric characters into the product price field. | ✓ | C3-4964 | ||
Offers History | In Offers History, the date of a completed donation will now show the date that the donation was transferred on. | ✓ | ✓ | C3-4924; C3-5016 | |
Reporting | All reports in Foodiverse are limited to a 90 day date filter to protect platform performance. There was a bug affecting this limitation which has now been resolved. | ✓ | ✓ | ✓ | C3-5078 |
Reporting | We improved the Impact Reports on Foodiverse to ensure that if a donor only sends estimated data and does not follow-up by sending product level detail data (aka actual data), the ‘Actual KGs’ cell will be blank. It was matching the ‘estimate’ data which was inaccurate. | ✓ | ✓ | ✓ | C3-4913 |
29 March 2023 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.1 | Automatic update |
Web app | 3.1.1 | Automatic update |
Mobile iOS app | 3.1.1 | Automatic update |
Mobile Android app | 3.1.1 | Automatic update |
Middleware | 3.1.1 | No changes required |
APIs and Integrations | 3.1.1 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
Donation Receipt | From now on, if a donor fails to send us product level detail (PLD) after a donation has been marked transferred, Foodiverse will automatically send an email to the recipient(s) 24 hours later to tell them that this information has not been provided by the donor. | ✓ | ✓ | ✓ | C3-4788 |
Donation Record | Numerical data in the ‘Donation Record’ will now be rounded up to a maximum of 3 decimal points. | ✓ | ✓ | ✓ | C3-4755 |
Food Categories | Admin users can now configure the order of the default food categories they want to show to their branches. For instance, they can configure their most popular default food category to appear at the top of the list on the ‘Prepare Donation’ screen on mobile and web. This can be done in the ‘Organisation Settings’ section of the web app. For more information, please read this Knowledge Hub article | ✓ | ✓ | C3-4817; C3-4818; C3-4785 | |
Food Categories | We have simplified the donor user’s experience of adding categories to a donation (if they have permissions to do so). | ✓ | C3-4823 | ||
Food Categories and PLD | We have made some small improvements to the ‘Food Details’ section of the mobile app. This section is where donors input what food they would like to donate. We have made these improvements for two main reasons:
| ✓ | C3-4835; C3-4838 | ||
Food Categories and PLD | We have added the ability for donor users to add product details to their donations on the mobile app. For more details, please read the updated ‘Donor User Guide’ | ✓ | C3-4839; C3-4841 | ||
Food Categories and PLD | Donors who include product level detail (PLD) before offering a donation were unable to edit these in their Organisation settings. Instead, they had to delete the old product and add a new product. This has now been resolved. | ✓ | C3-4870 | ||
Food Classifications | When the ‘food classifications’ or ‘storage types’ were being updated in the user interface, the change was not being recorded in the backend / database. This also affected users trying to update food classifications using the APIs. This issue has now been resolved. | ✓ | ✓ | ✓ | C3-4639; C3-3680 |
Knowledge Hub | We have updated the ‘User Views’ knowledge hub article. For more information, click here. | ✓ | ✓ | ✓ | C3-4734; C3-4911 |
Language Settings | We removed the language selection drop down field from the registration page. We did this because it was a repeated preference setting as the page also includes a flag language preference setting button which has been moved to the top of the registration page so that is a more prominent preference setting. | ✓ | ✓ | ✓ | C3-4702; C3-4703 |
Language Settings | Mobile app users who now try to log into their app with different mobile language settings to their registered language settings will now see a pop-up message asking them to confirm which language they would like to proceed with using. | ✓ | ✓ | C3-4872 | |
Mobile App | In most cases, ‘Offer Time’ is visible to donors and charities when offering and accepting a donation. We found one scenario where this wasn’t happening, namely when a charity clicked through to an offer from the mobile app dashboard. This issue has now been resolved. | ✓ | C3-4848 | ||
Mobile App | We’ve made an improvement to the mobile app so that it’s more difficult to remove a food category option from the ‘Prepare Donation’ screen. | ✓ | C3-4803 | ||
Mobile App | Charity users will now see a ‘pin’ icon after they have accepted their donation which, if they click it, it will open their default maps app (e.g. Google Maps or Apple Maps) and direct them to the donors location. | ✓ | C3-4804 | ||
Mobile App | We have added a ‘date filter’ to the Offers History Page on mobile so that charity users can more easily search for specific donations. | ✓ | C3-4858 | ||
Mobile App | Some android mobile app users were experiencing issues with logging in and out of the app. This issue has now been resolved. | ✓ | ✓ | C3-4888 | |
Notifications | Some charity users continued to receive SMS donation alerts despite their notification preferences being set to ‘Never send me sms’. This issue has now been resolved. | ✓ | C3-4655 | ||
Registration Page | In some cases, foreign phone numbers weren’t being recognised by the Foodiverse registration page. We have now resolved this. | ✓ | ✓ | ✓ | C3-4740 |
Registration Page | Users registering on Foodiverse will now see the ‘Org Type’ option ‘Food Network’ instead of ‘Food Bank’ to reduce confusion. | ✓ | ✓ | ✓ | C3-4890 |
Registration Page | From now on, all food classification options will be pre-selected for new users registering on Foodiverse to reduce clicks. | ✓ | ✓ | ✓ | C3-4891 |
Reports | An issue was discovered whereby ‘FoodNet Admin’ users were unable to run the Charity Branch Impact Report for a large Charity organisation. This issue has now been resolved. | ✓ | C3-4881 | ||
Reports | Foodiverse ‘Food Bank’ Report Users can now more easily filter their search results by Organisations. Instead of just searching for an organisation in the search bar, a user will now see a dropdown list of all of the Organisation’s in their food net. Users should only be able to see organisations based on their user type and permissions. | ✓ | C3-4597 | ||
Reports | Foodiverse Report Users can now more easily filter their search results by donor or charity branches. Instead of just searching for a branch name, a user can now ‘type and search’ for the name so that the potential options are more obvious and you can also multiselect options. | ✓ | ✓ | ✓ | C3-4598 |
Reports | To improve ‘Donor KPI Summary’ and ‘Donor Impact Summary’ Report initial loading time, the time filter will now always default to ‘Month (Daily)’ data & the current month | ✓ | ✓ | C3-4905 | |
Reports | As a reports user, I want my selected ‘User View’ to determine which organisation, branch and label data and filters that I can see. | ✓ | ✓ | ✓ | C3-4929 |
Temporary Calendar | Temporary Calendar users were experiencing issues with being able to upload a CSV file with temporary schedule changes. This issue has now been resolved. | ✓ | C3-4669 | ||
Temporary Calendar | Temporary Calendar users were experiencing schedule issues when setting a temporary schedule for more than one consecutive week. This issue has now been resolved. | ✓ | C3-4760 | ||
Translations | We have made various improvements to our Czech and Slovak translations | ✓ | ✓ | ✓ | C3-4725; C3-4928; C3-4928; C3-4806; C3-4836; C3-4877; C3-4882; C3-4931 |
User Onboarding Improvements | Branch Admins who wish to ‘Join a new Food Net’ will now see ‘Featured Food Nets’ when they click ‘Join a Food Net’. Featured Food Nets will include Foodiverse key accounts. Branch Users can search for other food nets on the new ‘Other Food Nets’ tab. | ✓ | ✓ | ✓ | C3-4900 |
User View | The User View filter should automatically reflect the user’s permissions (e.g Administrator). This was not working and we have now resolved the issue. | ✓ | ✓ | ✓ | C3-4829 |
Web App | On the Donations page and the Offers History page, some users may have noticed that the ‘Donation Status’ was not transitioning from status ‘Ready’ to status ‘Offering’. This has now been resolved. | ✓ | ✓ | ✓ | C3-4814 |
Web App | We removed some of the demo food bank options appearing to users in the ‘Join a Food Net section’ to improve the user experience. | ✓ | ✓ | ✓ | C3-3250 |
Web App | Admins adding a New User may have noticed that the user’s status was showing as ‘Inactive’ instead of ‘Awaiting Activation’. This has now been resolved. | ✓ | ✓ | ✓ | C3-4716 |
25 January 2023 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.1.0 | Automatic update |
Web app | 3.1.0 | Automatic update |
Mobile iOS app | 3.1.0 | Automatic update |
Mobile Android app | 3.1.0 | Automatic update |
Middleware | 3.1.0 | No changes required |
APIs and Integrations | 3.1.0 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
Add Category & Product Details to Donations | We have added a new configuration to the web app that allows Org Admins to configure how much category and product detail they are permitted to add to a donation. To learn more, please see the Knowledge Base article here. | ✓ | C3-4633; C3-4634; C3-4693; C3-4712; C3-4607 | ||
Add Category & Product Details to Donations | We fixed a bug on the web app where users were unable to create a new product and its details while creating the donation. | ✓ | C3-4609 | ||
Donation Receipt | We fixed a bug where, in cases where a donor is using a custom unit of measure, the donation receipt which is emailed to the user was not distinguishing between that unit of measure and what that represents in kilograms. | ✓ | ✓ | ✓ | C3-4754 |
Donation Record | We made some formatting improvements to the Donation Record on the Mobile App so that it is easier to read. | ✓ | ✓ | C3-4556 | |
Donations | As a foodbank being offered food via the Foodiverse web and mobile, they will now see two options if they wish to mark a donation as ‘Not Transferred’ by clicking the ‘Feedback’ button:
Option 1: Refused at Donor Option 2: No Food Available at Branch | ✓ | C3-4293 | ||
Donations | On the web app, we improved the instruction for how the ‘accept-by time’ works when creating a donation. | ✓ | C3-4050 | ||
Donations | Food Bank users were experiencing issues filtering by Donor Branch on the new Donations page. This has now been resolved. | ✓ | C3-4676 | ||
eSign | We fixed a bug that was allowing esign users to complete a donation without adding an e-signature. | ✓ | ✓ | ✓ | C3-4590; C3-4772 |
eSign | We made a formatting improvement to the ‘Donation Record’ where only one e-signature is relevant. | ✓ | ✓ | ✓ | C3-4455 |
eSign | We fixed a bug where donations requiring an e-signature were remaining on the Dashboard on the mobile app even after the eSign process had been completed. | ✓ | ✓ | C3-4653; C3-4758 | |
Knowledge Base | The New Donor – Mobile User Guide has been updated to reflect some recent Mobile app changes. | ✓ | ✓ | C3-4529 | |
Knowledge Base | The Notification Window article has been updated. | ✓ | ✓ | C3-4608 | |
Knowledge Base | A Knowledge Base article has been created to explain the different types of Donation Email Receipts | ✓ | ✓ | ✓ | C3-4584 |
Knowledge Base | A Knowledge Base article has been created for the Product Logs Report | ✓ | ✓ | C3-4729 | |
Language Settings | We made some improvements to how language settings are set and saved in Foodiverse so that they are less likely to continuously revert to English. | ✓ | ✓ | ✓ | C3-4541; C3-4542; C3-4705 |
Manage Donations | We have fixed an issue that FoodNet Admins were experiencing where search inputs were not matching the filtered results on the ‘Manage Donations’ page. | ✓ | C3-4559; C3-4632 | ||
Mobile App | Donors using the mobile app will now see a precalculated ‘accept-by time’ when they are preparing a donation (‘accept-by time’ will default to 30 minutes before the collection window ends but can be configured in Organisation settings). | ✓ | C3-3965 | ||
Mobile App | Donors using the mobile app will now see an error message if they try to select a collection window where the accept-by time has already passed. | ✓ | C3-3966 | ||
Mobile App | Charities using the mobile app will now see an ‘accept-by time’ when they are accepting a donation so that they know how much longer they have until they have before the offer expires. | ✓ | C3-3967; C3-4654 | ||
Mobile Notifications | We fixed a push notification bug where donor users who were alerted that a donation had been accepted, were incorrectly being directed to a page telling them that the offer was no longer available. | ✓ | C3-4554 | ||
Mobile Notifications | We fixed a push notification app that was reverting a user’s language preferences back to English. | ✓ | ✓ | ✓ | C3-4555 |
Mobile Notifications | We fixed a bug where charity mobile app users were seeing the old version of the ‘Feedback’ page when they clicked on the push notification for an offer that they had already accepted. | ✓ | C3-4684 | ||
Multicollector | We fixed a multicollector bug that was inhibiting waitlist charities using the web & mobile apps from immediately accepting the remaining available, permissible categories that a primary charity does not have permissions to accept. | ✓ | ✓ | C3-4536; C3-4776 | |
Multicollector | We fixed a bug that was inhibiting unscheduled charities from accepting categories of food on the Food Board where multicollector was enabled. | ✓ | ✓ | C3-4264 | |
Offers History | We made some formatting improvements to the Offers History Page on the Mobile App so that it’s easier to read. | ✓ | ✓ | C3-4578; C3-4667 | |
Offers History | We fixed a bug where FoodNet admins were able to see donations offered to a member charity that were offered by a donor in another network on the Offers History page. | ✓ | C3-4640; C3-4733 | ||
Offers History | We greyed out the ‘Member Manager’ User Filter for Food Net Admins looking at the Offers History page as this user type is not relevant for charities. | ✓ | C3-4643 | ||
Offers History | We made an improvement to the Offers History page so that users can now filter the page by Charity Branch name/official ID as well as Donor Branch name/official ID. | ✓ | ✓ | C3-4577 | |
Offers History | We added a ‘Offer Status’ filter to the Offers History page so that users can more easily filter by whether a donation is pending, completed, etc. | ✓ | ✓ | C3-4522 | |
Offers History | We added a ‘User View’ filter to the Offers History page to improve loading time. | ✓ | ✓ | C3-4468 | |
Reporting Performance | We made some changes in the backend in an effort to improve reporting performance. | ✓ | ✓ | ✓ | C3-4302; C3-4714 |
Reports | We fixed a bug that was affecting the Donor KPI Report whereby the ‘Total Rates’ columns and the ‘Planned Rates’ columns were not downloading correctly when filtered as a subset to the whole KPI Report selection. | ✓ | ✓ | C3-4564 | |
Reports | We fixed a bug where the filters were not working on the Food Category Report. | ✓ | ✓ | C3-4717 | |
Reports | We fixed a bug where Food Net users of the ‘Impact Summary Page’ were unable to see results if they selected ‘All Donors’ or a specific donor with the filter ‘All time’. | ✓ | C3-4055 | ||
Reports | We’ve added 3 new columns to the Product Logs report on Foodiverse: Collected date, Unit of Measure & Currency. | ✓ | ✓ | C3-4412 | |
Reports | We made improvements to the Donor Impact and the Donor KPI Reports so that the column names in the report exports will:
1) Match what is in the UI and 2) Translate in accordance with the user’s language preferences. | ✓ | ✓ | C3-4478; C3-4600; C3-4601; C3-4588; C3-4641; C3-4642 | |
Reports | We fixed a bug where Donor Admins using the Product Logs page were not being directed to the correct donation on the ‘My Donations’ page when they clicked the ‘View’ button. | ✓ | ✓ | C3-4530 | |
Reports | We fixed a bug where users of the Impact Summary report were unable to see ‘Month (Daily)’ data. | ✓ | ✓ | C3-4558 | |
Reports | We added a label filter with typeahead search capability to all reports (except the Product Logs) so that it’s easier to limit a search which will lead to performance improvements | ✓ | ✓ | ✓ | C3-4599 |
Reports | Where applicable, donors who do not provide all of the possible information about a product offered as part of a donation will see a blank input in the Product Logs Report as opposed to seeing the status ‘null’. | ✓ | ✓ | C3-4675 | |
SMS | We made a change that means that when a new user is created, their permissions will default to ‘Never Send SMS’. This can be changed in the user settings if required. | ✓ | ✓ | ✓ | C3-4625 |
Temporary Calendar | As a FoodNet Admins using the ‘Temporary Calendar’ feature can now create and amend Donation Windows without any regard to future ‘Temporary Calendar’ entries for the same day. | ✓ | ✓ | C3-4526 | |
Terms and Conditions | We have made an update to the terms and conditions of the Foodiverse app. Please see the new version here. | ✓ | ✓ | ✓ | C3-4721; C3-4722; C3-4724; |
Translations | We have continued our efforts to translate Foodiverse into Czech and Slovak. | ✓ | ✓ | ✓ | C3-4454; C3-4513; C3-4531; C3-4706 |
Web Performance | We improved the performance of the ‘Manage Donations’ page for Food Nets and the ‘Donations’ page for Donors by
1) Adding a User view filter which users are recommended to use to improve the speed of search results and 2) Introducing a ‘Search & Submit’ functionality whereby the user must enter their required filters before any results will appear | ✓ | C3-4562 | ||
Web Performance | We made an improvement to the loading time of the ‘Join a Food Net’ page in a number of ways, including removing the ‘My Branches’ section which was slowing down page performance. | ✓ | ✓ | C3-3686; C3-4647; C3-4648 |
12 October 2022 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.0.19 | Automatic update |
Web app | 3.0.19 | Automatic update |
Mobile iOS app | 3.0.19 | Automatic update |
Mobile Android app | 3.0.19 | Automatic update |
Middleware | 3.0.19 | No changes required |
APIs and Integrations | 3.0.19 | No changes required |
Category | Update | Donor | Charity | Food Net | Reference |
API Documentation | We have updated API documentation with more information on donation responses. | ✓ | ✓ | C3-4333 | |
Donation Record | A donation record (similar to the email receipt) will be available to view in the Foodiverse web app and mobile app.
It will be accessible in My Donations for Donors, Offers History for Charities and Manage Donations for Food Banks. A donation record will only show when a donation is either marked transferred or not transferred. If a donation is rejected or accepted only, a donation record will not be generated. Please see this Knowledge Hub article for more information | ✓ | ✓ | ✓ | C3-4231; C3-4432; C3-4308; C3-4362; C3-4775 |
Email Receipts | Email receipts from donors who provide categorised product detail will now appear in a similar format to the new donation record. | ✓ | ✓ | C3-4349 | |
eSignature | When turned on at donor level, mobile app users will be required to add an esignature when marking a donation transferred or not transferred.
Please see this Knowledge Hub article for more information. | ✓ | ✓ | C3-4343; C3-4290; C3-4291; C3-4369; C3-4287; C3-4289; C3-4292 | |
Mobile App | We removed the grey space appearing on the mobile app ‘Live Donations’ page. | ✓ | ✓ | C3-4429 | |
Mobile App | The ‘Transfer Time’ disappeared from the ‘Active Donation’ screen for charities in the last release. This has now been resolved. | ✓ | C3-4410 | ||
Mobile App | The Status Page wasn’t clickable in the mobile app when we upgraded android users in the last release. This has now been resolved. | ✓ | ✓ | C3-4354 | |
Mobile App | We have improved the look and feel of the Offers History page to make it more intuitive and responsive. This will also allow for the new Donation Record feature to be visible where appropriate.
Please see this Knowledge Hub article for more information | ✓ | C3-4011; C3-4015; C3-4017; C3-4452; C3-4374 | ||
Mobile App | We improved some of the flickering that users were experiencing on the mobile app. | ✓ | ✓ | C3-4300 | |
Mobile App | We improved the wording on the dashboard once a charity has accepted a donation. | ✓ | C3-4327 | ||
Mobile App | When a donor is using the mobile app to donate food, we have made the preselected ‘Transfer Time’ more prevalent on the mobile app page.
Please see this Knowledge Hub article for more information | ✓ | C3-4364 | ||
Mobile App | A small percentage of charity users were seeing a ‘null error’ on the Offers History page. This has now been resolved. | ✓ | C3-4345 | ||
Notifications | We have rearranged the order in which the notifications appear on the ‘Active Donations’ screen to ensure the most important notifications appear at the top of the screen.
The new order for charities will be:
The new order for donors will be:
| ✓ | ✓ | C3-4413 | |
Notifications | When language settings are changed, the notifications will now translate accordingly. | ✓ | ✓ | C3-4451 | |
Notifications | Some charities were experiencing a two minute delay between when an action appeared on the ‘Active Donations’ screens and when a push notification would appear. This should now be reduced to approximately 15 seconds. | ✓ | C3-4453 | ||
Product Details | Web app users will now see unit price details (when they are inputted) recorded in the ‘View Products’ pop-up modal on the ‘My Donations’ page. | ✓ | C3-4342 | ||
Reports | Food Bank and Donor users looking at the Donor Branches KPI report were unable to click ‘Next’ to view the next page. This has now been resolved. | ✓ | ✓ | C3-4216 | |
Reports | Some users of the Food Category report spotted differences between the KG estimate in the summary and impact details tabs. This has now been resolved. | ✓ | ✓ | C3-4389 | |
Reports | All of the indexed colours for the pie charts in the Food Category Report have been corrected.
Please see this Knowledge Hub article for more information | ✓ | ✓ | C3-4298 | |
System Performance | A performance improvement was implemented for customers using the uncategorised product level detail API | ✓ | ✓ | C3-4303 | |
System Performance | The way ‘No Posting’ records were being generated were slowing down the system’s performance. This has been improved. | ✓ | ✓ | C3-4307 | |
Temporary Calendar | When uploading temporary schedules, the system was not taking into account whether the existing permanent schedule for a store was marked active or inactive and was making all of the temporary schedules active. This has now been resolved. | ✓ | C3-4430 | ||
Temporary Calendar | The system was blocking users from creating new permanent schedules on a day where old temporary schedules had existed. This has now been resolved. | ✓ | C3-4132 | ||
Translations | Various improvements to the Slovakian and Czech translations have been made across the web and mobile apps. | ✓ | ✓ | ✓ | C3-4408;
C3-3976; C3-4378; C3-4400; C3-4305; C3-4454; C3-4371; C3-4377 |
User View | A knowledge base article has been written to better explain how the ‘User View’ feature works across the web app.
Please see this Knowledge Hub article for more information | ✓ | ✓ | ✓ | C3-3803 |
10 August 2022 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.0.18 | |
Web app | 3.0.18 | |
Mobile iOS app | 3.0.18 | |
Mobile Android app | 3.0.18 | |
Middleware | 3.0.18 | |
APIs and Integrations | 3.0.18 | We have consolidated product information in the Foodiverse PLD and cPLD tables. Customers using these APIs should check their integrations are working as normal and reach out to their account managers for more information if necessary. |
Category | Update | Donor | Charity | Food Net | Reference |
e-Signature | It is now possible for donors to configure their settings to require an e-Signature after a donation has been accepted. The ability to add e-Signatures on the mobile app will be available in next month’s release. | ✓ | ✓ | C3-4057;
C3-4085 | |
Email Receipts | From Thursday, one of our major donors will begin to categorise the products that they donate. This means that donation email receipts to charities from this donor will now include categorised product level detail. | ✓ | ✓ | n/a | |
Feedback Button | Charities will no longer be able to mark a donation as ‘Transferred’ on the Web or Mobile app. Instead, they will be able to provide feedback when a donation has not been successfully transferred by clicking the new ‘Feedback’ button. | ✓ | C3-4061: C3-4062 | ||
Mobile App Upgrade | We have upgraded the Android app which means that Android users who update their app to version 3.0.18 will be asked to sign in again. | ✓ | ✓ | n/a | |
Mobile App | We have made improvements to the mobile app notifications so that, when the app is closed and a push notification from Foodiverse appears, when the user clicks on the notification, it will bring them to the correct corresponding page. | ✓ | ✓ | ✓ | C3-3813 |
Mobile App | We have made improvements to the mobile app notifications so that, when the app is open and a pop-up message appears, when the user clicks on the message, it will bring them to the correct corresponding page. | ✓ | ✓ | ✓ | C3-3814 |
Mobile App | We have clarified the errors that users will see if they struggle to sign in to the mobile app so that the Tech Support Team can isolate the issue even faster. Please see this Knowledge Hub article for more information . | ✓ | ✓ | ✓ | C3-3855; C3-4022 |
Mobile App | When a charity accepts their offer, FoodBank Admin mobile app users will now see the message ‘Your donation has been successfully accepted by x charity’ on the ‘Your Active Donations’. | ✓ | C3-3900 | ||
Mobile App | When a food bank branch accepts a donation, the message in ‘Your Active Donations’ will update to say ‘Please confirm when the donation has been collected’. | ✓ | C3-3969 | ||
Product Level Detail | We made some improvements to how categorised product level detail is being captured in the database. For information on this, please contact our Tech Support Team, stating the reference C3-4097. | ✓ | ✓ | ✓ | C3-4097;
C3-3407; C3-4070 |
Reports | Food Net Admin or Food Net Users of the Charity KPI Report will no longer see the ‘Member Manager or Viewer’ option in the ‘User View’ dropdown as it is not relevant. | ✓ | C3-3882 | ||
Reports | In order to improve the new Food Category Report’s performance, we have limited the date filter’s range to 90 days. We are actively working to improve this so that we can eventually remove the limitation. | ✓ | ✓ | C3-4110 | |
Reports | To learn more about the food category report, check out this Knowledge Hub article. | ✓ | ✓ | C3-4046 | |
Translations | We have made improvements to the Czech and Slovak language translations in the Foodiverse web app. | ✓ | C3-4044;
C3-4123 | ||
Web App | For multicollector donations, offers were appearing as ‘Pending’ to waitlist charities in ‘Manage Donations’ even when the food available for them was ‘Unsuitable’. This has now been resolved. | ✓ | C3-3790 | ||
Web App | Users who select a different ‘User View’ from their default view, will now continue to see data as the selected ‘User View’ as they navigate throughout the platform. | ✓ | ✓ | ✓ | C3-3799 |
Web App | For multicollector donations, when all of the food has been collected by the primary charity, the waitlist charity’s status will update to ‘Accepted By Other’ in the ‘Manage Donations’ and ‘My Donations’ sections in the web app. | ✓ | ✓ | C3-4014 | |
Web App | Where a donor has offered a donation with product level detail at the beginning of the donation process, charity users of the web app can now view the products before accepting the donation. | ✓ | C3-4265 | ||
Web App | Charity web app users can now search food donations by county on ‘My Food Bank Network’ by clicking on ‘Advanced Filters’ | ✓ | C3-3988 |
20 July 2022 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.0.17.2 | |
Web app | 3.0.17.2 | |
Mobile iOS app | 1.0.45 | |
Mobile Android app | 1.6.3 | |
Middleware | 3.0.17.2 | |
APIs and Integrations | 3.0.17.2 |
Category | Update | Donor | Charity | Food Net | Reference |
*New* Reports | The Food Category Report is now available for Foodiverse donors and food banks. This report allows users to view a breakdown of their donations by food category according to estimate and actual weight and price. | ✓ | ✓ | C3-3159 | |
Middleware | We have made some improvements to the Foodiverse Middleware to improve its reliability and performance. | ✓ | ✓ | C3-4221; C3-4209 |
29 June 2022 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.0.17 | |
Web app | 3.0.17 | |
Mobile iOS app | 1.0.45 | |
Mobile Android app | 1.6.3 | |
Middleware | 3.0.17 | |
APIs and Integrations | 3.0.17 |
Category | Update | Donor | Charity | Food Net | Reference |
Accept-by Time | Donor branches creating donations in the web app will see an improvement to how the system reflects the relationship between the ‘accept by time’ and the ‘collection window’. | ✓ | ✓ | C3-3894 | |
Accept-by Time | We have made some improvements to how the web app informs a donor branch user that they cannot proceed with a donation because their ‘accept by time’ is in the past. | ✓ | ✓ | C3-3896 | |
Donation Management | We have added a tooltip to help explain the difference between ‘actual’ and ‘estimated’ data on the Manage Donations Page, the My Donations Page and the Offers History Page. | ✓ | ✓ | ✓ | C3-3640
C3-3641 |
iOS app | We have updated the knowledge hub article on how to sign into and use the to iOS / iPhone Charity App | ✓ | C3-4056 | ||
Reporting | After the June 1st deployment, Donor KPI report columns were not downloading in full. This has been resolved. | ✓ | ✓ | C3-4054 | |
Reporting | We created a prototype report to help users better report on scheduling, specifically donation and collection windows. For users external to FoodCloud, this report is available on request via TST. | ✓ | C3-3963 | ||
Reporting | We have updated the knowledge hub article related to Foodiverse KPI reports and Foodiverse Impact reports | ✓ | ✓ | ✓ | C3-3992 |
Reporting / APIs | Previously, donors using the multicollector feature and the PLD APIs could only technically offer one food classification to one charity. This has now been resolved so that food can be accurately reported on when multiple collectors receive food from the same food classification as part of the same donation. For example, if a primary charity is offered all of the ambient food and the waitlist charity is offered all of the chilled food, if the primary charity cannot take all of the ambient food, the remaining ambient food can be given to the waitlist charity and accurately reported on. | ✓ | ✓ | ✓ | C3-4018 |
Schedule Management | We have created a knowledge hub article that explains how to extend a collection window across 1-7 calendar days | ✓ | C3-3997 | ||
Temporary Schedule Management | We made an improvement to the Temporary calendar CSV file upload to reduce the likelihood of an error message appearing. | ✓ | C3-4007 | ||
Temporary Schedule Management | In the June 1st release, we made it possible to extend a collection window over 1 to 7 calendar days in the permanent schedule. This is now also possible in the temporary schedule. | ✓ | C3-3958 | ||
User View | The ‘user view’ filter will now default based on the user type you are logged in as. For example, if you are logged in as an Org Admin, the results of the web app pages where this filter applies will default to the ‘Org Admin’ filter. The intention is that this will reduce the number of clicks for web app users. Web app users can continue to filter by other user view filters if they wish. | ✓ | ✓ | ✓ | C3-3798 |
01 June 2022 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.0.16 | Automatic update |
Web app | 3.0.16 | Automatic update |
Mobile iOS app | 1.0.45 | 15th June 2022 – Automatic update |
Mobile Android app | 1.6.3 | |
Middleware | 3.0.16 | Automatic update |
APIs and Integrations | 3.0.16 |
Category | Update | Donor | Charity | Food Net | Reference |
Android Mobile App | We have updated the Foodiverse Android Charity User Guide which can be found here: | ✓ | C3-3853 | ||
Android Mobile App | We have updated the Foodiverse Android Donor User Guide which can be found here: | ✓ | C3-3949 | ||
iOS Mobile App | Donor and food bank users of the ios app were not seeing reminders to donate when a donation window was scheduled. This has been resolved. | ✓ | ✓ | C3-3808; C3-3809 | |
iOS Mobile App | Users of the iOS app will no longer see a ‘view’ button on their dashboard when they are offered ‘unsuitable’ food donations or when they are being alerted that the donor does not have food to donate for a planned transfer window. | ✓ | ✓ | C3-3821 | |
iOS Mobile App | iOS mobile app users can now refresh the results on their dashboard to see any new notifications or reminders that might have just been posted to Foodiverse. | ✓ | ✓ | ✓ | C3-3823 |
iOS Mobile App | Donor iOS mobile app users will no longer need to select the branch from which they wish to make a donation, provided that the user signed-in only has permissions to donate on behalf of a single branch. | ✓ | C3-3825 | ||
iOS Mobile App | We made some language improvements to the iOS mobile app for Czech and Slovak users | ✓ | ✓ | ✓ | C3-3887 |
iOS Mobile App | iOS mobile app users can now see the address of a donor that has offered them a donation in the ‘Offers History’ section of the app. | ✓ | C3-3933 | ||
iOS Mobile App | Food Bank branches can now accept donations via the iOS Mobile App | ✓ | C3-3960 | ||
BETA App | Mobile app users that wish to use the BETA version of the mobile app for testing purposes can now do so as part of the new region selector on the mobile app. This will appear to users downloading the app for the very first time. For more information on how this works, please see this knowledge base article: | ✓ | ✓ | ✓ | C3-3661; C3-3662; C3-3659; C3-3658; C3-3836; C3-3858 |
Donation Management | To help with the performance and user experience of the ‘Manage Donations’ page, users will now input their filters and click submit before any data will load and appear to the user. | ✓ | C3-3869 | ||
Donation Management | We have made some improvements to how the timestamps appear in the ‘Manage Donations’ page on Foodiverse. For a better understanding of the changes and what each timestamp means, please see this knowledge hub article: | ✓ | C3-3775 | ||
Donation Management | Donors using the web app can now cancel out of the ‘Create or Edit PLD’ section when creating a donation with PLD. | ✓ | ✓ | C3-3679 | |
Labels | We have replaced the label filter with a ‘type and search’ instead of a dropdown as for some organisations, they had over 100 label options which meant they would often struggle to find the label they were looking for. | ✓ | ✓ | ✓ | C3-3778 |
New Feature | Donor’s can now configure the time by which they wish a charity to respond to a donation offer to between 0-90 minutes before the donor’s collection windows end. This time is known as the ‘Accept-By Time’ and is configurable in the Donor Organisation’s settings. It will default to 30 minutes before the donor’s collection windows end for all donors.
See Knowledge Hub article here Please note: Aspects of this feature are still in development. The ‘accept-by time’ configuration has passed testing for temporary schedules, however, by the next release, it should also be functioning on extended temporary collection windows. By the August release, we hope to improve the mobile app UI for charities and donors so that they are clear about the expected Accept-by Time. | ✓ | ✓ | C3-3881 | |
Product Level Details | The ‘Create PLD’ API docs have been updated. See here | ✓ | ✓ | C3-3846 | |
Reports | Donor Organisations can now configure their process success, posting compliance and food offered KPIs to highlight as red, amber or green depending on their own parameters. This can be configured in the Donor Organisation settings and will be reflected in the Donor Branch KPI report.
Instructions on how to configure this can be found here: Please note that this will not be available in Food Net reporting. | ✓ | ✓ | C3-3526; C3-3729; C3-3730 | |
Reports | As a donor with a donation window ending at 23:59, when I did not post a donation where an active donation window exists, a ‘No posting’ flag was not being not generated which affected KPI reports because ‘No postings’ help to calculate donor compliance in the KPI reports. This has now been resolved, however, please note that ‘No postings’ are generated approximately 5 minutes after an active donation window ends so it is important to be careful when planning active donation too close to midnight. | ✓ | ✓ | C3-3728 | |
Reports | Impact and KPI report users should now see a ‘totals’ row when they export their reports from Foodiverse. | ✓ | ✓ | ✓ | C3-3735 |
Reports | An improved filter has been added to the Donor KPI Report so that users can now select which columns they wish to analyse. This will hopefully allow users to better tailor the report to their needs and simplify the data they wish to view. | ✓ | ✓ | C3-3764 | |
Reports | To help with the performance and user experience of all Donor and Food Bank reporting, users will now input their filters and click submit before any data will load and appear to the user. | ✓ | ✓ | C3-3643 | |
Reports | Additional filters and columns were added to the PLD report available on Metabase to support users in finding the information that they need | ✓ | ✓ | C3-3761 | |
Reports | Donor KPI Summary Report users can now download the data in the trend graph and the donation funnel based on the selected filters. For more information on how these graphs work, please see this knowledge base article: | ✓ | ✓ | C3-3467; C3-3954 | |
Schedule Management | Food Bank administrators can now extend collection windows to span between 1-7 calendar days. This means that if a food bank is working with a donor who would like their collection window to stretch over a number of days (to a maximum of 1 week), this is now possible. In order to extend a collection window, please edit it and add the number of days by which you would like the window to extend.
Please note: This is not yet available on the temporary schedule but it should be included in the next release. | ✓ | ✓ | C3-3230 | |
User View | We have changed the ‘View Mode’ filter to be called ‘User View’ and for the dropdown to reflect the Foodiverse user types so that it is more clear what this filter’s function is. For certain pages on Foodiverse, the data will need to be filtered by user type which is why this filter exists. | ✓ | ✓ | ✓ | C3-3794 |
20th April 2022 – Product Update
Here’s what’s new in Foodiverse.
Component | Current Version | Change Notes |
Platform (backend) | 3.0.15 | Automatic update |
Web app | 3.0.15 | Automatic update |
Mobile iOS app
Mobile Android app | 1.0.44
1.6.3 | (20/05/2022) Automatic update
No change |
Middleware | 3.0.15 | Automatic update |
APIs and Integrations | 3.0.15 | Automatic update, no deprecations |
Category | Update | Donor | Charity | Food Net | Reference |
Bug | Donors using the web app were unable to mark an accepted donation as ‘Transferred’ or ‘Not Transferred’. This has now been resolved. |
✓ | C3-3588 | ||
Bug | Where a Charity Organisation has multiple branches, with memberships in different Food Nets, the charity branches were able to see Food Board offers from all of the Food Nets when they should only see Food Board offers from the Food Net they are a member of. This has now been resolved. |
✓ | C3-3543 | ||
Bug | Some Foodiverse Food Bank users were unable to see the Offers Table in the ‘Manage Donations’ page. This issue has now been resolved. |
✓ | C3-3685 | ||
Email Receipt | Where donors provide a breakdown of the specific products they donated via an integration with Foodiverse, this information was not included in the email receipt shared with donors and charities. This issue has now been resolved so that charities and donors will now see the product breakdown (PLD) in their email receipt. |
✓ |
✓ |
✓ | C3-3703 |
Multicollector Improvement | Improvements were made so that integrated charities (webhook) will only see Waitlist offers after the offer exclusivity time (typically 30 minutes) has passed. |
✓ | C3-3669;
C3-3673 | ||
Multicollector Improvement | Improvements were made to ensure that waitlist charities will not receive food offers if 1) max collectors has been reached and/or 2) if the primary charity has accepted all of the available food categories. |
✓ | C3-3265 | ||
Push Notifications | Some charities were receiving the corresponding push notification that was meant for donors app users such as ‘Charity X has accepted your donation’. This issue has now been resolved. |
✓ | C3-3218 | ||
*New Report* | Donor and Food Bank Report users will now have access to a new ‘Donor Organisation KPI Summary’ landing page when they navigate to the ‘ Donor Branch KPI Report’. This landing page summaries Donor KPI trends in accordance with the filter inputs. The original report can be viewed in the second tab labelled ‘Donor Organisation KPI Report’. |
✓ |
✓ | C3-3447;
C3-3458; C3-3597 | |
Reports | Some improvements were made to the loading time of the reports. We will continue to work to improve the latency issues. |
✓ |
✓ |
✓ | C3-3723 |
Reports | Reporting users can now add a ‘File Description’ when downloading reports in order to make it easier to find and distinguish between reports once they’ve been downloaded. This file description sits alongside the automatically generated file name. |
✓ |
✓ |
✓ | C3-3736 |
Reports | Improvements have been made to the ‘totals’ table available as part of the Foodiverse KPI and Impact reports. The figures should now include commas to make them easier to read and they should also wrap within the table cells so that they do not overspill within the Totals table. |
✓ |
✓ |
✓ | C3-3358 |
Reports | Some improvements were made to the KPI reports to ensure that the columns are less likely to misalign with the first row in the table. |
✓ |
✓ |
✓ | C3-3748 |
Reports | Food Net Member Viewers and Managers as well as Donor Org Branch Users and Viewers can download the data in the ‘Impact Bar Chart’ and the ‘Top Performer Chart’ in the ‘Donor Impact Summary Report’ based on the selected filters into a csv file. |
✓ |
✓ | C3-3465 | |
Reports | Some KG data discrepancies were found between the Donor Impact Summary page and Donor Impact Detailed Report. These discrepancies have been addressed and resolved. |
✓ |
✓ | C3-3705 | |
Web App | Some donor users were experiencing issues with being locked out of their accounts relatively regularly. This issue has now been resolved. |
✓ | C3-3719; C3-3722 | ||
Web App | Users in the UK and Ireland may have noticed timing discrepancies in the ‘My Donations’ and ‘Manage Donations’ pages. This was a result of daylight savings time and has now been resolved. |
✓ |
✓ | C3-3802 | |
Web App | Where users were using a ‘search type-ahead’ filter in the Foodiverse web app (such as that found on the ‘Create a Donation’ page), the Chrome browser ‘autofill’ was hiding the results. This has now been resolved. |
✓ |
✓ |
✓ | C3-3721 |
23 February 2022 – Product Update
Here’s what’s new in Foodiverse.
iOS version 1.0.43 – Android version 1.6.3
Category | Update | Donor | Charity | Food Net | Reference |
New Feature | Donors wishing to confirm the products that they donated to recipients AND for the weight of those products to be reflected in the donation’s impact and impact report to ensure more accurate reporting, can now do so via the categorised product level detail integration. The new ‘actual’ donation data will be visible in the web app to the food net, donors and orgs where an integration exists. If this integration does not exist, the data will appear as ‘estimates’. | ✓ | ✓ | ✓ | C3-3409;
C3-3408; C3-3606; C3-3594; C3-3521; C3-3604; C3-3412- C3-3422 |
Bug | The ‘SMS’ icon disappeared from the ‘Manage Donations’ UI for Food Net users. This has now been resolved. | ✓ | C3-3564 | ||
Bug | If a donation was rejected by a primary charity, the donation offer was appearing on the waitlist charity’s dashboard but a push notification was not being sent until 30 minutes had lapsed since the offer was made. THis has now been resolved so that charities will receive a push notification as soon as the primary charity rejects the donation. | ✓ | C3-2838 | ||
Bug | Donor users using the web app to create a donation were experiencing issues with donation transfer windows if they clicked ‘Back’ after inputting the donation quantities. This has now been resolved. | ✓ | C3-3037 | ||
Data Deletion | Updates to our internal processes will better support users that want to delete their personal information from FV, this aligns with new Google Play and Apple Store requirements. | ✓ | ✓ | ✓ | C3-3531 |
Improvement | In order to improve donor user experience, they will now be able to see which charities are assigned to which transfer windows (Web only). | ✓ | C3-3605 | ||
Improvement | Donors can now notify charities when they have no food available on days where they are not scheduled to post a donation (ie an inactive donation window is in place) | ✓ | ✓ | C3-3142 | |
Improvement | In order to improve the charity experience of where a donor offers multiple transfer window options to a charity, charities will now only see transfer window options in the future. Past transfer window options will ‘expire’ once the time has lapsed. | ✓ | C3-2588 | ||
Mobile App (iOS only) | On the iOS app, if a charity is sent a ‘No Availability’ notification, they can now click the view option to see which donor notified them. | ✓ | FCAPP-248 | ||
Mobile App (iOS only) | Donors using the iOS app will once again be able to input category quantities/figures rather than having to click the +/- buttons. | ✓ | FCAPP-301 | ||
Mobile App (iOS only) | From now on, it will be clearer to donors using the iOS app when a charity has marked a donation as transferred before they have had the chance to do so. | ✓ | FCAPP-289 | ||
Mobile App (iOS only) | From now on, primary and waitlist charities using the iOS app will be updated if a donation is accepted by a charity via the foodboard | ✓ | FCAPP-280 | ||
Mobile App (iOS only) | From now on, donations on the iOS app that have been marked as transferred will appear as ‘transferred’ instead of ‘collected’ in order to account for the scenario where a donation may have been delivered. | ✓ | ✓ | FCAPP-282 | |
Mobile App (iOS only) | On the iOS app, we’ve improved the appearance of the ‘donation statuses’ and the page titles so that they are easier to read in other languages and on smaller screens. . | ✓ | ✓ | FCAPP-271FCAPP-272 | |
Multicollector Improvement | In order to improve the charity user experience where multiple collectors can pick-up food, charity users will only be shown the collection windows that they are scheduled for as a default. | ✓ | C3-3217
FCAPP-290 | ||
UI Simplification | As part of the on-going UI simplification project, the Donations Menu Option under Manage Network Members has been removed. | ✓ | |||
Reports | In order to improve the performance of the Donor Impact Report, report users will now input their filters and click submit before tables and data will populate. | ✓ | ✓ | C3-3538;
C3-3539 | |
Reports | In order to improve the visualisation of data, a new donor impact summary page has been added to the Impact Report. | ✓ | ✓ | C3-3435
C3-3433 C3-3432 C3-3357 C3-3346 C3-3345 | |
Temporary Calendar and Temporary Schedules | All users will now see where a temporary calendar entry is in place on the web app on the new schedules widget on the top right hand side of the dashboard. Temporary schedules are also easier to edit and view in the UI in the ‘Manage Temp. Cal Schedules’ section for Food Nets and the ‘ and easier to view in the ‘Schedules’ section for Donors and Charities. | ✓ | ✓ | ✓ | C3-3442
C3-3327 C3-3323 C3-3478 C3-3441 C3-3440 C3-3569 |
Testing Improvement | As the platform grows and develops, we are working in the background to improve our automated testing. | ✓ | ✓ | ✓ | C3-3514 |
Web App | Based on feedback from users, we have replaced the term ‘Tag’ with the term ‘Label’ across the web apps front-end to improve the platform’s intuitiveness for users. | ✓ | ✓ | ✓ | C3-3281 |
20 January 2022 – Product Update
Here’s what’s new in Foodiverse.
Category | Update | Donor | Charity | Food Net | Reference |
New Feature | Donors wishing to input and save product level detail into the web app so that they can associate their products with future donations (across different browsers) can now do so as a result of the new Product Database. | ✓ | ✓ | ✓ | C3-3411
C3-3404 C3-3410 |
Middleware | Donors using the middleware were experiencing issues when posting donations into inactive donation windows. This is now resolved. | ✓ | C3-3437 | ||
Mobile App (Android only) | Donors, using the app on an android device, who posted a ‘No Availability’ offer were seeing a ‘view’ link after posting this offer which would lead them to a blank screen. This ‘view’ link has now been removed. | ✓ | C3-2814 | ||
Mobile App (Android only) | Donors, using the android app, who marked a donation as transferred after another user or charity had marked it transferred were receiving an error message. This has now been resolved so that donors should see the following message: Sorry, this action is not available. Someone may have already marked this offer transferred | ✓ | C3-3273 | ||
Mobile App (iOS only) | Donors, using the app on an iOS device, posting an unplanned donation were not being offered a future ‘transfer’ window to select and so had to create a custom transfer window. This has now been resolved so that when an unplanned donation is being posted, a selection of future transfer windows appear to the donor to select from. | ✓ | FCAPP-283 | ||
Mobile App (iOS only) | Donors, using the app on an iOS device, were experiencing issues posting food as they had to input food categories twice in order to be able to post successfully. This issue has now been resolved. | ✓ | FCAPP-287 | ||
Reports | In the Daily Compliance report, the calculation for posted donations was actually showing the number of offers made (one donation can be offered to multiple recipients). This has now been rectified. | ✓ | ✓ | C3-3195 | |
Reports | Food Net and Donor Report users will now see a new ‘totals’ feature on the Impact and KPI reports | ✓ | ✓ | C3-3430
C3-3244 | |
Reports | As per user requests, we have updated training material on how to interpret the donor KPI report. These can be accessed here on our Knowledge Hub. | ✓ | ✓ | C3-2810 | |
Temporary Calendar and Temporary Schedules | We have made a number of UI improvements to the donor temporary calendar feature to ensure that bulk changes are easier to review and that individual dates can be edited after applying bulk changes. | ✓ | C3-3316- 3321
C3-3264 C3-3284 C3-3287 C3-3325 C3-3355 C3-3400 | ||
Translations | Additional translations into Czech and Slovak have been made to the web app, android app and the site terms & conditions | ✓ | ✓ | ✓ | C3-3118 C3-2555 C3-2677
C3-3085 C3-3087 FCAPP-212 FCAPP-213 |
Web App | In the country dropdown on the Foodiverse registration page and the ‘manage organisation’ page, the countries will now appear in alphabetical order making it easier to choose from. | ✓ | ✓ | ✓ | C3-3153 |
Web App | The UK was not appearing in the country dropdown on the oodiverse registration page and the ‘manage organisation’ page. This has now been resolved. | ✓ | ✓ | ✓ | C3-3399 |
Web App | Donor Admin users using the ‘My Memberships’ page will now be able to filter by membership status. | ✓ | C3-2950 |
01 December 2021 – Product Update
Here’s what’s new in Foodiverse.
Category | Update | Donor | Charity | Food Net | Reference |
New Feature | Food Net Admins can now update donor schedules temporarily to reflect temporary changes to donor schedules. This will benefit donors who wish to update their schedules over the holiday period. | ✓ | ✓ | ✓ | C3-3177- C3-3189; C3-3240 |
Donation Status | Based on charity feedback, we now no longer show offers with the ‘Accepted By Other’ status on the Offers History page. | ✓ | ✓ | C3-2841 | |
Food Net Memberships | We have upgraded the performance of the membership page so that the data loads more quickly. This is also relevant for customers with integrations. | ✓ | C3-2845 | ||
Mobile App | The Donation details page titles on the iOS and Android apps will now distinguish when the details are referring to a ‘Live’ donation (a donation that is currently available to accept) and a ‘Previous’ donation (a donation that was accepted in the past). | ✓ | ✓ | FCAPP-240
C3-3076 | |
Mobile App (Android only) | Further improvements have been made to the android app Czech and Slovakian translations. | ✓ | ✓ | ✓ | C3-3066
C3-3067 |
Mobile App (iOS only) | iOS users will see changes to the options shown to them when they choose to mark a donation as ‘Not Transferred’. This change was made to align the iOS app with the android app. | ✓ | ✓ | FCAPP-273 | |
Mobile App (iOS only) | iOS app Charity Users will now see the relevant branch name when viewing the Waitlist Offers page. This change was made to align the iOS app with the android app. | ✓ | ✓ | FCAPP-251 | |
Mobile App (iOS only) | iOS Donor users were not getting reminders to post donations when a schedule is in place. This has been fixed. | ✓ | FCAPP-261 | ||
Mobile App (iOS only) | iOS Charity users were being brought to the incorrect screen when they received a push notification about a donation from a donor. This has been fixed for Primary scheduled charities. This will be fixed for Waitlist scheduled charities in a subsequent release. | ✓ | ✓ | FCAPP-230 | |
Mobile App (iOS only) | We have updated our platform to allow iOS app users to logout of the app without experiencing issues. | ✓ | ✓ | ✓ | C3-3164 |
Mobile App (iOS only) | iOS Donor users were unable to see their food classification allowances when adding food categories to a donation. This has now been fixed. | ✓ | ✓ | FCAPP-206 | |
Reports | Some iterative performance improvements have been made to help speed up the time it takes to export Foodiverse reports. Further performance improvements will be made in subsequent releases. | ✓ | ✓ | C3-3207 | |
Schedules | Donor branches that have moved to a different network may have experienced issues viewing their schedules. This is now resolved. | ✓ | C3-3222 | ||
Web App | On the web app, the ‘Offered at’ Timestamp for Waitlist charities will now be clearer as it will only include a timestamp if the offer was offered to the waitlist before the primary charity has accepted it. | ✓ | ✓ | ✓ | C3-2841 |
Web App | Donors who are admin for multiple donor branches and who are using the web app to donate food will now have the ability to type the name of their branch in the ‘Create Donation’ modal as a quicker search solution. | ✓ | ✓ | C3-2993 |
03 November 2021 – Product Update
Here’s what’s new in Foodiverse. For each change, the check marks which user types are affected.
Category | Update | Donor | Charity | Food Net | Reference |
Bug / High Priority | Since our last release, many donor and charity users were experiencing issues with logging into the app. This issue has now been resolved. | ✓ | ✓ | C3-3140 FCAPP-263 | |
Bug / High Priority | Charities will no longer see offers that were accepted by other charities in their ‘Offers History’ | ✓ | C3-2903 | ||
Bug / High Priority | The ‘Impact’ data on the web app dashboard was overcounting where multiple offers to charities had taken place. This is now fixed. | ✓ | ✓ | ✓ | C3-3148 |
Bug / Notifications | Links to the Foodiverse app within email notifications have been updated to show the correct corresponding web/app page | ✓ | ✓ | C3-3054 | |
Bug / Notifications | ‘Please post’ reminders were continuing to display to donors with inactive donation windows. This issue has now been resolved. | ✓ | C3-3146
C3-3196 | ||
Bug / Reports | Users who use the Product Logs report on the web app were unable to click the magnifying glass icon to be brought to the original donation reference. This issue has now been resolved. | ✓ | ✓ | C3-3030 | |
Bug / Web App | The accept by time was not displaying on the ‘Selected for You’ section of the web app. This has been fixed. | ✓ | ✓ | C3-3138 | |
Bug / Web App | Donors who tried to enter product level detail and then changed their mind were unable to progress their donation. This has now been fixed. | ✓ | C3-3069 | ||
Bug / Web App | The web app login page will no longer need to be refreshed upon login | ✓ | ✓ | ✓ | C3-2664 |
Mobile App
(iOS only) | We conducted a comparison of the iOS and Android apps and found that the ios required some development in order to align with the Android app. iOS users will now experience an app that is more aligned with that of the Android app.
Reference: FCAPP-260, FCAPP-252-254, FCAPP-249, FCAPP-245-247, FCAPP-239-243, FCAPP-236 , FCAPP-235, FCAPP-233, FCAPP-224-229, FCAPP-222, FCAPP-221, FCAPP-218, FCAPP-199 | ✓ | ✓ | See update column. | |
Mobile App | The apps are now available in Slovakian and Czech languages. Language settings can be updated in the settings section of the mobile app. | ✓ | ✓ | C3-2681
C3-3062 FCAPP-217 FCAPP-216 | |
Mobile App | Charity users may see the new status ‘voided’ in their Offers History. This occurs where a request has been made to remove a donation offer in the case of duplication or error. | ✓ | FCAPP-205 | ||
Mobile App | ‘No Availability’ and ‘Unsuitable’ notifications will now appear in the ‘Pending Actions’ section of the app dashboard as well as in ‘Offers History’ page. | ✓ | C3-3049
C3-3039 FCAPP-215 | ||
Reports | Users who use the Foodiverse reports will now see a link to a reporting glossary so that they can look up the definitions for specific data columns and KPIs | ✓ | ✓ | C3-2182 | |
Reports | Users have requested that donations migrated from the old app to the new app which are visible in ‘Offers History’ and ‘My Donations’ reflect the correct date. This work has been completed. | ✓ | ✓ | ✓ | C3-2215 |
Reports | ‘Unsuitable’ and ‘No Availability’ responses were not being recorded as part of KPI reporting for charities. This has now been resolved. | ✓ | C3-2749 | ||
Security | Mobile app users will no longer have to log in every 7 days, they will have to log in every 90 days | ✓ | ✓ | ✓ | C3-3012 |
Testing | The Foodiverse engineering team have been making improvements to the testing that takes place before deployments. As the Foodiverse platform grows, more and more testing is required so this automated testing improvements will help to make testing even more reliable and efficient. | ✓ | ✓ | ✓ | C3-1417
C3-3047 C3-3108 C3-3137 |
Web App | The Foodiverse Registration page has been improved to make it more explicit which phone number will receive SMS updates | ✓ | ✓ | ✓ | C3-2355 |
Web App | In ‘Manage Donations’, the accept by time will now show the exact time and date by which the donation should be accepted by. This was replaced by the number of hours and minutes left. | ✓ | C3-2874 |
06 October 2021 – Product Update
Here’s what’s new in Foodiverse. For each change, the check marks which user types are affected.
Category | Update | Donor | Charity | Food Net | Reference |
Donation Receipt Email | Based on the introduction of additional food safety law in the UK, we introduced some additional features to cater for allergen information which can be provided by the donor and sent to the charities in the donation receipt email | ✓ | ✓ | C3-2969 | |
Donation Receipt Email | The donation receipt email has been updated with additional information such as donor name, collection times etc for further traceability and transparency | ✓ | C3-3071 | ||
Donation Receipt Email | The donation receipt email is now sent to the donor’s branch admins as well as charity’s branch admins. | ✓ | C3-3071 | ||
Reporting | Based on the new Voided donation status, we updated our KPI reports to exclude any Voided donations from the donation-related KPI columns for more accurate representation of KPI data. | ✓ | ✓ | C3-3068 | |
Bug / Product Data Entry | Users adding Product Level Detail at the start of the donation process were unable to alter the existing product records. This has now been resolved | ✓ | C3-3094 | ||
Bug / Product Data Entry | Users who logged out had to re-enter their list of product records which could be used for adding products to a donation. This has now been resolved. | ✓ | C3-3065 | ||
Bug / Donation Reminder | Donors who had inactive donation windows had NoPost records generated when they did not post for that window. This was unintended and is now resolved. | ✓ | C3-3110 |
22 Sept 2021 – Product Update
Here’s what’s new in Foodiverse. For each change, the check marks which user types are affected.
Category | Update | Donor | Charity | Food Net |
New Feature | Food Net Managers will now be able to mark donations windows ‘active’ when they should be tracked in KPI reports. They will also be able to mark donations as ‘inactive’ to flag that the donation window is available for recruitment but should not be marked active until a primary or waitlist charity (depending on the established organisation preference or configuration) is recruited to a corresponding transfer window. | ✓ | ✓ | |
New Feature *Beta | Food Net Managers can now mark donations as ‘void’ when it is established that a donor posted multiple times by mistake. This will ensure that these donations are then discounted from Impact Reporting for Food Nets, Charities and Donors. | ✓ | ✓ | ✓ |
New Feature *Beta | Donor users of the web app will now be able to input product level detail whilst they post a donation. | ✓ | ||
Web App | Users registering on the Foodiverse web app will now be able to choose their language settings. For the time being, English is the only language available. | ✓ | ✓ | ✓ |
Web / Mobile Apps | For security purposes, users logging into the Foodiverse web or mobile app will now be asked to reset their password after 5 failed attempts to log in. This new security requirement will help to protect user data. | ✓ | ✓ | ✓ |
Mobile Apps | The mobile apps are now integrated with FoodCloud’s status page so that the technology team can communicate to app users if there are any updates or issues users should be aware of. Status page updates will appear as an orange alert on the app. | ✓ | ✓ | ✓ |
Mobile Apps | Charity mobile app users will notice a change in language on the Foodiverse App Dashboard as follows: Selected for you → Waitlist Offers Foodbank Network → Network FoodBoard Offers Public FoodBoard → Other FoodBoard Offers | ✓ | ||
Mobile Apps (Android Only) | Android charity app users will notice a change to language on their app. ‘Time left’ will now appear as ‘Accept By’ so that it will now be clearer to charities by which date and time they need to accept the donation before it expires. | ✓ | ||
Mobile Apps (Android Only) | Android app users will now be able to view their personal and branch details in the ‘My Profile’ section. | ✓ | ✓ | |
Mobile Apps (Android Only) | When creating a custom or ad-hoc transfer window, android donor mobile app users can now type the name of a charity into a search box in order to find a specific charity that they wish to donate to. | ✓ | ||
Mobile Apps (Android Only) | From now on, the android app will only be supported on devices with the Android 5.0 version of the operating system or higher installed. | ✓ | ✓ | |
Mobile Apps (iOS Only) | iOS mobile app users may have experienced difficulties accepting donations when they configured their zoom settings to 2.5x or to 3.0x the screen size. This has now been resolved. iOS mobile app users may continue to experience difficulties if their type/lettering is enlarged. We are continuing to work on resolving this issue. | ✓ | ✓ | |
SMS | For SMS users, the number they see in the donation text message in order for them to respond (e.g. Y[number] and N[number]) will now reset to 1 on a nightly basis provided they have accepted all current offers. | ✓ | ||
Integration Bug Fix | Some donors, whose in-store devices are integrated with the Foodiverse system, were experiencing a bug where charity chilled permissions were not translating from Foodiverse’s system to their device. This update will resolve this issue. | ✓ | ✓ |
*Beta – This is a prototype feature and will require further development.
Foodiverse Product Update: 25 Aug 2021
Here’s what’s new in Foodiverse. For each change, the check marks which user types are affected.
Category |
Update |
Donor |
Charity |
Food Net |
UI/UX |
It was discovered that donors were permitted to donate food from categories with classifications they weren’t approved for. This was prioritised due to food safety implications and is now fixed. | |||
UI/UX |
Filtering bug fixed: You can now filter donation data by end state and it works properly. It no longer defaults to Quarantined. We have also included the day of the week beside each donation date, to give more context to the date. | |||
Mobile Apps |
We prepared a translation file so that the Android app can be translated into new languages. | |||
Integrations |
One retailer wanted to add “Chilled” food category as one of their default options at the integration level. This is completed. | |||
Integrations |
We investigated and built improvements to suppport stability and performance in the Middleware. We delpoyed multiple patches to the Middleware release containing these improvements. | |||
Integrations |
We completed a technical guide on how to post donations in bulk to enable partners and internal users. | |||
Notifications |
Bug fix: We turned on donation reminders for charities who have selected to receive them. | |||
Notifications |
Due to small a configuration error, SMS was temporarily broken. This is now fixed. | |||
DevOps |
Configuration: We set up Metabase (program that allows us to search for and view platform insights) on Azure in our UAT and QA Environments. |
Foodiverse Product Update: 22 June 2021
Important update to the Foodiverse Platform
Foodiverse User Logins
We are making an important update to the platform. This will cause all users to be logged out after tonight’s donations. Please log back in tomorrow morning to continue with donations as usual.
We are upgrading our user authentication system to improve the reliability of the platform. Thank you for understanding and we apologise for the inconvenience caused.
Foodiverse Product Update: 2 June 2021
Here’s what’s new in Foodiverse
Foodiverse Web App
- Donors posting donations from the web app are now prompted to post an unplanned donation if they do not have an expected donation window on their schedule that day.
- In the web app, the “Received” status should not be visible to platform users. This was a bug that was confusing to some platform users. We removed the “action” pop-up dialog that sometimes asked users to mark a donation as “Received.” This status relates to when a posted donation is received by the platform, not when the food offer is physically received by the charity.
- The “Contact Us” link on the Foodiverse web app now leads to the contact page in the Knowledge Hub, rather than directly creating a Partner Support email which is a tech support inbox that is being decommissioned. Information on how the platform works and who to contact if you require support can be found on the Knowledge Hub or at foodiverse.net/help-centre
- The Donation reference ID was not appearing on the Food Board for all users, even though there was a space for it. This reference ID is now visible.
- Timestamps on each donation in the Manage Donations or My Donations sections of the web app now show more information about each offer, such as the time at which it was offered, accepted or rejected. This will help diagnose issues charities may be having by giving the viewer a clearer picture of where a given donation ended up.
Mobile Apps
- If a donor creates a donation, but there is no available donation window, the app will now default to “Unplanned.” Expected donation windows should only be configured in the web app and, thus, reflected in the mobile app where a primary charity or waitist charity is ‘scheduled’ so that KPI reporting can be as accurate as possible.
- If a user attempts to log in with invalid credentials, we now present them with a clear error message stating that either the username or password they entered was incorrect.
- In “My Donations” on the Android app, the user will see the previous 7 days of their donation windows as a default. This can be adjusted by the user with date pickers.
- We carried out performance and stability improvements on the Android app.
Reporting
- If a charity who accepted a donor’s offer was not approved to receive all the categories in that donation, the impact report figures still reflected the weight of the entire donation (including the segment that was not suitable for them). This is now fixed to reflect only the parts of the donation that were actually accepted.
- In this release, we are launching the MVP of our new Data Export feature. In the first iteration, this new feature allows Foodiverse reporting users to select a date range and some filters on the Donor Branch KPI report,, then download the results. When a download is started, the user will see a popup dialog informing them that the download is in progress. When complete, they will receive an email which will link them to a “My Files” section in their profile. From there, they can download their selected report as a CSV file. This feature will be available on all reports soon and we encourage all users to get familiar with this format by testing this feature.
- The Charity compliance report was missing the “Expected Accepted” column, which tells you how many times they accepted offers on days when they expected to receive them. This is now present.
- The column “No Availability Rate” was mislabelled in the KPI report. This is now fixed.
- We added timing compliance KPIs to the Donor Branch KPI and Donor Org KPI reports.
- We did data cleansing tasks weekly to ensure that “unplanned” donation windows were not showing as Expected donations. Going forward, where there is no primary charity expecting a donation, the donation will not be marked as Expected. It will only show up in Total Donations in the reports.
- We fixed a bug where percentage KPIs were showing as zeroes on the FoodBank Network Organisation Compliance Report.
- We fixed a calculation error in the Donor Branch KPI report.
- We fixed an issue with the date filters on all Foodiverse Reports. The filters will now return data from the full selected date range..
- We’ve implemented “view mode” in the KPI reports to allow the display of rates or total numbers. The option to switch between view modes improves readability and relevance of the report.
Backend/APIs
- We fixed a bug that prevented a donor from selecting a transfer (formerly collection) window that had already started.
- We’ve made changes to the API that returns available donation windows to the Mobile and Web apps in an improved order. These updates ensure that the user is presented with the most likely donation window as a default. If a donor creates a donation, but there is no available donation window, the donation will now default to “Unplanned.” These backend changes will help with reporting accuracy, as donors will not be RAG’d on an offer unless an expected (formerly scheduled) donation window exists.
- We’ve updated the Manage Donations API endpoint to include the charity UUID in the response. This helps API users to identify which charities were offered a given donation.
- When a “No Posting” was recorded in a donation window, the window was considered to be “used.” We’ve adjusted this so that a donor can use the most recent donation window to create a donation, even if a “No Posting” has already been recorded for that window.
DevOps
- We’ve made performance and stability improvements to the Foodiverse jobs container and EU Production Kubernetes cluster.
Foodiverse Product Update: 28 April 2021
Here’s what’s new in Foodiverse 3.0.0
Foodiverse Web App
- We fixed a bug in “advanced” integration settings. Now, when you subscribe to receive a webhook about an event, you will be able to see that your changes have been saved.
- For organisation admins managing a user on the Foodiverse web app , the “Resend Activation Email” button was broken. This button now triggers an activation email to the user as expected.
- When viewing donation details, some category items appeared to be listed twice. This is now fixed.
- Charities are now able to search for a specific offer within their Offers History page.
Mobile Apps
- In the Android app, some donation details were appearing without the correct category labels. This mismatch is now fixed.
- We fixed a bug on the mobile app where the Impact page wasn’t loading the impact figures for individual branches.
Notifications
- We fixed an error in the email that lets a donor know when it’s time to post. The email now arrives on time, with the correct posting time.
- We reduced the number of emails we were sending to charities about their donations. The volume of emails we were sending was causing delays in donation processing.
- We were sending SMS notifications to charities on the waitlist, when these notifications should only be sent via the app. This caused confusion and is now reversed so that only Primary charity branches receive the SMS.
- SMS messages to Primary charity branches will now read as follows:
8kgs available from Example Donor for collection on 22 April, 16:00-17:00. Text back Y1 to accept or N1 to reject. For more info about offer, download the Foodiverse app here: https://foodiverse.net
- On the web app, charity org admin’s can now update their charity branch SMS and Push notification settings by choosing from the following options:
- i) ALWAYS send me SMS
- ii) Send me SMS ONLY when I’m not logged in with a smartphone (DEFAULT)
- iii) NEVER send me SMS
Reporting
- We adjusted calculations in the Charity Branch KPI report so that the figures reported will now be more accurate.
- In the Donor KPI report, the search bar was broken, and it was not possible to search and filter at the same time. Both issues are now fixed.
- Due to how Foodiverse now collects data, KPIs are calculated somewhat differently to before. For more information, please check out our Knowledge Hub article on the new KPI Report. There will be further updates on KPI reporting in future releases.
- We reviewed requirements and designed an implementation plan for the “Export to CSV” function for in-app reporting. This feature will be developed and refined over the course of the next few sprints.
- A review of all Foodiverse in-app reporting was conducted to ensure all reporting calculations were as expected.
- For donors with a donation schedule, the ‘Create a Donation’ notification will stay on their Donor Dashboard, ‘Your To Do List,’ for 60 minutes prior to the start of the window, and for 60 minutes after the window ends.
- ‘No Posting’ notifications will also appear under My Donations on the Donor account at the end of the Posting window, if the Donor Branch has not donated. ‘No Posting’ notifications are required in order to calculate compliance in in-app reporting.
Backend/APIs
- For retail partners using an integration with our “PLD” API, product level detail will now be sent automatically with donations that are posted via that integration.
- We investigated and improved the way we record a “No Posting” status for expected donations.
- We fixed an issue with historic donations (dated on or before 21 March 2021). Some of the donations that were migrated from the old system into Foodiverse were showing the incorrect food classification (Ambient, Chill, Frozen, Hot). This is no longer an issue.
- When a charity belonged to two Food Networks, the admins from both networks were able to see full details about the charity’s schedule. We now include placeholder text to show WHEN a charity has a slot in another network, but not WHO will be donating to them during that slot.
- We fixed a food classification issue for charities who wished to update their food classification preferences (Ambient, Chilled, Frozen, Hot) in their Organisation settings. Their updates were not persisting across all platform functions. This issue has now been resolved.
- Charities were seeing the same donation multiple times on pending actions and in their “offers” table. This is now corrected.
- Webhooks were being sent twice or multiple times, causing delays and undue strain on the processing of donations. This is now fixed.
- We have extended the expiration time of the “activation link” sent to newly registered users. The activation link will now last 48 hours instead of 60 minutes, so new users will have more time to activate their accounts after registration.
- We fixed a bug where some food categories, such as cereal, were being labelled with the wrong food classification. All categories are now updated to reflect their proper classifications.
DevOps
- Due to the start of daylight savings time, we adjusted the hours at which the cache updates throughout the day, to ensure that data refreshes don’t interfere with peak donation times.
- Foodiverse uses Microsoft Azure hosting services. In line with recommended best practices, the tech team continually reviews and iterates on this configuration to ensure the highest level of security, stability, and performance.
- Copia is hosted on Heroku. Heroku informed us of an update to their system which meant we needed to manage our Copia configuration to ensure that users of Copia continued to be able to send PLD.