Contents
New
Sensitive data scanner
Account admins on Enterprise plans can scan their Quickbase applications to help identify different types of sensitive data such as Name, Location, Email, Phone number, Social Security number, and more. Access the Sensitive Data Scanner in your Admin Console in the Apps section.
Open the Data Scanner to start a scan of an application. In a scan, you can review sensitive data found and download detailed results.
Learn more about using the sensitive data scanner in the Scanning data in apps for sensitive information help center article.
Gantt Plugin
App administrators on Enterprise and Business plans now have access to the fully interactive Gantt Plugin for Quickbase. Use the plugin to visualize project data and view it in an interactive interface. The plugin includes powerful project management features such as dependency types, baseline dates, automatic scheduling, and resource management.
By default, the Plugins feature is not active. In the Admin Console, an account admin needs to navigate to Permissions and select All users can install and edit plugins for the Plugins setting. This setting can take a few minutes to apply, and you might need to refresh the page or clear your cache.
Download the Quickbase template application, and then install the plugin by navigating to App settings > Plugins to start managing your project data. Customers with enablement service plans can utilize their hours for help with getting the Gantt Plugin installed in their existing apps. The plugin requires a specific app structure, so we recommend starting with our template app.
When you launch the plugin from your app, your project information displays in a way that you can drag and drop, rearrange, and expand and collapse different details, tasks, and information. We make it easy to undo and redo changes or export all project information.
Enhancements
SCIM user provisioning – update sso UniqueID
You can now use SCIM to update the ssoUniqueID for provisioned users. For example, if your active directory issues a temporary email address for guest users at the time of provisioning, use SCIM to update the ssoUniqueID so the SAML finds the correct user when they log in.
Learn more about how you can use the SCIM user provisioning enhancement in the help center.
Beta opportunities
No beta opportunities this month. Read next month's release notes for more opportunities.
What’s fixed in Quickbase
|
ISSUE |
AREA AFFECTED |
WHAT WAS BROKEN |
WHAT WE FIXED |
|
|
Table reports |
Column headers aren’t truncated if the field name is longer than the column width. |
Now, words in headers display based on the longest word. This improvement to column headers works with the intuitive widths released in September. |
|
QBE017519 |
Quickbase Sync |
The wrong icons were being displayed for Date/Time and Time of Day fields in the list of fields to connect when creating a connected table. |
The correct icons now display for Date/Time and Time of Day fields. |
|
QBE017525 |
Account Management |
The number of nested groups was missing from the tooltip in Permissions page grid. |
The tooltip in Permissions page grid now includes the number of nested groups. |
|
QBE017526 |
Account Management |
Incorrectly filtered information was occasionally shown in the dialog window for adding a new user to the Permissions page grid. |
Now the information displayed in the dialog window is filtered correctly.
|
|
QBE017527 |
Account Management |
Pipelines page was sometimes loading an incorrect list and status of channels. |
The correct list now loads. |
| QBE17484 | Charts |
The color of series options wasn’t being honored in certain conditions. |
The selected color of the series options is now correctly used in all conditions. |
|
QBE17174 QBE17596 |
Email Notifications, Subscriptions, Reminders |
Only one single record notification was being triggered when multiple records were added through the API. |
A multi-record notification is now triggered when multiple records are added through the API. |
| QBE017532 | Formula Queries |
GetRecordByUniqueField() was showing as an error when the function was set up correctly |
GetRecordByUniqueField() is no longer be highlighted as an error when set up correctly. |