Blog Post
Hi Everyone,
We have some changes coming up with our April release I thought a lot of you would be interested to see some of the upcoming changes we have for formula-url and formula-rich text fields so wanted to highlight them here:
@Avinash Sikenpore
The new open a formula as a pop up function should help you with your first point in your list. You should now be able to have a pop up of that report without pulling your user away from their main page once the April release goes live.
As to your other feedback it is always really important for us to get specific use cases like that so we can get a clear picture of where the experience gaps exist for you. There are some things we aren't going to be replicating in the platform after Javascript is shut down but there are opportunities for these needs to inform our continuing platform enhancements. I don't have a specific release or date for you but I know button styling is something we are often talking about evolving in the future.
@Jake R Thank you for your feedback we are certainly taking in all the feedback and concerns we are getting from our customers. This change is motivated by a need for security and reliability which at this time does trump some of the user experience pieces that Javascript is being used for today in the platform. Unfortunately that means that there are going to be pain points during this transition but your feedback and the feedback of other builders helps us to pin point areas where we can alleviate that pain and offer alternatives ahead of the specific retirement dates (many of the above enhancements in the April release got a higher priority due to customer feedback). There are going to be instances where we aren't going to offer one to one alternatives because the use of Javascript was so varied (and at times at odds with best practices and those same security concerns) but we do want to do the best to offer better workflow alternatives with a much better security and reliability focus. Was there a specific workflow or pain point you have that we might be able to help with or speak to specifically?
We have some changes coming up with our April release I thought a lot of you would be interested to see some of the upcoming changes we have for formula-url and formula-rich text fields so wanted to highlight them here:
More control over formula-url and formula-rich text fields
These features and capabilities include:
-
Open a formula url as popup allows builders to set a website to open in a popup window and the existing setting to open in a new tab. You can use the same functionality with formula-rich text by applying the CSS class (OpenAsPopup).
-
Builders can now use a new CSS class (SaveBeforeNavigating) inside of a formula-rich text field so that Quickbase saves the record before navigating when this setting is used.
Note that only one of the above workflow classes is supported per formula-rich text.
Embed a secure, external website as an iframe on a form. This provides builders a way to embed YouTube videos or other file services (Box, Drive, etc.) as a file preview. For security purposes, the only *.quickbase.com URLs that are supported are for code pages. All other native pages (*.quickbase.com URLs) do not function when embedded on a Quickbase form.
If you are interested in what other features our April release has the release notes are now live right here.
@Avinash Sikenpore
The new open a formula as a pop up function should help you with your first point in your list. You should now be able to have a pop up of that report without pulling your user away from their main page once the April release goes live.
As to your other feedback it is always really important for us to get specific use cases like that so we can get a clear picture of where the experience gaps exist for you. There are some things we aren't going to be replicating in the platform after Javascript is shut down but there are opportunities for these needs to inform our continuing platform enhancements. I don't have a specific release or date for you but I know button styling is something we are often talking about evolving in the future.
@Jake R Thank you for your feedback we are certainly taking in all the feedback and concerns we are getting from our customers. This change is motivated by a need for security and reliability which at this time does trump some of the user experience pieces that Javascript is being used for today in the platform. Unfortunately that means that there are going to be pain points during this transition but your feedback and the feedback of other builders helps us to pin point areas where we can alleviate that pain and offer alternatives ahead of the specific retirement dates (many of the above enhancements in the April release got a higher priority due to customer feedback). There are going to be instances where we aren't going to offer one to one alternatives because the use of Javascript was so varied (and at times at odds with best practices and those same security concerns) but we do want to do the best to offer better workflow alternatives with a much better security and reliability focus. Was there a specific workflow or pain point you have that we might be able to help with or speak to specifically?