Install & configure

How a NetSuite administrator installs the Implementation Tracker bundle and connects it to FullClarity. The whole sequence takes about ten minutes and only has to be done once per engagement.

Who can do this: NetSuite administrators only.

What you'll do

  1. Install the Implementation Tracker bundle from the SuiteApp Control Centre.
  2. Get the configuration payload from your FullClarity consultant.
  3. Create a single Tracker Configuration record in your account and paste the payload's values.
  4. Confirm the tracker connects — the Health row on the Implementation Tracker page should say Connected.

Step 1: Install the bundle

The Implementation Tracker is delivered as a managed SuiteApp.

  1. Open Customization → SuiteCloud Development → SuiteApp Control Centre.
  2. Search for FullClarity Implementation Tracker and click Install.
  3. If Code Library and Portal aren't already in the account, they install as dependencies. This is normal.

After install you'll see a new menu entry at FullClarity → Implementation Tracker. Don't open it yet — it won't be able to reach FullClarity until you've completed the configuration record below.

Step 2: Ask FullClarity for your engagement payload

Your FullClarity consultant creates the engagement record on their side and sends you a one-time JSON payload containing four values:

  • API URL — the address the tracker uses to reach FullClarity.
  • API token — a long string the tracker presents on every request so FullClarity knows the requests are coming from your account.
  • Engagement key — identifies which engagement on FullClarity's side the tracker is bound to.
  • WebSocket URL — used for the optional live-update features (lock indicators, cross-user notifications) when those are enabled.

Keep the payload private — anyone with the API token can read and write your tracker data, so treat it like a password.

Step 3: Create the Tracker Configuration record

  1. Navigate to Lists → FullClarity → Implementation Tracker Config → New.
  2. Paste each value from the payload into the matching field:
    • API URL
    • API Token
    • Engagement Key
    • WebSocket URL
  3. Leave Last Health Check blank — the tracker fills it in automatically the first time the page loads.
  4. Click Save.

You should have exactly one Tracker Configuration record per NetSuite account. If you delete it or have a second one floating around, the tracker won't be able to decide which engagement to connect to.

Don't reuse a configuration across engagements

Each engagement has its own API token and engagement key. If you start a second implementation later (for example, adding Subcontracts on top of an existing Project Financials install), ask FullClarity for a new payload and replace the values on the existing record — don't try to keep the old token around.

Step 4: Confirm the connection

  1. Open FullClarity → Implementation Tracker.
  2. The first load takes a few seconds — the tracker has to authenticate to FullClarity and pull the current Issues and UAT data.
  3. When the workspace renders, the connection is working. If FullClarity has seeded any UAT scenarios for your engagement, they'll already be visible on the UAT tab.

The Last Health Check field on the Tracker Configuration record is stamped with the current time on every successful load. You can use that to confirm the integration is still healthy at any point.

Granting access to the right users

Anyone in your account with permission to access the FullClarity menu can open the tracker. There are no separate per-user permissions inside the tracker itself for the implementation period — by design, the implementation team should all be able to see and contribute.

To restrict the tracker to specific NetSuite roles, edit the Audience tab on the Implementation Tracker Launcher Suitelet deployment. See Permissions for the full model.

Disabling or replacing the tracker

If an engagement ends or has to be reset, FullClarity will revoke the engagement on their side. Once revoked, the tracker shows a "This tracker has been disabled by FullClarity" message and stops accepting changes. The historical data remains on FullClarity's side for reference.

To replace a revoked engagement with a fresh one, ask FullClarity for a new payload and update the four fields on the existing Tracker Configuration record. Save the record and reload the Implementation Tracker page — it should reconnect against the new engagement.

Common stumbling blocks

  • "Tracker server unreachable" toast on first load. Almost always a typo in the API URL, or a copy-paste that lost the https:// prefix. Open the Tracker Configuration record and compare every character against the payload FullClarity sent you.
  • Tracker loads but Issues and UAT tabs are empty. Normal on a brand-new engagement. Ask your FullClarity consultant whether UAT scenarios have been seeded yet — if not, FullClarity will provision them and they'll appear after a refresh.
  • "Token revoked" or "disabled by FullClarity" appears immediately after pasting a payload. The token may have been issued to a different account than the one you're installing into. Confirm with FullClarity that the payload matches the NetSuite account ID you're installing the bundle in.

Next steps

Last Updated: