policydb-spreadsheet

To build an editable policy spreadsheet, initialize a Tabulator 6.3-based component using the initSpreadsheet(config) API. This wires your data, columns, and server endpoints to render a scalable grid with bulk editing and virtual scrolling.

Configure bulk editing in a policy data grid by passing patchUrl, addRowUrl, and exportUrl into the initSpreadsheet(config) function. This API-driven approach wires server endpoints for cell-level updates and row-level editing.

Tabulator 6.3 supports virtual scrolling for large data tables and allows left-frozen fields. This maintains reference context when scrolling through hundreds of wide policy records while ensuring smooth rendering performance.

Yes, you can export editable policy data grids to XLSX for reporting by configuring the exportUrl endpoint. This allows teams to export updated policy attributes and tracked changes directly from the Tabulator-based spreadsheet component.

The best way to maintain theming consistency across multiple policy wrappers is to use a Tabulator-based spreadsheet component with built-in theming options. This ensures brand uniformity across policies, clients, and followups wrappers.

You should not use a Tabulator-based spreadsheet for policy data management if your workflow lacks API-driven endpoints for patching, adding, or exporting data. It requires server-side integration to handle row-level edits and bulk updates effectively.