Module · Doing the same things by conversation✅Knowledge checkCheck: can you drive it by asking?4 questions · Pass at 60%1. You have connected a client's org to your own tools and you are about to run a bulk edit. What do you do first?Take a backup of the orgAsk it to show you what it is about to change, and check which workflows trigger on the thing you are editingSwitch the affected workflows off for the durationNothing — a bulk edit through a key is not different from one through the UI2. You ask for a workflow and it comes back valid and runnable. Are you finished?Yes — runnable means the trigger, the references and the path all check outNo, but only because it still has to be activatedNo. Valid and runnable say it will execute, not that it does what you meant — open the canvas and read itYes, provided you also asked it to validate the spec rather than the saved workflow3. What is different about checking an agent, compared with checking a rules workflow?Nothing — both are checked by validating and then reading the canvasAn agent cannot be validated, so it must be run insteadAn agent needs its knowledge base checked, and a workflow does notA workflow is wiring you check on a canvas; an agent is a job description you check by reading the prompt and asking it what you least want it to answer4. A client's branch manager wants to build things by asking, and does not want a terminal. What do you point them at?Xen, inside the product — the same capabilities with a workspace panel, and nothing to configureAn API key of their own, with the config block from lesson oneThe canvas, because conversation is a partner toolA shared connection on your machine that they send requests toCheck answers← Back to Expedify in an AfternoonNext topic →
