Fastfield — Dispatch Tasks from Pipelines
As part of the Fastfield integration, you can dispatch a task/form using our new Pipelines channel and it can also be recalled. This capability will be released to all customers, in open beta, on September 29th.
Pipelines — Use static IP addresses for outgoing pipelines
If you are on the Enterprise plan you can now use static IP addresses for any outgoing pipelines. This means that all outbound pipelines calls for all Pipeline channels will always come from the same IP addresses. This adds an additional layer of security to your integrations because you can add the IP addresses to the allow lists of other cloud-based software. For more information see IP Policies.
Simplified authentication for the Quickbase channel
Pipeline builders can now use simplified authentication with the Quickbase channel. This new capability streamlines and secures the process of connecting to Quickbase apps as you can use a default pre-provisioned user account for the realm that respects the user access level, instead of creating and managing user tokens for the apps they want to automate and integrate with. Any existing pipelines will continue to run using the tokens they were assigned originally unless manually changed.
For more information about the new authentication options, see Simplified Authentication in our help center.
We'll be releasing this change in stages. Use this list to help you know when it will be available in your account. Note: These dates are subject to change.
Realms beginning with
Anticipated rollout date
Optimized paths to Pipelines Designer or Legacy Pipelines Builder
We've revamped and simplified the pipeline design process which minimizes the number of steps you'll need to access either the Pipelines Designer or the Legacy Pipelines Builder.
When you click Create pipeline, a dialog appears, prompting you to confirm your preferred version.
In the action bar, you can change the name of your pipeline or add a description.
Many of our builders need to expose a form to their users outside of the context of a Quickbase app. We’re improving this pattern in our new form experience. While building a form, you can click on the ‘Share’ icon to easily copy a URL that will direct users to a form without the Quickbase navigation elements.
You can choose to direct their users to a particular page after the record is submitted. The options are:
- Viewing record: shows the record just submitted in View mode
- Show confirmation message: shows a default confirmation message
- Redirect to a URL: will open the specified URL after the record is submitted
- Add another: reloads the form and allows the user to submit another record
We’ve supplied sample code so you can quickly embed a form in a Quickbase code page or external site. While you can achieve the same result using an ifv URL parameter, this makes it easier to organize links and embed forms.
Enhancements to auto-generated forms
We’ve updated how components and fields that are generated at the time relationships are created to appear on forms to help our users get started more quickly. When a relationship between two tables is built we:
- Create a new section at the bottom of the form
- Add a report component using the Report link field that’s automatically generated
Connected tables (Quickbase Sync) are part of Connection Central
Connection Central helps app builders understand how their apps are integrated, by displaying a list of pipelines connected to the app. Now we are making it even easier to understand how your apps are integrated, by adding connected tables (created with Quickbase Sync) to Connection Central. It will show app admins which tables in their app are being used as the source of a connected table, where the connected table resides, who owns the connection, and when the connected table was last refreshed.
Pipelines - Tag limits increased
You can add tags to each pipeline when you create them or edit them. You can now create up to 100 tags, and each pipeline can have up to 30 tags associated with it.
Table reports remember your page when navigating back
Table reports will remember the page you were on if you navigate back using your browser’s back button, the “return” option from new forms, or a redirect parameter in a formula URL button.
Data Analyzer (DA) is the latest Quickbase’s AI Machine Learning (ML) feature that provides you with trends and insights for your data. You can also deploy the ML model to predict the outcome in new and existing records.
An example use case: Based on historical sales data, DA can identify major trends and can provide win/loss probability for currently open opportunities.
Also, app admins can access “Outcome Suggestions” on the app dashboard, which give ideas on how Data Analyzer can help with improving the business process that the application is managing.
Outcome suggestions - General Information:
- Outcome suggestions results are based on the app schema (table and field names and app and table descriptions) combined with Generative AI.
- Outcome suggestions can be triggered by app admins only.
- This capability is currently only available for realms hosted in the United States for Business and Enterprise plans.
- Admins may opt-out realm(s) from this functionality by submitting a tech support ticket.
To build your first ML model with Data Analyzer:
- Go to Exchange
- Get the Data Analyzer Template App
- Install the Data Analyzer plugin in the template app
- Click New Model from the Template App dashboard and click Start the wizard in the new model form
- Select the desired data and outcome parameters
- Click Analyze
In a few minutes, the model record you created will be filled with information for the ML model.
Note: You need to install the Data Analyzer only once (steps 1-3) and simply select in which app the data you want to be analyzed.
You can build models on up to 10 unique outcome fields for the whole realm.
For extensive information, see Data Analyzer.
Build an app with next-gen Smart Builder
A new way to start a custom app with Smart Builder.
To start a new app, answer a few questions about the business problem you need to solve.
- purpose of the app, and
- what you want to track, report on, or manage.
Smart Builder, through Generative AI, will determine the
- tables, fields, and relationships;
- industry and use case specific reports; and
- dashboards; then
- populate the app with relevant sample data; and
- provide a summary of the app with some suggested next steps.
Within minutes, you’ll have a robust, scalable Quickbase app to explore, continue building, or start using in your business.
- Creating an app with Smart Builder uses the information entered by the user and Generative AI to define the app.
- This capability is currently only available for realms hosted in the United States.
- Available in all realms starting October 3, 2023.
- Admins may opt-out realm(s) from this functionality by submitting a tech support ticket.
We appreciate your feedback and encourage you to report any issues or suggestions through the product feedback option.
|HOW TO PARTICIPATE
|The latest updates in Pipelines Designer bring a range of new features, including an infinite canvas workspace, an enhanced step configuration process, the ability to rearrange steps using drag-and-drop, a new code editor, a step reference validator, and numerous other additions.
|Beta September 7
|Available to try in Pipelines
What’s fixed in Quickbase
|WHAT WAS BROKEN
|WHAT WE FIXED
|When a reference field on a form related records to a parent Connected Table, the Create new record option was visible
|The Create New Record option is no longer visible in reference fields that point to Connected tables
|In some cases where fields that were set to Read Only in the form settings they could be modified on the form
|No users are able to update fields that are set to Read Only in the form settings.
|In some cases, use in a form wasn’t appearing in the Field Usage section of the field properties
|All form usage is now correctly reflected in the Field Usage page of the Field settings
|Occasionally when a form had values that were pre-filled using URL parameters, form rules that used those values in conditions wouldn’t fire.
|Form rules correctly fire when they reference fields that are pre-filled using URL parameters
|When an admin right-clicked on a form element in a Subform the link to field settings or form element settings would take them to the wrong place
|Users are now directed to the appropriate field/form element settings
|Help text defined at the field level for checkbox type fields will not display on new forms.
|Help text is now visible on checkbox fields
|Users were unable to save changes to a form rule when they changed the Run change actions when a condition changes from false to true checkbox
|This Forms issue was fixed.
|Incorrect warning messages display when form rules have missing fields in the conditions or in the actions.
|Appropriate messages are presented with information about the form rules problems.
|Changes to file attachment fields weren’t triggering Pipelines.
|Changes to file attachment fields now trigger Pipelines
|Form rule conditions that referenced a value that contained a comma couldn’t be saved and you received an error stating the rule had incomplete conditions.
|Users can now save form rules with conditions that contain a comma.
|Form rules incorrectly showed an error message when a condition or action referenced an Address Subfield
This Forms rule issue was fixed.
|We routed users to the wrong page when a custom Subform was used and a user clicked the Next/Previous icons
Users are correctly routed to the next record in the report using the custom subform
|Form rules that hid the first page on a form would also hide the pinned section.
The pinned section still appears when the first page of a form is hidden via form rule
|The confirmation dialog to delete records in an embedded report on a form was displayed offscreen.
We fixed the positioning of the dialog menu
|Formula queries that referenced date/time and time of day fields were evaluating the time using the browser’s timezone, not the app timezone.
Formula queries run on new forms now use the app’s timezone to evaluate time of day and date/time fields.
|When a user changes a field value in a form that triggers a rule to switch from true to false, occasionally the required/un-required status of the affected fields doesn't update as expected.
Form rules work as expected when a rule moves from true to false.
|Formula fields that call reference or proxy values for conditioned relationships may cause conditional dropdowns to fail.
Formula fields can reliably be used in conditional dropdowns
|Form rules that contained formulas that referenced the Date Created field caused the form to crash.
This formula works correctly.
|Form rules that displayed messages in a modal wouldn’t reliably trigger if the form had multiple rules that displayed modals
All rules that have show modal messages will run if their condition is met.
|Fields used in forms would not appear on the Field Usage page.
All usage in forms is now accounted for in the Field usage section.
|When using a form, you were occasionally prompted that they’d lose changes when navigating away from a form, even when no changes were made.
You are no longer warned that their changes may not be saved when no changes were made to the form.
|In the Quickbooks Channel, when trying to create an invoice, the decimal is removed if quantity is not a whole number, then an error displays stating the amount is incorrect due to the quantity.
The decimal issue was fixed.
|In the Snowflake Channel, the Export Records to CSV function failed to construct a CSV because of an undefined escape character.
The export CSV issue was fixed.
|There was an unexpected error during the automation migration of the Quickbase channel account provisioning.
The migration issue was fixed.
|Missing error message when a summary report was missing a group by field. If you created a summary report, but then the field that controlled the grouping was deleted, your summary report would load as a completely blank page.
After this fix, if the grouping on a summary report is misconfigured, an error message prompts you to fix the report. If you don’t have edit permissions, you will be prompted to ask someone who has edit permissions to fix the report
|Users were unable to use the Find/replace in these records feature to replace reference field values in table reports.
Reference fields are able to be updated through Find/replace in these records