Guide Designer
This content is for Spring ’26. Switch to the latest version for up-to-date documentation.
The Guide designer is where administrators compose guides: canvas-based authoring for steps, survey controls, formatting, Studio asset references, embedded tasks (orders, audits, linked guides, and more), and conditional navigation logic. Draft guides iterate until you publish, then reps run them offline through visit tasks.
Create a new guide
Section titled “Create a new guide”- From Aforza Sales, open the top dropdown and select Visit Planning.
- In the left menu choose Guides, then Create New.
- Name the guide top-left.
- Add steps with Add Step or drag toolbar items onto the canvas; name steps and drop elements into each step to build your flow.
Publish a guide
Section titled “Publish a guide”Guides save as drafts until you publish-only published guides are available for visit tasks.
Create a new guide version
Section titled “Create a new guide version”The live guide is read-only once published-select New Version to fork a draft.
- Choose Guides → pick the guide → New Version.
Delete a guide
Section titled “Delete a guide”- Choose Guides → locate the guide → Delete.
Export a guide
Section titled “Export a guide”Published guides expose Export; file saves locally as JSON for backup or transfer.
Import a guide
Section titled “Import a guide”Library Import ingests packaged definitions-titles may prefix [Imported] until renamed.
Checks when importing:
- Studio asset references must point at your Studio tenant.
- Image references must resolve to Studio assets or permitted Salesforce files.
- Custom object controls need mobile configuration for forms, CRUD visibility, filters, and objects to sync alignment-see your organisation’s mobile setup guide.
- Linked guide elements must reference guides stored in your org.
- Audit steps must pick audit types that exist organisationally-see administration standards for audit setup.
Guide steps
Section titled “Guide steps”A guide comprises steps of two flavours:
- Rich text steps - one rich-text pane-ideal for cover or thank-you pages.
- Custom steps - one or more elements below.
Guide step elements
Section titled “Guide step elements”Custom steps stack elements from four families.
Survey
Section titled “Survey”Input controls for execution:
- Single line text, long text, number
- Multiple choice list, checkbox, toggle, dropdown
- Phone, email, link URL
- Date, date and time, time
Format
Section titled “Format”Layout helpers-rich text, divider, spacer-so reps stay oriented.
Capture or show media-photography, Studio renditions, signatures, van manifest, Studio workflow returns, charts.
Embeds Aforza tasks:
- Audit (types published to the org)
- Order
- Payment
- Linked guide
- Van load
- Custom object
- Smart action
Guide step element options
Section titled “Guide step element options”Each element exposes settings for required vs optional responses and multiple-choice layout.
Guide logic
Section titled “Guide logic”Conditions show or hide blocks from answers or prior steps.
- You need a guide, step, and at least two blocks before logic applies. Rich text steps may not drive logic predicates.
- AND vs OR groups define whether all or any predicate passes.
- Operators vary by datatype.
- Logic runs only for published guides during Aforza Mobile execution.
Step navigator
Section titled “Step navigator”The step navigator lists every step once the rep is inside a step-different from landing navigation. Users jump freely; reordering steps in authoring updates navigator order immediately.
Guide results
Section titled “Guide results”Aggregated submissions appear under Visit planning → Guide results (searchable by account, visit, or user) with PDF export; visit records also expose the Guide tab for a single execution. See Guide results.