đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
In Skuid on Salesforce (SFX), it's possible to build and save a page that's larger than the character limit.
Skuid's page composer should visually show a user how large the page is (its XML length) in comparison to how close they are to the limit.
If the page's XML length is nearing the limit, the page composer should guide users towards the best practice of splitting new functionality into a separate page (leveraging page-include components).
The page composer should disable the page composer's save button if the user's unsaved changes might generate XML that's too big to be saved correctly.
The save process should validate the XML that's being saved before any data changes are made.
It'd be great to have visibility into this before running into the limit and losing the work that was in flight when you hit it. Love this idea!