Users cannot save branding that contains unsupported content. This change affects branding set both at the app level and at the realm level. We disabled the ability to insert and/or edit custom code such as JavaScript in custom branding on June 13. We also updated this style so that filters or searches applied on new table reports before entering grid edit are maintained when you save or cancel out of grid edit.
Quickbase release notes how to#
Read more about how to use the new style and why we made these changes in our Quickbase Community article or help center.
However, we’ll keep the toggle around for a period of time while we confirm that this style serves the needs of the Quickbase community. We removed the word “beta” from the table report toggle to reflect this.Įventually, we’ll remove the toggle entirely so all customers will use this style. The new table report style is now the default for all users. To learn more about the capability and the use cases it supports, review our Automation migration help topic, or read more on the Automating with Pipelines Quickbase Community page. You can migrate one automation at a time, and there's no limit to the amount of automations you can migrate. You can continue running your automated workflow without interruption, while the flexibility, scalability, and speed of Pipelines ensures that your processes are always ready to grow with your business.īeginning June 21, you can find the new migration capability on any page that displays automations in your Quickbase apps. Use this new capability to easily convert your existing Quickbase automations into Pipelines. New Automations to Pipelines migration capability
0 kommentar(er)
