Roadmap

{“ops”:[{“insert”:”When a user navigates to a different dashboard using a button widget (not a browser button), ensure that the dashboard they navigate to provides a way for them to return to the original dashboard. This will improve user experience by allowing easy navigation back to where they started.”},{“insert”:”n”},{“insert”:”n”,”attributes”:{“block-id”:”block-db8ed0d6-4a80-45e1-8cfb-f786b4c9188a”}},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“attributes”:{“bold”:true},”insert”:”Title:”},{“insert”:” “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1526″,”title”:”feat: add dashboard breadcrumb navigation system”}}},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“attributes”:{“bold”:true},”insert”:”Created by:”},{“insert”:” Malachi Bazar on 01/06/2026 04:21 PM (America/Chicago)”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Summary by CodeRabbit:”},{“insert”:”nnNew FeaturesnAdded breadcrumb navigation trail in dashboard headers (desktop and mobile), allowing users to track and navigate back through their dashboard history.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Added home button in breadcrumb to quickly return to the main dashboards view.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Enhanced navigation when drilling down from widget buttons and drilldown actions to maintain navigation history.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”nDocumentationnUpdated guidance for Angular 19 component declarations to reflect new defaults.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n✏️ Tip: You can customize this high-level summary in your review settings.n”}]}

Implement integration with Autotask to enable seamless synchronization of tickets, contacts, and project data between our platform and Autotask. This integration will allow users to automate workflows, improve service delivery, and centralize client management. Key features should include:

Ticket syncing
Contact and company data integration
Automated status updates and notifications
Secure authentication and data transfer
Custom mapping for fields and workflows

Incremental Syncing Strategy
There is a specified total to sync
Find the count of all items that have been entered a week ago. If there are less items than the total count to sync, increase the filter range to 1 month and so on until the count of items is more than the required amount or the count hasn’t increased between 3 searches.

Companies
Contacts

{“ops”:[{“attributes”:{“block-id”:”block-a610be32-7772-4f10-80e7-15cf659cbd71″},”insert”:”n”},{“insert”:”n”},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1537″,”title”:”feat: add HaloPSA integration with multiple data endpoints”}}},{“insert”:”nn”},{“attributes”:{“bold”:true},”insert”:”Summary:”},{“insert”:”nAdd HaloPSA integration with OAuth2 Client Credentials flownImplement data sync for 5 endpoints: Tickets, Clients, Agents, Actions, InvoicesnAdd Pydantic models for data validation with human-readable field aliasesnSupport incremental sync for Tickets, Actions, and Invoices via timestamp fieldsnFull sync for Clients (daily) and Agents (every 30 min) due to API limitationsnn”},{“attributes”:{“bold”:true},”insert”:”Endpoints:”},{“insert”:”nn”},{“insert”:”nnnn”,”attributes”:{“table-col”:{“width”:”150″}}},{“insert”:”Endpoint”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-eigk-1″,”row”:”row-eigk”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Sync Type”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-eigk-2″,”row”:”row-eigk”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Interval”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-eigk-3″,”row”:”row-eigk”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Ordering Column”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-eigk-4″,”row”:”row-eigk”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Tickets”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-3fdm-1″,”row”:”row-3fdm”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Incremental”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-3fdm-2″,”row”:”row-3fdm”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”5 min”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-3fdm-3″,”row”:”row-3fdm”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”last_update”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-3fdm-4″,”row”:”row-3fdm”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Clients”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-n7qj-1″,”row”:”row-n7qj”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Full”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-n7qj-2″,”row”:”row-n7qj”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Daily”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-n7qj-3″,”row”:”row-n7qj”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”id”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-n7qj-4″,”row”:”row-n7qj”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Agents”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-iuoy-1″,”row”:”row-iuoy”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Full”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-iuoy-2″,”row”:”row-iuoy”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”30 min”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-iuoy-3″,”row”:”row-iuoy”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”id”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-iuoy-4″,”row”:”row-iuoy”,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Actions”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-rua2-1″,”row”:”row-rua2″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Incremental”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-rua2-2″,”row”:”row-rua2″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”5 min”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-rua2-3″,”row”:”row-rua2″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”actiondatecreated”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-rua2-4″,”row”:”row-rua2″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Invoices”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-m448-1″,”row”:”row-m448″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”Incremental”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-m448-2″,”row”:”row-m448″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”60 min”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-m448-3″,”row”:”row-m448″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”last_modified”},{“insert”:”n”,”attributes”:{“table-cell-line”:{“cell”:”row-m448-4″,”row”:”row-m448″,”colspan”:”1″,”rowspan”:”1″}}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Test Plan:”},{“insert”:”nVerify OAuth2 authentication with HaloPSA credentials”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Test initial data pull for each endpoint”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Verify incremental sync works correctly for Tickets, Actions, Invoices”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Confirm pagination handles large datasets properly”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Test field validation and alias mapping in Pydantic models”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“italic”:true},”insert”:”No coderabbitai summary or comments were found for this pull request.”},{“insert”:”n”,”attributes”:{“header”:2}}]}

