Process Areas#

Opening Process Areas#

Go to Projects → Processes → Templates. Templates are grouped under Ante's seven standard areas, the same for every company and always in this order:

• Order to Cash — quotes, orders, delivery to the customer, invoicing and collection
• Procure to Pay — purchase requests, purchase orders and paying suppliers
• Inventory & Logistics — receiving, stock moves and counts, deliveries and production
• Treasury & Accounting — credit and debit notes, petty cash, reimbursements
• People — payroll runs and payroll requests
• Projects & Services — client onboarding, project changes and assets
• Other — workflows that fit none of the above

Your company's own Process Areas (for example a Client area "Order to Cash — Client: Ito Nobu") sit inside the standard area they belong to, each with Open the map to see how its workflows start each other. A workflow in none of your areas shows under its standard area directly, under Other workflows. If one of your areas has no Pre-sale or Client mark and the same name as its standard area (for example your own "Order to Cash"), it isn't shown twice: its workflows sit directly under the standard area, and its Open the map and Edit are on the standard area's row. A standard area with nothing in it still shows, closed, with "No workflows yet". The standard areas can't be renamed or removed. New Process Area adds one of your own. The view buttons also offer the older grouping by category, a list and a grid.

Creating a Process Area#

1. Click New Process Area
   Give it a name (for example "Order to Cash — Client: Ito Nobu"), pick the standard area it Sits in(required — for example Order to Cash), add a short description, and optionally the module it belongs to.
2. Add its workflows
   On the area's page, choose a workflow under Add a workflow and click Add. You can also set the Process Area field in a workflow's basic info in the builder.

Reading the Map#

The map is drawn from each workflow's own steps and arrows, in a light BPMN style, so every workflow you build maps itself. Each workflow is a pool: a band headed by its name and main owner department.

• A thin circle is where the workflow starts; a thick circle is an End, named by its outcome when it has one.
• A rounded box is a step.
• A diamond is where a step branches. Each path carries its condition ("Standard", "Advance Order", "Total ≥ PHP 1,000,000"). The main path runs along the top; other branches sit below in a different tint, and either flow back into the step they rejoin or end at their own End.
• A dotted arrow over the top goes back to an earlier step (for example Rejected).
• A darker box is a workflow the step starts and waits for (Purchase, Delivery, Billing…). When the step does nothing else, the step and that workflow are one box, titled by the step. Click it to open the workflow; Show steps lists its steps on the map.
• A dashed arrow into another pool's start: the step starts that workflow and carries on — it runs separately or once per part. The label says when it starts.
• A dimmed pool: a workflow outside this area that starts, or is started by, one inside it.

Wide maps scroll sideways inside the frame. Use the zoom buttons or Fit to see the whole area. Click a pool's name to open that workflow in the builder. In the builder, the workflow's Start panel also lists what starts it — every step of a published workflow that starts this one, with when and whether it waits.

Starting Another Workflow#

In the builder, open a step and choose the workflow it starts under Starts sub-workflow. Then choose Start when:

• When the step starts — as soon as the step becomes active.
• When the step is done — when the step is completed (the default).
• When its document is issued — when the step's form is submitted; each issued document starts its own copy.
• For each finished part — on a step done in parts, every finished part starts its own copy.
• When a condition is true — checked when the step is done, with the same conditions as a branch arrow (an answer, the document total, stock, a price change).

Tick wait to keep the step open until the started workflow finishes; the step then finishes with it. Without it, the started workflow runs alongside and the order screen marks it Runs alongside. The same event never starts a second copy, even if a form is submitted twice. An order doesn't finish while a workflow it started is still running — the order shows Waiting for it and finishes when it does — unless the step is set toMay keep running after the order finishes. A Delivery Receipt always starts its Delivery workflow when the receipt is issued, and waits for it.

Applies to lines where limits the start to orders that have such a line: the item is stocked goods (so an order of services only skips Delivery), the item is a service, or a line field equals a value. When the moment comes and no line of the step's form (or the form before it) matches, the workflow isn't started and the order's History shows didn't start its workflow with the reason. The started workflow still sees all the order's lines.

What a Workflow Needs Before It Starts#

On the workflow's Start panel, Must be on the order before it starts lists the documents it needs handed over — for example, Collection needs an Invoice. The workflow starts only when its order already has an issued one of each; a draft, one waiting for approval or a voided one doesn't count. If the moment comes too early, it isn't started (a step that waits for it stays open). A workflow with such inputs can't be started on its own.

Cancelling or Losing an Order#

When an order is cancelled or marked Lost, every workflow it started — and every workflow those started — is undone too, latest first. Each one runs its own undo: its documents are voided (a purchase order cancelled, a delivery cancelled, an invoice voided), the same as cancelling that workflow on its own. The cancel warning lists them before you confirm, and the builder's Outputs panel shows each workflow's undo.

Cancelling twice is safe: workflows already cancelled are skipped.

Undoing Stock#

A Delivery Receipt (once dispatched), Receiving Report, Goods Receiving, Stock Transfer or Stock Adjustment that moved stock can be undone while the goods can still be recovered. Open the document and choose Undo Stock — or use the Undo Stock button next to it in a cancel or send-back that stopped.

1. Check what moves back
   The dialog lists each item, the quantity and where it goes back to.
2. Do the physical step first
   Bring the goods back (or take them out) as the dialog says.
3. Give the reason and confirm
   Tick that the goods are back, then Undo Stock.

Accounting reverses the cost entry first, then the stock moves back, the document is voided with your reason and the order's History records it. A cancel or send-back that was waiting on it can then go ahead.

Sending Back to an Earlier Workflow#

When a workflow finds something that must be fixed earlier — Billing finds a wrong price on the order — open it and choose More → Send back to an earlier workflow. Pick the step to reopen in a workflow above it (the one that started it, or further up) and give the reason. The dialog lists what will be undone: this workflow and every workflow started from that step onward, latest first, each by its own undo — the same as a cancel.

The step reopens and the steps after it wait again; when it is done again, it starts its workflows afresh. The order's History shows who sent it back, from where and why, and that the undone workflow "was voided" — the order itself goes on. On the order's timeline the undone run stays on its card marked Void, its steps struck through, next to the fresh run.

Seeing the Whole Order: the Chain Tab#

The order screen's Chain tab shows the order and every workflow started under it as a tree — each one indented under the workflow that started it, with the step that started it, its status and the documents its own steps made (number, status, date, amount). Click a started workflow to open it. A document attached to the order but made elsewhere sits under the order itself.

Changing or Deleting an Area#

Use Edit to rename an area, change its description or move it to another standard area. Take out removes a workflow from the area. Deleting an area keeps all its workflows; they are simply no longer in an area.

Process Areas in the Library#

When you export a workflow package from a workflow that is in an area, the package carries the area's name. Installing the package puts every installed workflow into the area of that name, and creates the area if it doesn't exist yet.

How It Connects#