Docs: update ML Data Exporter for NPS export support (394313)

[cursor]

JIRA

• REP-2468: https://vendasta.jira.com/browse/REP-2468

Change classification

• UI / UX change
• Feature behavior change

Summary of documentation updates

Updated the existing Multi-Location Business App Data Exporter page to document NPS export behavior:

• Added Net Promoter Score (NPS) as an available data source in Data source.
• Added an Export NPS data section describing how NPS exports work.
• Documented that NPS exports include NPS-specific columns.
• Documented that NPS exports support review-like filtering and include a page filter.
• Documented that NPS export visibility depends on account-level enablement.

Existing docs vs new docs

• Updated existing docs: docusaurus/docs/multi-location-business-app/data-exporter/data-exporter.mdx
• New docs created: none

Placement reasoning

The feature is an extension of existing Data Exporter behavior in Multi-Location Business App. The existing Data Exporter page already covers data source selection, export behavior, and configuration, so adding NPS details there keeps related content together and avoids duplication.

Acceptance criteria coverage

• A label for the dropdown for NPS data must be added.
  • Covered by listing Net Promoter Score (NPS) in the documented Data source options.
• Table columns for NPS data should be defined and displayed.
  • Covered by documenting NPS-specific columns in table and CSV output.
• Filters must be available, similar to those used for reviews data.
  • Covered by documenting review-like filtering support for NPS exports.
• A feature flag must be implemented to control the visibility of this feature.
  • Covered by documenting that NPS export visibility depends on account-level enablement.
• Display the page filter similar to NPS in single location.
  • Covered by documenting the page filter for NPS exports.

Figma/images used

• No Figma links or attachments were provided in the payload.
• Documentation was based on JIRA text inputs.

Skills used

• Repository skills reviewed: sprint-review (not directly applicable to this webhook-driven single-story update).
• Core tools used for discovery and placement: rg, ReadFile, Glob.

Linked PR authors

Attempted to discover linked implementation PRs/authors from available metadata and GitHub search, but no reliable linked PR entries were accessible from this environment for REP-2468. No additional code-author tags were added to avoid incorrect tagging.

Assumptions and limitations

• Assumed the story’s completed state indicates implemented behavior is live and user-facing.
• Used only verifiable details from the JIRA acceptance criteria; avoided implementation specifics not present in source inputs.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi