AutoFlow for SITE
AutoFlow for SITE connects AutoFlow with SITE by Singhammer IT Consulting AG. With the app installed, your flows can watch SITE's documents and master data the same way they watch sales orders or customers: react when a contract changes, stop a work order from being released without a contact person, or start a flow straight from an incident.
The app is a free add-on to AutoFlow. It is available on-premises only (SITE is an on-premises solution), one build per SITE version:
| SITE version | Business Central | Needs AutoFlow |
|---|---|---|
| SITE 2024 | BC 24 | 24.0.38 or later |
| SITE 2025 | BC 26 | 26.0.38 or later |
| SITE 2026 | BC 28 | 27.0.47 or later (the AutoFlow 27 build runs on BC 28) |
Your partner installs it next to AutoFlow and AutoFlow Core; no activation or licence of its own is needed.
What you can do
The table shows which SITE documents work with which trigger. A tick means the document can be picked in that trigger once the app is installed.
| SITE document | Record created or modified | Document released | Document posted | Page opened / closed | Start Flow |
|---|---|---|---|---|---|
| Customer Contract (header and lines) | ✓ | – | – | ✓ Customer Contract card | ✓ card and list |
| Vendor Contract (header and lines) | ✓ | – | – | ✓ Vendor Contract card | ✓ card and list |
| Service documents: Work Order, Incident, Problem, Hardware Change, Software Change (header and lines) | ✓ | ✓ | ✓ when the document is closed | ✓ the five document cards | ✓ the five cards, their lists and the SITE Service List |
| Installed Item | ✓ | – | – | ✓ Installed Items card | ✓ card and list |
| Order Demand (header and lines) | ✓ | ✓ | ✓ | ✓ Order Demand Sales card | ✓ card and list |
A few things worth knowing:
- Contracts and installed items have no status in SITE, so there is nothing to release or post. Contract billing creates ordinary sales and purchase invoices: use the built-in Document posted trigger on Sales Header or Purchase Header and filter on SITE's Contract No. field to react to a contract invoice.
- "Document posted" on a service document means closing it. The flow runs while SITE moves the work order, incident or change to the closed documents. An Error step keeps the document open; Set field values writes into the document before it is archived.
- Releasing a service document or an order demand fires the flow whichever way the release happens: the Release action, an admin completion or a status that releases the document. An Error step cancels the release and the document stays open.
- Reopening has no trigger of its own. Use Record created or modified on the service header or order demand header with the watched field Status and a filter
Status = Open. - The service documents share one table pair (SITE Service Header / SITE Service Line). To react to incidents only, filter on Document Type (and Service Desk Type for incident vs. problem).
Examples
- Require a Contact on a work order before it can be released.
- Set the Salesperson on every new customer contract from the customer card.
- Send a Teams message when an incident with priority High is created.
- Offer a Start Flow action on the incident list that creates a follow-up task for the selected incidents.
Installation
- Install AutoFlow Core and AutoFlow (see Installation).
- Install the AutoFlow for SITE build that matches your SITE version. The download is in the same place as the AutoFlow on-premises packages; ask your partner.
- Open a flow and pick a SITE table or page in the trigger. Without the app, the trigger's status line tells you the table is not supported, and the flow cannot be published.