Flows
Each flow is one workflow — its own settings, its own connections.
Available workflows
Untick one to stop it being offered for a new
flow. Flows already running on it keep working — this is the
shop window, not a switch.
…
…
Connections
Which of this client's saved connections this flow uses. Add them under Connections first.
Settings
Scan position
How far through Cin7 this flow has read. It picks
up from here on the next run, however long it has been off — so
nothing falls through a gap.
Your local time.
Anything already sent won't
go twice — the flow keeps a record of every invoice it has
exported.
What this partner does not want
Every partner eventually asks for something
nobody else does — no cancelled invoices, no test orders, only
certain customers. Rules go here rather than in the code, and
read the same field names as the map: anything you can send is
something you can filter on.
Edit the rules
Field map
Edit the map
Every field the partner receives is here, next
to where its value comes from. Nothing outside this map leaves
the building. A change is tried against a real document before
it can be saved, so a broken map cannot reach a partner.
What it produces
Cross-references
Translate the partner's values into yours. Anything not listed passes through unchanged.
| Type | Their value | Your value |
|---|
Pending orders
Anything still in flight, plus anything that failed.
Tick rows to deal with several at once.
A busy flow makes thousands of
these. The last 7 days is the starting point; widen it when you
are looking for something older.
Received
Files that arrived: the ones that reached Cin7,
with the reference they landed as, and the ones that didn't —
a resent copy of an order already in Cin7, or an order a
filter rule stopped. Open a resent copy to see what is different
about it and decide what to do with it.
Sent
Files this flow wrote back out — invoices,
tracking, whatever the partner receives. Open one to see exactly
what went.
Operations log
Polls, settings changes, credential updates and
transport failures. Clearing is permanent — these don't come back.
Connections
Credentials you enter once and reuse across as many flows as you like.
Add a connection
…
…
Details
Software4Business sets
these up. If something here is wrong, let us know.
Credentials
Stored encrypted. They are never shown again — leave a field blank to keep what's saved.
Files
What this connection can see, read-only. It reaches
exactly what these credentials reach — no more.
History
Only Software4Business sees this. Every change,
test and pause, by whom. Put back returns the name,
settings and credentials to exactly how they were just before
that change — so anything changed since, a newer password
included, goes back too. Credentials stay encrypted throughout,
and putting back can itself be undone from here.
Documents
Every order that has passed through, newest first.
Document
History
What we sent to Cin7
Order data
Advanced — edit the raw order data
Original file from the partner
Settings
Preferences for your account.
Error alerts
When an order fails, the alert email goes here. Leave blank to route alerts to Software4Business.
Email (Postmark)
One Software4Business Postmark server sends for every
client, so everything goes out from our own verified address.
Problems only we can fix always come to our address below, whatever a
client has set. Nothing is sent for ordinary success.
Change password
Clients & logins
Each client gets their own logins, connections and flows.
Clients
| Client | Flows | Connections | Logins |
|---|
Logins
Passwords are stored scrambled, so nobody — us
included — can look one up or send it again. Email reset link
sends a link to choose a new one (it works once, for an hour).
Set password is for when email isn't the way; tell them what
you set. Either one signs them out wherever they were signed in.
| Client | Role | Added | Status |
|---|
Create a flow
Creates it paused. Choose its connections on the flow's Setup tab, then start it.
Email log
Every email EDI Hub tried to send — sent, refused, or not sent and why.
| When | Client | Kind | To | Subject | Result |
|---|