You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're in the final implementation phase for card feeds in NewDot, and as part of that initiative, we need to add a way for admins to bulk select all cards from a certain feed.
Rather than add two separate filters (and the accompanying search syntax), we're going to add a way to bulk select a whole series of cards in the Card filter. The benefit of this is that we prevent search "collisions" on two separate filters. For example, imagine that we had a filter for Feed. If you selected Chase for that option, you would also be selecting all Card numbers that also belonged to the same feed. However, in our current logic the Card filter would be empty.
Long story story, a feed is just a way of bulk selecting cards. Similarly, the Card filter is already by design a way to select one or more cards. As a result, we're going to do the following:
Keep the name of the Card filter
Within the Card filter, admins will see two sections: Card feeds and Individual cards (note for emphasis: the workspace role for member never sees the Card feeds section)
Further, within the Card feeds section, if a user has more than one feed, then we'll append either the domain name or the workspace name (e.g. All Expensify - [workspace name] or All Expensify - [domain]. The domain name only applies for domain feeds, and the workspace feed only applies for workspace feeds. These names are truncated where applicable.
When a value is selected in the Card feeds section, that's equivalent to a user individually selecting all individual cards. However, we don't do that when a feed is selected, as the card feed is it's own distinct selection.
It's also worth noting that it's possible to select an entire feed as well as individual cards that may not be part of the same feed. Similarly, if a feed is chosen and individual cards within the same feed are also chosen, that's the same as just selecting the feed.
Finally as a reminder, the search input only appears when a given list has more than 8 options. This is our standard for when the search input is shown versus not, though I'm including this as a reminder.
Taken together, the updated filter will look like this.
The text was updated successfully, but these errors were encountered:
We're in the final implementation phase for card feeds in NewDot, and as part of that initiative, we need to add a way for admins to bulk select all cards from a certain feed.
Rather than add two separate filters (and the accompanying search syntax), we're going to add a way to bulk select a whole series of cards in the
Card
filter. The benefit of this is that we prevent search "collisions" on two separate filters. For example, imagine that we had a filter forFeed
. If you selectedChase
for that option, you would also be selecting allCard
numbers that also belonged to the same feed. However, in our current logic theCard
filter would be empty.Long story story, a feed is just a way of bulk selecting cards. Similarly, the
Card
filter is already by design a way to select one or more cards. As a result, we're going to do the following:Card
filterCard
filter, admins will see two sections:Card feeds
andIndividual cards
(note for emphasis: the workspace role formember
never sees theCard feeds
section)Card feeds
section, if a user has more than one feed, then we'll append either the domain name or the workspace name (e.g.All Expensify - [workspace name]
orAll Expensify - [domain]
. The domain name only applies for domain feeds, and the workspace feed only applies for workspace feeds. These names are truncated where applicable.Card feeds
section, that's equivalent to a user individually selecting all individual cards. However, we don't do that when a feed is selected, as the card feed is it's own distinct selection.Taken together, the updated filter will look like this.
The text was updated successfully, but these errors were encountered: