Currently, we make rapid file changes and have to test by uploading the file each time to a particular space's "static resources". However, Jive aggressively caches based on the URL, so subsequent changes are never seen/respected despite a checksum difference.
Is it possible to define per-space/URL addresses that Jive will NOT cache? Is there a function made available to FTL/SOY files that can randomly generate a UUID or content-based hash that can be used in the URL calling the asset? Is there anything sans setting a server-wide disabling of cache that we can do to help expedite our workflow?