Good morning, I'm wondering what is the recommende...
# box-products
h
Good morning, I'm wondering what is the recommended Coldbox approach for storing temporary settings/filters? For example, I have a tabular list of purchase orders and at the top of the page there are options to filter the list down by department, order number, date submitted, etc. The previous way I would accomplish this was to store the filter(s) in the user's session, like session.POfilters.department = dept_id This would allow the user to filter the list, open a purchase order to work on, then upon returning to the list the filter(s) would still be in place until they cleared them or logged out.
r
Just a different approach, but I do this often and use cgi.query_string on redirects and back buttons. This way the user stays on the same search filters/results and no sessions needed.
p
I have utilized this for things that are multi-step related and pass around data I need to retain
r
@Patrick good idea I always think of it just for messages but it would be perfect for that
🤘🏻 1
h
I used to pass filters in the query strings or form scope, but Flash RAM looks like what I'm looking for, thanks for the suggestion.
👍🏻 1
b
@hemi345 There's nothing wrong with still using the session scope in ColdBox.
The ColdBox flash ram is nothing more than a facade to the session scope by default anyway.
h
yeah, as I was reading the docs on flash ram, I see that. I might as well try to use it on this site redesign though as it looks like it has a few nice features to help manage it.