11.12.23
Contents
New
New API for SAML Token Exchange
A new RESTful API is available for customers to exchange a SAML assertion for a Quickbase token. This API complies with RFC 8693 to allow for secure communication to Quickbase APIs without any tokens being stored on another server. Users can choose which type of authorization for the API to return based on which type of call they need to make subsequently (XML, RESTful, or SCIM).
Enhancements
Improvement to the Fastfield and Quickbase Integration
You can now use Global Workflow in Fastfield to update a record and add a record. This is based on having a field marked unique on the destination Quickbase table.
Performance Analyzer updates
API_GenResultsTableis now handled in the performance analyzer.
New Fields available in Admin Console connected tables for Apps
Beginning November 13th, the following new fields will be available in Quickbase Sync’s Admin Console connected table for Apps:
- Manager Status
- # of users with any access
- # of users with direct access
- Last Access
- Mobile offline enabled
- Data change logs enabled
- Sandbox required
- Sandbox enabled
You can also take advantage of the new data for existing connected tables. The new fields will be available for selection on the fields page:
Updates to Connection Central for Quickbase Sync
App administrators can use the Quickbase Sync tab of Connection Central to see which tables in the app are being used as the source of connected tables. Look for these enhancements to the Quickbase Sync tab:
- The realm hostname is provided in addition to the realm name.
- You can filter the list of connections by using the Search field at the top.
- You can export a CSV of the connections currently shown in the list by clicking the download icon in the upper right corner of the page.
Quickbase Sync SFTP Connections - ending support for SHA-1
Quickbase is focused on continually helping our customers improve their security by using the safest security protocols and aligning with industry best practices for data security and integrity. For that reason, Quickbase Sync (for connected tables) is updating the SFTP connector to only allow connections to SFTP servers that use SHA-2. See this article in Community for additional information.
The current version of the SFTP connector (Version 1) will continue to be available until May 2024 to give you time to transition your existing SFTP connections to the new version (Version 2). New connections created after the November 2023 release must use Version 2.
If you are the owner of an existing SFTP connection, confirm with the administrator of your SFTP server that it is not using SHA-1. Then follow these steps to update your existing connection to use Version 2 of the SFTP connector:
- Select the user dropdown on the Global bar, then choose My Preferences.
- In the My Connections section, select the SFTP connection you want to update.
- Change the Client Version from 1 to 2 and re-enter the SFTP password.
- Click the Save button to save your change.
- Go to one of the connected tables that uses the connection and manually refresh the table to confirm that the refresh works.
Note: You will be able to switch between Version 1 and Version 2 for existing connections until Version 1 is retired next year.
Platform Analytics integration reads reporting optimized
We're excited to announce a significant improvement in Platform Analytics. Admins using the system will now experience faster loading times when accessing the "View integration reads" feature on the integration reads tile. You should experience this today. Data now refreshes hourly for these reports.
Increased payload size in RESTful API
We’ve increased the limit from 10 MB to 25 MB in the upsert API.
Added Generative AI Control to Admin Console
Starting on Tuesday, November 14th, Realm Admins may enable or disable all Generative AI features through a new capability in the Admin Console through the Policies section. Generative AI features are enabled by default.
Platform capabilities that are controlled by the policy are listed for reference in the description of the control.
Note: At the time of release, the setting will respect any previous requests to opt-out of Generative AI features.
AI Smart Builder (Beta) enhancements
We continue to improve the app-building capabilities of AI Smart Builder. This release includes:
Improvements to the Create App Wizard
- Added visual indicators for word count limitations for text fields when creating a new app with Smart Builder.
- If multiple app builds are attempted by the same user, the status of the in-progress app may now be accessed.
Improvements to App Creation and Sample Data
- Added international addresses to sample data to create more diverse map reports.
- Added restrictions for creating tables and sample data for out-of-compliance data, such as credit card numbers, so that Smart Builder doesn't generate these kinds of data.
- Smart Builder will no longer generate an app without tables.
Report enhancements
Added the ‘Group by Parent’ enhancement for auto-generated bar charts.
Exchange (Beta) Enhancements
Jinja Snippets
You can now browse and consume Jinja snippets for pipelines in the exchange. We will be adding many useful snippets in the coming weeks, so be sure to check frequently for updates. The Jinja snippets can be copied to your clipboard and pasted directly into the Pipelines designer.
Image Carousel
In Exchange, you can now browse through images of resources via a carousel view. We will be updating existing resources with images over the coming weeks. This will be beneficial for users to understand what a resource does and looks like before installing it.
User Permissions for Enterprise Customers
Account administrators in enterprise accounts can now choose which users may access the Quickbase Exchange. The ‘Specific Users’ option will interact with the table on the account permissions page in the same manner as user token creation access. These permissions control access to both the Exchange and Exchange beta. This permission will continue to apply to the new Exchange once the legacy Exchange is retired.
For customers who have already disabled the exchange via the existing account level control, the exchange will remain disabled for all users. If the existing control is enabled, the default state of this new control will be “All users can access the Quickbase exchange.
Support for Community Contributions
We have added support to give attribution to members of the Quickbase Qrew who have submitted resources to the Exchange. We would like to thank the Qrew members who have already contributed a resource; we will be reaching out and starting to publish these resources in the coming weeks. If you are interested in contributing a resource (app, formula, or Jinja snippet), please click the Submit a Resource button in the top right corner of the Exchange.
Super Users
We’re enabling Super Users for all our Business and Enterprise customers. The capability will be defaulted on for all new customers, too. Up to 10 Realm and Account Administrators can be promoted to Super Users by a Realm Administrator. They will be granted full access to all applications in the realm they are part of.
You can still disable the functionality for your realm by submitting a case to our Technical Support team. Read more: Super Users.
End of Support
iCal fields
iCal fields are reaching End of Support with this release. We have not yet determined the date for End of Life.
We’re retiring iCal fields since pipelines offers a more streamlined method for integrating meeting schedules across systems. Specifically, our Outlook and Google Calendar channels have made iCal fields redundant.
vCard fields
vCard fields are reaching End of Support with this release. We have not yet determined the date for End of Life.
We’re retiring vCard fields since pipelines offers a more streamlined method for integrating contacts across systems, making vCard fields redundant.
What’s fixed in Quickbase
The actual date of deployment of the fix will appear in the WHAT WE FIXED column unless the fix is deployed on the day of the monthly release.
| ISSUE | AREA AFFECTED | WHAT WAS BROKEN | WHAT WE FIXED |
| QBE018544 | Admin Console | App management transferring from the admin console is inconsistent. | App management transferring from the admin console has been made consistent with the flow from the app settings page. Validation will be required from the receiver. |
| QBE018550 | Fields | Selecting searched address values may intermittently fail to populate subfields. | Subfields are now correctly populated. |
| QBE018563 | Forms | Proxy fields required at the form level no longer display a red asterisk. | Form level proxy fields now display a red asterisk when required. |
| QBE018573 | Mobile | The mobile app displays a Dashboard as a Home page when an App Home Page is selected as the default mobile home for a role. | The mobile app now honors the app admin’s selection in the mobile drop-down and displays the correct Home Page/Dashboard. |
| QBE018040 | Mobile | Users were unable to preview files in the mobile app from some accepted URL formats in a Formula URL field. |
Users can now preview files from accepted URL formats in the mobile app. The issue is resolved in the mobile app version 1.55. |
| QBE018218 | Mobile | Previewing images in the mobile app may show the image zoomed and/or cropped. |
Images now appear correctly when previewed in the mobile app. The issue is resolved in the mobile app version 1.55. |
| QBE017952 | Pipelines | The "File Created or Modified" trigger step will not trigger when files are uploaded or drag-and-dropped into the OneDrive. This is inconsistent with expected behaviors, as the "File Created" step will trigger on these events. Currently, the "File Created or Modified" step will only trigger on file modifications and when a user utilizes the "+ New" option to create a file directly within the drive. |
The "File Created or Modified" trigger step now triggers when files are uploaded or drag-and-dropped into the OneDrive. |
| Pipelines | Static IPs not fully used for Snowflake DataSync channel |
Enable support for Snowflake Network Rules to implement additional IP filtering for Snowflake Internal Staging when using the ENFORCE_NETWORK_RULES_FOR_INTERNAL_STAGES flag. To make use of Snowflake additional services protection you need to have Pipelines Static IPs feature enabled. |
|
| QBE018577 | Pipelines | Export to YAML does not return the "Last Modified By" field in the filter. |
YAML works as expected. |
| QBE018601, QBE018602, QBE018603 |
Quickbase Sync | Connected tables for Gmail labels with a name that contained any of the following characters failed to return the expected messages during a refresh: exclamation mark (!), pound sign (#), or percent sign (%) anywhere in the name; apostrophe (‘) at the beginning or end of the name; apostrophe (‘) anywhere in the name of a sub-label. |
Connected tables for Gmail labels with names that contain those characters will refresh successfully. |
| QBE018586 | Аudit Logs | Data change logs were not properly showing changes to file attachment fields. |
Data change logs now display properly. |
| QBE018614 | Reports | When using the qname parameter to query a report, an incorrect report title was displayed |
The correct report title is now displayed |
| QBE018611 | Forms | Form rules to change value were not respecting the setting “Run change actions when a condition changes from false to true” |
Form rules correctly respect this setting |
| QBE018604 | Forms | Form rules were showing conflicts when applying actions on pages and fields with the same ids |
Form rules accurately show conflicts |
| QBE018388 | Forms | Fields filter in form rules was not listing fields from “Display message” actions |
Field filter list all fields used in form rules |
| QBE018512 | Forms | Multi-select fields with choices sourced from another field cannot be used effectively in form rules conditions |
Multi-select fields list all choices when specifying a condition in form rules |
|
|