{“ops”:[{“attributes”:{“block-id”:”block-264938ec-0738-41fa-8280-1695cf9d29ed”},”insert”:”n”},{“insert”:”n”},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“attributes”:{“bold”:true},”insert”:”Title:”},{“insert”:” “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1573″,”title”:”fix: prevent 2FA dialog race condition during token URL login”}}},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“attributes”:{“bold”:true},”insert”:”Created by:”},{“insert”:” Malachi Bazar on 01/15/2026 03:51 PM (America/Chicago)”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”nPull Request Summary”},{“insert”:”n”,”attributes”:{“header”:4}},{“attributes”:{“bold”:true},”insert”:”Summary:”},{“insert”:”nSkip showing the 2FA reminder dialog when there’s a pending token login (?token=xxx in URL). Fixes race condition on slower machines where the 10ms init timeout fires before the router processes the token.nn”},{“attributes”:{“bold”:true},”insert”:”Root Cause:”},{“insert”:”nWhen users arrive with a token URL, the AuthService 10ms timeout could fire before the router processes the query param, causing prompt2FA() to run with stale user data. This caused the 2FA dialog to appear for Liongard users even though it shouldn’t.nn”},{“attributes”:{“bold”:true},”insert”:”Solution:”},{“insert”:”nAdded a check at the beginning of prompt2FA() to return early if a token is present in the URL. After the token is processed and removed from the URL, initAppWithAuth() is called again, triggering prompt2FA() with the correct user data.nn”},{“attributes”:{“bold”:true},”insert”:”Test Plan:”},{“insert”:”nLog in as a Liongard user via token URL”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Verify the 2FA dialog does NOT appear”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Test on slower network (Chrome DevTools → Network → Slow 3G)”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Verify lint passes: npx nx lint frontend”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Verify build succeeds: npx nx build frontend”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:{“divider”:true}},{“insert”:”n”}]}

Search the codebase for TODO TLA TEMPLATE for the relevant code.

1 – We need a new request CHECK_USE_TEMPLATE_LIMIT request that batches the errors for USE_TEMPLATE so the front end can display what’s wrong to the user while they’re in the template menu
2 – We need a COUNT_DASHBOARD_LIMIT_ITEMS request that will be used by CHECK_USE_TEMPLATE_LIMIT and used in general for showing how much sTuFf a template holds. Probably will also be used by other requests for minimal code duplication
3 – Add validators to USE_TEMPLATE at appropriate places, dash count in the first lines and the other items as needed

base branch:

Search the codebase for the keyword TODO TLA WF , this will point to all the spots that have to be addressed.

base branch:

developer.simplesat.io

{“ops”:[{“insert”:”n”,”attributes”:{“block-id”:”block-8a938a85-87c9-4dd9-8c84-fc699c9d9000″}},{“insert”:”n”},{“insert”:”Related Pull Request”},{“insert”:”n”,”attributes”:{“header”:2}},{“insert”:”n”},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1555″,”title”:”fix: add restoration logic for Date types in generate_modal_data function”}}},{“insert”:”nn”},{“attributes”:{“bold”:true},”insert”:”Summary by CodeRabbit:”},{“insert”:”nnDate x-axis values now receive the same flooring and aliasing treatment previously applied only to datetime values, ensuring consistent aggregation and labeling in data modals and charts.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Improves display accuracy and consistency for date-based visualizations, reducing mismatches between date and datetime presentations.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}}]}

