Skip to main content
A Sync run asks whether two systems hold the same records. A lifecycle asks a different question: where do records stall on their way through? It follows NetSuite records from a start record, such as a sales order, through the stages that should follow it, and puts every record in exactly one named place. The answer is never zero; it is a count per place, and the places marked as findings are the ones worth acting on. Lifecycles are built on run flowcharts: charts of yes/no questions, where each question is one reconciliation and the questions under it answer only for the records that reached them. A lifecycle writes its chart for you. Imported NetSuite checks arrive as charts you can extend.

​
Before you start

Confirm:
  • A NetSuite connection exists for the account. See Connect NetSuite.
  • You are a Tenant Admin for the active tenant. Creating and changing runs requires tenant edit access.

​
Create a lifecycle

Every option below is read from the NetSuite account itself, so nothing is typed and nothing is offered that the data does not contain.
1

Start a Lifecycle

On Home, choose Create Run, then answer What kind of run? with Lifecycle.
2

Pick the account and records

Answer Which account? with the NetSuite connection. With only one account, Darpan skips this card. Then answer Which records? with the record type the lifecycle starts from. Only record types that have records are offered.
3

Pick the stages

Answer What happens to a record? with the stages that should follow, in any order; Darpan orders them as the data does. The stages that at least half of these records go on to are chosen for you.
4

Leave records out

Answer Leave out any records? with a field, then a value, to leave out records that should not be judged. Repeat for each rule, and choose Nothing (or Nothing else) to move on.
5

Say when a record is late

Answer When is a record late? with a day count, or Same day. The default is the first day by which at least 90% of records have reached the last stage. Choose Save lifecycle.
Darpan names the lifecycle, orders its stages, and names every place a record can stop. The new run opens on its own page, and Home lists it under Lifecycle.

​
Run it

On the run’s page, choose the play icon (Open run) and answer Which days should this run look at? with Previous day or Last N days, then choose Run. A lifecycle’s window ends the late-after period back from today, so records too new to have finished are not judged. The result’s This Run section shows the Window it covered, in the zone the run was anchored in.

​
Read the run page

Open an execution to see its result:

​
Tune it

Choose the gear (Run settings). The page, Update the lifecycle., shows the lifecycle as one line, and each change sits where it acts: Choose Save to store the changes.

​
Questions and flowcharts

A run that is not built from stages shows Questions instead: the chart itself. Each box is a question, labelled with what its “no” is called, and each edge says yes (with its count once run), no, or why.
  • Select a question to edit it: its Rule (an existing rule set), the Question wording, and the Finding its “no” is called. Choose Save question.
  • Add next question adds a question on the yes branch; Ask why adds one on the no branch.
  • The Start question uses a one-source rule. Every record it returns is a yes, so it has no finding.
  • A question under one that failed or was switched off is not run (AUT_STAT_NOT_RUN).
The chart can be edited while the run is not running. A result shows its questions with counts, and Question Runs lists each question’s own run with its state and yes/no counts, and the reason when it failed or was not run. A finding with records opens them.

​
Import NetSuite Checks

Import NetSuite Checks on Home turns the tenant’s existing NetSuite checks into runs: one run per population (account, record type, and how the key is built), with a Start question and each check as a yes question under it. Home offers it to editors whose tenant has a one-system NetSuite run. It is safe to repeat: a second import adds only checks not yet in a run. Darpan reports how many checks it imported into how many runs, or No new NetSuite checks to import., and names the reason for each check it skipped.

​
Retire a run

The trash icon (Delete run) on a lifecycle’s page archives it. It leaves Home and cannot run again; its past results stay readable. Nothing is deleted.
Lifecycle tiles cannot be pinned on Home yet.

​
Next step

To compare two systems instead, set up a Sync run: Set up a reconciliation run. For how a question’s own result reads, see Review results.