Blog Post
@Michael Frishman There is going to be some pain points when it comes to our locking down of Javascript functionality and removing it from form and branding injection. It was driven in large part by the need to remove this security concern and also to allow development going forward. That is why in our current framework we are locking the ability to create or edit new Javascript in April but not immediately breaking anything existing, though now as always things may break over time as we launch new features and functionality since they were not supported or tested against.
This is in effort to allow customers time to transition where we do have tools available, and we have been publishing some new resources on how to replicate some uses of Javascript in forms and branding using Code pages, which are allowed and aren't getting locked down. You can find our ongoing example of that here in our Code Page sample app. We have also recently made the change to making Quickbase channel Pipelines free so a number of workflows that used those buttons to move around data can now use the integration powers of Pipelines to address those needs securely. There are still going to be some gaps though, is there a specific use case you are worried about?
This is in effort to allow customers time to transition where we do have tools available, and we have been publishing some new resources on how to replicate some uses of Javascript in forms and branding using Code pages, which are allowed and aren't getting locked down. You can find our ongoing example of that here in our Code Page sample app. We have also recently made the change to making Quickbase channel Pipelines free so a number of workflows that used those buttons to move around data can now use the integration powers of Pipelines to address those needs securely. There are still going to be some gaps though, is there a specific use case you are worried about?