A Reservation's context consists of four parts
| The Resource Type of the resource the reservation is shown in, or the Resource Type of the resource. Only applicable on the Resource Calendar and only part of the context for backward compatibility with the old Reservation_Display__r.ResourceType__c field |
|---|
| The Reservation Type of the reservation. Not applicable for a resource display context. |
|---|
| The View the reservation or resource is currently shown in |
|---|
| The Calendar the reservation or resource is currently shown in |
|---|
So for example a reservation of type: Meeting, with B25__Resource__c = MeetingRoom 1 (of type MeetingRoom), being viewed on the Calendar called Resources on the View WeekView, would have the context of :
Resource Type | MeetingRoom |
|---|---|
Reservation Type | Meeting |
View | WeekView |
Calendar | Resources |
But if the user changes to the view DayView the context would change to:
Resource Type | MeetingRoom |
|---|---|
Reservation Type | Meeting |
View | DayView |
Calendar | Resources |
Determining what context will be used to determine what hover and what titles will be shown.
When determining what context to use, Booker25 GoMeddo compares the reservation context or the resource context to all contexts that have been defined.
...
Second, the remaining contexts are ranked in the following way:
Matching resource type
Matching reservation type
Matching view
matching calendar
Empty values do not count as a match.
...
Now follow a few examples of what context would match in certain situation using the following contexts:
Context name |
|---|
|
|---|
|
|---|
|
|---|
| ||||
|---|---|---|---|---|
Fallback Context | ||||
Meeting Context | Meeting | |||
Staff Meeting Context | Meeting | Staff Calendar | ||
Staff Calendar Context | Staff Calendar |
A Reservation with Reservation Type: Meeting on the Resource Calendar will use the Meeting Context. The Staff Meeting Context is discarded because the Calendar has a conflicting value and the Fallback Context has no matches to add to it's rank.
...
| Info |
|---|
Be careful when using Sharing on Contexts. When a user can see two or more Reservation Display Context records with the exact same context, Booker25 GoMeddo does not know which Context to prefer and picks one at random. |
When Sharing is set to Private for Reservation Display Contexts, you can show different titles and hovers for different users, based on what context is shared with them. Booker25 GoMeddo normally prevent duplicate contexts to be inserted, to prevent ambiguity as to what context to show. When checking for such duplicate Contexts, Booker25 GoMeddo takes in to account the Sharing Identifier field. Use this field to identify with what Public Group of users this record is shared, and Booker25 GoMeddo will allow you to insert duplicate contexts if the value of this field is different.