معمولاً رستورانها دارای قسمتهای نشیمن مجزا هستند، مانند بار یا پاسیو. Action Center از این تمایز پشتیبانی می کند و به کاربر اجازه می دهد منطقه را برای رزرو جدول مشخص کند. نمونه ای از این مورد در زیر نشان داده شده است، که در آن در دسترس بودن برای "بار" و "پاتیو" متفاوت است و به طور مشخص به کاربر ارائه می شود:
این جداسازی موجودی را می توان با تنظیم فیلدهای room_id
و room_name
در پیام resources
یک شکاف دسترسی به کار برد.
// A resource is used to disambiguate availability slots from one another when // different staff, room or party_size values are part of the service. // Multiple slots for the same service and time interval can co-exist when they // have different resources. message Resources { // One of staff_id, room_id, or party_size must be set. // Optional ID for a staff member providing the service. This field identifies // the staff member across all merchants, services, and availability records. // It also needs to be stable over time to allow correlation with past // bookings. (optional but required if staff_name is present) string staff_id = 1; // Optional name of a staff member providing the service. This field will be // displayed to users making a booking, and should be human-readable, as // opposed to an opaque identifier. (optional but required if staff_id is // present) string staff_name = 2; // An optional ID for the room the service is located in. This field // identifies the room across all merchants, services, and availability // records. It also needs to be stable over time to allow correlation with // past bookings. (optional but required if room_name is present) string room_id = 3; // An optional name for the room the service is located in. This // field will be displayed to users making a booking, and should be human // readable, as opposed to an opaque identifier. (optional but required if // room_id is present) // In dining a room name should only be used for seating areas such as the bar // or patio and should not be used for fixed price menus, special activities, // or any other non-room value (such as reservation or dinner). It is strongly // recommended that the default seating area not have a room associated with // it. string room_name = 4; // Applicable only for Dining: The party size that can be accommodated // during this time slot. A restaurant can be associated with multiple Slots // for the same time, each specifying a different party_size, if for instance // 2, 3, or 4 people can be seated with a reservation. (optional) int32 party_size = 5; }
این اطلاعات بخشی جدایی ناپذیر از تعریف اسلات است و باید در فیدها و همچنین تمامی عملیات رزرو و بهروزرسانی بیدرنگ گنجانده شود. میتوانید نمونههایی از room_id
و room_name
را ببینید که در مثال Feed Dining, Vertical-Specific Feed مشخص شدهاند.