Chapter 1 — Dashboard & apps(Tutorial example at the end)

1.1　Dashboard

The default home page after sign-in. Charts and shortcut cards summarise recent activity so you can gauge message volume, workflow usage, and form approval status without opening every screen.

What to notice on the screen

• Charts (top area): e.g. last-seven-days message trend, most-used workflows, form review status (pending / approved / rejected).

  

• Apps cards (if your role allows): shortcuts to Published apps, Running forms, and Running apps, with approximate counts.
• Studio cards (if allowed): shortcuts to forms, templates, workflow designer, datasets, etc. — exact tiles depend on permissions.
  
  
• Admin cards (if allowed): summaries for contacts, broadcast groups, tags; some admin items may exist only in the left menu without a dashboard tile.

Why don’t I see a section?

The dashboard only shows features you are allowed to use. Ask your administrator to enable them under Admin → Permission management.

Why doesn’t the number on a card match the list?

Figures may be aggregated or cached and can lag slightly; refresh and compare again. Pending work counts are authoritative in the Running forms list.

1.2　Published apps

Lists workflows your company has activated. Manually triggered flows can be started here with one action; automatically triggered flows run by system rules — you can usually view them here but not press “start”.

Common actions

• In the manual trigger area, find the flow card. Use the text area to enter an opening message (leave empty if the flow does not need one). Use the paperclip for attachments, or drag files onto the rocket icon or the composer; press send to start. You need at least some text or one file before the request is sent.
• If your company uses queued (background) starts, the toast may say the job was queued rather than finished immediately; execution counts still update after processing.
• To see how a run went, open Apps → Running apps.
• To edit or deactivate a flow, go to Studio → Workflow designer; this page does not edit definitions.

1.3　Running forms

Everything that needs your action in one place: e.g. forms waiting for approval after a customer or colleague submits, or steps marked for human handling. Filter the list, then open each item to approve or send back.

Approve one request (example)

1. Open Running forms.
2. Use filters at the top (workflow name, form, dates, etc.).
3. Click View or Approve, confirm content, then approve or reject; if the UI asks for comments, fill them in before submitting.

These tasks usually come from “send form” or approval steps in a workflow; they appear in your list after the other party submits.

1.4　Running apps

Use this to track each workflow run: current step, success, failure, or stuck — handy for support, audit, or vendor follow-up.

Check progress for one run

1. Open Running apps.
2. Filter by workflow name, date range, or status to find the row.
3. Open the row or click View to see the timeline and per-step status.

Status may show as running, completed, failed, cancelled, etc. (per UI). “Running” means not finished yet — possibly waiting for a customer reply, a manager approval, or backend processing.

Filters, paging, and sort order for this list are kept in the browser tab’s session; if you navigate away and return, you often keep the same filters (closing the tab or clearing site data resets them).

If a run includes WhatsApp Flows (Meta Flows) submission data, the viewer tries to render JSON as tables, clickable links, and attachment previews so you can match what the customer sent in chat.