Publishing writes the flow to your 3CX. Until then the flow only exists in JEDWare. Publish… in the toolbar opens the review, and the review has a switch with two choices:
Read Testing safely: sandbox and live first if you have not.
In a sandbox review the incoming number row is greyed out: a test never changes where your number points. In a live review that row is highlighted and says “This changes what callers hear”.
If the flow still has problems, the dialog lists them under “Fix the problems before publishing” and the publish button stays off. “Nothing to publish. 3CX already matches this flow.” means there is nothing to do.
If a step fails half-way, the designer rolls back what it already created and shows “Publish failed and was rolled back” with the log. Your 3CX is left as it was. Copy log puts the log on the clipboard for support.
If someone changed 3CX in the Admin Console while you were looking, publishing stops with “3CX changed while you were looking. Review the changes again.” Read the new list and publish again.
A flow remembers two sets of numbers, sandbox and live. Testing never touches the live objects and publishing live never touches the sandbox objects. The header shows both stamps, and each card shows both numbers.
| Object | Created | Changed | Deleted |
|---|---|---|---|
| Queue, ring group or menu the designer made (tag new, later a number) | yes | yes | when you remove it from the flow and publish, or on undo |
| Existing queue, ring group or menu (tag 3CX) | no | only with Let the designer change this 3CX object on | never |
| Inbound rule (your number) | never | its destinations only | never |
| Extensions, trunks, office hours, holidays | never | never | never |
| Call script (see Running a flow as a call script) | on deploy | on deploy | never by a publish |
Objects the designer created are marked in 3CX so it recognises them later. Removing such a step from the flow warns: “8001 will be deleted in 3CX when you publish.”
Next: Undo a publish and history.
