What? By clicking a reschedule button on My Schedule page, user will see a meeting reschedule component in a dropdown panel.
Why? To make the rescheduling action more straightforward by removing the need of opening the profile page.
Built by: Nathan
What? Organisers can limit the number of contact details visibility options available to participants.
Why? So that organisers can enforce participants to share their contact details if they included a consent in registration forms.
Built By: Ania, George, Nathan
What? Web-networking and teams exports are unified. They contain additional details about meeting participants and contacts, including contact details and metadata.
Why? To provide the same amount of information across various export files.
Built By: Charlie, Ania, Craig
What? Integration with remote simultaneous interpretation apan additional set on session.
Why? With Interprefy, meeting and event participants can enjoy real-time interpreting in their chosen language.
Built By: George
What? The meetings & insights sections in the dashboard have been replaced with cumul insights panels.
Why? To provide more granular insights, increase consistency of insights across the dashboard as well as empower the data squad to make its own changes without interruption from the organiser squad.
Built by: Guy
What? Updated New Session Summary with a cumul panel. This will allow for filtering of meeting types for all statistics.
Stats shown on new cumul panel: total sessions, total session attendees, unique session attendees, session per attendee.
Why? To provide more standard and better granular insights, increase consistency of insights across the dashboard.
Built by: Ollie
What? Updated New Session Summary with a cumul panel. This will allow for filtering of meeting types for all statistics.
Why? To provide more standard and better granular insights, increase consistency of insights across the dashboard.
Built by: Ollie
3. New API Endpoint for Recommendations/Answered
What? Get all the recommendations between things in a container with skipped and interested actions.
Why? To allow organisers to capture this data from our api endpoints.
Built by: Ollie
Fixed: Issue for processing invalid metadata
Fixed: Disable team upgrade button on the inbound leads list when an upgrade is not available
Fixed: PR issue for share in Hosted Buyer
Fixed: Inconsistencies between activation data in Dashboard and API
Fixed: Unable to add Recommendation block to Home Feed
Fixed: Lambda error - not enough arguments within format string
Fixed: Error around Navigation Items or Event Selector on QA Dashboard
Fixed: An issue with Relationships on the new dashboard
Fixed: Duplicate warning in Event Data Type settings
Fixed: Unable to press on Profile button on New Dashboard
Fixed: The ability to press on "companies" or "items" if there are no associated profiles in the app or event
Fixed: An error where users are unable to open an application with an event expert user level
Fixed: The ability to select a Data Type in the left side bar when I don't have an event selected
Fixed: Clicking on data types on app level does not return anything
Fixed: Company Chat cannot be turned on from new dashboard
Fixed: Smart Marketing link not being created
Added a warning copy below the 'display name' 'can meet' and 'can be interacted with'
Added 'Enable Homefeed Navigation' to the App Config and Special Actions' page & check that functionality is not added to mobile check box on Event Setup
Improved Left Side Bar on Old and New Dashboard
Disabled lambda function for production so that we can create unique index for thing id.