2026-03-18 Cross App SIG Meeting notes
Date
Mar 18, 2026
Attendees
Joe Reimers, Kimberly Smith, Tara Barnett, Laura Daniels, Charlotte Whitt, Owen Stephens, Alissa Hafele, Maura Byrne, Kristin Martin
Homework
Housekeeping
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
5 min | Announcements/Housekeeping |
|
|
40 min | Acquisitions Functionality | Joe Reimers |
|
5 min | Monitoring |
|
|
Notes
Housekeeping
Reminder that our April 1st meeting is canceled for calendar calming (Easter week).
The group is still seeking a co-convener; Laura Daniels has expressed interest but a second person is needed. Tara will remain through March and April while the search continues.
A draft WOLFcon working session has been prepared but needs a volunteer to submit and present it, as Tara will not be attending in person or virtually.
Default search behavior in acquisitions
Joe presented an issue raised by the Stripes team: the Acquisitions app remembers filters from session to session (durable/sticky filters), which is inconsistent with the default Stripes behavior of starting with no filters selected.
When a user pastes a URL in Orders, the app's remembered/durable/sticky filters are applied on top of it, causing unexpected results--what you see in the app may be different from what another user sees with the same URL. All agree strongly that pasted URLs must be obeyed absolutely—the URL should always take precedence over any stored filter state, even mid-session.
Owen noted that Agreements has a similar but distinct behavior: default filters are applied on load, but the address bar always takes precedence over them.
Hard refresh should also reset filters.
We talked about desired behavior--do we want some aspect of durable/sticky filters to remain between sessions, or do we want defaults that can be set intentionally in the app?
Folks expressed strong preference for user-configurable default filters over session-memory behavior, noting that sticky filters from a previous session are frequently confusing in workflows.
This is more work but potentially more useful. This distinction was widely supported in chat.
The ideal solution is personalization—allowing each user to set their own default filters per app. Laura noted in chat that she would not want the same defaults as many of her staff, reinforcing the case for per-user rather than tenant-wide settings.
Would it be possible to "save" a set of filters from within the app UI?
On setting defaults:
Personalization should probably be per-app or per-section of FOLIO rather than a single global toggle.
How do we highlight to users that personalized defaults are applied? The little gray x next to the search is insufficient. Should we use better icons, maybe a summary at the top somewhere?
Next Steps
The group agreed user stories should be collected from all relevant SIGs—app by app—to capture when preserving the last filter is useful vs. when defaults or a clean state are preferred.
At our next meeting, we will draft a short slide deck and a set of talking point to take to individual SIGs.
We also need a list of all SIGs and who is responsible.
We can update the wiki page ourselves, Joe says.
Once SIG feedback is collected, Joe will work with Stripes to define and build out the feature properly.
What we agreed on for personalized defaults:
URLs should always be obeyed
Hard refresh should reset filters--you should not have to log out and in again to reset
Some degree of persistence within a session may be desirable across apps--we need to understand the current and desired behavior
Defaults that are retained between sessions should be set user-by-user.
Defaults should be set within the app rather than in settings.