Repository navigation
Update FullStory for E/A#106001 Category restriction warnings and offline expense recategorization #106305
Description
What changed
#106001
Members now see “Category not allowed” on expenses when their workspace restricts them from using the selected category. The warning clears immediately when they select an allowed category or clear the selection, including offline; moving expenses checks the destination expense owner’s category access.
Suggested tracking
| Type | What to track | Name | Where in code | Details | Confidence |
|---|---|---|---|---|---|
| Event | Exposure to the category restriction error | Error_message (existing event) | MoneyRequestView category error display, src/components/ReportActionItem/MoneyRequestView.tsx:1555–1571 | Reuse Error_message with screen_name set to the actual screen, component_name=MoneyRequestView, error_location=category, error_code=categoryNotAllowed, error_type=policy_violation, error_message=Category not allowed. Emit once when this specific violation becomes visible, using structured violation data and the category row’s visibility gates—not translated-text matching or every render. This captures an error condition, not a click; no new event name is needed. Send only constant error metadata, not category names, expense details, or owner identifiers. Do not treat optimistic warning removal as confirmed success. | high |
Open questions
Is an equivalent category restriction error already captured by a definition configured outside the repository in FullStory? Confirm before adding instrumentation to avoid double-counting.
Activity