Your first card

Create a card in a Workfloor assembly lane for a Salesforce change, then follow it from the brief through Flux's plan, changes and pull request to a merged change.

A card is one piece of work in an assembly lane. This page follows one card, "Require a close reason on lost opportunities", from the brief to a merged pull request.

Write the brief

Open Assembly Lanes and select New task (or the + on a stage's column). The dialog asks for:

  • Title — what the change is.
  • Context — the description Flux works from.
  • Repository — the repository the change is made in.
  • Workflow stage — where the card starts.
  • Workfloor Foreman — the card's assignee. Every task needs one.
  • Put an agent to work right away — starts Flux when the card is created; otherwise the card waits until an agent is started.
The New task dialog filled in with the title Require a close reason on lost opportunities, a description asking for a validation rule and an Apex test, the Plan stage, a foreman and Flux selected
The New task dialog for a Salesforce change.

Here the context asks for a validation rule on Opportunity requiring Close Reason when the stage is Closed Lost, and an Apex test for both cases.

The assignee answers Flux's questions and approves its plan. With Workfloor's GitHub App, Flux pushes and opens pull requests as the assignee.

The lane board with the new card in the Plan column, marked as running
The card appears in its stage and shows what Flux is doing.

Flux plans

When the card's agent starts, Flux works on it. In a Plan stage it reads the repository and writes a plan: its approach and a checklist of steps. Select the card to open its page.

A card's Plan tab with the plan's goal and approach, a question from Flux with two options, and Request changes and Approve plan buttons
The Plan tab. The conversation with Flux is docked on the right.

The header shows the card's status, stage and assignee. The tabs include Plan, Changes, Conversation and Summary; the conversation with Flux stays docked beside them.

To respond to the plan:

  • Comment. Select text in the plan to leave a comment on that passage. Comments are queued, and Request changes sends them to Flux, which revises the plan.
  • Ask now. From a selection, ask Flux about that passage. It answers in a thread without revising the plan.
  • Answer. When Flux asks a question in the plan, choose an option. The card shows Question until it is answered.
  • Approve plan. Approving moves the card to the stage that follows in its lane, typically where the build starts.

Review the changes

In the build stage, Flux changes metadata and code in its own checkout. Changes shows the files and the diff, as Diff or Diagram, Unified or Split. Follow the agent keeps the view on the file Flux is editing.

A card's Changes tab with a file tree and a diff, and Flux's question docked on the right
The Changes tab with Flux's question in the conversation.

If Flux needs a decision while it builds, it asks in the conversation and the card waits for the assignee. Answer with the question's options or in the message box, which also sends Flux a message at any time.

The pull request and moving on

When Flux opens a pull request on GitHub, it links it to the card, under Linked work in the header. In a review stage, the header offers Approve review to move the card on, or Send back… to return it to an earlier stage.

A card in the Review stage with a linked pull request in the header and Approve review and Send back buttons
A card in review with its pull request linked in the header.

Merge the pull request on GitHub once its checks pass. The item moves to Merged on the Mission Control tracker. The card moves on as its lane's ways out say; a lane can also archive its cards once their change is released.

Next: Mission Control.

On this page