LCS - List of Completed Betty Blocks Platform Enhancements

The Low Code Solutions Service Team maintains a list of platform enhancement requests that have been submitted to and completed by Betty Blocks.

Any active platform enhancement requests that have been prioritized with input from the Low Code Solutions Advisory Board and submitted to Betty Blocks to be added to their product roadmap can be found on the Betty Blocks priorities web page

The list below contains all platform requests that have been completed. 

List of features requested of Betty Blocks and subsequently added
Date Completed Title Description Reason for Need
Released to production 6/21/24 Unify style options across components

Unify this so that all all components can be styled the same way. Betty Blocks introduced CSS (style sheets) that can be used instead of default styling.

Developer ease of use
Released to production 6/19/24 Adding SSO Authorization capabilities to my.bettyblocks.com at the organizational level

To successfully on-board and manage wider campus adoption of the platform and eventually citizen development, we need the ability to manage who has access and what roles they are assigned per organization utilizing UW's SSO. Note: This is separate from End-User SSO and management which is completed and verified working.

Proper Governance
Released to production 6/19/24 Release Notes improvement needed

The release notes need to be more comprehensive, published regularly and provide insight into what is going to be released prior to the release of the functionality

Customer preparedness and understanding
Released to production 6/6/24 Permission needed to be able to see applications in an org

Right now, the ability to see applications within an organization is tied to the default Admin role. We’d like the Org Admins to be able to 1) see the applications that are in their assigned orgs, 2) manage users in those applications and 3) be able to do a pre-launch checklist and flip those apps to Live when ready for production. The inability to do 1) makes 2) and 3) not feasible.

Proper governance, monitoring
Released to production 6/6/24 Permission needed to be able to delete apps at the org level

The ability to create an application permission has been created within the organization. However,  the ability to delete an application is tied to the default Admin role, we need that to be a separate permission

Governance, Dev functionality
Released to production 5/6/24 UW and parent org app templates and blocks much more obvious

The filters used to search for blocks in the Block Store are now stored to improve the ease of use when finding blocks to install.

Impact to user experience
Released to production 5/6/24 Platform oversight - add Blocks to the company overview

The request is to add Blocks to the company overview - who the owner/builder is, the organization location and sharing level (developer, orgs and developers, BB store).

Proper governance/maintenance
Released to production 4/4/24 Requirement to meet UW's Digital Accessibility Policy

Certain form components needed to be changed to meet accessibility standards. Reassessment done by UW's accessibility team and a kb indicates the outcome and those items to avoid.

US accessibility Laws
Released to production 4/4/24 Separate permission needed to move app from one org to another org

Currently, the user would need the Administrator role in both the originating organization and the destination organization to move an application from one org to another. A custom role would not have this capability. The request is to make this functionality a separate permission and not part of the Administrator role.

Proper governance/maintenance
Released to production 4/4/24 Separate permission needed - app name change

Currently, all of the capabilities under a single application>Settings>Options are functionality within the default Admin role, including the ability to change the application name. The request is to have separate permissions for each functionality.

Proper governance/maintenance
Released to production 4/4/24 Separate permission needed - app identifier change

Currently, all of the capabilities under a single application>Settings>Options are functionality within the default Admin role, including the ability to change the application identifier. The request is to have separate permissions for each functionality.

Proper governance/maintenance
Released to production 4/4/24 Admin role permission needed - Setting URL Hostname for an application

Currently, the permission to set/change the URL Hostname for an application is funcitionality within the default Admin role. The request is to have separate permissions for each functionality.

Proper governance/maintenance
Released to production 3/21/24 Application template versioning tracking

Add the ability to track which Application templates were used when creating an application such that if BB upgrades cause the need for a change or UW wants to change the standard templates/components, the service team can inform those to update if desired.

Proper governance/maintenance
Released to production 3/21/24 Permission to turn apps into app templates

Currently, only the administrator role can make an application a template that is automatically available within the organization it is built

Proper governance

Released to production 3/21/24 Permission to add users to an application

Currently, the user must have the default administrator role to add users to an application (e.g. an application is built and someone wants to add another developer or even tester at IDE level to that application.)

Proper governance
Released to production 3/21/24 Permission to change user roles for an application

Currently, the ability to change user role at the application level (e.g. switch a user from Low-code dev to Bus Tech) is part of the default administrator role. The request is to separate this functionality into a permission.

Proper governance
Released to Production on webpage 1/22/24, ability to export Released to Prod 3/8/24 Platform oversight - user's roles in orgs and apps

Awareness for the service team of every user - Indication of the role(s) in each org and role(s) in each application for every user at that snapshot point in time

Proper governance, Security Assessment
Released into Production 3/4/24 Ability to create custom roles and edit permissions at the application level

