Skip to the page
Cockpit Flight Deck ManualMuse for Mule.

Back matter

Screenshots to capture

Real captures come from the product owner's test drive. Each figure in the manual is a labelled box until its capture is in place. Capture each one exactly as described, with no real customer data on screen, and draw the numbered call-outs.

  1. Salesforce Setup home of a new Developer Edition org Figure 1 Not yet captured
    Page
    The org's Setup home (gear icon, then Setup), signed in to org 1
    State
    Quick Find box visible at the top left; browser address bar visible and ending in .salesforce.com; no real data on screen
    Call-outs
    1 Quick Find search box; 2 Address bar ending in .salesforce.com
    Used in
    Chapter 3, Pre-flight: make your test accounts
  2. Anypoint Platform home of a new trial account, with the address bar Figure 2 Not yet captured
    Page
    anypoint.mulesoft.com (or eu1. / gov.) after the trial set-up finishes
    State
    Address bar visible so the region can be read; organisation name visible
    Call-outs
    1 Address bar host (shows the region); 2 Organisation name
    Used in
    Chapter 3, Pre-flight: make your test accounts
  3. The private cockpit-practice repository on GitHub Figure 3 Not yet captured
    Page
    github.com/<test user>/cockpit-practice
    State
    Private badge and the README visible
    Call-outs
    1 Private badge; 2 README
    Used in
    Chapter 3, Pre-flight: make your test accounts
  4. The new Slack workspace with the cockpit-practice channel Figure 4 Not yet captured
    Page
    The Slack workspace opened in the browser
    State
    Channel list shows #cockpit-practice; one message posted in it
    Call-outs
    1 Workspace name; 2 #cockpit-practice channel
    Used in
    Chapter 3, Pre-flight: make your test accounts
  5. The Request access page Figure 5 Not yet captured
    Page
    /request-access, signed out
    State
    Empty form: the email, name, company and purpose boxes and the Request access button
    Call-outs
    1 Email you sign in with; 2 What would you use Cockpit for?; 3 Request access button
    Used in
    Chapter 4, Boarding
  6. The Waiting for approval screen Figure 6 Not yet captured
    Page
    /app, signed in with an address that is not yet approved
    State
    The pill, the sentence, the three numbered steps and the Request access button are visible
    Call-outs
    1 Waiting for approval pill; 2 Signed-in-as line; 3 Request access button
    Used in
    Chapter 4, Boarding
  7. The sign-in page Figure 7 Not yet captured
    Page
    /sign-in, signed out
    State
    The Cockpit mark and the Google button (and the Apple button if it shows)
    Call-outs
    1 Google button
    Used in
    Chapter 4, Boarding
  8. The console on first sign-in Figure 9 Not yet captured
    Page
    /app, approved account, nothing connected, Sandbox mode, first week of the trial
    State
    Trial bar visible, Chats button, Download button, mode chip, Brain button, org picker and message box all visible; window about 1280 px wide
    Call-outs
    1 Rail; 2 Trial bar; 3 Chats button; 4 Mode chip showing Sandbox; 5 Brain button; 6 Org picker; 7 Message box and microphone
    Used in
    Chapter 4, Boarding
  9. The Chats panel with a few chats Figure 10 Not yet captured
    Page
    /app, Chats button pressed
    State
    At least three chats listed; one with the green Sandbox tag; one with its Options menu open showing Rename, Make this chat sandbox and Delete
    Call-outs
    1 New thread; 2 Search chats; 3 Sandbox tag; 4 Options menu
    Used in
    Chapter 5, The controls
  10. The Brain panel on the Activity tab Figure 11 Not yet captured
    Page
    /app, a chat in which the Copilot has read something, Brain button pressed
    State
    Activity tab showing tool lines; API usage and the Safety badge visible; Sandbox on
    Call-outs
    1 Tabs: Activity, Approvals, History, Settings; 2 A tool line; 3 API usage; 4 Read-only badge
    Used in
    Chapter 5, The controls
  11. The mode panel opened from the chip Figure 12 Not yet captured
    Page
    /app, mode chip clicked
    State
    Sandbox on: master switch off, every connector row reading read only in Sandbox
    Call-outs
    1 Master switch; 2 A connector row; 3 Mode settings link
    Used in
    Chapter 5, The controls
  12. The Connectors page before anything is connected Figure 13 Not yet captured
    Page
    /app/connections
    State
    New approved account; Available tab selected; Salesforce and MuleSoft cards above the tabs; search box visible
    Call-outs
    1 Settings list at the left; 2 Search; 3 Connected and Available tabs; 4 Salesforce card; 5 A Connect button
    Used in
    Chapter 5, The controls
  13. The Salesforce card with a connected org Figure 14 Not yet captured
    Page
    /app/connections, after org 1 is connected
    State
    One org listed with its health label and the Rename, Reconnect and Disconnect buttons
    Call-outs
    1 Add Salesforce org; 2 Org name and type chip; 3 Health label; 4 Rename, Reconnect, Disconnect
    Used in
    Chapter 5, The controls
  14. The Approvals page with nothing pending Figure 15 Not yet captured
    Page
    /app/approvals
    State
    No pending approvals: the All clear message and the Back to the console link
    Call-outs
    1 Refresh; 2 All clear message
    Used in
    Chapter 5, The controls
  15. The Account page Figure 16 Not yet captured
    Page
    /app/account
    State
    Scrolled to show Identity through Usage; no real name or email visible (use the test account)
    Call-outs
    1 Sign out; 2 Standing approvals; 3 AI processing; 4 Downloads; 5 Usage; 6 Delete account
    Used in
    Chapter 5, The controls
  16. The message box while the microphone is listening Figure 17 Not yet captured
    Page
    /app, microphone pressed
    State
    The Stop listening button and the note Listening... visible
    Call-outs
    1 Microphone button (listening); 2 Listening note
    Used in
    Chapter 5, The controls
  17. The Mac and Windows download cards Figure 18 Not yet captured
    Page
    /app/account, Downloads section
    State
    Both cards visible, in a browser on the system whose card is first
    Call-outs
    1 Download button; 2 Install steps
    Used in
    Chapter 5, The controls
  18. The Cockpit menu of the desktop app Figure 19 Not yet captured
    Page
    The Mac or Windows app, Cockpit menu opened
    State
    The Cockpit menu open with New chat, Connections, Workbench and Approvals and their shortcuts visible
    Call-outs
    1 New chat; 2 Connections, Workbench, Approvals; 3 Shortcuts
    Used in
    Chapter 5, The controls
  19. The Diagnostics copied message in the desktop app Figure 20 Not yet captured
    Page
    The Mac or Windows app, Help menu, Copy Diagnostics pressed
    State
    The message Diagnostics copied and its sentence about account details
    Call-outs
    1 Help menu entry; 2 Diagnostics copied message
    Used in
    Chapter 5, The controls
  20. The Cockpit can't be reached screen in the desktop app Figure 21 Not yet captured
    Page
    The Mac or Windows app started with the internet switched off
    State
    The heading, the sentence about checking the connection and the Try again now link
    Call-outs
    1 Heading; 2 Try again now link
    Used in
    Chapter 5, The controls
  21. The console on a phone-width screen Figure 22 Not yet captured
    Page
    /app in a 390 px wide window
    State
    Bottom bar rail, the short mode chip, and the message box visible
    Call-outs
    1 Bottom rail; 2 Short mode chip; 3 Message box
    Used in
    Chapter 5, The controls
  22. The four-step Salesforce guide in Cockpit Figure 23 Not yet captured
    Page
    /app/connections/salesforce/setup
    State
    Step 1 with Production (login.salesforce.com) selected; the Callback URL and Scopes boxes filled in; consumer boxes empty
    Call-outs
    1 Org type choice; 2 Callback URL; 3 Scopes box reading api refresh_token; 4 Step 4 button
    Used in
    Chapter 6, Connecting each system
  23. The External Client App's OAuth settings in Salesforce Figure 24 Not yet captured
    Page
    Setup, External Client App Manager, the Cockpit app, OAuth settings
    State
    Enable OAuth ticked, the callback URL set, exactly the two scopes, PKCE ticked; secrets not on screen
    Call-outs
    1 Callback URL; 2 The two scopes; 3 PKCE option
    Used in
    Chapter 6, Connecting each system
  24. The Cockpit connected app's scopes in Anypoint Figure 25 Not yet captured
    Page
    Anypoint Access Management, Connected Apps, the Cockpit app
    State
    Type App that acts on its own behalf; the four View and Read scopes listed; client secret not on screen
    Call-outs
    1 App type; 2 The four read scopes; 3 Environments chosen
    Used in
    Chapter 6, Connecting each system
  25. GitHub asking to authorize Cockpit Figure 26 Not yet captured
    Page
    The GitHub authorization page reached from Connect GitHub
    State
    Signed in as the test account; the permission list visible
    Call-outs
    1 Signed-in account; 2 Requested access; 3 Authorize button
    Used in
    Chapter 6, Connecting each system
  26. The Slack app's OAuth and Permissions page Figure 27 Not yet captured
    Page
    api.slack.com/apps, the Cockpit app, OAuth & Permissions
    State
    Redirect URL saved; User Token Scopes and Bot Token Scopes listed; no secret on screen
    Call-outs
    1 Redirect URL; 2 User Token Scopes; 3 Bot Token Scopes
    Used in
    Chapter 6, Connecting each system
  27. Postman's API keys page with the new key Figure 28 Not yet captured
    Page
    go.postman.co/settings/me/api-keys
    State
    Key named Cockpit with an expiry; the key value must NOT be visible in the capture
    Call-outs
    1 Key name; 2 Expiry
    Used in
    Chapter 6, Connecting each system
  28. The Connectors page with every test account connected Figure 29 Not yet captured
    Page
    /app/connections
    State
    Two Salesforce orgs, two MuleSoft connections, GitHub, Slack and Postman connected; every capability tag reading Read only (Sandbox)
    Call-outs
    1 Two Salesforce orgs; 2 Two MuleSoft connections; 3 Capability tags
    Used in
    Chapter 6, Connecting each system
  29. The answer to How close is this org to its API limits? Figure 30 Not yet captured
    Page
    /app, a chat on org 1, Sandbox
    State
    The question, the answer with real numbers, and the API meter line above the message box
    Call-outs
    1 The answer's numbers; 2 API meter line
    Used in
    Chapter 7, Your first flights
  30. The test pull request on GitHub Figure 31 Not yet captured
    Page
    github.com/<test user>/cockpit-practice/pull/1
    State
    One added file, AccountUpdater.cls, visible in the Files changed tab
    Call-outs
    1 Pull request number; 2 File name
    Used in
    Chapter 7, Your first flights
  31. A finished Org Discovery Report in a chat Figure 32 Not yet captured
    Page
    /app, after /discovery on a connected org
    State
    The report's top: title, date, first section, and the download buttons
    Call-outs
    1 Report date; 2 A not-readable marker if present; 3 Download buttons
    Used in
    Chapter 7, Your first flights
  32. The Switch to Production mode confirmation Figure 33 Not yet captured
    Page
    /app, mode chip, master switch turned on
    State
    The confirmation text and both buttons visible
    Call-outs
    1 Confirmation text; 2 Switch to Production mode; 3 Stay in Sandbox
    Used in
    Chapter 8, Production flight
  33. A real approval card for a Salesforce create Figure 34 Not yet captured
    Page
    /app, Production mode, after asking for an Account
    State
    The whole card visible: summary with the org, the input, fingerprint, tags and both buttons, still pending
    Call-outs
    1 Summary and target; 2 Exactly what will run; 3 Blast radius; 4 Approve and Deny
    Used in
    Chapter 8, Production flight
  34. The Account found in Salesforce after approval Figure 35 Not yet captured
    Page
    Salesforce, Accounts list view, org 1
    State
    Exactly one Cockpit Test Drive One account visible
    Call-outs
    1 Account name; 2 Created date
    Used in
    Chapter 8, Production flight
  35. The Captain's team members page with one active and one invited person Figure 36 Not yet captured
    Page
    /app/team, signed in as a Captain, on a build with Teams switched on
    State
    The Invite someone form and two team members visible: one Active with the access lists, one Invited with Send again; use fake addresses such as test.user@example.com
    Call-outs
    1 Invite someone form; 2 Starting access list; 3 Connector access lists; 4 Save access button; 5 Role list and Change role; 6 Send again; 7 Remove
    Used in
    Chapter 9, Captain and Crew
  36. The team page as a team member sees it Figure 37 Not yet captured
    Page
    /app/team, signed in as a team member (not a Captain)
    State
    The team name, the line naming the Captain, and the What you can use list with at least one Read only and one Not enabled; fake names and addresses only
    Call-outs
    1 Team name; 2 Captain line; 3 What you can use; 4 Ask your Captain note
    Used in
    Chapter 9, Captain and Crew
  37. The team door of the sign-in page Figure 38 Not yet captured
    Page
    /sign-in?door=crew, signed out, on a build with Teams switched on
    State
    The line about the invited address, the email and password form and the Sign in with Google instead link; no Google button
    Call-outs
    1 Invited address line; 2 Email and password form; 3 Sign in with Google instead link
    Used in
    Chapter 9, Captain and Crew
  38. A MuleSoft approval card whose target names the environment and its type Figure 39 Not yet captured
    Page
    /app, Production mode, a chat asking Cockpit to restart an application in a sandbox environment
    State
    The whole card visible, with the target line naming the environment and its type in brackets, still pending; fake application names only
    Call-outs
    1 Target line with the environment type; 2 Exactly what will run; 3 Approve and Deny
    Used in
    Chapter 10, Troubleshooting
  39. The Workbench with a query and its result rows Figure 40 Not yet captured
    Page
    /app/workbench, a Salesforce sandbox org chosen
    State
    The sample query run on a throwaway org; the org badge, the Run button, the result line and at least three rows visible; no real customer data on screen
    Call-outs
    1 Org picker and read-only badge; 2 Query box; 3 Run button; 4 Result line; 5 Sortable column headings; 6 History and Saved
    Used in
    Chapter 13, The Workbench
  40. The Workbench Objects tab with an object open Figure 41 Not yet captured
    Page
    /app/workbench, Objects tab, the Account object chosen
    State
    Search box, the object list and the Fields tab with the Add buttons visible
    Call-outs
    1 Search objects; 2 Custom objects only; 3 Fields, Relationships, Record types; 4 Add button
    Used in
    Chapter 13, The Workbench
  41. The Workbench MuleSoft tab with deployments Figure 42 Not yet captured
    Page
    /app/workbench, MuleSoft tab, a sandbox environment chosen
    State
    State counts and the deployments table visible, at least one deployment Running; no real application names that you do not want shown
    Call-outs
    1 Connection and Environment; 2 State counts; 3 State of a deployment; 4 APIs tab
    Used in
    Chapter 13, The Workbench
  42. The Workbench result chart of a GROUP BY query Figure 44 Not yet captured
    Page
    /app/workbench, Query tab, a COUNT() ... GROUP BY query run on a throwaway org, Chart view chosen
    State
    The Table and Chart switch, the Bars and Line buttons, the Label and Number lists and a bar chart of at least three bars; no real customer data on screen
    Call-outs
    1 Table and Chart switch; 2 Bars and Line; 3 Label and Number lists; 4 The numbers behind the chart
    Used in
    Chapter 13, The Workbench
  43. The Workbench Logs tab with one Apex log open Figure 45 Not yet captured
    Page
    /app/workbench, Logs tab, a log from a throwaway org opened
    State
    The Show list set to Errors, the search box, the line count and a few numbered lines; no record values on screen
    Call-outs
    1 Show list; 2 Search the log; 3 Line count; 4 More lines
    Used in
    Chapter 13, The Workbench
  44. The Workbench MuleSoft tab with an application's logs open Figure 46 Not yet captured
    Page
    /app/workbench, MuleSoft tab, a sandbox environment, Logs pressed on one application
    State
    The Period, Lines and Show lists and a few log lines, no real application names that you do not want shown
    Call-outs
    1 Details and Logs; 2 Period; 3 Search these lines
    Used in
    Chapter 13, The Workbench
  45. The project board with cards in all four columns Figure 47 Not yet captured
    Page
    /app/board, a build with the board switched on, a project in discovery
    State
    The three phase boxes, the four columns with at least one card each, one card reading moved by itself with its reason line, and the Add a chat to this project list; fake chat titles only
    Call-outs
    1 Phase boxes; 2 Waiting on you column; 3 A card moved by itself and its reason; 4 Move to list; 5 Add a card box
    Used in
    Chapter 14, The project board
  46. The board's phase confirmation Figure 48 Not yet captured
    Page
    /app/board, after pressing the button that says Discovery is complete, open Design
    State
    The question Move to Design? This is your go-ahead and is recorded, with both buttons visible
    Call-outs
    1 Confirmation question; 2 Yes, open Design; 3 Not yet
    Used in
    Chapter 14, The project board
  47. The Health section of the Admin page Figure 49 Not yet captured
    Page
    /app/admin, signed in as the owner, on a build with the Health view switched on
    State
    The one-line verdict, the tiles, and the two hourly bar charts all visible
    Call-outs
    1 Verdict line; 2 Tiles; 3 Requests per hour chart; 4 Slowest 5% per hour chart
    Used in
    Chapter A, Appendices