Skip to main content
Use Automations when your role includes configuring firm workflows. Before publishing, confirm the intended trigger, conditions, action, and reviewer with the person responsible for that process. A trigger is the event that starts the workflow. Conditions limit when it runs. An action is the work it performs, which may require approval.

​
Review the configured workflow

  1. Open the automation’s editor.
  2. Select the trigger on the canvas. Check When this happens and any Start only when… rules in the Inspector.
  3. Select each action and verify its inputs and approval settings.
  4. Check the Activation checklist for unresolved configuration.
Automation studio with an Invoice created trigger, Stage Expenses for Payment action, Inspector, and Publish live control.

An invoice-staging demonstration workflow. Select a node to review its configuration in the Inspector.

​
Publish and activate

  1. Wait for the draft to show Autosaved.
  2. Select Publish live and check the publication confirmation.
  3. Set the automation to On when it should begin responding to matching events.
  4. Use Published view to inspect the live version.
An autosaved draft and a published live version are different states. Check the version and On/Off control before expecting the workflow to run.

​
Verify an actual run

  1. After the intended event occurs, open Run history.
  2. Select the matching run by event, time, and case.
  3. Review its overall status and individual steps.
  4. If approval is pending, the assigned reviewer must complete that review.
  5. Check the resulting record as well as the run status.
Workflow Run details showing Succeeded and one successful expense-staging step.

Run details show that the expense-staging step succeeded.

Test workflow previews behavior without changing case data. A preview does not establish that the live event or its resulting action succeeded. If a run fails, inspect its step details and verify existing records before retrying. For the accounting steps, see invoice review and staging.

​
Check the scope before a live test

A workflow’s name helps people recognize it; its trigger and conditions determine which events qualify. For an invoice workflow, inspect the actual invoice-number rule rather than relying on a name such as “Demo review.” Review these parts together: For the invoice-staging example, the action is Stage Expenses for Payment, the reviewer is a Specific team member, and the review can leave funding undecided until payment. Your administrator should choose the reviewer and notification channels that match your firm’s process.

​
Understand publication states

After publishing, reopen the workflow and verify its published version and On/Off state. Then create or perform the intended test event using a clearly identified test record approved by your firm.

​
Follow a pending or failed run

A run can pause at Pending approval. Open its review package or find the request in Approvals, review the action, and check the run again after the decision. If a step reports that no eligible reviewer exists, ask an administrator to check Approvals Review permission and case access. Being called a firm administrator or accounting reviewer does not by itself establish both requirements. After correcting the cause, Re-run workflow is available in run details. Before using it, inspect the earlier steps and resulting records so that you understand what already happened. Match the retried run to the original event, then verify the business result separately. A Succeeded staging run should be accompanied by the expected invoice and expense state. It is not evidence that a payment was sent.