Deploy the QuickBooks on-premise CData connector as part of Sprint 97. Ensure all necessary configurations and testing are completed for a successful deployment.

{“ops”:[{“insert”:”[datatype-api-689bb499c5-zvdb6] Status code: 400″},{“insert”:”n”,”attributes”:{“block-id”:”block-59dcc3db-95b9-4225-b7f3-425b9cc9bde6″}},{“insert”:”[datatype-api-689bb499c5-zvdb6] Response text: {“error”:”invalid_grant”,”error_description”:”AADSTS700084: The refresh token was issued to a single page app (SPA), and therefore has a fixed, limited lifetime of 1.00:00:00, which cannot be extended. It is now expired and a new sign in request must be sent by the SPA to the sign in page. The token was issued on 2026-01-15T16:18:32.9241057Z. Trace ID: 5d1859d2-4191-4bfd-a34f-e40576d74900 Correlation ID: f6189c9c-d7eb-49ed-90e4-63a68aa9f9ee Timestamp: 2026-01-16 17:35:29Z”,”error_codes”:[700084],”timestamp”:”2026-01-16 17:35:29Z”,”trace_id”:”5d1859d2-4191-4bfd-a34f-e40576d74900″,”correlation_id”:”f6189c9c-d7eb-49ed-90e4-63a68aa9f9ee”,”error_uri”:””},{“insert”:”https://login.microsoftonline.com/error?code=700084″,”attributes”:{“link”:”https://login.microsoftonline.com/error?code=700084″}},{“insert”:””}”},{“insert”:”n”,”attributes”:{“block-id”:”block-48caee1e-41ee-4064-9a65-3ca4aa99edc6″}},{“insert”:”[datatype-api-689bb499c5-zvdb6] Failed to refresh oauth token for source 8105d388-ad22-476e-97b6-98ab03cfd0ae. Error: Error refreshing oauth token”},{“insert”:”n”,”attributes”:{“block-id”:”block-6f479955-6b22-4055-a0c9-5e0a278933e5″}},{“insert”:”n”},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“attributes”:{“bold”:true},”insert”:”Title:”},{“insert”:” “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1584″,”title”:”fix: use confidential client flow for Excel OAuth to fix 24h token expiry”}}},{“insert”:”nn”},{“attributes”:{“bold”:true},”insert”:”Description:”},{“insert”:”nProblemnMicrosoft SPA refresh tokens expire after 24 hours (error AADSTS700084), breaking Excel sync jobs.nnSolutionnSwitch from SPA (PKCE) to Web (confidential client with client_secret) OAuth flow.nnChangesnBackend: ExcelOauthHandler now uses client_secret instead of PKCE”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Frontend: AzureOauthCallbackComponent no longer sends codeVerifier”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”nImpactnNew integrations: Tokens refresh indefinitely”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Existing: Need re-auth when current token expires”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”nTestingn✅ OAuth flow worksn✅ Token refresh worksnn”},{“attributes”:{“italic”:true},”insert”:”No coderabbitai summaries or comments were found for this PR.”},{“insert”:”n”,”attributes”:{“header”:2}}]}

{“ops”:[{“insert”:”Sentry Issue: [RESPLENDENT-BACKEND-1DR](“},{“insert”:”https://resplendent-data.sentry.io/issues/6708744446/?referrer=ClickUp”,”attributes”:{“link”:”https://resplendent-data.sentry.io/issues/6708744446/?referrer=ClickUp”}},{“insert”:”)nn“`nTraceback (most recent call last):n File “incremental_sync_worker.py”, line 306, in incremental_data_syncn update_response = await integration_map(n File “scripts/cloud_sync_agent/data_integrations/connectwise_api.py”, line 282, in get_updated_rowsn df = await get_connectwise_data(request_info, cw_report_prop)n File “scripts/cloud_sync_agent/data_integrations/models/connectwise/helpers.py”, line 369, in get_connectwise_datan raise HTTPError(nHTTPError: n Error getting data from ConnectWise.n Error code: 500n{n “code”: “ConnectWiseApi”,n “message”: “A timeout has occured. Please try again.”n}n ConnectWise Company: teqguysn n“`nby “},{“insert”:”[email protected]”,”attributes”:{“link”:”mailto:[email protected]”}},{“insert”:”n”},{“insert”:”n”,”attributes”:{“block-id”:”block-bb33235f-e158-41c8-b2a0-82793d3583bf”}},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request: “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1578″,”title”:”fix: prevent ConnectWise 500 timeout errors from being sent to Sentry”}}},{“insert”:”n”,”attributes”:{“header”:3}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”@coderabbitai summary:”},{“insert”:”nFixes RESPLENDENT-BACKEND-1DR. The issue was that: ConnectWise API timed out due to unencoded ‘>’ in the URL’s ‘conditions’ parameter for TicketAudit report.nn”},{“attributes”:{“bold”:true},”insert”:”Key Fixes:”},{“insert”:”nIntroduced a new custom exception, “},{“insert”:”ConnectWiseTimeoutException”,”attributes”:{“code”:true}},{“insert”:”, to specifically identify ConnectWise API 500 timeout errors.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Modified the ConnectWise API helper to raise “},{“insert”:”ConnectWiseTimeoutException”,”attributes”:{“code”:true}},{“insert”:” when a 500 status code is received, logging the error locally.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Updated the incremental sync worker to catch “},{“insert”:”ConnectWiseTimeoutException”,”attributes”:{“code”:true}},{“insert”:” and log it without sending it to Sentry.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Ensured that other HTTP errors from ConnectWise continue to be reported to Sentry.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”nThis fix was generated by Seer in Sentry, triggered by [email protected]. 👁️ Run ID: 8732367n”},{“insert”:{“divider”:true}},{“insert”:”n”}]}

Integration level inputs:
form builder with json positioning for each piece you can pick the dtype for each one

Stuff that varies by the table:
config for last update filtering (optional maybe)
config for column selection (optional)
config for page size / page selection

{“ops”:[{“insert”:”n”,”attributes”:{“block-id”:”block-6eca0c63-3e0f-45a6-aaeb-70e5afe63a5b”}},{“insert”:”n”},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1540″,”title”:”feat: add wl_env_id to JWT token for Pendo account ID”}}},{“insert”:”nn”},{“attributes”:{“bold”:true},”insert”:”Summary:”},{“insert”:”nAdd wl_env_id field to JWT tokens so Pendo can identify accounts using the wl_env_id prefix instead of instance.nn”},{“attributes”:{“bold”:true},”insert”:”Changes:”},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Backend”},{“insert”:”napps/backend/src/scripts/models/request_models.py: Add wl_env_id: str | None = None to JwtTokenPayload”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”apps/backend/src/scripts/Authenticator.py: Include wl_env_id=customer.wl_env_id in token payload”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Frontend”},{“insert”:”napps/frontend/src/app/interface-registry/data-service.interface.ts: Add wl_env_id?: string to IUserTokenPayload”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”apps/frontend/src/app/services/pendo.service.ts: Update account ID format to ${userData.wl_env_id || userData.instance}_${userData.serviceProviderId}”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”apps/frontend/src/app/services/auth.service.ts: Extract wl_env_id from token for Pendo initialization”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Details:”},{“insert”:”nPendo account ID now uses wl_env_id when available, falling back to instance for backward compatibility”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Supports both internal login and external API token generation (no additional changes needed for external API)”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Users will need to re-authenticate to get tokens containing the new wl_env_id field after deployment”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“italic”:true},”insert”:”No coderabbitai summaries or comments were found for this PR.”},{“insert”:”n”,”attributes”:{“header”:2}}]}

{“ops”:[{“insert”:”n”,”attributes”:{“block-id”:”block-2eda50ca-9071-48dd-97a3-c19b816ccd5a”}},{“insert”:”n”},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1572″,”title”:”fix: offline dialog showing up for users on slow computers/proxies”}}},{“insert”:”nn”},{“attributes”:{“bold”:true},”insert”:”Summary:”},{“insert”:”nAdds /api/health endpoint to verify actual backend connectivitynReplaces unreliable navigator.onLine browser API with health check pollingnImplements retry logic (3 retries over ~10s) before showing offline dialognAdds dismiss button for users to manually close false positive dialogsnn”},{“attributes”:{“bold”:true},”insert”:”Problem:”},{“insert”:”nSome users were seeing the “You are offline” dialog even when online. This was caused by navigator.onLine returning false in certain network configurations (proxies, VPNs, corporate firewalls).nn”},{“attributes”:{“bold”:true},”insert”:”Solution:”},{“insert”:”nInstead of trusting the browser’s network detection, we now ping the actual backend /api/health endpoint every 30 seconds. If a health check fails, we retry 3 more times over ~10 seconds before showing the offline dialog. This prevents flapping on intermittent connections.nn”},{“attributes”:{“bold”:true},”insert”:”Test plan:”},{“insert”:”nVerify /api/health returns 200 OK”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Stop backend while frontend is running → offline dialog appears after ~10s”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Restart backend → dialog disappears on next poll”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Click “Dismiss” button → dialog closes and stays closed until next offline event”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“italic”:true},”insert”:”No coderabbitai summaries or comments were found for this PR.”},{“insert”:”n”,”attributes”:{“header”:2}}]}

