04.10.22
Contents
New
New audit log activities: user and role modifications
When an app builder assigns a new role to a user or updates the configuration of a role, the security and privacy of the data stored in the app can be impacted. Account admins need visibility into these types of activities to ensure they are complying with legal and corporate policies. That's why we added new activities to audit logs, covering user, group, and role modifications. The new activities are:
- Granted user access
- Revoked user access
- Updated user access
- Invited users
- Created roles
- Deleted roles
- Updated roles
- Granted group access
- Revoked group access
For example, companies using audit logs may see activities like these:
- Ariel Adams created the role Executive in app "Subcontractor Management"
- Vanna Kumar enabled app management and sharing for users with the role Representative in app "Subcontractor Management"
- Vanna Kumar enabled adding records for users with the role Manager on table Opportunities in app "Subcontractor Management"
- Ariel Adams removed vkumar@example.com from the app "Subcontractor Management"
- Vanna Kumar granted access to arieladams5@example.com with role Administrator in app "Subcontractor Management"
Note: These changes are captured even when made within Sandbox.
Visit our audit logs help page to read more about the patterns captured in each of these events.
Beta opportunities
| Feature | Description | status | how to participate |
|---|---|---|---|
| Report Caching |
Enterprise plan customers can use report caching to help maximize their performance at scale. Report caching minimizes the time Quickbase needs to re-calculate reports based on pre-determined business logic. |
Beta | Eligible customers will receive invitations |
| Report settings panel – Kanban | Update report settings more quickly for your Kanban reports using our new report settings panel. | Beta | Sign up in our early access app. Select Building Apps under Program Area. |
| Pipelines permissions | Access additional permission options for building pipelines. Enterprise plan customers can specify who can build pipelines and what channels they can use. | Beta | Sign up in our early access app. Select Platform Administration under Program Area. |
| Procore Channel in Pipelines | Builders can now connect to Procore, the leading construction project management software. Mutual customers can now trigger, create, update, query, and delete data within Companies, Projects, RFIs, Users, Roles, Vendors, Budgets, and more. | Beta | Reach out to your Customer Success Manager, or ask to get included by messaging us in our Quickbase Community slack workspace in the #pipelines channel. |
| Autodesk Channel in Pipelines |
Autodesk is a popular tool for designs, drawings, renderings, and visuals of buildings and architecture. Customers who use Autodesk can now:
|
Beta | Reach out to your Customer Success Manager, or ask to get included by messaging us in our Quickbase Community slack workspace in the #pipelines channel. |
What’s fixed in Quickbase
| Issue | Area affected | Description |
|---|---|---|
| QBE016846 | Reports | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name, a search with no results would garble the word. . |
| QBE016847 | Charts | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name, then created a chart report, if the chart report was empty, the record name would display incorrectly. |
| QBE016848 | Reports | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name, the record name would appear incorrectly in multiple areas across the legacy style table report and chart reports. |
| QBE016849 | Email notifications | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name, the record would appear incorrectly in several areas in the email notifications builder. |
| QBE016850 | Mobile app | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name, the record would appear incorrectly in several areas in the Quickbase mobile app. |
| QBE016852 | Importing | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name in a table, then attempted to import data to the table from a file, the record names would appear incorrectly during the import process. |
| QBE016853 | App and table settings | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name for a table, then used a formula to add a start date, the record name would appear incorrectly in the start date hover text. |
| QBE016775 | Forms | When UTF-8 was enabled at an app or realm level, and a user used a non-English word, such as “Niño,” as a record name, the record would appear incorrectly in several areas in forms. . |
| QBE016774 | Email notifications | Formula rich text fields were appearing as code in some email notifications. |
| QBE016815 | New style table report |
When a user opened a table report, left it open for more than around 15 minutes, and then tried to apply dynamic filters, the report would go blank. |
| QBE016837 | Email notifications | Quickbase logos in HTML email notification templates would display incorrectly large when a user viewed the email in Outlook web. This problem did not affect the Outlook desktop app. |
| QBE016858 | RESTful APIs | We renamed the ForeignKey property in the REST API serializer from `targetTargetName` to `targetTableName` |
| QBE016859 | Performance optimizer | When users ran the Performance Optimizer in simulation mode, the Result column indicated invalid choices as “removed,” which was inaccurate. Now, the result column says “will be removed.” |