#158 — Correct on-boarding detection logic.

Repo: Twill-AI/twill-ai-ui State: closed | Status: done Assignee: Unassigned

Created: 2024-12-11 · Updated: 2025-03-11

Description

Caused by https://twill-network.slack.com/archives/C06UCQP1BFC/p1733850394085219 (1st item).

UI should differentiate “tenant doesn’t have data to show Home” and “tenant has all integrations disabled”.

Note that if tenant has 1 state=ready integration and it is being restarted or disabled then integration’s state turns to “not_ready” and turns to “ready” or “error” only after BusinessData service confirms that synchronization with Rutter was finished. So using just GET /integrations output is not enough.

Actually keeping state of “user has some data” on back-end is error prone solution. While this effectively means that GET /home returns something (because “recents” field here may be empty only if user have not created any queries).

AC:

• Show on-boarding questionnaire only if GET /self-management/tenant llm_info is empty.
• Show Home screens in 2 cases:
  • GET /self-management/tenant returns 200 with not empty llm_info and GET /integrations returns at least 1 integration with state in [ready, not_ready, failed] (note that state=disabled is not a reason to hide Home screens),
  • OR response of GET /home is not empty.

Notes

Add implementation notes, blockers, and context here

Related

Add wikilinks to related people, meetings, or other tickets