Flows

#About Flows

Manage data integration flows between systems. This is a working page: a list or workspace where you find and act on records in BSuit ERP (Integration). It is used by staff (internal users). What you can see and do depends on your role and permissions.

#How to open it

In BSuit ERP, open Integration and choose “Flows”, or go directly to the address /integration/flows.

#What you can do here

These controls are present in the page’s implementation. Whether you see a given one also depends on your permissions and on the data shown.

1. Add new records — a form opens for the details.
2. Change existing records.
3. Delete records (you are asked to confirm).
4. Bring records in from a file.
5. Export what you see to a file.
6. Print or save as PDF.
7. Attach or upload files.
8. Search within the page.
9. Filter the data shown.
10. Sort by a column.
11. Page through long lists.
12. Open dialogs or drawers for detail and confirmation.

#Fields

When you enter or change a flow, these fields are on the form. Required fields must be completed before you can save.

#What the list shows

The list displays these columns; use search and filters to narrow it.

1. Code
2. Name
3. Direction
4. Entity Type
5. Trigger
6. Last Run
7. Active

#How to add a flow

Steps follow this page’s form. You need permission to create records here.

1. Open Integration › Flows from the menu.
2. Choose the Add button (a plus icon) above the list. The form opens in a dialog.
3. Complete the required fields: Code, Name, Entity Type.
4. Some fields offer a fixed list: Direction: Inbound, Outbound; Trigger Type: Manual, Scheduled, Event, Webhook; Request Method: GET, POST, PUT, PATCH, DELETE; Canonical Payload Schema: None (no validation), Order, ASN, Shipment Status, Invoice, Inventory Snapshot, Master Data.
5. Save. The new record appears in the list; use search or the filters to find it again.
6. To change it later, open the record from the list and edit it.
7. Deleting asks you to confirm. Records that other records refer to may be refused or may affect them (see “Where … is used as a reference”).

#Observed on a running system

On 2026-09-21 this page was opened in a browser as a test administrator. This is what was visible on screen. Your own view can differ with your role, data and settings.

#If something is missing or fails

1. No data: confirm the company or context selected in the top bar, and any filters or date range in use.
2. An action is hidden or disabled: it usually needs a permission your role does not have. Ask an administrator to check your effective access.
3. An error message appears: note the message, the page address and what you were doing, and contact support with those details (never include passwords).

#About this guide

This guide was generated from the page’s implementation. It has not yet been reviewed by a person against a running system, so treat it as a reference for what the page contains rather than a complete procedure.