Configuring Blueprints for the Frontend Builder

A Reservation Blueprint defines the structure of the reservation that GoMeddo creates when a customer completes a booking in the Frontend Builder. It tells GoMeddo what fields to set, which dimensions (such as resources or staff) to include, and how long the appointment is.

The Blueprint also acts as the "type" of appointment a customer sees and selects in the booking widget — shown by name, description, and image.

How to create a Blueprint

Go to Reservation Blueprints in GoMeddo in Salesforce and click New.

Basic Setup

Field	What it does	Tips
Name	The name of the Blueprint, shown to customers in the booking widget.	Keep it descriptive. Example: Full Body Checkup, Meeting Room 60 min
Description	A short explanation shown to customers in the booking widget.	Describe what the customer is booking. Example: A 60-minute checkup with a nurse.
Image URL	URL of an image shown next to the Blueprint in the booking widget.	Use a square image. Leave blank if not needed.
Duration	How long the reservation lasts, in minutes. Also determines the length of each time slot in the widget.	Required. Example: 60 for a 1-hour appointment.

Fields to Set

This section defines which fields GoMeddo automatically fills in on the reservation when it is created. You can add as many fields as needed — common ones are Reservation Type, Status, and Resource.

For each field, you choose a Method to Get Value:

Literal Value

Sets a field to a fixed value you enter manually. GoMeddo always uses this exact value.

Supported types: String, Boolean, Currency, Double, Integer, Long, Percent, Date, DateTime

Example: Set Title to "Intake Appointment" — every reservation from this Blueprint gets that title.

Record by Name

Looks up a Salesforce record by name and sets it on the field.

Example: Set B25__Reservation_Type__c to "Consultation" — GoMeddo finds the Reservation Type named "Consultation" and links it to the reservation.

Make sure the name matches exactly (including capitalisation) with the record in your org.

Child of Parent Resource

Selects a Resource that is a child of the resource on the parent reservation in the resource hierarchy.

Example: A parent reservation is at "Amsterdam HQ". This method tells GoMeddo to assign a meeting room that sits below "Amsterdam HQ" in the resource tree.

Filter Rule (optional): Narrow down which child resources qualify — for example, only resources of type "Intake Room". The more specific, the better the performance.

Available at Parent Resource

Selects a staff member (or other dimension) who has been made available at the parent resource via GoMeddo's Multi-Dimensional Availability (MDA) configuration.

Example: A customer selects "Amsterdam HQ". GoMeddo checks the MDA records and only considers nurses who are available at that location.

Filter Rule (optional): Restrict which staff or dimensions are considered — for example, only staff with the role "Nurse". Always be as specific as possible to keep performance fast.

Records matching condition

Selects dimension records by querying the object directly, using a Condition you configure. This method does not look at the parent reservation's resource at all, which makes it the way to build a Blueprint that has no Resource — for example an appointment with an advisor where the location is irrelevant.

Set Filter Condition on the Field to Set to the Condition Name of the Condition you want to use.

Example: You want a Blueprint that books a Student Advisor and nothing else. Add a Field to Set for B25__Staff__c, choose Records matching condition, and point Filter Condition at a Condition with one element: field B25__Role__c, operator =, value Advisor. Every Advisor is now a candidate, with no building or room involved.

Filter Rule (optional): Narrows the result further, exactly as it does for the two methods above.

Filter Rules

Filter Rules apply to the Child of Parent Resource, Available at Parent Resource, and Records matching condition methods. They narrow down which records GoMeddo considers when calculating available combinations.

This matters because GoMeddo checks every possible combination of dimensions for availability before showing time slots. More combinations means slower performance. A tight filter rule keeps this manageable.

Best practice: Always filter as specifically as possible. Avoid leaving these open-ended.

In addition to setting fields on the reservation itself, a Blueprint can automatically create Dimension Junction records. Dimension Junctions link a reservation to a dimension record — for example, a piece of equipment or a required resource feature.

Each entry in Related Lists to Set defines one junction record to create. You configure it the same way as Fields to Set: pick the junction object, then use Fields to Set to specify what values to put on it (using the same methods: Literal Value, Record by Name, Child of Parent Resource, Available at Parent Resource, Records matching condition).

Example: Every "Yoga Class" reservation automatically gets a junction record linking it to the "Yoga Mat" equipment dimension — no manual input needed from the customer or admin.

Performance tips

GoMeddo calculates all possible dimension combinations for a Blueprint before checking availability. Every additional dimension multiplies the number of combinations to check.

To keep things fast:

Use Filter Rules to limit which resources and staff are considered
Only include dimensions that are strictly necessary
Avoid open-ended "Available at Parent Resource" configurations without filters
When specifying a Record matching condition make sure to filter for only the records that might be candidates.

Quick reference

I want to...	Use this method
Always set the same Reservation Type	Record by Name
Always set the same Status	Record by Name
Set a fixed title or text value	Literal Value
Automatically tick a checkbox	Literal Value
Assign a room inside the selected building	Child of Parent Resource
Assign staff available at the selected location	Available at Parent Resource
Auto-create a Dimension Junction on the reservation	Related Lists to Set
Assign staff by role, skill or any other field, regardless of location	Records matching condition
Build a Blueprint with no Resource at all	Records matching condition for every dimension field avoiding Child of Parent Resource and Available at Parent Resource.