Seven steps an admin completes to bring a Tessera instance fully online inside NetSuite.
Standard SuiteApp bundle deployment via the NetSuite bundle manager. Creates all custom record types, SuiteScripts, Suitelets, portlet scripts, and File Cabinet assets.
Admin enters license key. Tessera calls the Tessera license service via N/https to validate. Tier (Standard or Advanced) is written to the Tessera account configuration record.
Guided Suitelet walks the admin through account-level setup. Provisioning script runs automatically: detects OneWorld, active segments (Class, Department, Location), open period count, and multicurrency posture. Admin sets default subsidiary scope and notification email.
A default catch-all Approval Domain is created automatically on first run. Admin carves out sub-domains (by subsidiary, segment, or business type) as needed and assigns approvers. The global backup approver covers any domain without a named approver.
Can be revisited at any time. Required before metrics can be activated.
Admin selects which pre-built metric packages to activate (DSO, Gross Margin, MRR, Burn Rate, etc.). Custom metrics are built via the Tessera Metric Wizard. All metrics — seed or custom — require Controller sign-off before activation.
The Cached Result Layer Map/Reduce job runs for the first time, computing and storing Metric Results for all active metric definitions. Subsequent runs are scheduled. Portlets display a stale indicator until this first run completes.
Note: Runtime depends on how many metrics are active and how much transaction history the instance has. Set expectations with users before this run.
Admin follows the Tessera portlet placement runbook to add Tessera Portlets to each NetSuite role's home dashboard. Tessera Admin tracks completion by role via a checklist record.
Note: NetSuite has no API for dashboard portlet placement. This is a manual admin action. The runbook must be airtight — it's the step most likely to cause support requests.