# Override caching of attribute values in user form for interactive apps

**URL:** <https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676>\
**Category:** Feature Requests and Roadmap Discussion\
**Tags:** feature-request\
**Created:** [January 17, 2020, 9:05pm UTC](https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676 "2020-01-17T21:05:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rengland](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/rengland/32/227_2.png) [@rengland](https://discourse.openondemand.org/u/rengland)\
**Post date:** [January 17, 2020, 9:05pm UTC](https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676/1 "2020-01-17T21:05:48Z")

</div>

Is there a way to override the caching of values assigned to job submission settings in the user forms for interactive applications? The caching is a nice feature at times, but we have seen several cases where users are requesting more resources than they really need for some of their submissions, and it seems that it is because they don’t bother to update the forms to accommodate smaller jobs after they have already run some larger jobs.

We are using OOD 1.1.5.

Thanks,

Richard

---

<div class="post-metadata">

**Author:** ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)\
**Post date:** [January 17, 2020, 10:17pm UTC](https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676/2 "2020-01-17T22:17:19Z")

</div>

Not natively it seems. Someone asked the same thing [in this question](https://discourse.openondemand.org/t/verifying-a-few-details-about-rstudio-app-setup-configuration/664/4) so if you don’t mind I’m moving this to feature requests.

Eric asks in the other topic what they envision for this? I guess it’s a question of scope - toggling caching for a single element, per application or system wide?

---

<div class="post-metadata">

**Author:** ![rengland](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/rengland/32/227_2.png) [@rengland](https://discourse.openondemand.org/u/rengland)\
**Post date:** [January 22, 2020, 4:20pm UTC](https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676/3 "2020-01-22T16:20:47Z")

</div>

My preference in an attribute cache toggle feature would be a system-wide toggle with other optional “exception” toggles at the application level to override the system toggle, and more optional toggles at the attribute level to override the application toggle. If I had to choose just one, though, it would be a toggle on each attribute - the reason being that as I’m creating a new application configuration, I tend to just copy-and-paste, so it really isn’t that inconvenient for me. But that’s just my two cents. Others may feel differently.

---

<div class="post-metadata">

**Author:** ![efranz](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/efranz/32/27_2.png) [@efranz](https://discourse.openondemand.org/u/efranz)\
**Post date:** [January 22, 2020, 5:24pm UTC](https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676/4 "2020-01-22T17:24:20Z")

</div>

This actually seems like a straightforward thing to implement. I opened [https://github.com/OSC/ondemand/issues/386](https://github.com/OSC/ondemand/issues/386) to track this work.

---

<div class="post-metadata">

**Author:** ![westburg.2](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@westburg.2](https://discourse.openondemand.org/u/westburg.2)\
**Post date:** [May 26, 2022, 4:11pm UTC](https://discourse.openondemand.org/t/override-caching-of-attribute-values-in-user-form-for-interactive-apps/676/5 "2022-05-26T16:11:40Z")

</div>