Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Follow these instructions to perform a clean install and configure GoMeddo

1. Install GoMeddo.

You will find the latest installation link here: Install the latest version

Note

Important! Make sure to always install “For Admins Only” and that Folders and Enhanced Sharing is enabled for Lightning Email Templates

If you receive an error that the install is failing because of either ‘(Booker25EmailTemplates) To create email template folders, enable Folders and Enhanced Sharing.’ or `(GoMeddoOrangeBlackFav) You do not have the level of access necessary’, please follow these steps.

2. Assign Licenses

Assign GoMeddo licenses and Permission Sets to any user in your org that will work with the GoMeddo calendar: 
Assign Licenses & Permission Sets

3. Remove Double Booking permission from System Administrator profile

When installing a package, Salesforce automatically assigns all custom permissions in that package to the System Administrator profile. This is fine for all permissions except the Double Booking permission, as this can give the impression that the conflict checking is not working. Only assign this permission deliberately to users who should always be able to double book.

  1. Go to Setup > Profiles

  2. Go to the System Administrator profile

  3. Under the Custom Permissions section, remove B25.Allow Double Booking

4. Set permissions

Enable real-time calendar updates

Make sure relevant users see updates on the calendar in real-time: 

Enable real-time calendar updates

(Optional) Add Reservation Contact permissions

If you intend to link multiple Contacts to Reservations, follow this article: 

Add Reservation Contact permissions

5. Start configuring GoMeddo

Add Resources to your org

Define a Resource Type and Resource hierarchy for your org: 

Set up the Resource Types & Resources hierarchy

Set up the reservation titles and hovers

Define what information should be shown on the Reservation blocks and the Reservation hovers

Customise the Reservation fields shown on the calendar and hovers

6. Migrating to a Sandbox

If you have GoMeddo installed on your production org, and you create a partial sandbox, GoMeddo will most likely not work properly. This is due to not all configuration records being copied to the sandbox. If you want to maintain your production org's GoMeddo configuration, there are several options:

  1. Create a full copy sandbox.

  2. Create a partial sandbox and migrate all your GoMeddo config data from production to the new sandbox.

  3. Create a partial sandbox and reset the GoMeddo config data

The last option is fairly low effort and can be enough if you only want to test certain functionality. How to reset GoMeddo's configuration is described here:

Reset configuration data (Sandbox Refresh)

Filter by label (Content by label)
showLabelsfalse
max5
spacesBPD
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel in ( "installation" , "clean-install" ) and type = "page" and space = "BPD"
labelsclean-install installation

Page Properties

hiddentrue
Related issuesAfter doing the First time set-up and authentication

You will start with creating the main event, the main event is the parent event in case there are multiple sub-events. If not, the main event will also be the sub-event.

Navigate to “GoMeddo Events” using the App Launcher

Create new Main event

Event details:

  • Give the event a Name

  • Give the event a Event Url Suffix to create the event url, for example http://events.gomeddo.com/hollanduniversity/openday
    The event url suffix is “openday”

  • Enter the Contact Email, if visitors will reply to the ticket email, they will be sent to this emailadress

  • Enter the Email signature, this will be the signature in the email of the tickets.

  • Privacy statement, will provide a link to the privacy statement applicable to this event (url field)

  • Terms & Conditions, will provide a link to the terms and conditions applicable to this event (url field)

  • Description, here you can enter the description of the main event.

  • Location, here you can add the location of the event.

  • Capacity, this will be the capacity of the main event, it’s not possible to book more tickets then this number

  • Visitor fieldset, the visitor object can be extended with more fields, putting the name of the visitor fieldset will extent the “visitor form” when booking a ticket. Extending the visitor information and form

  • Use custom email template, this settings allows you to disable the standard email and pdf creation.

Event dates

  • Start: This is the date & time when the event actually takes place

  • End: This is the date & time when the event actually ends

  • Visible from: This is the date & time when the event is visible to book (empty is always visible)

  • Visible untill: This is the date & time when the event is visible to book (empty is always visible)

Styling

Frontend-view, here you can determine if your visitors will select tickets or events.

Ticket view

...

Event view

Image Added

See the picture and the corresponding numbers below to see how you can adjust and whitelabel the event to you style.

  1. Image, here you can add a url to an image specific for this main-event. This will be shown on the website and tickets to visualize the main event

  2. Icon, here you can add a url to an icon for this event, this will be shown on top of the page and will be your main events “branding

  3. Completed State Color, here you can specify a hex code which will determine the color of the “allready completed” steps.

  4. Selection Color, here you can specify a hex code which will determine the color of the “selected events” on the website

  5. Background color, here you can specify a hex code which will determine the background of the website.

  6. Call to action color, here you can specify a hex code which will determine the color of the “action buttons”

...

Create sub-event (session)

If your event also has sessions or sub-events which can be booked, you can create those in a similiar way to a main event. Go to “related” as part of the main event, and create new sub-event.

Event details

  • Parent Event:

  • Name

  • Description

  • Capacity

Event dates

  • Start: This is the date & time when the event actually takes place

  • End: This is the date & time when the event actually ends

  • Visible from: This is the date & time when the event is visible to book

  • Visible untill: This is the date & time when the event is visible to book

Styling

  • Image, here you can add a url to an image specific for this sub-event. This will be shown on the website and tickets to visualize the subevent as a card