To offer parent and child reservations on an external website or mobile app, start with a Reservation Blueprint. A Reservation Blueprint defines what a combination of a parent reservation and its child reservations consists of, which combinations the API considers, and which fields GoMeddo sets on which reservation.
Reservation Blueprints work with the API and the timeslot picker. To use them on a calendar inside GoMeddo, you need custom form logic that creates the child reservations.
Make each blueprint as specific as possible. A blueprint determines how many combinations GoMeddo has to check for conflicts, and that check is demanding for Salesforce, so keep the options as limited as possible.
Every extra Staff member, Resource, or child reservation multiplies the number of combinations.
Blueprint
A blueprint defines how long a reservation takes and in which order the child reservations take place. Set the Duration in minutes, and use the Order field on child blueprints to control their sequence: lower numbers come first. Use Interval to set the number of minutes between the start times of the timeslots GoMeddo offers, or leave it empty to offer back-to-back timeslots. If you want buffer time between child reservations, give them a Reservation Type that has a buffer.
If a blueprint uses the Child of parent resource or Available at parent resource method, the parent reservation must have a Resource in the B25__Resource__c lookup.
Fields to set
A blueprint also defines which fields GoMeddo sets on the parent or child reservation. For example, you can set the Reservation Type, or require a Staff member or a Resource.
Each field to set has a Method To Get Value. There are 6 methods:
|
Method to get value |
Description |
Example usage |
|---|---|---|
|
Copy from parent reservation |
Copies the value from the parent reservation. |
Put all reservations on the same Resource. |
|
Literal value |
Puts the literal value or ID you enter in Literal Text Value in the field. GoMeddo casts the value to the data type of the field where it can, and otherwise treats it as a string. Supported data types:
|
|
|
Record by name |
Sets the field to the record with the name you enter in Record Name. |
Set a Reservation Type. |
|
Child of parent resource |
The Resource of the child reservation must be a child of the Resource of the parent reservation. |
Give the child reservation a Resource that is a child of the Resource of the parent reservation. |
|
Available at parent resource |
The Staff member or other dimension record must be available at the Resource of the parent reservation, based on Multi-Dimensional Availabilities . |
Only consider Staff members who are available in Amsterdam. |
|
Records matching condition |
Considers all dimension records that match a Condition. Unlike the two methods above, this method doesn't look at the Resource of the parent reservation, so you can use it on blueprints that have no Resource at all. Set the Filter Condition field to the Condition Name of the Condition you want to use. |
Only consider Staff members with the Advisor role, regardless of location. |
Filter rule
With Child of parent resource and Available at parent resource, you can select a filter rule in the Dimension Filtering Rule field. The rule narrows down which dimension records GoMeddo considers. For example, child reservation 1 needs a Resource of type Intake room that is available in the parent Resource. Or only Staff members of type Nurse are considered for child reservation 1.
Filter Condition
When a field uses Records matching condition, the Filter Condition field holds the Condition Name of a Condition custom metadata record. GoMeddo turns that Condition into a query against the field's object and uses the matching records as the candidates for this field.
A few rules apply in this context:
-
The fields used in the Condition Elements must exist on the object of the field to set. For example, a Condition used on a Staff field can only refer to fields on
B25__Staff__c(relationship fields such asB25__Account__r.Typeare allowed). -
The supported operators are
=,!=,<,>,<=, and>=. -
Placeholder values such as
{B25__Contact__r.Gender__c}are not supported here. Placeholders compare against another reservation, and there is no other reservation involved when GoMeddo selects candidate records. -
If the Condition has no Condition Logic, GoMeddo combines all its Condition Elements with AND.
-
Each field that uses this method costs one extra query, so reuse a single Condition across fields where you can.
If the Filter Condition is empty, points at a Condition that does not exist, or refers to a field that does not exist on the object, GoMeddo returns an error that says which field and Condition caused it.
Example setup
This example creates a parent blueprint for a 60-minute appointment and a child blueprint for a 15-minute intake.
Create the parent blueprint
-
In the App Launcher, search for and select Reservation Blueprints.
-
Click New.
-
Enter Appointment as the Reservation Blueprint Name.
-
Enter 60 as the Duration.
-
Click Save.
GoMeddo opens the new blueprint:
Set the Reservation Type of the parent
Record by name looks up the Reservation Type by its name, so make sure a Reservation Type named Appointment exists.
-
On the Fields To Set tab of the blueprint, click New.
-
Enter
B25__Reservation_Type__cas the Field API Name. -
Select Record by name as the Method To Get Value.
-
Enter Appointment as the Record Name.
-
Click Save.
The field to set looks like this before you save it:
Create the child blueprint
-
On the Child Blueprints tab of the Appointment blueprint, click New.
-
Enter Intake as the Reservation Blueprint Name.
-
Enter 15 as the Duration.
-
Enter 1 as the Order. The order determines the sequence in which the child reservations take place.
-
Click Save.
GoMeddo fills in Parent Blueprint with the Appointment blueprint:
Add the fields to set of the child
Open the Intake blueprint. On the Fields To Set tab, add a field to set for each of these fields:
-
Reservation Type: enter
B25__Reservation_Type__cas the Field API Name, select Record by name, and enter Intake as the Record Name. -
Staff: enter
B25__Staff__cas the Field API Name and select Available at parent resource. GoMeddo then only considers Staff members who are available in the Resource of the parent reservation, based on Multi-Dimensional Availabilities . -
Resource: enter
B25__Resource__cas the Field API Name and select Child of parent resource. The Resource of the intake must then be a child of the Resource of the parent reservation.
The Staff field looks like this:
The Resource field looks like this:
The Fields To Set tab of the Intake blueprint now shows the three fields:
Related pages
To use blueprints through the API, see these pages: