Configuration Jive Widget

Data

• Endpoint (endpoint, default: ["1"])

  • One or more endpoint selectors passed to GraphQL operations.

  • Accepted formats:

    • array input from widget config (["1", "2"]),

    • JSON string arrays ('["1","2"]'),

    • bracketed list strings ([DB1,DB2]),

    • comma-separated strings (DB1,DB2).

  • Examples: ["1"], ["1", "2"], ["TANGO_HTTP_1", "TANGO_HTTP_2"].

• Search Cache TTL (seconds) (searchCacheTtlSeconds, default: 86400)

  • Controls how long the search index cache is considered fresh.

  • 86400 means the cache expires after 24 hours.

  • 0 means the cache is immediately expired and will refresh whenever the widget evaluates cache freshness.

• Highlight Search Matches (highlightSearchMatches, default: true)

  • Enables visual highlighting of matching text in:

    • device tree labels and device names,

    • attribute names,

    • command names,

    • property names.

  • Set to false to disable highlighting while keeping search/filter behavior unchanged.

• DevString View Mode (devStringViewMode, default: plain)

  • Controls how DevString values render in scalar details and non-numeric spectrum tables.

  • Options:

    • plain: raw string output.

    • json-tree-expanded: parsed JSON tree with all levels expanded.

    • json-tree-collapsed: parsed JSON tree with nested levels collapsed behind expand arrows.

Cache Expiration Behavior

Search index cache is stored in browser localStorage, scoped by widget instance and endpoint set.

• If a valid cache exists and is not expired:

  • search is immediately available,

  • no automatic refresh is started.

• If cache is expired:

  • existing cached results are used immediately (if present),

  • refresh runs in background to replace stale data.

• If no cache exists:

  • the widget builds the index from live queries,

  • search is temporarily disabled until the first index build completes.

Manual refresh is always available from the cache card via Refresh now.