You may have noticed we released a significant upgrade to b.world in late October. We're grateful for the recommendations and guidance our customers and partners have provided - and hope you'll see your priorities reflected in this update.
Check out the following for a detailed list of improvements and fixes to the platform by functional area of the application. Oh yeah...and stay tuned, we have something exciting planned for Stories in November.
No duplicate stakeholders: It’s no longer possible to add two stakeholder records that are exactly the same (with the exception of differences in letter case). For example, if there’s a stakeholder record with the Name field filled in as ‘Bob Peterson’ and no other fields filled in, the platform will not allow adding another record with the Name field filled in as ‘bob peterson’ with no other fields filled in. However, if there’s a stakeholder record with the Name field filled in as ‘Bob Peterson’ and the Organization filled in as ACME, the platform will allow adding another stakeholder record where the Name field is filled in as ‘Bob Peterson’ and the Organization field is empty.
NOTE: In the future, we plan to add further rules and checks around what it means to have a duplicate record.
Auto-generated data entry table: The most impactful upgrade in this release is that blank data tables are auto-generated for each indicator based upon the start and end date for each indicator. This means that users no longer need to manually add table rows and select ‘last date of reporting period.’ This expedites and greatly improves your experience during the data entry process. In addition, b.world has a variety of rules in place to populate default start and end dates for each indicator, which you can change as needed.
Separate page for data grid: The data table for each indicator now lives on a separate page from the Logframe landing page, providing a clearer separation between indicator setup and data entry and more screen real estate for large data entry tasks.
New location for data entry: Data entry is now performed in a sidebar versus in the grid itself, providing a cleaner experience for data entry, especially when there are many disaggregates for an indicator.
Data visualization: The other significant upgrade in this release is the introduction of data visualization. Visualizations are auto-generated for each indicator as soon as any data is populated for that indicator. Users can:
Toggle between a line graph and bar chart
Have the option to hide/show disaggregate data (when they are defined in an indicator)
Have the option to hide/show data points on the visualization
Add a title to the visualization
Change the default axis titles
Download a PNG of the visualizations
Data summing across reporting periods: For integers and decimals that are incremental and can be added together across reporting periods, the platform calculates a sum at the bottom of the data table. For all other data types and conditions, a sum is not shown.
Data entry validation: New rules have been put into place based on the selected data type which dictate how the numbers should be entered and how they appear in the data table; users are provided with clear guiding messages for assistance. These data entry validations will help you enter quality data in b.world based on your indicator definition.
Data type can’t be changed after data entered: After data is entered for an indicator, the data type can no longer be changed. This will help mitigate potential data quality issues.
Baseline and Target entry: Users can now set baseline and target dates and values for indicators.
Updated sample for ‘Rate’ unit of measurement: The example provided for a ‘Rate’ unit of measurement has been updated to provide clearer guidance on how Rate units of measure should be defined.
Different buttons on Indicator Setup screen when editing: The button types/names on the Indicator Setup screen are now slightly different when initially setting up the indicator versus editing it for a clearer user experience.
Updated text for data aggregability: The text on the Indicator Setup screen asking users whether an indicator’s data can be aggregated across reported periods has been updated to be more user-friendly.
New tasks added to top: The newest task is now added to the top of the To Do list rather than the bottom so that users don’t have to scroll to the bottom of the screen to see newly created tasks.
D. Account Management
Change password messaging: Users receive clear messaging indicating if their password change was successful or not.
b.world in Spanish: Users can change their browser language to Spanish. b.world will be translated into Spanish, and date formats will be adjusted accordingly as well.
NOTE: b.world’s compatibility with other languages will be coming in the future. At this time, b.world’s interface only changes if the browser language is set to American English or Spanish. If the browser language is set to anything but these two languages, b.world will default to American English.
Sidebar aesthetic: The look and feel of the left-hand navigation sidebar has been updated to have a cleaner look.
F. Bug Fixes and Minor UI Improvements
Onboarding: Clicking ‘Back’ after being prompted to join a team resulted in an error.
Onboarding: Admins no longer see an error after approving users who’ve requested to join their team.
Projects Page: If project titles were too long, they exceeded the width of the project ‘cards.’ Now ellipses are shown for long titles, with the full title available upon rollover.
Projects Page: Content no longer bleeds off the right side of the screen.
Projects Page: When on the list view, users couldn’t toggle back to the grid view.
Overview: When people added as stakeholders to a project were deleted form the project, they were also deleted from the team. People deleted from a project can now be added to projects without having to be re-entered as new stakeholders.
Overview: ‘null’ is no longer displayed when there is no organization entered for a person who’s been added as a project stakeholder.
Logframe: Indicator rows no longer bleed off the page if there are more than four goals.
Logframe: When an indicator had dimensions and disaggregates, the screen contents bled off the page, making the Settings button/screen to the edit the indicator inaccessible.
Logframe: Activity dates now appear on-screen in addition to appearing upon rolling over the activity name.
Logframe: Clicking on the information bubble (‘i’) when adding an indicator from Project Elements into the Logframe resulted in seeing a blank template that was supposed to be populated with details about the indicator. This screen is now populated with the appropriate information.
Logframe: Indicators couldn’t be deleted, but now they can be again.
Logframe: After selecting an indicator from Project Elements for addition to the Logframe, the Back button on the screen wasn’t working.
Logframe: When SDG indicators were added to the Logframe, the indicator text was truncated on the Logframe landing page.
Logframe: The indicator ‘delete’ icon was in the wrong spot.
Logframe: Integer and decimal data could be saved even when the sum of the disaggregates exceeded the topline value.
Logframe: Activity dates couldn’t be modified.
Tasks: If the browser language was set to British English or any language that resulted in a dd/mm/yyyy date format, the system was incorrectly displaying an error message for any dates where the day was >12.
Tasks: The ‘Cancel’ link was removed on task cards because it was inconsistent with the design of other similar screens in the application, so it was removed.
Budget: After adding the initial transaction to a budget, there’s only one way—versus two different ways—to add additional transactions. This removes visual noise and any potential confusion.
Budget: After linking a transaction to an activity, the activity would reappear and then disappear with cycles of clicking; activities now persistently appear as they are supposed to.
Budget: Incorrect error message was appearing after user entered Transaction Date incorrectly.
Budget: The fill bar corresponding to transactions wasn’t updating in response to adding transactions to a budget.
Budget: The Edit/Delete menu persisted on the page even after Edit or Delete was selected. This was also happening when trying to edit an indicator on the Logframe.
Stories: The outline formatting functions in the Stories toolbar for each story answer wasn’t functioning properly.
Stories: Stories were editable in Preview mode but shouldn’t have been.
Project Elements: Entering text into the Search function didn’t appropriately filter the records on the page .
Project Elements: Clicking the table headers (e.g., Description) was showing a blank, unnecessary screen. This screen has been removed.
Project Elements: When adding an indicator, the wrong language was displaying for the aggregability question.
Project Elements: When adding a global Project Element (goal, indicator, etc.), the user saw a confirmation message to indicate that the element had been added successfully.
Team Administration: Updating a user’s name in the Team Administration section incorrectly removed said user’s admin status.
Team Administration: An email address was required to add a new team member, but the system falsely looked like it was adding team members even when email addresses were missing.
Global: b.world-specific 404 error pages were not showing when an incorrect URL was entered.
Global: Guiding text was remaining in some form fields after the fields were filled out.
Global: Error messages were remaining on some screens even after removing the errant data.
G. Backend and Security Updates (Private)