This is a prod container issue, we have many ws_api and one server.py. They’re on entirely different machines mediated by rabbitMQ, so either we move the refresh logic to server.py or we use rabbit MQ to talk to server.py.

Research redis alternatives, we have apache ignite, redis had an open source controvercy

Try redis to docker-compose.yaml and then we try adding it to the rest of the deployment to see how it’s handled

Vin asked that we temporarily disable this upgrade subscription thing. It’ll just be disabled for right now and say “Contact your AM for details to upgrade to Visual Insights Pro.”

{“ops”:[{“insert”:”Related Pull Requests”},{“insert”:”n”,”attributes”:{“header”:2}},{“insert”:”n1. “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/back-end/pull/1927″,”title”:”Add scheduling system (Back-end)”}}},{“insert”:”n”,”attributes”:{“header”:3}},{“attributes”:{“bold”:true},”insert”:”Creator:”},{“insert”:” Michael Ribca”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“attributes”:{“bold”:true},”insert”:”Created At:”},{“insert”:” 12/25/2025 11:33 AM (Europe/Bucharest)”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Summary by CodeRabbit:”},{“insert”:”nnRelease Notesnn”},{“attributes”:{“bold”:true},”insert”:”New Features”},{“insert”:”nAdded comprehensive schedule management system for administrators.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Enables creation, retrieval, updating, and deletion of schedules associated with customers.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Each schedule can contain multiple timing rules with customizable times and timezone settings.”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n✏️ Tip: You can customize this high-level summary in your review settings.n”},{“insert”:{“divider”:true}},{“insert”:”n2. “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1512″,”title”:”Add scheduling UI (Front-end)”}}},{“insert”:”n”,”attributes”:{“header”:3}},{“attributes”:{“bold”:true},”insert”:”Creator:”},{“insert”:” Michael Ribca”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“attributes”:{“bold”:true},”insert”:”Created At:”},{“insert”:” 12/25/2025 11:33 AM (Europe/Bucharest)”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“bold”:true},”insert”:”Summary by CodeRabbit:”},{“insert”:”nn@coderabbitai summaryn”},{“insert”:{“divider”:true}},{“insert”:”n”},{“attributes”:{“italic”:true},”insert”:”This information was appended automatically to document relevant pull request activity for changelog purposes.”},{“insert”:”n”}]}

