Quick start

The fastest path from a freshly-configured Implementation Tracker to your first issue logged and your first UAT result recorded.

Before you begin

This page assumes someone has already installed the tracker bundle in your NetSuite account and pasted the FullClarity-supplied configuration. If that hasn't happened yet, start with Install & configure instead — it takes a few minutes for the NetSuite administrator and only has to be done once.

Open the tracker

From the NetSuite top menu, choose FullClarity → Implementation Tracker. The tracker opens inside your normal NetSuite chrome, with two tabs across the top: Issues and UAT.

If you can see the tabs but no data, that's normal on a brand-new tracker — the Issues tab will be empty until you log the first one, and the UAT tab will only have test scenarios once FullClarity has seeded them for your engagement.

If the tracker shows an "unreachable" or "disabled" message, see Common stumbling blocks below.

Log your first issue

  1. On the Issues tab, click + New Issue. A form opens.
  2. Fill in Title — keep it short and specific ("Estimate column header says Margin % but should say Markup %"). This is the only required field.
  3. Add a longer Description if useful — what you did, what you expected, what happened.
  4. Set Status (defaults to Open) and Priority (defaults to Medium).
  5. If the issue relates to a specific NetSuite record (an invoice, a project, an estimate), paste its URL into Linked NetSuite URL. That gives the FullClarity team a one-click jump from the issue back to the underlying record.
  6. Click Create.

The new issue appears at the top of the list with an auto-assigned number (#1, #2, ...). The FullClarity team will see it on their side within seconds.

For the full field reference see Issue fields.

Record your first UAT result

  1. Switch to the UAT tab.
  2. Each row is a test scenario FullClarity has prepared for your engagement (for example, Create a progress claim on a stage-billed contract). The rightmost columns are cycles — Cycle 1, Cycle 2, and so on — one per round of testing.
  3. Work through the scenario in NetSuite. When you're done, click the cycle cell for that row.
  4. Pick a result from the dropdown:
    • Pass — the scenario behaved exactly as the Expected result column described.
    • Fail — something didn't match. The tracker will offer to log an issue at the same time (see below).
    • Blocked — you couldn't run the scenario (for example, a prerequisite was missing). Note why in the issue you'd log alongside.
    • N/A — the scenario doesn't apply to your business. Use sparingly.

For the full meaning of each status see UAT result statuses.

When a test fails: log the issue from the same screen

When you choose Fail on a cycle cell, the New Issue form pops open with the title already filled in — for example, UAT fail: Create a progress claim on a stage-billed contract. The test is automatically linked to the issue so the FullClarity team can see exactly which scenario failed and how to reproduce it.

Add a description (what you actually saw versus what you expected), pick a priority, and click Create. The cycle stays marked as Fail — there's no need to set the result again.

Common stumbling blocks

  • "Tracker server unreachable" toast. The tracker can't currently talk to FullClarity. This is usually a temporary network issue and resolves on its own. The tracker will keep retrying — once it reconnects, your data reloads automatically. If it persists for more than a few minutes, contact FullClarity.
  • "This tracker has been disabled by FullClarity" message. The engagement has been closed, usually because the implementation has been signed off. The tracker is read-only at this point — for new issues, use FullClarity's regular support channel.
  • An issue I edited reverted to a different value. Someone else edited the same field a moment before you did, and the system kept the most recent change. The tracker will show a toast naming what happened and what the current value is. Either accept the current value or click Retry on the toast to re-apply your change.
  • I can't see the issue I just created. Click Refresh in the tracker's action bar. Issues should appear immediately, but if the connection had a brief hiccup, a manual refresh forces a reload.

Next steps

  • Log an issue — every field on the form, when to use which.
  • Run a UAT cycle — recording results, signing off a cycle, starting a new cycle when re-testing.
  • Issue fields — the complete reference.
Last Updated: