[UXPROD-3958] Configure Fast Add Suppressed by Default according to the app where Fast Add is opened from Created: 09/Jan/23 Updated: 30/Nov/23 |
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Erin Nettifee | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | check-out, courses, enettifee-reviewed, inventory | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Development Team: | None |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R3 |
| Description |
|
Current situation or problem: This includes whether the instance is suppressed from discovery by default. Some libraries would like the ability to configure suppress from discovery according to the app where Fast Add was used. E.g., they want Fast Add records created from the Courses app to be available in discovery by default, but they want fast add records created from the Check out app to be suppressed by default. In scope
Out of scope
Use case(s)
Proposed solution/stories Links to additional info
Questions |
| Comments |
| Comment by Thomas Trutt [ 08/Feb/23 ] |
|
I wonder if a better approach would be to allow for different FastAdd templates. |