{“ops”:[{“insert”:”Need to make sure that when in edit mode that the grid isn’t in compact mode.”},{“insert”:”n”,”attributes”:{“block-id”:”block-2aea602c-0807-4ba2-8b62-c355c3f7ba42″}},{“insert”:”n”,”attributes”:{“block-id”:”block-e2496669-3a96-4fd8-9fc1-98792517a780″}},{“insert”:”Also, fix this issue:”},{“insert”:”n”,”attributes”:{“block-id”:”block-b8ce5de8-1a95-4b2c-bd91-b94cc24a073e”}},{“insert”:”TypeError: Cannot read properties of undefined (reading ‘set’)”},{“insert”:”n”,”attributes”:{“block-id”:”block-0258ab00-0485-4c6e-8b34-86b265f56fac”}},{“insert”:” at DashboardDateFilterComponent2.initState (dashboard-date-filter.component.ts:176:17)”},{“insert”:”n”,”attributes”:{“block-id”:”block-a6e7af3e-2971-45f3-b4df-c95319aa3fd7″}},{“insert”:” at “},{“insert”:”Object.next”,”attributes”:{“link”:”http://Object.next”}},{“insert”:” (dashboard-date-filter.component.ts:112:14)”},{“insert”:”n”,”attributes”:{“block-id”:”block-3ee8c63c-85d6-4f09-a7ea-7d58620083f8″}},{“insert”:”n”},{“insert”:{“divider”:true}},{“insert”:”nRelated Pull Request”},{“insert”:”n”,”attributes”:{“header”:3}},{“attributes”:{“bold”:true},”insert”:”Title:”},{“insert”:” fix: dashboard widget and dialog bugs”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“attributes”:{“bold”:true},”insert”:”URL:”},{“insert”:” “},{“insert”:{“link_mention”:{“url”:”https://github.com/Resplendent-Data/front-end/pull/1558″,”title”:”https://github.com/Resplendent-Data/front-end/pull/1558″}}},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”nPull Request Description”},{“insert”:”n”,”attributes”:{“header”:4}},{“attributes”:{“bold”:true},”insert”:”Summary”},{“insert”:”nnWidget overlap fix: Disable gridster compaction during widget editing to prevent other widgets from shifting up and overlapping the edited widget when savingnDate filter crash fix: Reorder class properties in DashboardDateFilterComponent to prevent “Cannot read properties of undefined” errors when store emits synchronouslynDialog input fix: Add missing @input() decorators to dialog context properties in TemplatePreviewDialogComponent and Setup2FAModalComponentnn”},{“attributes”:{“bold”:true},”insert”:”Test plan”},{“insert”:”nnEdit a widget on a dashboard that has other widgets below it, save the widget, verify other widgets don’t shift up”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Open the global date filter on a dashboard, verify no console errors”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Click preview on a template in the template gallery, verify the preview dialog opens without errors”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”Test 2FA setup flow, verify the modal opens correctly”},{“insert”:”n”,”attributes”:{“list”:”bullet”}},{“insert”:”n”},{“attributes”:{“italic”:true},”insert”:”No coderabbitai summaries or comments were found for this PR.”},{“insert”:”n”,”attributes”:{“header”:2}}]}

Need to separate templates by creators too

Integrate ADP to automate payroll, manage employee data, and streamline HR processes within our platform.

Update the permissions logic so that users with member-level permissions can create share links only if the dashboard they are trying to share is in a dashboard group that they have access to. This ensures that members cannot share dashboards outside of their permitted groups.

When a max with is enabled, enable word wrapping.

Feature request from Wipfli

Connect Gmail to send, receive, and organize emails within our platform. Users can streamline communication and manage correspondence more efficiently.

Integrate Google Ads to track campaign performance, manage ad spend, and analyze advertising ROI directly from our platform.

Connect HubSpot to manage contacts, track sales pipelines, and automate marketing workflows directly from our platform.

Balance
Customer Session
Event Destinationsv2
Files
File Links
Mandates
Confirmation Token
Tokens

Balance Transactions
Charges
Customers
Disputes
Events
Eventsv2
Payment Intents
Setup Intents
Setup Attempts
Payouts
Refunds

Steps:
add data to DB for intergration
add oauth handler
front end – add a oauth component for stripe oauth
Hook up oauth handler to giant if list
refactor dumb if/else oauth list
Use smileback as oauth context for AI

Make logging in harder for you and the bad guys.

Hello Mr Mal. I would like to request a possible feature in your lovely resplendent…. Custom images for backgrounds of the Bar graphs. Who needs bland colors nowadays anyways, ya know?
Imagine my face elongating vertically more and more as I complete tickets and/or enter more time for the ‘Lubbock Weekly’ board, for example.  Wouldn’t that be great, right?

A visualization that shows on or off. Something like a nuclear power plant control panel that either shows “you’re dead” or “you’re okay”

Requested by ITCM, 99Ten, Spera

It would be really nice to be able to rename columns at the widget level as well. In this example I can’t rename them on the join as this same join is used in data modifier that needs to know the difference between the actual hrs te and tix etc.

Rotate through a playlist of dashboards.

A screen or menu to make it easy to see what’s using your datasets.

The user can change how many points are on the chart
Set the max width of the chart and let the user zoom the chart if it goes past the max width

A place to show all widgets across all dashboards that users can copy to dashboards