Currently, any Admin has the ability to create a custom role and specify permissions under User Management **at the application level**. Right now there are 3 default roles **at the application level**: Citizen Dev, Business Tech, Low coder. As Betty Blocks expands the permissions at the application level, we need a separate permission be able to create new custom roles and set permissions therein, instead of all of this functionality being tied to the Admin role.

Proper governance
Released into Production 3/4/24 Encrypted configuration Values exposed

Configuration values like passwords and API tokens can be exposed to user that should not know the credentials via output in an Action.

Security Issue
Released into Production 3/1/24 Ability to create custom roles and edit permissions at the organization level

Currently, any Admin in an organization has the ability to create a custom role and specify permissions under User Management. This functionality is tied to the Admin role, but there isn’t a separate permission. Request: Make a separate permission at the customer and organization level allowing for the creation of custom roles (and assigning permissions to those roles).

Proper governance, Security Assessment Gap
Decided other enhancements fulfilled the need 2/21/24 Add the ability to tag/flag orgs

Currently, the UW orgs have a hierarchy via name/process. The request is to have a way to flag orgs as Overarching, Parent, Child, etc.

Company Overview functionality and releasing blocks to company level fulfill need

Proper governance
Released into Production 2/12/24 Nested data containers can load all of their content twice Bug: Nested data containers can load all of their content twice even with "Only render children when data is present" is checked.  Setting a conditional under the nested data containers to confirm the id has loaded resolves this issue.   Its really impacting the load experience in my app as it double flashes with data on the page. Impact to user experience
Released into Production 2/8/24 Add block permissions and BB block public store prior approval needed Decide who has the ability to release blocks, to promote blocks/make blocks visible within your org/company, or promote blocks to the BB public store Proper governance
Released into Production 2/2/24 Dates in update forms return the wrong date

When using an update form and a date field is present, the date component is returning the day before. I.E. if the saved date was 01/01/24 the date input component returns 12/31/23 and saves 12/31/23. Impact to user experience and potentially incorrect data saved
Released into Production 1/12/24 Model schema view intermitently shows wrong type of relation When viewing an applications data model in the schema viewer the direction of a relationship is often wrong with the one-to-many pointing the wrong way. Impact to dev functionality
Released into Production 1/8/24  Add relational property to an existing Form should work out of the box  Property selection wizard: -If the user selects a property that is a relation that would generate an auto-complete or multi-select auto-complete, the correct setup should automatically be created so that the field just works out of the box and should put the correct value into the action and populate the select or auto-complete with the correct model and values. Currently, this doesn't happen automatically.  This is critical for further adoption of the platform. While the service team can work around these issues our Distributed IT folks need this to be better 
Released into Production 1/8/24  Hidden input component > non-property based, should have the input type selector shown in the popup  Property selection wizard - -Hidden input should have the type of data being passed (text, number, checkbox) by default in the initial setup screen and if a property is chosen that is a number or checkbox it should automatically match the variable type of the property chosen. Currently, this doesn't happen automatically.  This is critical for further adoption of the platform. While the service team can work around these issues our Distributed IT folks need this to be better 
Released into Production 12/22/23 Bridge model - missing documentation of how to use and improving the way it work ins pages/actions The UW Service Team has Documentation (see Low Code Solutions kbs) for this but there is no documentation from BB on this topic.  Lack of training Documentation
Released into Production 12/6/23  Platform oversight - apps, templates per org  Awareness of all of the orgs, applications, templates that exist across all of the UW tenant and the ability for the service team to make know the owner of each so we can notify them of name changes, inactivity, and/or other clean-up (Does not include blocks)  Proper governance, Security Assessment Gap 
Released into Production 12/6/23  Platform oversight - number of unique users applied towards licensing limit  Awareness for the service team to know the unique user count towards the 150-developer limit (Workaround: BB mentioned that they do a count every Monday morning and could share a list of users with written consent from the service team)  Proper governance 
Released into Production 12/6/23  Ability to not have personal trial-orgs created,  yet have access to training.betty.app  Prevent a personal trial-org from being created for every new my.bettyblocks user, but still have the ability for them to access training.betty.app. During set-up the new my.bettyblocks user will be given access to the appropriate Playground org and have a play/training application set up there.  Proper governance 
Released into Production 11/14/23 Adding Relational properties to a back office via the setup wizard orphans actions BUG: When creating a page from the Back Office template and adding properties from a relationship. The page creation can fail but still creates the actions which are non deletable. if the page creation is successful and then you delete the BO page 3 non deletable actions remain orphaned. Impact to dev functionality


Keywordsfixes, bug, update   Doc ID133954
OwnerMaddie S.GroupLow Code Solutions
Created2024-01-11 08:51:51Updated2024-07-15 12:37:37
SitesDoIT Enterprise Business Systems - Low Code Solutions
Feedback  0   0