Why Are Things Still Showing Up As Using JS?
Like some others, I have been working on adjusting a few pieces of our app to accommodate for the new JS usage rules and I have quite a few fields that I thought were fixed as I am now directing the ...
Forum Discussion
Posting an example of a field that says it still contains JavaScript would be the most helpful thing here I think. When you load into the field in your app do you get a little popup in the bottom right corner saying you still need to change it?
Not sure about the JavaScript Usage App, never seen that.
Not sure about the JavaScript Usage App, never seen that.
Thanks Austin. I do not get the "unsupported code" popup when I open those fields anymore, which is part of the reason I assumed the fields were fixed (and they very well may be).
The Inserted Javascript Usage app was something quickbase released on resources.quickbase.com with the initial announcement about the changes that is supposed to identify areas in your app(s) where unsupported scripting is in use so developers can fix it. From my understanding, it scans your apps weekly and I figured it would no longer display fields once they had been corrected, but I feel like I'm doing a lot of assuming here. That was the main point of my question--I'm just disappointed to have not received the gratification of a smaller number after making changes.
------------------------------
Ryan Huffman
------------------------------
The Inserted Javascript Usage app was something quickbase released on resources.quickbase.com with the initial announcement about the changes that is supposed to identify areas in your app(s) where unsupported scripting is in use so developers can fix it. From my understanding, it scans your apps weekly and I figured it would no longer display fields once they had been corrected, but I feel like I'm doing a lot of assuming here. That was the main point of my question--I'm just disappointed to have not received the gratification of a smaller number after making changes.
------------------------------
Ryan Huffman
------------------------------
- Is your app sandboxed? Even without a sandbox created if it is enabled that often prevents things from being done to it. It is the reason I both love and hate the App Library that someone released before. It does not update an app when the sandbox is open because field settings are not accessible.
It is not. We are on the Premier level plan and I don't think we pay for that because I never asked anyone to.
Might just be a bug in the Javascript app. I'm fairly sure the fields I've been working with are clear. All I'm doing is creating buttons that direct users to a code page with some URL tags and dynamic styling information. As you mentioned, I no longer get the warning when I go to edit those fields.
Thanks for your answers!
------------------------------
Ryan Huffman
------------------------------- Hi Ryan,
In the Inserted Javascript Usage App fields that have been address don't disappear from the app since it is possible for fields to be edited to have javascript in them again at the time of the next audit. Instead in the app if you click on the View All Exceptions button on the dashboard, and looks at the Last Identified On column, you can see the last time the app detected unsupported content in that field. Then if you look into the app branding you can see the last time the app was updated. If your Last Identified On date is before the last time the app was updated then that field is currently not flagging any content. The fact that the Unsupported Content Pendo message no longer appears for a given field, is strong evidence that your update fixed that field. I hope that helps with identifying the fields you have resolved.
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------
