Add comprehensive Hex documentation with 14-day visibility limitation #2010
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add comprehensive Hex documentation with 14-day visibility limitation
Summary
Replaces the placeholder Hex documentation (which was just a card linking to a Tally form) with comprehensive user-facing setup documentation. The new documentation follows the same structure as other BI tool integrations (like Sigma) and includes the critical 14-day visibility limitation as specified in the Linear ticket ELE-5071.
Key additions:
The 14-day limitation is based on the
days_back: int = 14parameter found inHexQueryHistoryReader.read_hex_queries_from_history()in the elementary-internal codebase.Review & Testing Checklist for Human
HexQueryHistoryReaderimplementation actually uses 14 days and that this matches the user-visible behaviorNotes
/cloud/integrations/bi/sigma.mdxas requested